There was a recent database updated the "magic" number for several locations. The magic is the middle number in the "zmw" identifier. The zip still works, and each location still works, but the magic has changed. This happens when locations change, zone identifiers go away, or there are zip code updates. The National Weather Service recently released a zone update which prompted us to update our database. The zip code search and city name search still works correctly for those locations. I'm sorry for the issues this has caused with your stored IDs.

Is it possible to have a unique id for a given location/station, which is returned by the autocomplete api and never changes? Because zip codes in US and UK are OK, but in a country like Bulgaria they are not very reliable. Another possible workaround would be: provide some mapping between old ZMW's and new ones, so we can update our clients with the new IDs.

Did this also affect the times? Since this same date, I have noticed that when I ask for a day's history, it goes from 12:54 AM EST (the local timezone) to 11:54 PM GMT. So every day is missing several hours. It seems to be the same for JSON and XML requests, and I've tried several locations in EST and got the same results.

We are trying to work with the Weather Channel location IDs, which do not change. There's never been a zmw matching document or function, so once we get the location IDs working we can stick with those.