[postgis-devel] [PostGIS] #1051: Tiger Geocoder 2010 normalize_address bug - postDirAbbrev doesn't parse
PostGIS
trac at osgeo.org
Fri Jun 24 09:51:08 PDT 2011
#1051: Tiger Geocoder 2010 normalize_address bug - postDirAbbrev doesn't parse
-----------------------------+----------------------------------------------
Reporter: mikepease | Owner: robe
Type: defect | Status: reopened
Priority: critical | Milestone: PostGIS 2.0.0
Component: tiger geocoder | Version: 1.5.X
Resolution: | Keywords:
-----------------------------+----------------------------------------------
Changes (by mikepease):
* status: closed => reopened
* resolution: fixed =>
Comment:
Hi, Regina.
I got your latest code and your changes worked! Super!
normalize_address() now seems to get the direction suffix properly.
However, I'm still having an issue with the geocode() function incorrectly
choosing the wrong street, getting the "North" street instead of the
"South" street for example. Here's an example in downtown Minneapolis, MN
where the Avenue numbers split in the middle of the city 1st-10th Ave
North and 1st-10th Ave South.
--This incorrectly geocodes to 150 2nd Ave *South* instead of north[[BR]]
select (g.addy).*, astext(g.geomout), g.*
from geocode('150 2nd Ave S, Minneapolis, MN 55401') as g
--This fuzzy match does find 150 2nd Ave *South* in its list of candidate
matches[[BR]]
select (g.addy).*, astext(g.geomout), g.*
from geocode('150 2nd, Minneapolis, MN 55401') as g
Since the fuzzy match finds the correct street in its list, there appears
to be an error in selecting the correct street for and exact match.
Let me know what you find with this.
Thanks for all the quick work!
Mike
--
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1051#comment:8>
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.
More information about the postgis-devel
mailing list