Opened 9 years ago

Closed 9 years ago

#3161 closed defect (fixed)

geocode_intersection returns a null rating for a specific intersection

Reported by: alexreinhart Owned by: robe
Priority: medium Milestone: PostGIS 2.1.9
Component: tiger geocoder Version: 2.1.x
Keywords: Cc:

Description

I'm using the TIGER data for Pennsylvania (loaded with Loader_Generate_Script) to geocode a large quantity of addresses. One particular address returns a NULL rating, despite returning an address:

crime=# SELECT rating, pprint_addy(addy), st_astext(geomout) FROM geocode_intersection('Main St', 'Geneva St', 'PA', 'Pittsburgh', '15201');
 rating | pprint_addy |         st_astext          
--------+-------------+----------------------------
        | Main St, PA | POINT(-80.22262 41.571597)
(1 row)

crime=# SELECT rating IS NULL, pprint_addy(addy), st_astext(geomout) FROM geocode_intersection('Main St', 'Geneva St', 'PA', 'Pittsburgh', '15201');
 ?column? | pprint_addy |         st_astext          
----------+-------------+----------------------------
 t        | Main St, PA | POINT(-80.22262 41.571597)
(1 row)

The point returned is not in Pittsburgh, but I don't know if that's TIGER's fault or PostGIS's.

My version is

 PostgreSQL 9.3.8 on x86_64-unknown-linux-gnu, compiled by gcc (Ubuntu 4.8.4-2ubuntu1~14.04) 4.8.4, 64-bit POSTGIS="2.1.2 r12389" GEOS="3.4.2-CAPI-1.8.2 r3921" PROJ="Rel. 4.8.0, 6 March 2012" GDAL="GDAL 1.10.1, released 2013/08/26" LIBXML="2.9.1" LIBJSON="UNKNOWN" RASTER

Thanks.

Change History (3)

comment:1 by robe, 9 years ago

Milestone: PostGIS 2.1.8PostGIS 2.2.0

will look at this for 2.2. Don't have PA data loaded at moment.

comment:2 by robe, 9 years ago

Okay i still need to investigate where the null is coming from, but the 2015 seems to return more records (or again the changes I made to geocoder_intersection to increase limit affected this:

SELECT rating IS NULL, pprint_addy(addy), st_astext(geomout) FROM geocode_intersection('Main St', 'Geneva St', 'PA', 'Pittsburgh', '15201');

Gives

 ?column? |            pprint_addy            |          st_astext
----------+-----------------------------------+-----------------------------
 f        | 345 Main St, Pittsburgh, PA 15201 | POINT(-79.956508 40.466613)
 f        | 346 Main St, Pittsburgh, PA 15201 | POINT(-79.956508 40.466613)
 f        | 347 Main St, Pittsburgh, PA 15201 | POINT(-79.956508 40.466613)
 f        | 348 Main St, Pittsburgh, PA 15201 | POINT(-79.956508 40.466613)
 t        | Main St, PA                       | POINT(-80.22262 41.571597)
(5 rows)

comment:3 by robe, 9 years ago

Milestone: PostGIS 2.2.0PostGIS 2.1.9
Resolution: fixed
Status: newclosed

fixed at r13958 for PostGIS 2.2 and backported to 2.1 (for 2.1.9) at r13959

Note: See TracTickets for help on using tickets.