Opened 23 months ago
Closed 19 months ago
#5331 closed defect (fixed)
reverse geocoder sometimes doesn't return a street and address when it should
Reported by: | robe | Owned by: | robe |
---|---|---|---|
Priority: | medium | Milestone: | PostGIS 3.1.9 |
Component: | tiger geocoder | Version: | 3.3.x |
Keywords: | Cc: |
Description
There are a lot cases where reverse geocoder does not return an address, because tiger seems to have quite a few unnamed streets and many with no ranges, such as highways.
Planned fix is to prefer addressable ranges even if it isn't the closest as long as it's within 70 meters.
In my testing the new approach for this query:
SELECT pprint_addy(addy[1]), ST_ASText(intpt[1]) , (intpt[1]::geography <-> ST_SetSRID(var_pt,4269))::numeric(10,2) AS dist_m FROM ST_Point( -122.077435,37.414167) AS var_pt, tiger.reverse_geocode_testing( var_pt );
Will give
pprint_addy | st_astext | dist_m ---------------------------------------------+---------------------------------------------+-------- 1382 la Avenida St, Mountain View, CA 94043 | POINT(-122.0775952717109 37.41362206134327) | 62.23 (1 row)
vs. the old apprach
pprint_addy | st_astext | dist_m -------------------------------------------+----------------------------------------------+-------- N Shoreline Blvd, Mountain View, CA 94043 | POINT(-122.07799538107314 37.41415350501974) | 49.51 (1 row)
I'm going to test with several more. I had already deleted some unnamed streets from my set to avoid blank addresses being returned, so in many cases the situation is worse than this.
Note:
See TracTickets
for help on using tickets.
In 58b3f23/git: