On Apr 20, 5:16 am, niklas <[email protected]> wrote: > I know there are lots of streets in Sweden called > "Drottninggatan" (Queens road), that is why we use it as a test case > for getting multiple suggestions. > > And by saying "'Drottninggatan' is an address" - I meant it's not a > city or region. > > Now that the address/street name issue is out of the way, does anyone > have any info on the changed behaviour of the getLocations function?
I still go with my original guess: > Perhaps the geocoder database was updated but it could be: yes, the behavior of the geocoder changed. Perhaps your issue is a regression, perhaps it is by design, we don't have any insight into that. You could try creating an "issue" in the issue tracker, but as v2 is officially deprecated, I wouldn't expect much. I do expect that the same backend is used for both v2 and v3 and the geocoding webservice, so if you get the issue in the right place, it might get attention, but I don't know where that would be. As Mike Williams used to say "never trust a geocoder". -- Larry > > On 20 Apr, 11:17, Andrew Leach <[email protected]> wrote: > > > On 20 April 2011 10:03, niklas <[email protected]> wrote: > > > > "Drottninggatan" is an address > > > No, it's a street name. An address needs to be more specific -- unless > > the street is unique or uniquely famous. But even something like > > "Downing Street" defaults to Denver rather than London. > > > So you could have "Drottninggatan, Landskrona" or "Drottninggatan, > > Malmo", and the relevant tv transmitter differs greatly between those > > two addresses. > > -- 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.
