Geocoding Service with suggestions enabled returns invalid matches

[ChrisCarter]

I have a 10.3 geocoding service with suggestions enabled which is based on address points.  The endpoint can be accessed here:  http://gis.anaheim.net/arcgis/rest/services/AddressPointGeocoder/GeocodeServer

Everything works correctly except for the suggestions, which seem to be returning invalid matches.  For example, if you test the Suggest functionality here:  http://gis.anaheim.net/arcgis/rest/services/AddressPointGeocoder/GeocodeServer/suggest and type in 1240 E Diana, you get 3 suggestions:  http://gis.anaheim.net/arcgis/rest/services/AddressPointGeocoder/GeocodeServer/suggest?text=1240+e+d...

but only one is valid (1240 E Diana Ave). 

Where did the other two come from?  Maybe I am misunderstanding how suggestions work, but I expected the geocoding service to query the data on the fly and only present valid matches.

-Chris

[ShanaBritt]

Michael:

The Create Locator tool will only be available in ArcGIS Pro and the locators created with the tool can be published to ArcGIS Server 10.6.1 or later, where they can then be used in ArcMap 10.7 as services. The locators cannot be used locally in ArcMap. You can still use the Create Address Locator tool in ArcGIS Pro to create locators that can be used locally in ArcMap, but when published as a service the suggestion problem will still be present.