[postgis-devel] [PostGIS] #1382: Some addresses take a long time to geocode or normalize
PostGIS
trac at osgeo.org
Sat Dec 17 21:02:45 PST 2011
#1382: Some addresses take a long time to geocode or normalize
----------------------------+-----------------------------------------------
Reporter: raviada | Owner: robe
Type: defect | Status: assigned
Priority: medium | Milestone: PostGIS 2.0.0
Component: tiger geocoder | Version: trunk
Keywords: |
----------------------------+-----------------------------------------------
Comment(by robe):
Ravi,
Okay that seems to agree with around what I am getting for that address.
I get 19 seconds for no limit and 18 seconds for limit. But the address it
returns is completely wrong. I'll put in a separate ticket for this. I
think it might be the Astoria throwing it off.
since if I run this:
{{{
select pprint_addy(addy), ST_AsText(geomout), rating FROM geocode('2601
24TH AVE, NY 111022337',2);
-- it returns this:
0 24th Ave, New York, NY 11102 POINT(-73.9184479285714 40.7744440102041)
15
}}}
Which is much more accurate.
If I reverse geocode:
{{{
-- answer tiger geocoder is returning (with Astoria)
SELECT pprint_addy(addy[1]), array_to_string(street, '|') from
reverse_geocode('POINT(-73.9750505 40.613036)', true) As g;
--
6148 24th Ave, NY 11204 1404 - 1416 Dahill Rd|2301 - 2399 62nd St
}}}
-- to rule out a tiger data issue, I reverse geocoded what google returns.
-- though the place seems suspiciously missing, thought that could be a
reverse geocode issue.
{{{
SELECT pprint_addy(addy[1]), array_to_string(street, '|') As
cross_streets from reverse_geocode('POINT(-73.918402 40.774441)', true) As
g;
---
2607 24th Ave, NY 11102 2301 - 2399 26th St|2300 - 2398 27th St
}}}
--
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1382#comment:9>
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