[postgis-tickets] [PostGIS] #2289: Redesign Geocoder (was: Redesign Tiger Geocoder)

[PostGIS]

#2289: Redesign  Geocoder
----------------------------+-----------------------------------------------
 Reporter:  woodbri         |       Owner:  robe          
     Type:  enhancement     |      Status:  new           
 Priority:  medium          |   Milestone:  PostGIS Future
Component:  tiger geocoder  |     Version:  2.0.x         
 Keywords:                  |  
----------------------------+-----------------------------------------------
Changes (by robe):

  * milestone:  => PostGIS Future


Comment:

 I've retitled this :)

 It is my plan for a more generic geocoder, but not for the tiger one and I
 expect both to live in parallel for a while.  The problem is that this
 requires an overhaul of how I'm doing queries and also my reverse geocoder
 logic.  Since its working well for ME :) and the project that originally
 funded it (mostly geocoding and reverse geocoding highways and ramps in
 MA), I really don't want to mess with it until I get more funding for it.

 What you are describing I consider more of a whole rewrite project with
 consideration of what is salvageable in current tiger geocoder and porting
 that over.  The queries which is the brunt of my effort on it is NOT
 SALVAGEABLE unfortunately as it relies on a lot of tables from tiger. It
 uses featnames, edges, faces, addr etc. to determine side of street
 alternative names, street range etc etc.

 Out of curiosity how many rows does your stdaddr table have for example to
 satisfy just MA?

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/2289#comment:1>
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.