[postgis-tickets] [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.1.0
 Component:  tiger geocoder  |     Version:  trunk        
Resolution:                  |    Keywords:               
-----------------------------+----------------------------------------------

Comment(by woodbri):

 Mike,

 I think that Tiger has closer to 30-40 million records and you have the
 problem of doing this every year that they release data updates. I have I
 thought about a way to create extra tables to store this information in
 and then reapply it if appropriate to successive updates.

 It would also be possible to license the USPS zip+4 data and match that to
 the Tiger data to improve the data. At some point you need to ask if
 licensing something like Navteq isn't a more appropriate if you can afford
 that.

 Speaking of parcels, I just added them to my Navteq geocoder (not based on
 the this Tiger geocoder) but the process was reasonably trivial since the
 parcel points were linked to the street segments. If you use straight
 parcel data then you have to build and standardize the addresses of the
 parcels and query them separately, or preprocess the data to link them to
 the appropriate Tiger edges.

 Anyway, I would be interested in working on either of these projects also.

-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/1052#comment:28>
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.