[postgis-devel] [PostGIS] #1073: Normalizing irregular zipcodes

[PostGIS]

#1073: Normalizing irregular zipcodes
----------------------------+-----------------------------------------------
 Reporter:  mikepease       |       Owner:  robe         
     Type:  defect          |      Status:  new          
 Priority:  high            |   Milestone:  PostGIS 2.0.0
Component:  tiger geocoder  |     Version:  1.5.X        
 Keywords:                  |  
----------------------------+-----------------------------------------------
 Hi, Regina.
 Thanks for all the great improvements with the geocoder.
 I found another issue that popped up in my testing.

 Some of the addresses in my database have incorrectly written zipcodes.
 Either they are not complete (<5 chars), have a dash hanging on the end
 (55401-), or there was a fumble fingers that added an extra digit in there
 somewhere (553404)

 Whenever the zip is not properly formed, no geocode is returned.


 --works with 5 digit zip[[BR]]
 select *
 from geocode('212 3rd Ave N, MINNEAPOLIS, MN 55401')

 --breaks with partial 3 digit zip[[BR]]
 select *
 from geocode('212 3rd Ave N, MINNEAPOLIS, MN 554')


 --breaks with extra dash[[BR]]
 select *
 from geocode('212 3rd Ave N, MINNEAPOLIS, MN 55401-')

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1073>
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.