On 10/03/2009, gpspassion <[email protected]> wrote: > > Possibly, but I can't see the benefit, if you typed an address you > didn't get your map centered on the "wilderness" so it's only hurting > those who used the geocoder () function as a parser.
but that was never documented behaviour, so there was no onus to maintain that feature. its just a shame the undocumented feature just changed. its still undocumented that a coord invokes the reverse geocoder (the docs specifically say that sending a GLatLng as opposed a string will be reverse geocoded) > > I guess I'm getting what I pay for, i.e. nothing, but it's a bit > worrying that Google would just change this out of the blue with no > documentation/warning to the people who depend on it. If they had to > change it for some reason, they should probably add a "flag" to allow > it to work the old way, by default : snapped - snap/off : 1 > > Hopefully they will reverse course as they did a couple of weeks ago > when the same thing happened, except it was only for a couple of > hours... > > > On Mar 10, 8:07 pm, Rossko <[email protected]> wrote: > > > Since sometime last night, the geocoder no longer works like it used > > > to. If you type in a position, it now appears to be "snapped" to a > > > road, it can no longer be "in the wilderness" > > > > That might mean it's working better than it used to from other > > people's viewpoint; instead of giving up on a wilderness location it > > now finds something nearby. > > > -- Barry - www.nearby.org.uk - www.geograph.org.uk - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
