[postgis-devel] [PostGIS] #886: Fix normalizing of multi street number range addresses and fractional street numbers

[PostGIS]

#886: Fix normalizing of multi street number range addresses and fractional
street numbers
----------------------------+-----------------------------------------------
 Reporter:  robe            |       Owner:  robe          
     Type:  defect          |      Status:  new           
 Priority:  medium          |   Milestone:  PostGIS Future
Component:  tiger geocoder  |     Version:  trunk         
 Keywords:                  |  
----------------------------+-----------------------------------------------

Comment(by robe):

 A number of the errors noted in #1077 of Brian's list are street number
 normalization which is not quite yet feasible to fix without augmenting
 norm_addy structure.

 My inclination is to just add an extra field called address_extra so that
 the current address field (which is badly named since it's really street
 number), would contain the first numeric segment of a street and
 address_extra would be a text field that would contain the rest of the
 street number.  This would solve street ranges, alpha numeric street
 issue, and most fractional street cases.  The pprint_addy would then be
 revised to take this new address_extra into consideration when formulating
 the display.

 So for example:
 19126-20 =>  address: 19126  address_extra: -20
 4D => address: 4, address_extra: D
 123 1/2 => adress: 123, address_extra: 1/2

 For geocoding we'll just ignore the address_extra part since in most
 cases, they don't add any benefit to geocoding.

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