US Address Standardization

[reachsam11]

What should be the override pattern for the below addresses
Is there a way i can overide to force 'ATTN: POSTMASTER' to Additional Address column, no matter what the input pattern is. There are about 100+ diff input/unhandled patterns starting with 'ATTN: POSTMASTER'

Address (Input Pattern)
-------------------------------------------
ATTN: POSTMASTER RTE 222 A MAIN ST ( E+R^I+T )
ATTN: POSTMASTER RT 111 MAIN ST ( E+R^+T )
ATTN: POSTMASTER MILE 666 RCHRDSN HWY ( E++^+T )
ATTN: L GONZALEZ 1234 W 55RD AVE PL ( EI+^D>TT )

[ray.wurlod]

I take it you don't want to create your own rule set and modify the Pattern Action Language.

You could use an input pattern override with a pattern that begins with the literal. I am not sure how you need to handle GONZALEZ in your example.

[stuartjvnorton]

What should be the override pattern for the below addresses
Is there a way i can overide to force 'ATTN: POSTMASTER' to Additional Address column, no matter what the input pattern is. There are about 100+ diff input/unhandled patterns starting with 'ATTN: POSTMASTER'

Address (Input Pattern)
-------------------------------------------
ATTN: POSTMASTER RTE 222 A MAIN ST ( E+R^I+T )
ATTN: POSTMASTER RT 111 MAIN ST ( E+R^+T )
ATTN: POSTMASTER MILE 666 RCHRDSN HWY ( E++^+T )
ATTN: L GONZALEZ 1234 W 55RD AVE PL ( EI+^D>TT )

You could do something like this in PAL:

E | ** | R
COPY_S [2] tmp
PREFIX " " tmp
PREFIX [1] tmp
COPY tmp {AdditionalAddressInfo}
RETYPE [1] 0
RETYPE [2] 0

E | ** | ^
COPY_S [2] tmp
PREFIX " " tmp
PREFIX [1] tmp
COPY tmp {AdditionalAddressInfo}
RETYPE [1] 0
RETYPE [2] 0

You might need more like them to stop at unit types, level types, etc.
In the examples above, should "MILE" be an R?