Or even they were correct in the past and now are incorrect ;)
http://groups.google.com/group/google-maps-api/browse_thread/thread/a3a354002f09f946/da9fed0dec96f1a8


On 4 Maj, 20:19, Daniels Lee™ <[email protected]> wrote:
> Hey Carl,
>
> Unfortunately, geocoding a physical address is never 100% guaranteed to
> yield correct results.  Our web service finds the best match and returns it.
>
> How many results are returning in your GeocoderResult object set?  Is the
> USA location included in them?
>
> If you indefinitely want your Geocoding results to return back to you
> locations within the US, you can always specify a region or bounds within
> your GeocoderRequest 
> object:http://code.google.com/apis/maps/documentation/v3/reference.html#Geoc...
>
> This would get you the results you want.
>
> Hope this helps,
>
> Dann
>
>
>
> On Fri, Apr 30, 2010 at 4:50 PM, nyc <[email protected]> wrote:
> > Dann,
>
> > I am submitting -- Lakewood, WA  and it returns - Lakewood WA,
> > Australia  when I am looking for Lakewood, WA, USA. I have set the
> > region=us and it still returns Lakewood WA, Australia.
>
> > Is this something you can fix?
>
> > Thanks
> > Carl
>
> > On Mar 9, 7:10 pm, Daniel Lee <[email protected]> wrote:
> > > We're happy to announce the launch of our new Google Geocoding Web
> > > Service.  Take a moment and read through the public blog post:
> >http://googlegeodevelopers.blogspot.com/2010/03/introducing-new-googl...
>
> > > The geocoding response format has been revamped to offer a number of
> > > improvements, which includes a flatter format, the ability to tag
> > > address components with multiple types, and added support for full
> > > names and abbreviations for countries and states.  Here are two
> > > examples of geocoding request/responses, one forward and one reverse:
> >http://maps.google.com/maps/api/geocode/xml?address=sydney&sensor=fal....
> > ..
>
> > > In addition to response format changes, geocoding requests no longer
> > > require Maps API keys.  However Maps API Premier customers are
> > > required to
> > > URL-sign their requests to the new service:
> >http://code.google.com/apis/maps/documentation/premier/guide.html#URL...
>
> > > The old geocoding service has been retroactively named to "Geocoding
> > > V2 Web Service", which will remain maintained and supported in
> > > accordance with our deprecation policy stated in the Maps API Terms of
> > > Service.
>
> > > Be sure to revisit the documentation for more details:
> >http://code.google.com/apis/maps/documentation/geocoding/
>
> > > ----
>
> > > As always, please post any feedback or concerns you have here.
>
> > > Thanks!
>
> > > Dann
>
> > --
> > 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]<google-maps-api%[email protected]>
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/google-maps-api?hl=en.
>
> --
> Daniels Lee
> Developer Programs Engineer
> Google, Inc.
> 345 Spear Street
> San Francisco, CA 94105
> 650 253 0967
>
> --
> 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 
> athttp://groups.google.com/group/google-maps-api?hl=en.

-- 
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.

Reply via email to