On Jul 19, 10:57 am, David Roberts <david.robe...@firehoop.com> wrote: > I have a website which uses the Google geocoder to determine > coordinates from an address. Disambuguation is resolved in the case > of multiple results being returned by displaying a list of all > returned "formatted_address" which the user can then select. I then > use this to populate the search box (for future search purposes) and > use the location for that address. > > Suddenly (since yesterday, 18th July) all subsequent geocode lookups > using the exact address string selected by the user on the first > lookup also produce multiple results. This was not the case before > yesterday.
Something changed, probably a geocoding database update. > > For example, a search for Bradford (with the bounds limited to the UK) > returns three results... > > Bradford, UK > Trafford, UK > Bradford-on-Avon, Wiltshire, UK > > Selecting "Bradford, UK" and using this as the address parameter for > another search returns FOUR results... > > Bradford, UK > Trafford, UK > Bradford-on-Avon, Wiltshire, UK > Bradford, Greater Manchester M11, UK > > What's going on? Did the release on 18th cause an "unexpected" > effect? Why would you necessarily expect "Bradford, UK" to return a single set of coordinates (other than it has in the past)? (at least 3 of those four results look reasonable to me; the result doesn't seem unexpected to me, and the first result is the "best" match.) -- Larry -- 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 google-maps-js-api-v3@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
