On 15 December 2011 07:39, PoojaC <[email protected]> wrote: > Thanks for your reply. > When I investigated further on this issue, i found out that the reason is > not that this address is new or not in geocoder db but the issue is the > postal code. When i remove the postal code, it gives me the correct lat/long > coordinates. Now, as far as i could see, this is happening with addresses of > India only. One solution would be to remove this postal code but they would > not return precise results for other addresses. Moreoever, why is this > happening at all when geocoding api accepts the postal code in the input > address?
The API accepts whatever you give it, which it then tries to make sense of. This spreadsheet may not be entirely up-to-date, but it shows a minimum state (the actual result could be better than indicated). It shows that geocoding in India is "same as tiles", which I doubt includes postcode data. http://gmaps-samples.googlecode.com/svn/trunk/mapcoverage_filtered.html If you do include postcode data for countries which are shown as "same as tiles", the API is likely to get confused. -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" 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-js-api-v3?hl=en.
