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

 That name is fine. I imagine we will be building more specific tables as
 needed and I structure my Tiger data a lot differently than I think you
 do. I have C code that denormalizes the Tiger data into single side
 records so a single TLID might generate 1+ records if it has multiple
 sides, address ranges and city names associated to it.

 I built and installed pg 9.2 using mingw64 but didn't use the debug flags.
 Typically stuff that works with debug and not optimized indicates one of
 two things:

  * the optimizer is broken in the compiler
  * the code being compiled is broken and overwriting something

 I could be wrong, but I thought the later is fairly common with 64 bit
 stuff because things (structures) need to be aligned on 8 byte boundaries
 and padded where are most 32 bit compilers don't have that requirement.

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