I have a composite locator with road centerlines. When I enter an intersection with "/" as the intersection connector in ArcGIS Pro, it returns me the correct intersections. When I share the locator to my enterprise portal and try the same thing, I get an error 400 saying it can't complete the operation or it provides an incorrect result.
I have seen that there was a bug in Desktop for this that ESRI said they would never address: https://support.esri.com/en/bugs/nimbus/QlVHLTAwMDA5NjE2OA== but I believe they fixed it in ArcGIS Pro, but not on ArcGIS Server (we are using 10.8.1).
Has anyone else experienced this issue? Any other connector I put into the locator will work in the service, just not "/". It's a big deal for us because all of our 911 dispatchers have been trained for years to use "/"
Thanks in advance!
I haven't actually run into this particular issue, but I am running into all sorts of other geocoding and data issues related to 10.7.1 and Pro 2.8.2 as well ad Server 10.8.1. Seems like those of us that decide to upgrade get punished by using the latest technology...
Umm.... Let's see....
With ArcGIS 2.8.2, I can't source data from server 10.7.1. I'm currently having a problem with arcpy creating locators with data sourced from AGOL. I've upgraded and de-graded ArcGIS Pro so many times I've lost count of the issues I've encountered.
Short response to your OP: when I worked in 9-1-1, I gave them one choice for an intersection locator; the ampersand (&). I know 9-1-1 dispatchers can be a tough crowd but my guess is you can get them to change before you see resolution on the ESRI side of things.
If you have created a locator with the Create Locator tool based on the Street Address role and have modified the intersection connectors property in the locator properties in Pro 2.7 or later to include the slash (/), you must publish to Enterprise 10.9 or later to make use of the modified intersection connectors, side offset, end offset settings. https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/tips-for-improving-geocoding-quality.ht...