[postgis-tickets] [PostGIS] #5408: regression failure on tiger geocoder pagc_normalize_address

[PostGIS]

#5408: regression failure on tiger geocoder pagc_normalize_address
---------------------------------+---------------------------
 Reporter:  robe                 |      Owner:  robe
     Type:  defect               |     Status:  new
 Priority:  medium               |  Milestone:  PostGIS 3.3.4
Component:  pagc_address_parser  |    Version:  master
 Keywords:                       |
---------------------------------+---------------------------
 Checking to see what triggered this.

 In fixing the postgis_tiger_geocoder regression runnings, I discovered
 this test is failing


 {{{
 SELECT '#1051d' As ticket, * FROM pagc_normalize_address('212 3rd Ave N
 Minneapolis, MN 55401');
 }}}


 It returns:


 {{{
  ticket | address | predirabbrev | streetname | streettypeabbrev |
 postdirabbrev | internal |  location   | stateabbrev |   zip   | parsed |
 zip4 | address_alphanumeric
 --------+---------+--------------+------------+------------------+---------------+----------+-------------+-------------+---------+--------+------+----------------------
  #1051d |     212 |              | 3RD        | AVE              |
 |          | MINNEAPOLIS | MN          | N 55401 | t      |      | 212
 (1 row)

 }}}

 So putting the suffix dir in the wrong location.  It must have worked at
 some point in time since I have it as a regression test.

 Note the regular tiger normalizer function works fine.


 {{{
 SELECT '#1051d' As ticket, * FROM normalize_address('212 3rd Ave N
 Minneapolis, MN 55401');
 }}}



 {{{
 ticket | address | predirabbrev | streetname | streettypeabbrev |
 postdirabbrev | internal |  location   | stateabbrev |  zip  | parsed |
 zip4 | address_alphanumeric
 --------+---------+--------------+------------+------------------+---------------+----------+-------------+-------------+-------+--------+------+----------------------
  #1051d |     212 |              | 3rd        | Ave              | N
 |          | Minneapolis | MN          | 55401 | t      |      | 212
 (1 row)
 }}}


 and if I use the address_standardizer_data_us dataset I also get a screwed
 up answer.


 {{{
 SELECT *
 FROM standardize_address('us_lex',  'us_gaz', 'us_rules','212 3rd Ave N
 Minneapolis, MN 55401')
 }}}
 So whatever it is is wrong in this dataset too:


 {{{
 building | house_num | predir | qual | pretype | name | suftype | sufdir |
 ruralroute | extra |    city     |   state   | country | postcode | box |
 unit
 ----------+-----------+--------+------+---------+------+---------+--------+------------+-------+-------------+-----------+---------+----------+-----+------
           | 212       |        |      |         | 3    | AVENUE  |
 |            |       | MINNEAPOLIS | MINNESOTA | USA     | N 55401  |
 |
 (1 row)
 }}}


 Testing my PostGIS 3.3.2 and that also gives wrong answer
-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5408>
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.