According to this Esri documentation about the Street Address Role for geocoding using centerlines data source:
“...Searching for street names is also an option with a locator created with the Street Address role, and the address field in a table of addresses must contain the street name in addition to the street's prefix direction, prefix type, street type, or suffix direction, if any. “
We do NOT want to enable the ability to just validate a street name by itself on our locator. We want to use centerlines for street intersections, but can have users get hits for just a single street name by itself. Such inexact locations (missing any building number) find their way into our 311 system, which is very bad.
Previously (version 10.6.1), this was not an observable behavior; there would not be a match is entering just a single street name by itself.
Solved! Go to Solution.
When you build a locator using the StreetAddress role with the Create Locator tool, you can disable the StreetName category in the Locator Properties or only check the StreetAddress and Street Intersection categories in the Categories section of the Locator Properties. This setting is maintained if the locator is published as a service. If you do not change the supported categories, when you batch geocode a table you can specify the categories you want matches for in Category parameter of the geocoding tools.
When you build a locator using the StreetAddress role with the Create Locator tool, you can disable the StreetName category in the Locator Properties or only check the StreetAddress and Street Intersection categories in the Categories section of the Locator Properties. This setting is maintained if the locator is published as a service. If you do not change the supported categories, when you batch geocode a table you can specify the categories you want matches for in Category parameter of the geocoding tools.
Duh, after reviewing time and again it was right there in front of my face the whole time!