I know this is an old topic, but it seemed appropriate for my question.
I am using JSMorley's JSMeterVIII\WXDataWeather skin, version Feb 7, 2017 (awesome skin, BTW). The skin is displaying all the data fine. Today I happened to notice that the temperature does not match what my phone was showing. If it was off by a degree or so I wouldn't have noted it, but it is by 4 to 6 degrees, which seemed big enough to tell me something wasn't quite right.
Left clicking on the skin will open weather.com for the correct location. The weather information there pretty much matches my phone, but it doesn't match what the skin is displaying. I did a little digging to learn how the weather data is gathered and found out about the WXDATA weather feed. Using the like in the skin code, I opened the feed in my browser and think I see why the data is not matching. It looks like even with the correct location code, the WXDATA feed information is coming from a different location.
Correct location information:
Code: Select all
<dnam>Crystal Lake, IL</dnam>
Incorrect observation station(?):
Code: Select all
<lsup>9/05/18 10:52 AM CDT</lsup>
<obst>Wheeling, IL, US</obst>
On the weather.com website I put in Wheeling, IL and sure enough, the data matches. I also tried changing my location code to some neighboring towns and they all seem to use Wheeling's data.
So I guess my question is, is this just a situation where weather.com has a limited number of locations that it uses for the WXDATA feed? I would have thought, since they have the data for all the different towns, that there would be a WXDATA feed for each one. I'm just wondering if this is just the way it is and there is nothing I can do about it to get my actual location's weather. Also, it looks like the WXDATA feed gets updated much less frequently than the actual website. Is that normal as well?
Thanks for any insight into how this works.