This has been an issue since the overhaul of locators at version 10. I've never been able to get the locators in any version 10.x.x to give me candidate alternatives similar to the ones in the US One Address with Zone locator from 9.3.1 (attached).
Here are examples of what I am talking about...
1st Scenario - How unit/suite/apt/etc is handled - The unit number doesn't exist in our address points layer unit field (ex. 912 E WASHINGTON ST #1) that the locator is built on, but the main address does (ex. 912 E WASHINGTON ST). Why doesn't the 10.5.1 locator (US Address - Single House Subaddress) return the main address as a candidate with a lower score than 100? I've set the spelling sensitivity and candidate score mins extremely low (See 1stScenario.png). The locator I made in 9.3.1 US One Address with Zone returns a candidate. Is there something I can change in the settings of the locator to get it to do what I'm looking for?
2nd Scenario - If an address doesn't exist in the locator. Alternatives with a low candidate score are not provided as an option to get me "close". When manually rematching addresses, I want to zoom to low scoring candidates that aren't a match so that I can easily see if the address does exist in real life, but is missing from our address points data which the locator is based on. The 9.3.1 locator does exactly this if I set the "Minimum Candidate Score" below 40 (See 2ndScenario.png). I have tried several 10.x locators, and haven't been able to recreate the experience. Am I missing something? Is there a way to recreate this specific 9.3.1 locator behavior? I want to published it to our ArcGIS Portal, but can't because Portal will only accept 10.1 and later locators.
Thanks,
Becky
