[postgis-devel] [PostGIS] #1614: More normalizer tricks

[PostGIS]

#1614: More normalizer tricks
----------------------------+-----------------------------------------------
 Reporter:  mikepease       |       Owner:  robe         
     Type:  defect          |      Status:  new          
 Priority:  medium          |   Milestone:  PostGIS 2.1.0
Component:  tiger geocoder  |     Version:  1.5.X        
 Keywords:                  |  
----------------------------+-----------------------------------------------

Comment(by mikepease):

 --County Road syntax is sensitive
 In a address database we have, they used a different syntax for listing
 county roads.
 Example:
 8435  COUNTY 20 RD SE, ROCHESTER, MN 55904

 This normalizes differently than:
 8435  COUNTY RD 20 SE, ROCHESTER, MN 55904

 But this second syntax stumps the normalizer.
 If you write it this way, then it works:
 8435  COUNTY ROAD 20 SE, ROCHESTER, MN 55904

 select * from normalize_address('8435  COUNTY 20 RD SE, ROCHESTER, MN
 55904')

 select * from normalize_address('8435  COUNTY RD 20 SE, ROCHESTER, MN
 55904')

 select * from normalize_address('8435  COUNTY ROAD 20 SE, ROCHESTER, MN
 55904')


 I can see why the first syntax may produce a reasonable, if not the
 desired, result.
 But the second syntax shouldn't get stumped.

 Looks like the look up table for for road type needs more versions of
 spellings to include:
 COUNTY RD
 as well as COUNTY ROAD

 Perhaps this is true for other street types too?

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