#1354 closed defect (fixed)
Problems geocoding addresses containing "ST STE"
Reported by: | bpanulla | Owned by: | robe |
---|---|---|---|
Priority: | medium | Milestone: | PostGIS 2.1.0 |
Component: | pagc_address_parser | Version: | master |
Keywords: | Cc: | woodbri |
Description
The geocoder gets confused by addresses with a type of "ST" followed immediately by an internal address beginning with "STE", even though normalize_address() appears to handle this without issue.
normalize_address()
SELECT addy.* FROM normalize_address('6226 E PIMA ST STE 999, TUCSON') AS addy;
Address | Pre-Dir | Street | Street Type | Post-Dir | Internal | Locality | State | Zip | parsed |
6226 | E | PIMA ST | St | STE 999 | TUSCON | AZ | t |
geocode() with bad string
SELECT g.rating, (addy).* FROM geocode('6226 E PIMA ST STE 999, TUCSON, AZ') AS g;
Rating | Address | Pre-Dir | Street | Street Type | Post-Dir | Internal | Locality | State | Zip | parsed |
100 | Tuscon | AZ | 85641 | t |
geocode() with amended string
If you replace "ST" with "STREET" the geocoder performs as desired.
SELECT g.rating, (addy).* FROM geocode('6226 E PIMA STREET STE 999, TUCSON, AZ') AS g;
Rating | Address | Pre-Dir | Street | Street Type | Post-Dir | Internal | Locality | State | Zip | parsed |
1 | 6226 | E | Pima | St | STE 999 | Tuscon | AZ | 85712 | t |
Change History (9)
comment:1 by , 13 years ago
Status: | new → assigned |
---|
comment:2 by , 13 years ago
Milestone: | PostGIS 2.0.0 → PostGIS 2.1.0 |
---|
comment:3 by , 13 years ago
Milestone: | PostGIS 2.1.0 → PostGIS 2.0.1 |
---|
comment:4 by , 12 years ago
Milestone: | PostGIS 2.0.1 → PostGIS 2.1.0 |
---|
comment:5 by , 12 years ago
Cc: | added |
---|
comment:6 by , 12 years ago
comment:7 by , 12 years ago
Component: | tiger geocoder → pagc_address_parser |
---|
rather than just push these, I'm going to move them to things that pagc_address_parser can handle or should and close them out once tested and pagc integrated as an option.
comment:8 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
This works fine with pagc_normalize function.
SELECT addy.* FROM pagc_normalize_address('6226 E PIMA ST STE 999, TUCSON') AS addy;
Yields:
address | predirabbrev | streetname | streettypeabbrev | postdirabbrev | internal | location | stateabbrev | zip | parsed ---------+--------------+------------+------------------+---------------+-----------+----------+-------------+-----+-------- 6226 | E | PIMA | St | | SUITE 999 | TUCSON | | | t
and then geocoder should do the the right thing with that, but I don't have AZ data loaded to verify.
comment:9 by , 12 years ago
oops forgot the AZ
SELECT * FROM pagc_normalize_address('6226 E PIMA ST STE 999, TUCSON, AZ') AS addy;
address | predirabbrev | streetname | streettypeabbrev | postdirabbrev | internal | location | stateabbrev | zip | parsed ---------+--------------+------------+------------------+---------------+-----------+----------+-------------+-----+-------- 6226 | E | PIMA | St | | SUITE 999 | TUCSON | AZ | | t
PAGC tools handle this.