On Sep 10, 4:03 am, Rossko <[email protected]> wrote: > > Are the differences documented? > > Not really, although the fact that differences exist is > -http://code.google.com/apis/maps/faq.html#geocoder_differences
Actually, that says that the geocoder API and the maps API may use different geocoders, not that the various ways to access maps use different geocoders. It looks like the static maps API isn't using USPS address standardization. If I put "JFK Parkway" (which the static map system does not recognize) through USPS address standardization, I get "JOHN F KENNEDY PKWY", which the static maps system recognizes. The main map system, though, recognizes "JFK Parkway". Checking the competition for "103 JFK Parkway, Short Hills, NJ, 07078". USPS: Recognized:OK, outputs "JOHN F KENNEDY PARKWAY" Bing Maps: Recognized OK, missed target by about 100 meters. Google Maps: Recognized OK, missed target by about 300 meters. This is the default address of "JFK PKWY" with no street number. Using "JOHN F KENNEDY PKWY": in front of building. Google static API: Misses "JFK Parkway", returns centroid of Short Hills, NJ Google geocoder API: Misses "JFK Parkway", returns centroid of Short Hills, NJ OpenStreetMap: No find. US Government National Map: Timed out. USC Geocoder; does not recognize "JFK". With "JOHN F KENNEDY", hits building driveway entrance. The best results were obtained by running the address through the USPS address standardizer, then through the USC geocoder. -- 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.
