[postgis-devel] [PostGIS] #1087: Ratings are off when zip is wrong or not present

[PostGIS]

#1087: Ratings are off when zip is wrong or not present
----------------------------+-----------------------------------------------
 Reporter:  robe            |       Owner:  robe         
     Type:  defect          |      Status:  new          
 Priority:  high            |   Milestone:  PostGIS 2.0.0
Component:  tiger geocoder  |     Version:  1.5.X        
 Keywords:                  |  
----------------------------+-----------------------------------------------
 Examples:


 {{{
 SELECT pprint_addy(addy) as geo_loc, rating
    FROM geocode('75 State Street, Boston, MA 02110', 3);

 or

 SELECT pprint_addy(addy) as geo_loc, rating
    FROM geocode('75 State Street, Boston, MA', 3);

 Has wrong zip and rates Milton the same so result of milton or boston is
 arbitrary if you choose to return just 1 result

             geo_loc            | rating
 -------------------------------+--------
  75 State St, Boston, MA 02109 |      2
  75 State St, Milton, MA 02186 |      2
  75 State St, Ludlow, MA 01056 |      5

 -- With exact zip rating okay --
 SELECT pprint_addy(addy) as geo_loc, rating
    FROM geocode('75 State Street, Boston, MA 02109', 3);

             geo_loc            | rating
 ------------------------------+--------
 75 State St, Boston, MA 02109 |      0

 In short rating should be penalizing Milton for not having exact match
 location and having a levenshtein distance zip further from target zip.

 }}}

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