Will it fit on the narrow template? It looks like there is too many columns to squeeze that narrow. I think it is the data in the fields that is making it that wide.
Worth noting that default color codings are based on m/s data values. Check NOAA report for unit of measurement and change values of logical expression accordingly e.g. km/h. Nice job!
Lars, I made a couple of changes in the attached file.
One change would allow a user to just select what wind unit they are using (mph, kmh, kts, or m/s) and the script would handle the rest.
I also added some code that will display a wind direction label for the month. But I don’t know how accurate averaging wind directions really is. For example, if you have two days with the wind from the north one day and from the south the next day, what should the ‘average’ be. The script will say east. Also, the wind direction listed in the dailynoaa reports is for the ‘dominant’ wind direction, not the average wind direction.
Tony - After I had ten years of data, I wrote an APL program to extract the highs, lows, rain, mtd, and ytd from the Weather Display logs. I also had a couple of years of data from before I started using Weather Display. I used this to update an almanac page on the website.
After I started using the PHP templates, I modified the program to produce csv files for my wxrecords.php script.
But unless you have several years of data, I don’t know how useful it is to have a records page.