Arcade docs: Equals() function doesn’t consider M-values

Bud — Wed, 16 Mar 2022 14:08:21 GMT

As far as I can tell, the Equals() function doesn’t consider M-values when comparing geometries.

See: Arcade: Editing M-values not treated as change to geometry

If that’s the case, then could a blurb be added to the Arcade docs that explains this? I know the docs hint at it with the “geographically equivalent” wording, but I think it could be clearer.

It might also help to explain whether Z-values get considered or not, too.

Re: Arcade docs: Equals() function doesn’t consider M-values

DuncanHornby — Wed, 16 Mar 2022 12:31:48 GMT

This is a good idea. Either update the documentation to be more explicit so its crystal clear that the test for equality does not test M or Z values or better still provide an additional new function maybe something like "EqualsMZ()" where the function not only tests the geometry but also any M or Z values that may exist?

idea Arcade docs: Equals() function doesn’t consider M-values in ArcGIS Pro Ideas

Arcade docs: Equals() function doesn’t consider M-values

Re: Arcade docs: Equals() function doesn’t consider M-values