History request with lat/lon in Sydney Australia returning results for "Asia/Yekaterinburg"

  • 1
  • Problem
  • Updated 1 year ago
  • (Edited)
Currently when we make an api request using a lat/lon for Sydney Australia, like so:

http://api.wunderground.com/api/<api_key>/conditions/history_20170306/pws:0/q/-33.95000000,151...

the current_observation has the correct location, but all the history entries are from the "Asia/Yekaterinburg" timezone with temperature values for that area, not the requested area.
{
 "current_observation": {
...
"local_tz_long": "Australia\/Sydney",
"local_tz_offset": "+1100",
"local_tz_short": "AEDT",
...
"observation_location": {
"city": "Sydney",
"country": "AU",
"country_iso3166": "AU",
"elevation": "10 ft",
"full": "Sydney, ",
"latitude": "-33.95000076",
"longitude": "151.17999268",
"state": ""
},
},
"history": {
"dailysummary": [
{
...
"date": {
"hour": "00",
"mday": "06",
"min": "00",
"mon": "03",
"pretty": "12:00 AM +05 on March 06, 2017",
"tzname": "Asia\/Yekaterinburg",
"year": "2017"
},
...
"meantempi": "30",
"meantempm": "-0",
...
}
],
...
}
}

Photo of ervandew

ervandew

  • 8 Posts
  • 0 Reply Likes

Posted 1 year ago

  • 1
Photo of Brendan Hayes

Brendan Hayes, Official Rep

  • 962 Posts
  • 122 Reply Likes
That la/lon isn't mapping to the Sydney airport where the history data comes from. Use this instead: /q/YSSY.json
Photo of ervandew

ervandew

  • 8 Posts
  • 0 Reply Likes
We don't use the airport code because that doesn't always work. I forgot which code was giving us issues, but it was returning results for some similarly named city in another country. We switched to using lat/lon to remove that ambiguity.

The lat/lon in my example may not be exactly at the Sydney airport, but it is in the Sydney area and no where near Russia (Asia/Yekaterinburg timezone).
(Edited)
Photo of ervandew

ervandew

  • 8 Posts
  • 0 Reply Likes
I think you should also take a closer look at the response example I posted. The current observation is in the correct area, the history is not. I think that clearly indicates an issue.