Geocoder Search Zooms to Incorrect Location (but returns correct result)

jay.guarneri_pww

I've been experiencing some issues with a custom, composite geocode service that I maintain. It contains geocoders that point to our internal data (in NH State Plane coords), as well as the World Geocode Service. What happens is when I use the search bar in Portal or Locate tool in Pro, it will often zoom to a very incorrect location in a manner consistent with a projection issue. However, the actual geocode result is in the correct location. Everything we geocode is in NH, but it very consistently zooms to S Central NY. In the screenshot below, the black dot is the geocode result, the red dot is the approximate location of the zoom extent. It seems to happen mostly with the results that are resolved from the World Geocode Service rather than from the geocoders built off of our internal data.

I do not see this issue in Field Maps. I also do not see the issue in Pro if I use the geocoder file that the service is published from. Are there any settings I'm missing on the Geocode Service or my maps that would resolve this issue?

I'm publishing to Enterprise 10.9.1 from Pro 3.1.1.

 

 

MelissaNorthey

We found that in our old SOP to create our address locator we used/linked the X and Y fields.  When we didn't put them in, as they are not required, it worked!  Our thought was that it was confusing it with lat/longs but our data is in StatePlane.  Honestly didn't dig much further into the reasoning once we found something that worked, we ran with it.