# Add unit to the fcsv header

**URL:** <https://discourse.slicer.org/t/add-unit-to-the-fcsv-header/13716>\
**Category:** Support\
**Created:** [September 27, 2020, 4:13am UTC](https://discourse.slicer.org/t/add-unit-to-the-fcsv-header/13716 "2020-09-27T04:13:47Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [September 27, 2020, 2:21pm UTC](https://discourse.slicer.org/t/add-unit-to-the-fcsv-header/13716/2 "2020-09-27T14:21:42Z")

</div>

I agree, length unit must be saved into markups file.

I guess it is not as a big problem for markups as for images and meshes, because markups rarely interpreted on their own and so the unit can be taken from the associated input data.

I will add this to the json format, but I would not touch the fcsv export, as it could break existing parsers that just ignore the first N lines of the file.

---

_[View the full topic](https://discourse.slicer.org/t/add-unit-to-the-fcsv-header/13716)._