search

geary / google-election-center-data

Automatically exported from code.google.com/p/google-election-center-data
0 stars 0 forks source link

When Google Geocodes Differently Than SoS, The API Fails #28

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
9312 PLEASANT AVE KANSAS CITY MO 64138

http://pollinglocation.apis.google.com/?q=9312%20PLEASANT%20AVE%20KANSAS%20CITY%
20MO%2064138
{"status":"NO_STREET_SEGMENT_FOUND","locations":[[]],"contests":[[]]}

Street seg is below. Almost positive bug comes from Google geocoding Pleasant 
St as "E Pleasant St" ... but shouldn't we have geocoded the segment as E 
Pleasant St as well?

  <street_segment id="8800025581749">
    <start_house_number>9300</start_house_number>
    <end_house_number>9415</end_house_number>
    <odd_even_both>both</odd_even_both>
    <precinct_id>3300025570100</precinct_id>
    <precinct_split_id>4400025570285</precinct_split_id>
    <non_house_address>
      <street_direction />
      <street_name>PLEASANT</street_name>
      <street_suffix>AVE</street_suffix>
      <address_direction />
      <state>MO</state>
      <city>KANSAS CITY</city>
      <zip>64138</zip>
    </non_house_address>
  </street_segment>

Original issue reported on code.google.com by aaro...@gmail.com on 20 Oct 2010 at 12:56

GoogleCodeExporter commented 9 years ago 
The way around i was doing geocoding didn't prioritize trying street number 
over not street-number.

Maps geocodes
pleasant ave, kansas city, mo, 64138 to
pleasant ave, kansas city, mo 64138

but it geocodes
9300 pleasant ave, kansas city, mo 64138 to
9300 e pleasant ave, kansas city, mo, 64138

I've fixed the priority to try with the segment low address version first, the 
pipeline should pick up the fix in the next hour, and rewrite all the segments 
appropriately.

Original comment by dan...@google.com on 20 Oct 2010 at 1:45

GoogleCodeExporter commented 9 years ago 
Fixed

Original comment by dan...@google.com on 20 Oct 2010 at 2:12