[postgis-tickets] [PostGIS] #2193: Utilize PAGC parser as drop in replacement for tiger normalizer

[PostGIS]

#2193: Utilize PAGC parser as drop in replacement for tiger normalizer
----------------------------+-----------------------------------------------
 Reporter:  robe            |       Owner:  robe         
     Type:  enhancement     |      Status:  new          
 Priority:  medium          |   Milestone:  PostGIS 2.1.0
Component:  tiger geocoder  |     Version:  trunk        
 Keywords:                  |  
----------------------------+-----------------------------------------------

Comment(by robe):

 Steve,

 As a general note I'm hoping to have this integrated in 2.1 tiger geocoder
 as an option. I guess we'll need to decide how the code base will work.
 I'm indifferent.
 1) Do we just point people at your repo to download the
 address_standardizer
 or do we incorporate that piece in PostGIS as an extra (in extras folder)
 separate but related to tiger_geocoder.

 2) If it's an extra I would document it in the PostGIS docs as a separate
 extra useable with tiger geocoder with its own dedicated section in the
 docs


 If separate -- I'd have it as a subsection in tiger geocoder docs -- where
 to download install and basic instructions for using with tiger geocoder
 and link to get more info.

 Similar to how we do libxml, json-c


 thoughts?

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