[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:  pagc_address_parser  |     Version:  trunk        
 Keywords:                       |  
---------------------------------+------------------------------------------

Comment(by robe):

 I made some more minor tweaks only thing left to do is bring the pagc code
 into code base:

 Regarding what gets included in PostGIS tree, would it just be this?

 http://pagc.svn.sourceforge.net/viewvc/pagc/branches/sew-
 refactor/pagclib/api/pgsql

 Or we need the whole api.  I'm guessing we need the whole api and pgsql
 since the pgsql seems to reference headers from the api.

 Anyrate won't do this until you have that last issue worked out with
 reusing the built standardizer for subsequent query calls.

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