Opened 7 years ago
Closed 5 years ago
#3983 closed defect (wontfix)
Towns with cardinal names not being parsed correctly by address_normalizer
Reported by: | andrewsi | Owned by: | robe |
---|---|---|---|
Priority: | medium | Milestone: | PostGIS 3.0.0 |
Component: | tiger geocoder | Version: | 2.2.x |
Keywords: | Cc: |
Description
Possibly related to https://trac.osgeo.org/postgis/ticket/1310
postgis_full_version gives me this: POSTGIS="2.2.2 r14797" GEOS="3.5.0-CAPI-1.9.0 r4084" PROJ="Rel. 4.9.2, 08 September 2015" GDAL="GDAL 2.0.2, released 2016/01/26" LIBXML="2.9.1" LIBJSON="0.12" RASTER
When I do a: SELECT * FROM normalize_address('214 LIVINGSTON AVE, NORTH, SC 29112');
The city name 'NORTH' is being returned as the postdirabbrev field, rather than in the city field.
Change History (6)
comment:1 by , 7 years ago
comment:2 by , 7 years ago
Milestone: | PostGIS 2.4.3 → PostGIS 2.4.4 |
---|
confirmed it's still an issue in 2.4.3
comment:3 by , 7 years ago
But I should add, that the address_standardizer extension gets this right.
\x SELECT * FROM pagc_normalize_address('214 LIVINGSTON AVE, NORTH, SC 29112');
outputs:
-[ RECORD 1 ]--------+----------- address | 214 predirabbrev | NULL streetname | LIVINGSTON streettypeabbrev | AVE postdirabbrev | NULL internal | NULL location | NORTH stateabbrev | SC zip | 29112 parsed | t zip4 | NULL address_alphanumeric | 214
comment:4 by , 7 years ago
Milestone: | PostGIS 2.4.4 → PostGIS 2.5.0 |
---|
comment:5 by , 6 years ago
Milestone: | PostGIS 2.5.0 → PostGIS 3.0.0 |
---|
comment:6 by , 5 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Update: I'm getting exactly the same error when I parse an address in the town of NORTH EAST, in Maryland