[postgis-tickets] [PostGIS] #3791: PostGIS tiger geocoder should use cousub in addition to place for non-specific
PostGIS
trac at osgeo.org
Mon Jul 17 23:54:19 PDT 2017
#3791: PostGIS tiger geocoder should use cousub in addition to place for non-
specific
-----------------------------+---------------------------
Reporter: robe | Owner: robe
Type: defect | Status: new
Priority: medium | Milestone: PostGIS 2.4.0
Component: tiger geocoder | Version: 2.3.x
Resolution: | Keywords:
-----------------------------+---------------------------
Description changed by robe:
Old description:
> Seems if you do:
>
> {{{
> SELECT pprint_addy(addy), ST_AsText(geomout), rating FROM
> geocode('Brooklyn, NY',1);
> }}}
>
> you get no answer back although Brooklyn is listed in
> tiger_data.ny_cousub.
>
> However if you use a value that is in ny_place such as
>
> {{{
> SELECT pprint_addy(addy), ST_AsText(geomout), rating FROM
> geocode('Bronxvilled, NY',1);
> }}}
>
> it works.
>
> tiger should try to use tiger.cousub as well as tiger.place.
>
> I think cousub might currently only be used for some joins.
New description:
Seems if you do:
{{{
SELECT pprint_addy(addy), ST_AsText(geomout), rating FROM
geocode('Brooklyn, NY',1);
}}}
you get no answer back although Brooklyn is listed in
tiger_data.ny_cousub.
However if you use a value that is in ny_place such as
{{{
SELECT pprint_addy(addy), ST_AsText(geomout), rating FROM
geocode('Bronxvilled, NY',1);
}}}
it works.
tiger should try to use tiger.cousub as well as tiger.place.
I think cousub might currently only be used for some joins.
this ticket was instigated by this stack exchange post:
https://gis.stackexchange.com/questions/247928/postgis-not-geocoding-
counties
--
--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/3791#comment:1>
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-tickets
mailing list