[PostGIS] #5690: Properly handle address numbers with dashes in them

[PostGIS]

#5690: Properly handle address numbers with dashes in them
----------------------------+-----------------------------
 Reporter:  robe            |      Owner:  robe
     Type:  defect          |     Status:  new
 Priority:  medium          |  Milestone:  PostGIS Fund Me
Component:  tiger geocoder  |    Version:  master
 Keywords:                  |
----------------------------+-----------------------------
 As noted on manning book site

 https://livebook.manning.com/book/postgis-in-action-third-
 edition/chapter-10/


 {{{
 Here in Hawaii we have a lot of neighborhoods with hyphenated address
 numbers, but these seem to cause issues with the TIGER geocoder. Any
 hyphenated addresses return a street number of 0 and a rating of 20 when
 geocoded. My naive guess is that this happens because the norm_addy type
 has integer address numbers and the hyphenated info is lost during
 conversion from string to norm_addy. Is this behavior possible to fix or
 mitigate? Or is the PostGIS geocoder function incapable of properly
 handling hyphenated addresses?

 An example address to test is ‘94-709 Kaaholo St, Waipahu, HI 96797’

 }}}


 Tiger geocoder does a poor job of geocoding addresses where adress number
 has dashes.

 I know I've done some work to improve this such as introducing a
 address_alphanumeric to preserve the original form of the address number,
 but forget where I left off with this.

 This isn't too high on my priority list though since most of the addresses
 I deal with don't have dashes in the address number, so probably won't do
 much for this in PostGIS 3.5
-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5690>
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.