I just submitted a similar question for the string "Orange, France". It returns a location at the France Pavilion in Epcot Center in Orange County Florida! In your case, if you zoom in close, the location is actually on Brussels Street in the Municipality of Cainta in the Philippines ... so in your case and mine, there's some sort of reason there. But it still doesn't explain why the geocoder returns a result that's different than Google Maps returns. I'd be very interested to find out why that difference exists.
Thanks, Dave On Dec 9, 11:05 am, Salar al Khafaji <sa...@typlab.com> wrote: > Hi, > > We are seeming an anomaly with a specific string when using the Geocoding > API. > > When searching for the exact string "Brussels (municipality)" on the > Geocoding API, we're getting a location in the Philippines while we're > expecting the capital of Belgium. This also occurs on the simple geocoding > example provided by > Google:http://code.google.com/apis/maps/documentation/javascript/examples/ge... > > However, searching for the same string on Google Maps is returning the > correct location:http://maps.google.com/maps?q=brussels+(municipality). We > do note that the suggest feature of Google Maps is also returning the > location in the Philippines, but it seems to be ignored when actually > performing the search. > > Is this an issue with the Geocoding API or on the Maps data level? We'd > love to see this resolved. > > Thanks! > Salar -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to google-maps-js-api-v3@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
