Freezing Saddles scoreboard software updates

[Steve O]

@hozn 109327 wrote:

wunderground.com

If you find a discrepancy in their data vs ours, let me know.

Here is the specific observation that was being used for the start (07:49) of your ride in “Vienna, VA” (the location of your ride, according to Strava — we take shortcuts and use the city when possible due to limitations in wunderground api usage allowances):
{
….
“fog”: “0”,
“hail”: “0”,
“heatindexi”: “-9999”,
“heatindexm”: “-9999”,
“hum”: “40”,
“icon”: “clear”,
“metar”: “METAR KDCA 201252Z 31008KT 10SM CLR M13/M24 A3042 RMK AO2 SLP302 T11331244”,
“precipi”: “-9999.00”,
“precipm”: “-9999.00”,
“pressurei”: “30.43”,
“pressurem”: “1030.2”,
“rain”: “0”,
“snow”: “0”,
“tempi”: “8.1”,
“tempm”: “-13.3”,
“thunder”: “0”,
“tornado”: “0”,
//

This has to be right. I distinctly remember there was no tornado that morning.

[Steve O]

@consularrider 109338 wrote:

I know that my closest weather station (Westover KVAARLIN28) was reading about 2°F that morning.

And since I live about 300 yards from consular, I presume mine was about the same.

[creadinger]

Yeah, I was thinking there was something wrong with the data matching up rides with temps. As of yesterday, it still said that my coldest ride was in early January – 12 degrees, measured in King George, VA.

I did an AM sleaze ride last Friday when it was super cold and everyone was in single digits or below zero, and it still lists 12 degrees as my coldest ride.

[hozn]

I guess the short answer is that the penalization does not selectively discriminate …. The better answer would be to always use lat/lon rather than town names. I am not sure the api limits will allow for that, but I will look into it.

[Author]

Posts