# MarkupsLine .fcsv loads as MarkupsFiducials

**URL:** <https://discourse.slicer.org/t/markupsline-fcsv-loads-as-markupsfiducials/11545>\
**Category:** Support\
**Tags:** markups\
**Created:** [May 14, 2020, 8:03pm UTC](https://discourse.slicer.org/t/markupsline-fcsv-loads-as-markupsfiducials/11545 "2020-05-14T20:03:49Z")\
**Posts on this page:** 5\
**Page:** 3

<div class="post-metadata">

**Author:** ![jclauneuro](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jclauneuro/32/1821_2.png) [@jclauneuro](https://discourse.slicer.org/u/jclauneuro)\
**Post date:** [June 12, 2020, 3:58am UTC](https://discourse.slicer.org/t/markupsline-fcsv-loads-as-markupsfiducials/11545/41 "2020-06-12T03:58:42Z")

</div>

Just made the following thread: [https://discourse.slicer.org/t/switching-to-json-for-markup-files-any-convergence-with-bids/](https://discourse.slicer.org/t/switching-to-json-for-markup-files-any-convergence-with-bids/)

---

<div class="post-metadata">

**Author:** ![muratmaga](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/muratmaga/32/3622_2.png) [@muratmaga](https://discourse.slicer.org/u/muratmaga)\
**Post date:** [June 12, 2020, 4:23am UTC](https://discourse.slicer.org/t/markupsline-fcsv-loads-as-markupsfiducials/11545/42 "2020-06-12T04:23:50Z")

</div>

> [@lassoan](#):
>
> No need to convert storage nodes. For export, you can create a temporary vtkMRMLMarkupsFiducialStorageNode, which does not interfere with the regular storage node that is used for saving (filename, format, and saved state are all preserved):

OK. @pieper and @smrolfe will work on a ‘Export’ fun will likely send a PR somepoint.

---

<div class="post-metadata">

**Author:** ![muratmaga](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/muratmaga/32/3622_2.png) [@muratmaga](https://discourse.slicer.org/u/muratmaga)\
**Post date:** [August 19, 2020, 3:08pm UTC](https://discourse.slicer.org/t/markupsline-fcsv-loads-as-markupsfiducials/11545/43 "2020-08-19T15:08:07Z")

</div>

ExportAs Subject hierarchy plugin is now available in the SlicerMorph extension. It allows export of non-fiducial Markup nodes to be saved in the lossy fcsv format through right-click context menu.

> **[SlicerMorph/SlicerMorph](https://github.com/SlicerMorph/SlicerMorph/tree/master/ExportAs)**
>
> Extensions to conduct 3D morphometrics in Slicer. Contribute to SlicerMorph/SlicerMorph development by creating an account on GitHub.

---

<div class="post-metadata">

**Author:** ![J\_Deng](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/j_deng/32/8020_2.png) [@J\_Deng](https://discourse.slicer.org/u/J_Deng)\
**Post date:** [September 11, 2020, 12:56pm UTC](https://discourse.slicer.org/t/markupsline-fcsv-loads-as-markupsfiducials/11545/44 "2020-09-11T12:56:53Z")

</div>

![image](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/f/f/ff64228180c4606165160370ae56e3ce1b514c50.png)  
I am using the latest preview version 4.11.0-2020-09-08 r29363 / c565268 to mark the anatomies in the 3D views. Among various possible options: annotation, markup, label, I’ve found markups are the closest ones to do so [as the markups can move together with corresponding anatomies in 3D]. But despite having changed default names MarkupsF… on the left panel, the names in 3D do not make corresponding changes. Am I using a wrong function to label structures or is is a glitch with the latest version? By the way, how to remove the cubical box lines and orientation indicators [S, L, I … ; the latter are often irrelevant to ultrasound volume data as we acquire images not in standard CT or MRI ways]. Thanks.

---

<div class="post-metadata">

**Author:** ![muratmaga](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/muratmaga/32/3622_2.png) [@muratmaga](https://discourse.slicer.org/u/muratmaga)\
**Post date:** [September 11, 2020, 2:59pm UTC](https://discourse.slicer.org/t/markupsline-fcsv-loads-as-markupsfiducials/11545/45 "2020-09-11T14:59:46Z")

</div>

My suspicion is you are using the create MarkupFiducial button, and then rename the resultant node later one, but not the individual fiducial point. The buttons shown below (two small red rectangles) are actually differ in functionality.

In any event, you can rename the individual points within a MarkupFiducial by expanding the Control Points tab, and changing the associated labels.

For SlicerMorph, we have a tutorial on markups (it is more towards landmark data collection), but I think it will be still useful if you are new to Slicer: [https://github.com/SlicerMorph/S\_2020/blob/master/Day\_2/Markups/Markups.md](https://github.com/SlicerMorph/S_2020/blob/master/Day_2/Markups/Markups.md)

[![](https://raw.githubusercontent.com/SlicerMorph/S_2020/master/Day_2/Markups/markupsModule1.png) ](https://raw.githubusercontent.com/SlicerMorph/S_2020/master/Day_2/Markups/markupsModule1.png)

[Previous page](https://discourse.slicer.org/t/markupsline-fcsv-loads-as-markupsfiducials/11545.md?page=2)