Hi Andrew! Thank you very much for your answer. What I don't understand is why I get a correct result when I calculate a route on maps.google.com (using Web-Interface). Didn't it use the same geocoding engine? Or maybe both addresses will be used to calculate the result?
Regards, Andrej On 14 Jan., 18:21, "warden [Andrew Leach - Maps API Guru]" <[email protected]> wrote: > On Jan 14, 5:11 pm, Andi <[email protected]> wrote: > > > > > For thepostcodeBT71 6LA I get an address Moy, Dungannon BT71 7 and > > if I check it using maps.google.com the distance between this address > > and my address is really about 9km. > > I would expect BT71 6LA toreturnBT71 6, not BT71 7. It looks as > though that's a mistake in the API. > > Anyway, the API doesn't do postcode-level geocoding. It truncates the > postcode to the sector (eg BT71 6) and uses the centroid of that > sector. So every postcode which starts BT71 6 will get thesame > geocode. Addresses are more accurate. > > Thus in your example, BT71 6LA to 32B Coalisland Rd is calculated as > though you had asked for BT71 6 [or maybe BT71 7 in this case] to 32B > Coalisland Rd, and that will be a lot further. > > UK postcode handling leaves a lot to be desired. Someone will chime in > with a Free Our Data link, I expect. > > 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 -~----------~----~----~----~------~----~------~--~---
