#1073 closed defect (fixed)
Normalizing irregular zipcodes
Reported by: | mikepease | Owned by: | robe |
---|---|---|---|
Priority: | high | Milestone: | PostGIS 2.0.0 |
Component: | tiger geocoder | Version: | 1.5.X |
Keywords: | history | Cc: |
Description
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
select *
from geocode('212 3rd Ave N, MINNEAPOLIS, MN 55401')
—breaks with partial 3 digit zip
select *
from geocode('212 3rd Ave N, MINNEAPOLIS, MN 554')
—breaks with extra dash
select *
from geocode('212 3rd Ave N, MINNEAPOLIS, MN 55401-')
Change History (2)
comment:1 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:2 by , 13 years ago
Keywords: | history added |
---|
fixed at r7517