Windy already offers an impressive number of activity‑specific layers—avalanche danger, icing, thermals, sea temperature, swell, tidal currents, solar power, new snow, freezing altitude, & many more—many of which are tailored to niche or professional users.
Given that, it’s surprising that there is no coherent set of layers geared toward UAV / drone pilots.
At the same time, UAV/UAS operations are heavily constrained by low‑altitude wind, visibility, & regulatory altitude bands (legally 0–400 ft in many jurisdictions).
Many drone pilots also care about geomagnetic conditions (Kp index) because GPS‑based navigation can be affected by space‑weather events, especially during geomagnetic storms or when flying near auroral zones.
A logical extension of Windy’s existing structure would be a drone‑oriented package of layers, such as:
Low‑altitude wind (0–400 ft):
A vertical‑profile slice or ribbon that shows wind speed & direction specifically in the 0–400 ft band, interpolated from the model’s lowest numerical levels.
Ideally selectable as a separate layer from the default “wind at surface” or “wind at 10 m” so that drone pilots can see shear & low‑level turbulence without misreading higher‑altitude flows.
Optional: turbulence or gust indicators at low levels (e.g., parameterized from vertical wind shear or convective mixing).
Low‑level temperature & visibility (0–400 ft):
Temperature & dew‑point profiles at those altitudes, since radiation fog, temperature inversions, & low‑level humidity directly affect visual line‑of‑sight & lens performance.
Visibility / obscuration indicators (fog, haze, precipitation intensity) tagged to the lowest model layers, ideally with simple thresholds (e.g., 5 km).
Regulatory altitude band overlay (0–400 ft):
A simple visual band on the vertical profile view that highlights the 0–400 ft column, clearly differentiating it from higher regulatory bands (e.g., for manned aviation, LAA, etc.).
This wouldn’t need to be airspace‑aware, but it would help drone pilots mentally map Windy’s model data to their legal operational envelope.
Kp / Geomagnetic activity layer:
A Kp index or geomagnetic activity map or overlay, possibly sourced from standard space‑weather feeds (e.g., NOAA SWPC or ESC‑Space).
This is especially relevant for UAVs relying on GNSS/GPS, since strong geomagnetic storms can increase signal‑noise, cycle‑slips, & degraded positioning accuracy.
Ideally, a simple color‑coded layer (e.g., low/moderate/high) would let pilots see when space‑weather conditions might stress their navigation systems.
Low‑altitude moisture and icing risk for UAVs:
UAVs are small, exposed, & often fly close to or through radiative cooling layers, where dew formation, condensation, rime, & even light icing can occur on rotors, arms, & sensors, particularly at night or in foggy conditions.
A low‑level moisture layer could show relative humidity or dew‑point spread near 0–400 ft, with clear thresholds for saturation risk (e.g., RH >90–95% & sub‑freezing temps indicating potential for rime/ice).
An optional icing‑risk flag at low altitudes (even if simplified) would help UAV pilots avoid flights where condensation‑on‑propellers, fogged‑lenses, or thin ice‑on‑rotors could degrade performance or trigger sensor faults.
Though such events are relatively rare, they are not a zero‑risk hazard, especially in winter coastal or frontal scenarios, & they justify a simple, low‑level “icing / dew / condensation alert” tagged to the drone‑flight band.
Optional but valuable:
Lightning risk in the boundary layer (where small UAS fly), if that can be parameterized from model‑cumulus fields.
Simple rain‑rate & cloud‑base indicators at low altitudes, since precipitation & cloud decks near 400 ft can quickly make operations unsafe or visually disorienting.
Right now, drone pilots have to cross‑check Windy with other apps or services to get that kind of picture. If Windy wants to be the one‑stop technical weather app for all aerial users—gliders, planes, & UAVs—adding a dedicated drone‑oriented package of layers would be a natural & valuable next step.
This is not a niche request: drone use is growing rapidly, & many users already rely on Windy for broader weather context. If this feature were implemented, it would mean fewer apps to juggle, less clutter, & more unified decision‑making for anyone flying small aircraft at or below 400 ft.
Other UAV pilots (of which I am one) may want to add more specific technical requirements or operational scenarios; this post is meant as a starting point for a focused discussion on what a proper drone‑oriented layer set could look like.
