# Exporting a segmentation paired to a custom colortable

**URL:** <https://discourse.slicer.org/t/exporting-a-segmentation-paired-to-a-custom-colortable/35719>\
**Category:** Support\
**Tags:** segmentation, custom-color-table\
**Created:** [April 24, 2024, 9:33pm UTC](https://discourse.slicer.org/t/exporting-a-segmentation-paired-to-a-custom-colortable/35719 "2024-04-24T21:33:21Z")\
**Posts on this page:** 1\
**Showing post:** 8

<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:** [April 25, 2024, 7:15pm UTC](https://discourse.slicer.org/t/exporting-a-segmentation-paired-to-a-custom-colortable/35719/8 "2024-04-25T19:15:39Z")

</div>

> [@jhlegarreta](#):
>
> I made sure that I am using exactly the names in my colortable, and have simplified it to the following:

I confirm that everything works as expected (i.e., labelmaps are exported with correct indices) when you replace underscore (\_) with space. I tested it 5.6.2. If 5.2.2 doesn’t export it correctly for you (with the replacement), you can install 5.6.2 and export in there.

> [@lassoan](#):
>
> They are global identifiers that can be shared between projects and they allow using different name variants and spelling for segment names.

I am not sure how this will fix the conversion to the labelmap though. Labelmaps are what goes into the ML training, and they need to have indices. So we will always need some sort of lookup between segment labels and labelmap indices, regardless if the segment labels comes from a standardized terminology. Or am I overlooking something?

---

_[View the full topic](https://discourse.slicer.org/t/exporting-a-segmentation-paired-to-a-custom-colortable/35719)._