Opened 11 years ago

Closed 11 years ago

#2380 closed defect (fixed)

Fix pagc lookup tables resolves BAY STATE incorrectly

Reported by: robe Owned by: robe
Priority: medium Milestone: PostGIS 2.1.0
Component: pagc_address_parser Version: 2.1.x
Keywords: Cc:

Description

I managed to have over replaced in my building of pagc lex, rules, gaz. This I confirmed is a screwup in my lookup tables rather than anything wrong with pagc.

Query:

SELECT (g.sa).*
FROM (SELECT standardize_address('lex'
       , 'gaz'
       , 'rules', '140 BAY STATE RD, BOSTON, MA 02215') As sa) As g;

-- Correctly Outputs --
 building | house_num | predir | qual | pretype |   name    | suftype | sufdir |
 ruralroute | extra |  city  |     state     | country | postcode | box | unit
----------+-----------+--------+------+---------+-----------+---------+--------+
------------+-------+--------+---------------+---------+----------+-----+------
          | 140       |        |      |         | BAY STATE | ROAD    |        |
            |       | BOSTON | MASSACHUSETTS | USA     | 02215    |     |

but my revised tiger version:

SELECT (g.sa).*
FROM (SELECT standardize_address('tiger.pagc_lex'
       , 'tiger.pagc_gaz'
       , 'tiger.pagc_rules', '140 BAY STATE RD, BOSTON, MA 02215') As sa) As g;

Just gives blank for everything. I assume I over replaced somewhere or added some junk record I shouldn't have.

Change History (3)

comment:1 by robe, 11 years ago

adding BAY STATE entry as token 5 fixed issue. Probably because I need things abbreviated, bout couldn't find a faulty record. I'll also need to upper case everything to keep formatting consistent. Will close after I test some more.

comment:2 by robe, 11 years ago

fixed for trunk 2.2 at r11686. Will backport to 2.2 once confirm looks right.

comment:3 by robe, 11 years ago

Resolution: fixed
Status: newclosed

fixed for 2.1 at r11703

Note: See TracTickets for help on using tickets.