nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

GeometryEngine value does not fall within the expected range

MarkCederholm

UPDATE: I was able to create a project that duplicates the problem [attached]. GeometryEngine at 100.2 has a problem which 10.2.7 doesn't have. I have two different geometries with the same spatial reference, yet hydrated from different sources (one from the map, one from a feature layer). If I try to to perform an operation such as Contains or Disjoint, I get the error "Value does not fall within the expected range". If I project one geometry to the other's SR then the operation works fine. The SR is defined by a WkText, and the WkText of both SRs is identical. Has anyone else seen this?

GeomTest.zip

Find more posts tagged with

Accepted answers

JenniferNery

Thank you for sharing your data and code. I'm able to reproduce the issue. SpatialReference.Equals should have been true regardless of z-value and GeometryEngine.RemoveZAndM should have been enough to clear feature geometry of z to allow GeometryEngine.Contains to work. However, SpatialReference.Equals still fail, although the wkt string matched. I have logged an issue for this.

Meanwhile, you can use the following workaround before calling GeometryEngine.Contains or SpatialReference.Equals.

geomFeat <SPAN class="operator token">=</SPAN> GeometryEngine<SPAN class="punctuation token">.</SPAN><SPAN class="token function">RemoveZAndM</SPAN><SPAN class="punctuation token">(</SPAN>geomFeat<SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">;</SPAN>
geomFeat <SPAN class="operator token">=</SPAN> Geometry<SPAN class="punctuation token">.</SPAN><SPAN class="token function">FromJson</SPAN><SPAN class="punctuation token">(</SPAN>geomFeat<SPAN class="punctuation token">.</SPAN><SPAN class="token function">ToJson</SPAN><SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">;</SPAN><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

All comments

MarkCederholm

Looks like the issue has reappeared at 100.12.0 -- now the error message is

"Invalid argument: geometry1 and geometry2 must have equivalent spatial references."

Fortunately, I've kept my workaround code.

UPDATE: I can't duplicate the error using the sample project above, so something else must be going on.

MarkCederholm

This issue appears to be fixed at 100.7.

JenniferNery

Meanwhile, you can use the following workaround before calling GeometryEngine.Contains or SpatialReference.Equals.

geomFeat <SPAN class="operator token">=</SPAN> GeometryEngine<SPAN class="punctuation token">.</SPAN><SPAN class="token function">RemoveZAndM</SPAN><SPAN class="punctuation token">(</SPAN>geomFeat<SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">;</SPAN>
geomFeat <SPAN class="operator token">=</SPAN> Geometry<SPAN class="punctuation token">.</SPAN><SPAN class="token function">FromJson</SPAN><SPAN class="punctuation token">(</SPAN>geomFeat<SPAN class="punctuation token">.</SPAN><SPAN class="token function">ToJson</SPAN><SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">;</SPAN><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.