More Than 78,000 request with querynotfound??

  • 1
  • Problem
  • Updated 5 years ago
We are having a problem with getting the list of cities/stations using (geolookup) feature, some of the returned results are not found when queried using the conditions/hourly requests...

The above scenario happened more than 78,000 times in our app and its just frustrating to have mismatches like that as our app is not handling them now and that will cause the user to see blank page.

From API key logs:
querynotfound 78804 2013-02-18 1 12 /api/API-KEY/forecast7day/conditions/hourly/radar/satellite/astronomy/alerts/lang:EN/q/pws:IWESTYOR40.json

KWASEATT108
IWESTYOR40
...
..
..

Any solution please?
Photo of EIZSOFT

EIZSOFT

  • 17 Posts
  • 0 Reply Likes
  • frustrated

Posted 5 years ago

  • 1
Photo of Brendan Hayes

Brendan Hayes, Official Rep

  • 962 Posts
  • 122 Reply Likes
Are you storing the geolookup and then reusing them later? It looks like the first station you mentioned stopped reporting last month.

http://www.wunderground.com/weatherst...

Same with the 2nd one on your list:
http://www.wunderground.com/weatherst...

It shouldn't have shown up in the /geolookup/ results if its not giving information right now, so it sounds like you might have stored or cached it?
Photo of EIZSOFT

EIZSOFT

  • 17 Posts
  • 0 Reply Likes
The app it self will save the location for reuse, so the user might have that station on his App.

We are going to update the app to check for such removed stations and to ask the customers to remove them.

Still the number of requests is too high, can we have a report of the dead stations??

Thanks a lot for your response.