[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:  high            |   Milestone:  PostGIS 2.0.0
Component:  tiger geocoder  |     Version:  trunk        
 Keywords:                  |  
----------------------------+-----------------------------------------------

Comment(by darkblueb):

 Notes on Geocoder 7691:
 ===============================================

 Input data is 400,000 correct residential addresses in Alameda County
   (or subsets thereof)

 Two runs
   no limit on results ("L_N"),
   Result limit = 1    ("L_1")

 Comparison Geocoder
   Brand-Y commercial geocoder  ("Brand_Y")



 Observations:
 ---------------------------------------------------------------

 * Less than 0.25 % of addresses had imperfect readings via
 normalize_address()
   (levenshtein distance between input address and pretty print normalized
 address)

 * L_1 has roughly 3% of geocoded points not near the actual address
   (Brand_Y < 26 thousandths of one percent for the same set)

 * L_N has > 10% of points not near the actual address

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