[postgis-devel] [PostGIS] #1052: Tiger Geocoder 2010 Geocode() "squishing" toward end of block

[PostGIS]

#1052: Tiger Geocoder 2010 Geocode() "squishing" toward end of block
-----------------------------+----------------------------------------------
  Reporter:  mikepease       |       Owner:  robe         
      Type:  enhancement     |      Status:  reopened     
  Priority:  medium          |   Milestone:  PostGIS 2.0.0
 Component:  tiger geocoder  |     Version:  trunk        
Resolution:                  |    Keywords:               
-----------------------------+----------------------------------------------

Comment(by mikepease):

 Thanks for all the explanation.

 I walked through the process of geocoding:
 3253 32nd Ave S Minneapolis     MN      55406

 I found the row in the edges table for this street is gid=540165
 The "rtoadd" column says 3299.

 But in reality, I think the last address on that block is 3253.
 There are 13 houses on the block, and I think the address number goes up
 by 4 for each house.

 So this discrepancy looks pretty consistent with the results I'm getting.
 Looking at the map I attached above to this bug report
 "shift_from_google_9-19-11.png",
 you can see the the south most address is getting shifted almost halfway
 up the block.  Look at 32nd Ave between 32nd and 33rd street since almost
 every house is displayed on that block.  All those addresses are squishing
 into the north half of the block.

 That makes sense now if Tiger thinks the addresses should go all the way
 to 3299 but they really only go to 3253.

 So, this unfortunately looks to be a pervasive problem in the street
 geometry here in Minnesota.  Do you have any sense how prevalent this
 issue might be nationwide?
 And is there anything that could be done about it?  I would imagine it's
 an enormous job to find the correct maximum address on each block in every
 state in the US.

 Google seems to know what the correct max address is, however.

 Would there be any way to compensate for an erroneous max address on a
 street segment?

 Seems like a difficult issue to resolve.

-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/1052#comment:13>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.