[Google Maps API v2] Re: reverse geocoding is incredibly far from given points

On Nov 6, 3:53 pm, Barry Hunter <barrybhun...@gmail.com> wrote:
> On 6 November 2010 23:33, Barry Hunter <barrybhun...@gmail.com> wrote:
>
> > Your code is just blindly taking the first placemark in the reverse
> > geocoding result. It might not be the best one (but usually is from
> > what I seen)
>
> > You can send a viewport along with the request:
> >http://code.google.com/apis/maps/documentation/javascript/v2/referenc...
>
> > setting it to the viewport of the map usually works well, but you can
> > also set it to a small bounding box (of a radius roughy the sort of
> > accuracy you would like.
>
> Oh, having actully tried that,www.nearby.org.uk/google/temp/reverse-geocoding-inaccuracy.html
>
> seems it doesnt work :(
>
> Also tried using &bounds=48.5872,39.3723|48.5874,39.3725 on a direct
> http request.
>
> You can see it definity works on Google Maps itself, try using the
> 'Whats here' right click context menu. You will see that the reverse
> geocoded (the RED pin) point varies with zoomlevel.
>
> I thought I had tried it in the API too at somepoint, but at least at
> the moment cant seem to get it to work.
>
> ... so the question is is this a feature request or a bug report.
> (will have to investigate what happens in GMaps API v3, as that is the
> only one Google are now supporting anyway)

Do you know that to be true?

My take is that while API v2 is deprecated, they will still fix bugs
and are still doing releases. They are unlikely to accept feature
requests for that version though, but I think a bug report would be
evaluated and might be fixed.

-- Larry

>
>
>
> > (this is because, rather just blindly picking the absolute closest
> > result, its actully looking for the most 'prominent'. So a point near
> > a village will often return a arbitary adress near the center (where
> > the placename label is drawn) - really just picking the village, but
> > its shown as an address level. You would think it might pick a
> > arbitary address of the edge of the village, but it doesnt do that.
> > So the bounding box is a good way to elevate the ranking of very close points)
>
> > - Or as Andrew says if just wanting it for directions, can just pass
> > coordinates the directions. It does 'absolute nearest' reverse
> > geocoding automatically :)
>
> > On 6 November 2010 20:43, graceman9 <gracem...@gmail.com> wrote:
> >> The problem is that geocoding is incredibly far from given points.
>
> >> Example:
> >>http://ezo.org.ua/code/maps/reverse-geocoding-inaccuracy/
>
> >> There are many places around a given point, but I get very distant
> >> results.
> >> Can I get back really nearest point?
>
> >> --
> >> 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 google-maps-api@googlegroups.com.
> >> To unsubscribe from this group, send email to google-maps-api+unsubscribe@googlegroups.com.
> >> For more options, visit this group athttp://groups.google.com/group/google-maps-api?hl=en.- Hide quoted text -
>
> - Show quoted text -

--
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 google-maps-api@googlegroups.com.
To unsubscribe from this group, send email to google-maps-api+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-maps-api?hl=en.