On Nov 17, 2:10 pm, "[email protected]" <[email protected]> wrote: > On Nov 17, 1:20 pm, Andrew Leach <[email protected]> > wrote: > > > On Nov 17, 8:14 pm, Josh <[email protected]> wrote: > > > > For example, geocoding "4401 Morella Avenue Studio city CA 91607" > > > gives results in Spain! > > > Tryhttp://maps.google.com/maps/geo?q=4401+Morella+Avenue+CA+91607&output... > > > The API doesn't know about "Studio City", and that is confusing it. > > But the API does know about Studio City (I > checked):http://www.geocodezip.com/example_geo2.asp?addr1=Studio%20City,%20CA&;... > > Just not with that zip code.
and the result that google maps gives: http://maps.google.com/maps?f=q&q=4401+Morella+Ave.Studio+City+CA+91607&ie=UTF8&hq=4401+Morella+Ave&hnear=California+91607&z=13&iwloc=A Looks to me like it comes from local search, not the geocoder. -- Larry > > > > > > > > But if I search for this same address on maps.google.com it shows up > > > in the correct place. > > > > Also, I did look at the FAQ and saw that sometimes there are > > > differences between the two geocoders (http://code.google.com/apis/ > > > maps/faq.html#geocoder_differences). > > > > Has the recent data update exacerbated these differences? > > > Possibly. The data update wasn't so much an update as a wholesale > > change of supplier. It's likely that TeleAtlas didn't want their data > > being used in the API and just given to the hoi polloi. > > > Andrew- Hide quoted text - > > - Show quoted text - -- 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=.
