Street number is geting identified as house number suffix

vimalvik · Post by **vimalvik** » Tue Jul 14, 2009 2:40 am

Street number is getting identified as house number suffix in US_ADDR ruleset.

Source Input: "50 THREE LAKES DR"

House Number: 50
House Number Suffix: 3
Street Name: LAKES
Street Suffix Type: DR

"3" is geting identified as House Number Suffix where idealy it should be either Street Name or, Street Name prefix.

Is there any other solution other than pattern overriding like editing classifications file.

JRodriguez · Post by **JRodriguez** » Tue Jul 14, 2009 7:35 am

Yes, you can edit the classification table for this entry and assign any other class instead of the default "C" (Cardinal Number)...but that will bring other issues when "Three" really mean "3"

I would stay put with the Input pattern overrides

vimalvik · Post by **vimalvik** » Wed Jul 15, 2009 3:39 pm

Input Records:

CASE 1 : 408-10 CARPENTER AVE NEWBURGH NY 12550
CASE 2 : 2-1 CANTERBURY CT MIDDLETOWN CT 06457

CASE 1 - Actual output from USPS
---------------------------------

408 CARPENTER AVE APT 10
NEWBURGH NY 12550-3352

CASE 2 - Actual output from USPS
---------------------------------

2-1 CANTERBURY CT
MIDDLETOWN CT 06457-4924

How to handle pattern overrides in these cases for the same(syntax) address values,
wherein one case it resolves to Streetnumber/Streetnumber suffix
and in anohter it resolves to Streetnumber and House Number.

ray.wurlod · Post by **ray.wurlod** » Wed Jul 15, 2009 4:24 pm

If they're few enough you could use input text override.

JRodriguez · Post by **JRodriguez** » Thu Jul 16, 2009 11:11 am

By default the tool will show results as expected by case No. 2 records. Because both cases contradict each other and to avoid changing the default behavior of the tool the approach should lean toward addressing the exception, case No.1, only

I would treat those records after the standardization process.The User Override GUI don't allow to conditionally take actions on a token, based on the value of another one. Anyway in a transfomer is a lot easier and you have more control. Pick those records where City/State is NEWBURGH/NY (Could be a list, so would like to investigate other cities where the addresses follow same standard), take the HouseNumberSuffix where not null and move it to HouseUnitValue

Input Text override is a better approach, but in this case the USADDR Rule Set will consider "408-10" and "2-1" as one single token, and the tool as I mentioned before in the GUI , don't allow substring or range actions on a single token

vimalvik · Post by **vimalvik** » Thu Jul 16, 2009 5:28 pm

Julio / Ray , Appreciate your quick responses. Thanks.

vimalvik · Post by **vimalvik** » Thu Jul 16, 2009 5:29 pm

Julio / Ray , Appreciate your quick responses. Thanks.