[postgis-tickets] [PostGIS] #3161: geocode_intersection returns a null rating for a specific intersection

[PostGIS]

#3161: geocode_intersection returns a null rating for a specific intersection
----------------------------+---------------------------
 Reporter:  alexreinhart    |      Owner:  robe
     Type:  defect          |     Status:  new
 Priority:  medium          |  Milestone:  PostGIS 2.1.8
Component:  tiger geocoder  |    Version:  2.1.x
 Keywords:                  |
----------------------------+---------------------------
 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.

--
Ticket URL: <http://trac.osgeo.org/postgis/ticket/3161>
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.