USADDR standardizing CR as COUNT (not CIRCLE, not COUNTY RD)

Infosphere's Quality Product

Moderators: chulett, rschirm

Post Reply
sportclimber
Charter Member
Charter Member
Posts: 15
Joined: Mon Jan 31, 2005 1:53 pm
Location: CO, USA

USADDR standardizing CR as COUNT (not CIRCLE, not COUNTY RD)

Post by sportclimber »

Hi:

I've got addresses such as 1525 CR 10 and 1525 KELTY CR.

Any suggestion how to make QualityStage see the first as 1525 COUNTY ROAD 10 and the second as 1525 KELTY CIR?

Out of the box functionality does the first correctly, but causes the second to become 1525 KELTY COUNT (COUNTY ROAD is truncated to 5 char because it's in the Street Suffix field which is only 5 char wide).

Thanks!
JamasE
Participant
Posts: 32
Joined: Sun Aug 31, 2003 5:52 pm

Re: USADDR standardizing CR as COUNT (not CIRCLE, not COUNTY

Post by JamasE »

sportclimber wrote:Any suggestion how to make QualityStage see the first as 1525 COUNTY ROAD 10 and the second as 1525 KELTY CIR?
Firstly, is this a hard and fast rule you want to programme? Is it always the case that <name> CR = CIR? (Or basically, is there always a pattern that will be CR = CIR?)

If so, add that pattern to the beginning of the rules so that, for example:

Code: Select all

^ | ? | T = "CR"
RETYPE [3] +
Will convert CR from street suffix to general alpha string. (I think. It's been a while since I pattern coded and haven't got access to try anything.)
Or just process it how you want, e.g.

Code: Select all

^ | ? | T = "CR"
COPY [1] {HN}
COPY [2] temp
CONCAT " CIR" temp
COPY temp {SN}
RETYPE [1] 0
RETYPE [2] 0
RETYPE [3] 0
(Not sure if the space will work. I remember having trouble trying to get spaces working elsewhen.)

Cheers,
Jamas
sportclimber
Charter Member
Charter Member
Posts: 15
Joined: Mon Jan 31, 2005 1:53 pm
Location: CO, USA

Post by sportclimber »

Thanks for the input. I think I'm going to have to do something like this, hopefully not too much more complex.
Post Reply