Wind & vector fields

Wind as data: GFS and HRRR winds from AWS, u and v components, speed and direction, arrows, barbs and streamlines, station observations, wind roses and vorticity.

Streamlines of the GFS 10 m wind over the Gulf of Mexico as Hurricane Helene approached Florida, spiralling into the storm, darker where the wind was stronger. a wind field, drawn as its flowGFS analysis, 00 UTC 27 September 2024: Helene 3 hours before landfall

Wind is a vector: a speed and a direction at every point, stored by weather models as two components, u towards the east and v towards the north. Every wind map is a choice about how to draw those vectors, as arrows, barbs, streamlines or colour, and every calculation is a choice about how to combine them, because directions cannot be averaged like numbers and a metre per second east is not the same distance on a longitude-latitude map as a metre per second north.

The guides here use real data throughout: the GFS model on AWS, downloaded a field at a time by byte range, checked against the National Hurricane Center’s best track for Hurricane Helene and against airport observations from NOAA’s Integrated Surface Database. GFS put Helene within a grid cell of its true position but at 77 knots against the observed 120.

🧭 Start with the concepts

The ideas the how-to guides below assume you already have.

⚙️ Then do the task

Step-by-step walkthroughs with code you can copy and adapt.

Show every how-to guide in this topic

🔧 When it breaks

The errors this topic produces, with the cause explained rather than just the command.

Related topics

Subjects that keep coming up alongside this one, most overlap first.

Keep browsing

Wind & vector fields sits in Analysis. Every topic on the site is listed on the topics index.