q/Russia/Moscow stopped working

  • 1
  • Problem
  • Updated 4 years ago
Any idea why q/Russia/Moscow.json does not work anymore? Stopped working relatively recently.

Requests
http://api.wunderground.com/api/_key_...
http://api.wunderground.com/api/_key_...

both return "not unique" response now:

{
"response": {
"version":"0.1",
"termsofService":"http://www.wunderground.com/weather/a...",
"features": {
"conditions": 1
}
, "results": [
{
"name": "Moscow",
"city": "Moscow",
"state": "",
"country": "RS",
"country_iso3166":"RU",
"country_name":"Russia",
"zmw": "00000.1.WUUBW",
"l": "/q/zmw:00000.1.WUUBW"
}
,
{
"name": "Moscow",
"city": "Moscow",
"state": "",
"country": "RS",
"country_iso3166":"RU",
"country_name":"Russia",
"zmw": "00000.1.27612",
"l": "/q/zmw:00000.1.27612"
}
]
}
}

Request: http://api.wunderground.com/api/_key_...

returns

{
"response": {
"version":"0.1",
"termsofService":"http://www.wunderground.com/weather/a...",
"features": {
"conditions": 1
}
,
"error": {
"type": "querynotfound"
,"description": "No cities match your search query"
}
}
}

Other cities like q/Russia/st_petersburg.json, q/Russia/novosibirsk.json continue to work as before.
Photo of peterfomin

peterfomin

  • 4 Posts
  • 0 Reply Likes

Posted 4 years ago

  • 1
Photo of afelicioni

afelicioni

  • 227 Posts
  • 43 Reply Likes
weather underground api geographic database is dynamic, as a living ecosystem.

once multiple locations (even if duplicates) get added, you can query for datas using the l key, as for example /q/zmw:00000.1.27612
Photo of peterfomin

peterfomin

  • 4 Posts
  • 0 Reply Likes
I see. So that's how the multiple locations are post-processed - that's good to know, thanks.

In terms of the data though - don't you think that it needs to be cleaned up? There is only one Russia/Moscow after all. A user interface could present a list of options for a user to select from but in this case city, state and country are all the same so it would be a less than ideal user experience.

Similar issue to http://apicommunity.wunderground.com/.... Except there even "l" value is exactly the same.
Photo of John Belmonte

John Belmonte

  • 18 Posts
  • 1 Reply Like
I saw the same thing with Stuttgart, Germany. I asked why there were multiple entries and was told:

"It happens when a WMO code changes and we don't get rid of the old one because we still have records associated with it. The trouble with housing years of historical data based on key IDs. Someday we will be using more of the weather.com LocationID system which handles changes a little bit better."