[postgis-users] Tiger geocoder - error instead of null when unlocatable

Regina Obe lr at pcorp.us
Sun Feb 7 07:44:46 PST 2016



Can you ticket this one in our ticket tracker - http://postgis.net/support/


Unfortunately I don't have Idaho data loaded in my instance and can't
trigger the problem with the data I have just by replacing the state.


It does sound like a bug though if other addresses work.  I'll try to take a
look at it next week while I'm looking at other tiger issues.











From: postgis-users [mailto:postgis-users-bounces at lists.osgeo.org] On Behalf
Of Matthew Syphus
Sent: Sunday, February 07, 2016 12:43 AM
To: PostGIS Users Discussion <postgis-users at lists.osgeo.org>
Subject: Re: [postgis-users] Tiger geocoder - error instead of null when


Apologies for not including version details originally.



"POSTGIS="2.2.1 r14555" GEOS="3.5.0-CAPI-1.9.0 r4084" PROJ="Rel. 4.8.0, 6
March 2012" GDAL="GDAL 1.10.1, released 2013/08/26" LIBXML="2.7.6"


PostgreSQL 9.5.0

CentOS 6.5




From: postgis-users [mailto:postgis-users-bounces at lists.osgeo.org] On Behalf
Of Matthew Syphus
Sent: Saturday, February 06, 2016 9:06 PM
To: postgis-users at lists.osgeo.org <mailto:postgis-users at lists.osgeo.org> 
Subject: [postgis-users] Tiger geocoder - error instead of null when


After following the instructions (several times) and apparently successfully
installing tiger geocoder and the tiger data for Idaho, I keep getting an
error when the geocoder can't find an address.


With a locatable address it works just fine.

SELECT * FROM geocode('3300 state st, boise, id 83703')


When an address is not locatable, I assume it should return null (and move
on to the next in the batch).

Instead, it returns an error:


SELECT * FROM geocode('3300 state st, neverland, id 9876543210')




ERROR:  column co.statefp does not exist

LINE 2: ...cefp = p.placefp)  LEFT JOIN county co ON ('16' = co.statefp...


(sub.predirabrv,sub.fename,COALESCE(sub.suftypabrv, sub.pretypabrv)
sub.predirabrv   as fedirp,    sub.fename,    COALESCE(sub.suftypabrv,
sub.pretypabrv)   as fetype,    sub.sufdirabrv   as fedirs,
coalesce(p.name,zip.city,cs.name,co.name)::varchar as place,    s.stusps as
state,    sub.zip as zip,    interpolate_from_address($1, sub.fromhn,    .



It doesn't seem to matter which address element causes the problem, the
error is the same and it kills the query.  Is there some error handling that
is getting missed? The examples I've seen look like it just returns null.
Thank you for any help.








This email has been scanned for spam and viruses by Proofpoint Essentials
cloud email security - click here
em&mail_id=Z07c%2BrvT0fHg&rid=6780640&report=1>  to report this email as


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20160207/9128de88/attachment.html>

More information about the postgis-users mailing list