Post

Instead of an Arcade implementation, I'm utilising an extended graphics layer which has some custom labelling logic attached. The main reason for this implementation was because I wanted more control over the labelling and specifying geodetic measurements vs projected measurements.

I think in a previous post I may have said we were using the measurements view model. But actually I've created a custom subclass of a sketch view model for the line measurements. It handles optimising when distances are calculated to ensure that only the new segment are being actively measured.

0 reposts1 like

Very cool! We’re in the process of improving the programmatic APIs for measurements and other such tools and this can feed right back into some of the designs and discussions we’ve had.

That would be amazing. My impression of the 2d measurements widget has been that it feels a tad "underpowered" at the moment. My biggest wishlist is: 1) Geodesic support for measurements (including supporting showing the drawn geometry as densified geodesic lines).

2) Additional labelling functionality. Including being able to manually set the label content. 3) COGO tooling - similar to the tooltip options in the sketch view model tooltip (note if this is implemented please let the tooltip lengths be set a geodesic!) Thanks Hugo!

Nice feedback, thanks! Regarding geodesic, the measurements are already geodesic for WebMercator and any geographic spatial references (eg WG84), and planar for any projected coordinate system (except for WebMercator). And sketch tooltip distances/lengths are handled the same way as well.