| Issue 995: | Bug: HTTP Geocoder will drastically change address without warning instead of returning best match | |
| 3 people starred this issue and may be notified of changes. | Back to list |
Sign in to add a comment
|
If the HTTP Geocoder is unable to find an address, it will completely change the address without warning the user, rather than returning the best match using the address components provided. Repro: Attempt to Geocode "0N943 BARTELT Rd, GENEVA, IL 60134" http://maps.google.com/maps/geo?client=YourClientString&sensor=false&output=xml&key=YourKey&q=0N943+BARTELT+Rd%2C+GENEVA%2C+IL+60134 Expected: Returned address has not had all address components completely changed; rather, the best accuracy match that does not invalidate all input address components is returned. Actual: Returned address is "39W943 Midan Dr, Elburn, IL 60119, USA", and is reported to have Address-Level accuracy. Notice this shares no components in common with the input address other than the "943" extension of the street number: <kml> <Response> <name>0N943 BARTELT Rd, GENEVA, IL 60134</name> <Status> <code>200</code> <request>geocode</request> </Status> <Placemark id = "p1"> <address>39W943 Midan Dr, Elburn, IL 60119, USA</address> <AddressDetails Accuracy = "8"> <Country> <CountryNameCode>US</CountryNameCode> <CountryName>USA</CountryName> <AdministrativeArea> <AdministrativeAreaName>IL</AdministrativeAreaName> <Locality> <LocalityName>Elburn</LocalityName> <Thoroughfare> <ThoroughfareName>39W943 Midan Dr</ThoroughfareName> </Thoroughfare> <PostalCode> <PostalCodeNumber>60119</PostalCodeNumber> </PostalCode> </Locality> </AdministrativeArea> </Country> </AddressDetails> <ExtendedData> <LatLonBox north = "41.8869099" south = "41.8806147" east = "-88.3901109" west = "-88.3964061"/> </ExtendedData> <Point> <coordinates>-88.3932585,41.8837623,0</coordinates> </Point> </Placemark> </Response> </kml> ********************************************************* For developers viewing this issue: please click the 'star' icon to be notified of future changes, and to let us know how many of you are interested in seeing it resolved. ********************************************************* |
||||||||||||
,
Jan 13, 2009
(No comment was entered for this change.)
Status: Accepted
Labels: Component-Data Internal-1580233 |
|||||||||||||
,
May 24, 2009
Changing status of "Accepted" issues to "Acknowledged", to clarify their state. We may not be able to resolve all bugs or fulfill all feature requests, but we do thank you for filing them, and we will continually revisit all acknowledged issues and evaluate their feasibility. Thanks!
Status: Acknowledged
|
|||||||||||||
,
May 30, 2009
There was some confusion with the change from the "Accepted" status to the "Acknowledged" status, and some developers took that to mean that their bug was being downgraded. This was only a wording change, not a priority change. We are still working on fixing many bugs (particularly the regression bugs), so a fix for your bug may still be coming in the future. After a discussion in the forum, we will now use "Confirmed" instead of "Acknowledged". This status indicates that we have verified the bug, reported it internally, and it is included in the list of bugs that we review each week (when determining what to fix next).
Status: Confirmed
|
|||||||||||||
|
|
|||||||||||||