I've been working on creating locators to improve our geocoding results. Most recently I created a Street address with Alternate Street Name role(s). It seems to work just fine for me, but I'm wondering about how the results are returned.
In an earlier attempt to create the same type of locator(see related post) I learned that the attributes used for geocoding in the primary table must be matched by the same attributes in the alternate names table.
Given the above mentioned requirement, my alternate street names table consists of 5 attributes:
Prefix Direction
AltName
Suffix Type
AltName suffix direction
JoinID
All of our alternate names are in the form of W 1200 S (Utah addressing; best system ever for geocoding!) However, when I look at the results I see for example:
Match_Addr 1895 S ST
Single Line Input 1895 S 1240 E
So that tells me that what ever the primary name of S 1240 E is has the Suffix Type of ST. No real mystery there.
But... In my alternate names table, can I suppress the value of Suffix Type to either blank or <null> to eliminate the confusion that will undoubtedly come with the Match_Addr?
Additionally, given the new style locators do not have an associated xml file, how does one programmatically change the various properties as shown in the Output Fields, Geocoding Options, etc? All our locators get re-created on a weekly basis using a python script as a scheduled task.
Shana Britt
Eric Anderson
Michael Volz (I figured this might be of interest to you Michael...)
That should just about do it....