Skip to content
This repository has been archived by the owner on May 7, 2024. It is now read-only.

Wunderground location name oddness #45

Open
benjymous opened this issue Jul 16, 2012 · 2 comments
Open

Wunderground location name oddness #45

benjymous opened this issue Jul 16, 2012 · 2 comments

Comments

@benjymous
Copy link
Owner

Sometimes the Wunderground location name can be somewhat inaccurate - It would be worth investigating if there's a different key in the json data that would be better to use

currently using "location.city", but there are also "display_location.city" and "current_observation.city" keys that might give a better fix

@dedee
Copy link

dedee commented Jul 19, 2012

Should be fixed with 3da73b2

@sdemills
Copy link

There could be other reasons for this perhaps. I have a sophisticated weather station and I provide a feed every 10 mins to Wunderground. Some weather stations provide a continuous live feed to Wunderground. If you ask for the weather in Ruddington, where I live, then if my data is fresher than the data from the live feed station then Wunderground users will see my data and the location will say Ruddington, if not then users will see the other station and the location will be Beeston.

Because of my interest in the weather, I use the weather app in MWM with Wunderground and I have been satisfied with what is displayed as the city though that may be because I'm aware of how the data is assembled and so would tolerate seeing a name that sometimes is not my precise location?

# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants