Latitude/Longitude geoCoding is Wrong for many locations. | The WeatherAPI Community Customer Community

The geoLookup for latitude/longitude seems off for many locations. For US lat/longs, we have seen city state to be off by few miles. The international lat/longs also seem to be way off. -33.794822,151.281077 returns Maryville, NW, Australia. The state code NW does not seem valid. I think it should be NSW. Also the correct mapping for that codes is Manly, NSW. So how bad is the wunderground geocode lookup? We are using this in our mobile weather app and many users are complaining about bad locations.. Could someone please respond?

Easilydo

2 Posts
0 Reply Likes
frustrated

Posted 7 years ago

7 years ago

Brendan Hayes, Official Rep

962 Posts
124 Reply Likes

We are aware that our lat/lon searches aren't the best at the moment. Searching by city name is actually the best. We're hoping to have a new database in 2 months that will fix the lat/lon issue. A good way to take care of the problem for your users is to offer them the chance to enter in their own location. "Not where you are? Enter your city."

Comment

7 years ago

Easilydo

2 Posts
0 Reply Likes

It's not a good user experience for our mobile app to get city/state information from the user when we have mobile device location with us. Also if we use a third party geoCode service like Google, we get accurate city/state but it is tough to construct a wunderground API query with citystate like https://.../conditions/q/CA/San_Franc...

Comment

7 years ago

Brendan Hayes, Official Rep

962 Posts
124 Reply Likes

You don't have to format it specifically that way. Try doing some searches like this:

http://api.wunderground.com/api/KEY/g...

Comment