[postgis-devel] [PostGIS] #1148: Geocoder has poor results with correct inputs

[PostGIS]

#1148: Geocoder has poor results with correct inputs
----------------------------+-----------------------------------------------
 Reporter:  darkblueb       |       Owner:  robe         
     Type:  defect          |      Status:  new          
 Priority:  medium          |   Milestone:  PostGIS 2.0.0
Component:  tiger geocoder  |     Version:  trunk        
 Keywords:                  |  
----------------------------+-----------------------------------------------
Changes (by darkblueb):

  * priority:  high => medium


Comment:

 I have written a new tool - alameda_tiger_peek.py; after the
 alameda_geocode.py pass ( which records detailed information on all stages
 of the geocoder ) this next tool operates on its output.

   Loop over the output of the geocoder and work on elements which : the
 input address starts with a number, the manhatten distance of the result
 POINT and the expected input POINT is greater than a threshold (0.01 now);
 from those, gather the UNIQUE street names from the input addresses (sum
 of the street name components 1-4 in norm_addy)

   Loop over the output of the geocoder again.. if the input address is on
 a street identified above, "peek" at the TIGER edges JOIN featurenames
 that are within a small buffer of the POINT of the expected geocode
 result, spit out those "peeks" to a csv, and remove that street name from
 the list of street names.

   The purpose of this is to help identify all cases where the geocoder
 performance is poor due to lack of information in TIGER, versus where the
 geocoder is actually failing in some way.. As noted previously, there
 could be a problem with the way the geocoder is loading data from TIGER
 that is not yet found..

   Bug Priority changed to medium, because some issues have been addressed.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1148#comment:17>
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.