AnsweredAssumed Answered

Issues with 10.3 Geocoding and confusing 100.0 scores

Question asked by dewright_ca on Jul 28, 2016
Latest reply on Jul 28, 2016 by bharold-esristaff

I have a address I am working with; 323 N Fifth Ave, Sequim WA, 98382. Now I use both commercial and internally developed data that goes into a composite geocoder set in a hierarchy based on the quality of said sources; pretty standard stuff.

 

So how can I get a result returned like this:

 

Score: 100.0

Address: 323 NORTH ST, SEQUIM, WA, 98382

Loc_name: HERE_Points

Score: 100

Match_addr: 323 NORTH ST, SEQUIM, WA, 98382

House: 323

Side: L

PreDir:

PreType:

StreetName: NORTH

SufType: ST

SufDir:

City: SEQUIM

State: WA

ZIP: 98382

 

Where the 'NORTH' as the street Name and 'ST' as SufType as swapped and the score of 100.0 is assigned. While further down the composite process I get this return as well:

 

Score: 100.0

Address: 323 N 5TH AVE, SEQUIM, WA, 98382

Loc_name: HERE_Streets

Score: 100

Match_addr: 323 N 5TH AVE, SEQUIM, WA, 98382

House:

Side: L

PreDir: N

PreType:

StreetName: 5TH

SufType: AVE

SufDir:

City: SEQUIM

State: WA

ZIP: 98382

 

How can I get a 100.0 score for both of these results in my composite; where obviously the first one swapped the street elements pretty extremely.

 

Maybe Bruce Harold , Agatha Wong or Brad Niemand can give me some insight; this is confusing us.

Outcomes