AWS/Weatherbug Stations commentary
Posted: Sat Apr 28, 2007 1:27 am
As a weather buff and scientist, I frequently refer to sources of climatic data to get an accurate idea of real time and recent weather conditions and trends in my area and further abroad. In this regard, I have found the information provided by AWS/Weatherbug very useful since it claims 8000 neighborhood stations across the US. I especially like looking up current weather conditions and data from offbeat locations. I've got a customized site list for spots all along the Gulf Coast where I live. One such site, for example, is Cathedral Academy, in the French Quarter of New Orleans. As far as I know, this is the only published w/station that has operated right in the French Quarter. Many sites have live cams, which is really cool, although quality varies.
However, using 'Weatherbug' (which claims to be the represent the third most frequently visited weather site after NOAA/weather.gov and weather.com) does appear to have some drawbacks:
If you use the paid WeatherBug program ($20/yr), be aware that it of course, takes up its share of space, and if it is loaded, produces annoying popups, including your 'home station' of choice upon boot and NWS weather statement prompts (which may or may not be important) which can't be killed until read.
The 'historical data' section for selected stations needs to be improved. Data only goes back one month and is generalized. Basic hourly data only can be retrieved from the past four months, not very long climatologically.
You can't look up climatalogical data for multiple stations at a glance, this must be done one site at a time.
Of the weather stations themselves, herein lies the real issue. While many stations report seemingly accurate real-time information, many suffer from apparent quality control issues.
It is fairly easy to tell if a rain gage is inoperative - if a heavy, widespread rain event occurs in one's area, you know everyone got some appreciable amount of rain. Specific location precip totals can easily be compared against radar estimate and the numerous other rain gages we have these days. A minority of WB stations in my area have what are obviously non-working or non-reporting rain gages. More significantly, many 'work' but apparently under report the totals either slightly or significantly; at least a third of the WB stations in my area appear too conservative. I have not seen any that over report, however.
Temperature bias is another aspect that seems a concern here - Again, while many WB stations consistently report a fairly accurate temperature, a high percentage produce suspect readings. In my area, I'd say about a third or more are not quite right. Commonly, WB stations seem a couple or more degrees off from where they ought to be - usually on the low side. High temperature bias seems to occur less frequently and if it does it's more often with the daily max temps (possibly due to overexposure). Suspected low temp bias appears to be more pronounced on colder, brisk days. I've determined many AWS/WB stations to be off a bit by comparing them repeatedly with nearby NWS stations, agricultural stations, cooperative stations and by interpolation with other WB stations at times when the regional temperature is very consistent, taking into account possible microclimate influence and geographical location.
I am wondering if any one else out there has found similar findings.
However, using 'Weatherbug' (which claims to be the represent the third most frequently visited weather site after NOAA/weather.gov and weather.com) does appear to have some drawbacks:
If you use the paid WeatherBug program ($20/yr), be aware that it of course, takes up its share of space, and if it is loaded, produces annoying popups, including your 'home station' of choice upon boot and NWS weather statement prompts (which may or may not be important) which can't be killed until read.
The 'historical data' section for selected stations needs to be improved. Data only goes back one month and is generalized. Basic hourly data only can be retrieved from the past four months, not very long climatologically.
You can't look up climatalogical data for multiple stations at a glance, this must be done one site at a time.
Of the weather stations themselves, herein lies the real issue. While many stations report seemingly accurate real-time information, many suffer from apparent quality control issues.
It is fairly easy to tell if a rain gage is inoperative - if a heavy, widespread rain event occurs in one's area, you know everyone got some appreciable amount of rain. Specific location precip totals can easily be compared against radar estimate and the numerous other rain gages we have these days. A minority of WB stations in my area have what are obviously non-working or non-reporting rain gages. More significantly, many 'work' but apparently under report the totals either slightly or significantly; at least a third of the WB stations in my area appear too conservative. I have not seen any that over report, however.
Temperature bias is another aspect that seems a concern here - Again, while many WB stations consistently report a fairly accurate temperature, a high percentage produce suspect readings. In my area, I'd say about a third or more are not quite right. Commonly, WB stations seem a couple or more degrees off from where they ought to be - usually on the low side. High temperature bias seems to occur less frequently and if it does it's more often with the daily max temps (possibly due to overexposure). Suspected low temp bias appears to be more pronounced on colder, brisk days. I've determined many AWS/WB stations to be off a bit by comparing them repeatedly with nearby NWS stations, agricultural stations, cooperative stations and by interpolation with other WB stations at times when the regional temperature is very consistent, taking into account possible microclimate influence and geographical location.
I am wondering if any one else out there has found similar findings.