On 4 February 2012 15:17, andy <[email protected]> wrote: > > their geo coding api is very poor i think pathetic is the right word. > ( strictly for india ).
http://gmaps-samples.googlecode.com/svn/trunk/mapcoverage_filtered.html shows that geocoding in India will find what is on the tiles. Postcodes are not supported, only the streetnames which are shown on the tiles. > since my app is store locator type for displaying a map the problem is > it fetches zip code in database for the corresponding listing for map > centring purpose and directions now for india it is of type > "110034" which correspond to china ( for google maps there can not be > any other location except this) hence the problem it centers map > around that. See http://econym.org.uk/gmap/didyoumean.htm for something which may help with ambiguous addresses. The example counts the number of results and asks for clarification if there is more than one: you could adapt this to verify that the address found by the geocoder is in India (as well) -- if it isn't, then ask the user to refine the address until it is found successfully. You may well be able to find an actual street address. Having found the user's location like that, you can then go ahead and use the standard store locator. However, there may well be geocoders which do know about Indian postcodes, which as you have thought would simplify the task quite a lot. -- You received this message because you are subscribed to the Google Groups "Google Maps API V2" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-api?hl=en.
