Issue 993 - gmaps-api-issues - Bug: HTTP Geocoder Drops Crucial Street Number Information

Issue 993:	Bug: HTTP Geocoder Drops Crucial Street Number Information	‹ Prev 405 of 981 Next ›
	2 people starred this issue and may be notified of changes.	Back to list

Status:	New
Owner:	----
ApiType-Geocoder
Type-Defect

Reported by patterson.ar, Jan 13, 2009

Complex Street Numbers appears to have crucial parts of the street number
dropped in the results from the HTTP Geocoder, with the Geocoder still
reporting Address-Level accuracy

Repro:

Geocode "33w878 Army Trail Rd, Wayne, Il 60184":
http://maps.google.com/maps/geo?client=YourClientString&sensor=false&output=xml&key=YourKey&q=33w878+Army+Trail+Rd%2C+Wayne%2C+Il+60184

Expected:

Returned result maintains "w878" portion of street number, or geocoder
reports something less than "Address-Level" accuracy

Actual: 

The following is returned:

<kml>
    <Response>
        <name>33w878 Army Trail Rd, Wayne, Il 60184</name>
        <Status>
            <code>200</code>
            <request>geocode</request>
        </Status>
        <Placemark id = "p1">
            <address>33 Army Trail Rd, Wayne, IL 60184, USA</address>
            <AddressDetails Accuracy = "8">
                <Country>
                    <CountryNameCode>US</CountryNameCode>
                    <CountryName>USA</CountryName>
                    <AdministrativeArea>
                        <AdministrativeAreaName>IL</AdministrativeAreaName>
                        <Locality>
                            <LocalityName>Wayne</LocalityName>
                            <Thoroughfare>
                                <ThoroughfareName>33 Army Trail
Rd</ThoroughfareName>
                            </Thoroughfare>
                            <PostalCode>
                                <PostalCodeNumber>60184</PostalCodeNumber>
                            </PostalCode>
                        </Locality>
                    </AdministrativeArea>
                </Country>
            </AddressDetails>
            <ExtendedData>
                <LatLonBox
                    north = "41.9558596"
                    south = "41.9495644"
                    east = "-88.2783514"
                    west = "-88.2846466"/>
            </ExtendedData>
            <Point>
                <coordinates>-88.2814990,41.9527120,0</coordinates>
            </Point>
        </Placemark>
    </Response>
</kml>

Notice the "w878" is dropped from the <address> and <ThoroughfareName>
elements, and accuracy is reported as "8" (Address-Level)

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

What does "w878" refer to? The returned result has the street number, so it is indeed
address level accuracy.

Comment 2 by patterson.ar, Jan 13, 2009

This is the historical addressing system for Chicago.

Chicago has a reference point at State St & Madison St in downtown Chicago. The
streets are divided into one mile-block sets, each containing 8 "reference" blocks
(and for the most part, those are where the actual streets are).

The address given indicates that the address on Army Trail Rd, in the set of blocks
starting 33 miles (or 264 "reference" blocks) west of this reference point (or in
other words, on Army Trail Rd in the 33rd block-set west). It then has a street
number of 878 in that block set (the first 8 indicates that it's actually on the 8th
"reference" block of that block set).

Thus the "w878" is actually a critical portion of the address provided, since it
indicates where in that one mile stretch of Army Trail Rd the address is.

Comment 3 by pamela.fox, Jan 13, 2009

Ah, interesting, I understand now.

What are you using the accuracy number for in this case?

Comment 4 by patterson.ar, Jan 14, 2009

We use the accuracy number to determine whether the geocode is good enough to map
with; we only show address-level as points on a map; all others we use for an
approximate location.

Comment 5 by ccarlinx, Mar 03, 2009

I am seeing similar issues with the St. Charles Area of IL.  Addresses like:  
5N145 PRAIRIE ROSE DR St. Charles, IL 60175 the geocode API mangles them.  The
maps.google.com also does the same, while both Yahoo and Microsoft do not.

► Sign in to add a comment