[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 robe):

 Bryan,

 Just to add to what Bitner is saying.  It's nice to have all these
 examples, but would be even nicer if you isolated 5-10 representative
 population cases I can stick in my regress script.  I wouldn't need as
 much time with that as trying to digest a 6 MB file and loading it.  That
 is useful for stress testing, but not terribly useful during development
 phase for me.

 So my ideal bug reports are the one you submitted about the normalize
 issues (with a set of examples I could easily test #1077) and the tickets
 that Mike Pease has been submitting like this one #1145 - a set of few
 concrete examples demonstrating the point I can chew on and dump into
 regress.

 Less is more :)

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