# JSON file contents questions

**URL:** <https://discourse.slicer.org/t/json-file-contents-questions/14832>\
**Category:** Support\
**Created:** [December 1, 2020, 5:34pm UTC](https://discourse.slicer.org/t/json-file-contents-questions/14832 "2020-12-01T17:34:17Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![muratmaga](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/muratmaga/32/83011_2.png) [@muratmaga](https://discourse.slicer.org/u/muratmaga)\
**Post date:** [December 1, 2020, 5:34pm UTC](https://discourse.slicer.org/t/json-file-contents-questions/14832/1 "2020-12-01T17:34:17Z")

</div>

We discussed this [here](https://github.com/Slicer/Slicer/issues/5261), but as far as I can it is not implemented for the latest stable.

Also, what is the purpose of the “orientation” tag?

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [December 1, 2020, 6:41pm UTC](https://discourse.slicer.org/t/json-file-contents-questions/14832/2 "2020-12-01T18:41:08Z")

</div>

Markups measurements are going through a large refactoring (allowing multiple measurements, measurment selection, per-control-point values, use that for coloring, etc.). We’ll get back to [https://github.com/Slicer/Slicer/issues/5261](https://github.com/Slicer/Slicer/issues/5261) after [https://github.com/Slicer/Slicer/pull/5322](https://github.com/Slicer/Slicer/pull/5322) is integrated.

Orientation allows you to record an orientation (surface normal, digitizer stylus orientation, etc) and use it for orienting point glyphs or use it for various comoutations. Currently it is not used for much and so the implementation is not fully complete. We need to decide to keep it (and fully complete the implementation) or drop it (and remove orientation support completely). We can now store custom per-point values, so we could store orientation there, but it would not automatically transform when the node is transformed, and orientation is not recorded automatically when the point is placed, so it is not a complete replacement yet.