[postgis-devel] [PostGIS] #1148: Geocoder has poor results with correct inputs
PostGIS
trac at osgeo.org
Thu Aug 4 11:06:26 PDT 2011
#1148: Geocoder has poor results with correct inputs
----------------------------+-----------------------------------------------
Reporter: darkblueb | Owner: robe
Type: defect | Status: new
Priority: high | Milestone: PostGIS 2.0.0
Component: tiger geocoder | Version: trunk
Keywords: |
----------------------------+-----------------------------------------------
Comment(by robe):
And to demonstrate -- if I insert this record:
{{{
INSERT INTO tiger_data.ca_featnames( tlid, fullname, "name", predirabrv,
pretypabrv, prequalabr,
sufdirabrv, suftypabrv, sufqualabr, predir, pretyp, prequal,
sufdir, suftyp, sufqual, linearid, mtfcc, paflag, statefp)
SELECT tlid, 'el Cajon Ave' AS fullname,'el Cajon' AS name, predirabrv,
pretypabrv, prequalabr,
sufdirabrv, suftypabrv, sufqualabr, predir, pretyp, prequal,
sufdir, suftyp, sufqual, linearid, mtfcc, paflag, statefp
FROM tiger_data.ca_featnames
WHERE tlid = '125027794' AND name = 'el Canon';
}}}
And then run this query:
{{{
SELECT pprint_addy(addy), ST_AsText(geomout) As coord, rating
FROM geocode('4533 El Cajon Ave, Fremont, CA 94536',1) As g;
}}}
The answer comes back pretty fast (175 ms on my crappy drive with many
other states loaded and with out that entry its very slow about 30 secs
and comes back as you said with the wrong answers)
with:
{{{
pprint_addy | coord | rating
--------------------------------------+--------------------------+--------
4533 el Cajon Ave, Fremont, CA 94536 | POINT(-122.0241 37.5582) | 0
}}}
--
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1148#comment:12>
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