The LatLonBox tells you the optimal viewport bounding box, according to our opinion. It does not tell you the actual bounding box of the geometry.
In the new upcoming geocoder format (which you can preview in Maps API v3), we supply both a bounds for the viewport and a bounds for the geometry size: http://code.google.com/apis/maps/documentation/v3/services.html#GeocodingResponses You're welcome to use ExtendedData in the current geocoder, but we likely will spend our time documenting the upcoming geocoder format instead of features in the old geocoder format. - pamela On Thu, Jun 18, 2009 at 9:19 PM, Mike Williams<[email protected]> wrote: > > Although it's not in the documentation yet, it's been announced here by > Pamela, so it should be OK to use. > > http://groups.google.com/group/Google-Maps-API/msg/58c1b09987b39e26 > > It doesn't seem to work so well on small features, like roads and > individual properties, returning boxes that are considerably larger than > you'd expect. > > -- > Mike Williams > http://econym.org.uk/gmap > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
