Opened 7 years ago
Last modified 6 years ago
#3791 new defect
PostGIS tiger geocoder should use cousub in addition to place for non-specific — at Version 1
Reported by: | robe | Owned by: | robe |
---|---|---|---|
Priority: | medium | Milestone: | PostGIS Fund Me |
Component: | tiger geocoder | Version: | 2.3.x |
Keywords: | Cc: |
Description (last modified by )
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
Note:
See TracTickets
for help on using tickets.