My favorites | Sign in
Project Logo
             
New issue | Search
for
| Advanced search | Search tips
Issue 994: Bug: Inexact address matches from HTTP Geocoder can have street number replaced with unit number
3 people starred this issue and may be notified of changes. Back to list
Status:  Confirmed
Owner:  ----
ApiType-Geocoder
Type-Defect
Component-Data
Internal-1580248


Sign in to add a comment
 
Reported by patterson.ar, Jan 13, 2009
In cases where an address is entered where an inexact match is found, the
HTTP Geocoder will replace the street number of the address with the unit
number provided rather than discarding the unit number and correcting the
street address.

Repro:
Attempt to geocode "612 Prospect St Apt 304, Seattle, WA 98109":
http://maps.google.com/maps/geo?client=YourClientString&sensor=false&output=xml&key=YourKey&q=612+Prospect+St+Apt+304%2C+Seattle%2C+WA+98109

Expected:
Address returned is "612 N Prospect St, Seattle, WA 98109" (one of the
results if you attempt to geocode "612 Prospect St, Seattle, WA 98109", and
the only one of address-level accuracy with zip 98109)

Actual:

Address returned is "304 Prospect St" (where the street number has been
replaced with the unit number):

<kml>
    <Response>
        <name>612 Prospect St Apt 304, Seattle, WA 98109</name>
        <Status>
            <code>200</code>
            <request>geocode</request>
        </Status>
        <Placemark id = "p1">
            <address>304 Prospect St, Seattle, WA 98109, USA</address>
            <AddressDetails Accuracy = "8">
                <Country>
                    <CountryNameCode>US</CountryNameCode>
                    <CountryName>USA</CountryName>
                    <AdministrativeArea>
                        <AdministrativeAreaName>WA</AdministrativeAreaName>
                        <Locality>
                            <LocalityName>Seattle</LocalityName>
                            <Thoroughfare>
                                <ThoroughfareName>304 Prospect
St</ThoroughfareName>
                            </Thoroughfare>
                            <PostalCode>
                                <PostalCodeNumber>98109</PostalCodeNumber>
                            </PostalCode>
                        </Locality>
                    </AdministrativeArea>
                </Country>
            </AddressDetails>
            <ExtendedData>
                <LatLonBox
                    north = "47.6320821"
                    south = "47.6257869"
                    east = "-122.3480025"
                    west = "-122.3542977"/>
            </ExtendedData>
            <Point>
                <coordinates>-122.3511501,47.6289345,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.
*********************************************************
 

Comment 1 by pamela.fox, Jan 13, 2009
(No comment was entered for this change.)
Status: Accepted
Labels: Component-Data Internal-1580248
Comment 2 by pamela.fox, 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
Comment 3 by pamela.fox, 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
Sign in to add a comment

Hosted by Google Code