Here's an updated version that is mostly generated automatically:
Forecast for Sunday May 31st, made on Sat May 30th, 2015 at 11pm
6a | 7a | 8a | 9a | 10a | 11a | 12n | 1p | 2p | 3p | 4p | 5p | 6p | 7p | 8p | 9p | 10p |
240 | 240 | 180 | 180 | 180 | 240 | 240 | 240 | 240 | 240 | 240 | 250 | 250 | 250 | 260 | 260 | 260 |
2.3 | 2.3 | 3.4 | 3.4 | 3.4 | 6.9 | 6.9 | 6.9 | 10.3 | 10.3 | 10.3 | 11.5 | 11.5 | 11.5 | 11.5 | 11.5 | 11.5 |
The first version (above) was done by hand just by copying the data from the web page and formatting it with my new BBCode for making tables. The second version was generated (mostly) automatically with a Java program that reads the National Weather Service XML data and then converts it into BBCode. It's a bit more accurate with numeric wind directions and fractional speed estimates.
One of the things that was puzzling me for a long time was an unexplained speed difference between what's displayed on the NWS web page and what's in their XML file. I think I've corrected it by assuming that the XML data is in
nautical miles per hour while the web site display is in "
regular" miles per hour. A factor of 1.151 (and rounding to integers) made them agree nicely.

The program also generates a plot:

- wind_2015_05_31.png (10.58 KiB) Viewed 6869 times
The middle line (green) is the wind speed (mph), and the bottom line (blue) is the wind direction. The top line (red) is the westerly (lift-producing) component of the speed on a west facing slope (I wrote this for Torrey). It's easiest to see the difference by looking at places in the red graph where the "lifting" component is zero. In most cases, you can look at the wind speed below it (green) and see that it's
not zero. But then when you look down at the direction, you'll find that it's "gone south" (or east) and that's why the lifting component is zero.