http://autocomplete.wunderground.com is broken.

  • 1
  • Problem
  • Updated 6 years ago
The Country to ISO on the wunderground API page has some issues.

edit 2/8, more... israel, iceland... did wunderground suddenly change this over to ISO convention without telling anyone, and secondly the country to iso table is now totally off....

Several of the codes documented on that table were working fine yesterday but today they have changed.

For example, Great Britan, Viet Nam, and Venezuela responded as expected from the table yesterday, but today they are not. Perhaps More?

The table in question:

http://www.wunderground.com/weather/a...

Based on what your autocomplete API is returning...

The correct wunderground code for Venezula should be VE

And the correct w code for Viet Name should be VN

EDIT: found another one... UK is not UK, but GB!

According to your table this should work:
http://autocomplete.wunderground.com/...

But it doesn't, this does however...

http://autocomplete.wunderground.com/...
(which actually follows ISO)

Oh yikes silly silly this is getting silly, so what happened to Gambia then?

Thanks.

p.s. are there any others?
Photo of logray

logray

  • 7 Posts
  • 0 Reply Likes

Posted 6 years ago

  • 1
Photo of logray

logray

  • 7 Posts
  • 0 Reply Likes
Hi, just checking if anyone has looked into this problem.

I emailed support as well but never received a response.

I am going to be releasing an application later this week and this would be a show stopper if this changes again after I release the app.

I don't mind it being ISO codes (in fact would prefer that) but am concerned the documentation says one thing but the autocomplete website is returning something different.

I suppose as long as it is something and it stays that way whichever way it should be that GREAT.

Thanks
Photo of Brendan Hayes

Brendan Hayes, Official Rep

  • 962 Posts
  • 123 Reply Likes
We are looking into this and talking about it internally...
Photo of Brendan Hayes

Brendan Hayes, Official Rep

  • 962 Posts
  • 123 Reply Likes
The table has been updated for UK = GB and you got those other 2 backward:

VS is Viet Nam in Wunderground code (ISO VN)
VN is Venezuela in Wunderground code (ISO VE)

We know that the ISO's are a bit of a mess and we are going to be working on standardizing and updating these over the next couple of months. Hopefully this helps with the current situation.
Photo of logray

logray

  • 7 Posts
  • 0 Reply Likes
Brendan,

I appreciate the response, however I would offer that there are still many gremlins lurking in your ISO matching table for the autocomplete URL. This all seemed to work fine about 6/7 days ago based on your match table, but on the day I wrote the original post everything went haywire and only the ISO codes match/make sense (which again is fine by me..., as long as it doesn't change (or does with notice)).

Example as I'm writing this PST 5:55pm 2/12/13:

------------------------------------

(1.) UK does not match London as your table says it should. However GB does. Here are the URLs to make it easy for you to understand...

MATCHES (ISO) http://autocomplete.wunderground.com/...

NO MATCH (WUN) http://autocomplete.wunderground.com/...

------------------------------------

(2.) VN matches VietNam (not Venezuela). VS does not match Vietnam...

MATCHES (ISO) http://autocomplete.wunderground.com/...

NO MATCH (WUN) http://autocomplete.wunderground.com/...

------------------------------------

(3.) VN should match for Venezuela (but guess what, VE is Venezuela).

MATCHES (ISO) http://autocomplete.wunderground.com/...

NO MATCH (WUN) http://autocomplete.wunderground.com/...

------------------------------------

I really don't want to go through the entire table, but I have a feeling I could find more examples, considering these were randomly selected (including GB).

When I switched my application over to use only ISO codes for autocomplete, it seems to work perfectly so far through several hours of testing.

So perhaps back to the drawing table with a response then?

Also if you DO decide to make changes in the future, will they be communicated somehow ???? (autocomplete is a critical part of my app and works GREAT/AWESOME when the data is reliable, however based on your response I may have to re-consider the launch date of my application, and even the use of country codes in the autocomplete URL if they will change in the future without notice).

And on a separate note. The good news is both the wunderground and ISO codes match on the API URL, I can use either interchangeably. So this issue appears to be isolated to the autocomplete URL's matching code.

Thanks again for your response and I look forward to your future replies.

-Logan
Photo of logray

logray

  • 7 Posts
  • 0 Reply Likes
Update: we figured out a way to use autocomplete in our app without using &c=. It doesn't work quite as well as it does when we can narrow results using a country code but it does seem to be acceptable.

Because of the workaround we implemented, the urgency level for us has been reduced, although we feel the issue should be addressed (we would like to use &c= to narrow results at some point in the future, if and when it gets sorted, or if a "final" configuration is announced).

Thanks again.