[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 woodbri):

 Regina,

 I think initially we should just create a directory in your source tree
 and put the files there. While I have created a branch in PAGC where I
 developed this code, I have not had time to review the code with Walter to
 figure out how it should be packaged or if it will even stay in the
 current form. I think that since PostGIS is the only user of this at the
 moment and it needs to be in a form suitable for including in PostGIS this
 makes the most sense for now. I the future as things change we can make
 some adjustments. In addition, to this Walter and I want to look at
 refactoring all of PAGC because their may be other useful bits that we can
 extract in a similar way. For now you need a stable fork just keep it in
 its own directory and we should be able to pull changes out of a similar
 directory that I will maintain in a PAGC branch, until we get our end
 sorted.

 Let me know if this makes sense for you.

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