[postgis-devel] [PostGIS] #1622: Geocoder gets different result when using limit parameter

[PostGIS]

#1622: Geocoder gets different result when using limit parameter
----------------------------+-----------------------------------------------
 Reporter:  mikepease       |       Owner:  robe         
     Type:  defect          |      Status:  new          
 Priority:  medium          |   Milestone:  PostGIS 2.0.0
Component:  tiger geocoder  |     Version:  1.5.X        
 Keywords:                  |  
----------------------------+-----------------------------------------------
 Here's another way to trick the normalizer/geocoder; sampled from an
 actual customer address list we have.

 The street type and the street direction are listed in a non-standard
 sequence in this list of several thousand addresses;

 501  7TH NW ST, ROCHESTER, MN 55901[[BR]]
 instead of[[BR]]
 501  7TH ST NW, ROCHESTER, MN 55901[[BR]]


 --finds the wrong address[[BR]]
 select (addy).*, *
 from geocode('501  7TH NW ST, ROCHESTER, MN 55901', 1)

 --Chooses
 "Tomah";"Pl";"NW";"";"Rochester";"MN";"55901" [[BR]]
 with a rating of 73 instead of the correct address with a rating of 4.

 --When you remove the limit parameter geocode(addy,1), it gets the right
 address with a better rating of 4[[BR]]
 select (addy).*, *
 from geocode('501  7TH NW ST, ROCHESTER, MN 55901')


 --This gets the correct answer when the street type and direction are
 listed in the standard sequence;[[BR]]

 select (addy).*, *
 from geocode('501  7TH ST NW, ROCHESTER, MN 55901', 1)

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1622>
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.