Select to view content in your preferred language

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

590
1
03-15-2022 06:44 PM
Status: Open
Labels (1)
Bud
by
Esteemed Contributor

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.

 

1 Comment
DuncanHornby

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?