On May 14, 4:34 pm, Reza <[email protected]> wrote: > > If you key in postcode YO21 3PU (or just YO21) you get taken to YO22 > 5LX. There are two retailers at YO21 which appear to be ignored! When > you zoom in to the map you can see that these two are one side of what > looks like an estuary in Whitby and there are two YO22 retailers > across the bay. However it doesn’t take you to these either - YO22 5LX > is a few miles away by the look of it. > > Is this a limitation of Google Maps API, or is there something we can > try to stop this from happening.
Google only geocodes postcode sectors (YO21 3). If I enter "YO21 3" I get the stockist in that sector. If I enter YO21 3PU, I reproduce your results. BUT I can't tell if those results are a result of Google's geocoding, or your selection based on their results. I think the thing to do is to explicitly allow -- even encourage -- full addresses to be entered instead of postcodes. And if a postcode is entered, then some nifty programming to strip off the walk letters at the end would be good (so that an entry of YO21 3PU means that YO21 3 is passed to the geocoder, since that's all that Google does anyway). There have been issues with Google's geocoding of postcodes in the past, where results have been one sector or district out. You may have found another instance. It's possible that in truncating YO21 3PU to get the sector, they are ending up with YO22 3. If Google don't have to truncate it, the postcode doesn't get altered and it's geocoded correctly. Andrew --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" 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 -~----------~----~----~----~------~----~------~--~---
