Geocoding API returning different result than default Google Maps results

[Salar al Khafaji]

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/geocoding-simple.html

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

[Dave]

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

[Barry Hunter]

Google Maps just ignores stuff in brackets. (or more precisely its
used as a custom label) GMaps doesnt even try to understand the
meaning of the "municipality" wording.

try clicking the marker on the map to get the balloon
http://maps.google.com/maps?q=brussels+(municipality)
and compare with
http://maps.google.com/maps?q=brussels+(hay,+this+looks+a+nice+place)

So (...) is special syntax for Google Maps website itself.
- which just happens to mean it doesn't interfere with the
'geocoding' process.

... so just strip of any bits in brackets when sending to the geocoder
- it's not going to work .

> --
> You received this message because you are subscribed to the Google Groups
> "Google Maps JavaScript API v3" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-maps-js-api-v3/-/3XtWH0pPv7IJ.
> To post to this group, send email to google-map...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-maps-js-a...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-maps-js-api-v3?hl=en.

[Andrew Leach]

On 9 December 2011 22:20, Dave <dme...@gmail.com> wrote:
> 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.

This Question is Frequently Asked.
http://code.google.com/apis/maps/faq.html#geocoder_differences

[eshon]

A couple weeks ago a Geocoding request for "Staten Island" or "Staten Island, NY" returned one location.  Now it's returning 2 or 3 locations with slightly different lat/lon's. 

One result is now "Richmond, NY" and the other is "Staten Island, NY", adding "NY" to the query may produce a 3rd result:

http://maps.googleapis.com/maps/api/geocode/json?sensor=false&address=staten+island

http://maps.googleapis.com/maps/api/geocode/json?sensor=false&address=staten+island+ny

I understand that geocoders are always 'best effort' and the underlying data may be changing but it'd be nice to be updated about these major changes so they're easier to respond to.