topic Re: Incompatible Spatial References in ArcGIS Pro SDK Questions

Incompatible Spatial References

AlexZlotin1 — Thu, 29 Oct 2020 16:04:19 GMT

In the Pro SDK API, I am getting the "Incompatible spatial references" error when performing Geometry Engine operations like Distance or Difference on two geometries. The first geometry comes from a feature in an enterprise geodatabase feature class contained in a feature dataset. The second feature comes from a file geodatabase feature class created programmatically, with the spatial reference copied from the SDE feature class. When I look at spatial references of both geometry objects in debug mode, they have identical WKT strings. The workaround I found was to convert both geometries to JSON and re-create them from the JSON strings. The Geometry Engine operations no longer fail.

My understanding is that as long as spatial reference WKT strings for two geometries are identical, their spatial references are the same. Is there something I am missing? Could this possibly be a bug?

I am using Pro 2.6 SDK. Thanks.

Re: Incompatible Spatial References

DavidWilton — Thu, 15 Jun 2023 10:48:53 GMT

I'm seeing exactly the same thing in pro 3.1.0, two features with the same spatial reference. The layers have the same spatial reference, I check they have the same WKID in code just to be sure, still fails.

Feels like a bug in the code of the geometry engine " at ArcGIS.Core.Geometry.GeometryEngine.CheckForEqualSpatialReferences(SpatialReference sr1, SpatialReference sr2)\

To me its feels like the code might be they are checking that they are the same instance of spatial reference object, rather than that they are the same?

My workaround therefore was to use the SR of on of the layers to rebuild the geometry of the other. In my case I used the SR of the polygon layer to create a new point

var point = new MapPointBuilderEx(inPoint.X, inPoint.Y, polyLayer.GetDefinition().GetSpatialReference()).ToGeometry();

Re: Incompatible Spatial References

DaveWilcox — Wed, 19 Jul 2023 00:28:20 GMT

I'm seeing the same thing with 3.0. I hope they eventually fix it!

Re: Incompatible Spatial References

MK13 — Thu, 13 Jun 2024 02:50:52 GMT

I am having the same issue at 3.3. @UmaHarano @Wolf @CharlesMacleod

Re: Incompatible Spatial References

AquanuityDevelopment — Tue, 20 Aug 2024 23:18:06 GMT

I am having this issue now and then from our users. Just hope Pro dev team can look into this.

Re: Incompatible Spatial References

RadekMandovec — Wed, 22 Oct 2025 11:46:15 GMT

I still have the same issue at 3.5.4, fortunately I use the solution by @DaveWilcox

Re: Incompatible Spatial References

AnnetteLocke — Fri, 24 Oct 2025 18:50:58 GMT

Hi Radek. I was just made aware of this issue. Can you check the xy-tolerances of the spatial references to see if they are the same? Thanks.

Re: Incompatible Spatial References

RadekMandovec — Wed, 29 Oct 2025 06:00:53 GMT

Hi Annette, the XYTolerance values are different. While the first feature has XYTolerance = 0.0002, the second one has 0.0001.

Re: Incompatible Spatial References

AnnetteLocke — Wed, 29 Oct 2025 22:18:55 GMT

The tolerances being different is the reason that the exception is thrown. I will look into changing the behavior so that if only the tolerances are different, then the operation will succeed. I need to test for unexpected repercussions before I can commit to the change, though. I will reply to this thread with the outcome.

Re: Incompatible Spatial References

AnnetteLocke — Thu, 30 Oct 2025 21:08:48 GMT

Radek, I will change this in the next release.

Re: Incompatible Spatial References

RadekMandovec — Fri, 31 Oct 2025 05:05:58 GMT

Thanks a lot.

Re: Incompatible Spatial References

RadekMandovec — Fri, 31 Oct 2025 06:32:08 GMT

Just a small note. The feature with XYTolerance = 0.0002 is the one I obtained by clicking on the map.

 var mapPoint = MapView.Active.ClientToMap(e.ClientPoint);

I tried to find out whether the Map itself has any XYTolerance, but I couldn’t find anything anywhere, so I actually don’t know where the point gets its XYTolerance from. However, it definitely differs from the XYTolerance of all connected feature classes.

Re: Incompatible Spatial References

RadekMandovec — Mon, 27 Apr 2026 06:31:02 GMT

Hi Annette, I just want to inform you I use ArcGIS Pro 3.6.3 at the moment and the problem is still there. Did you already fix it or not?

Re: Incompatible Spatial References

AnnetteLocke — Mon, 27 Apr 2026 20:15:24 GMT

Hi Radek, the issue was fixed in ArcGIS Pro 3.7 which is expected to be available in May.