@Sunderlandkyl what do you think would be a good solution? Maybe we could add an optional a color node input for segmentation labelmap export? Then the exporter could look up colors based on segment name or terminology. Some people already have a color table (which is used during import) and if the same colormap is used for export then the labelmaps would remain consistent.
There was also a similar question for the import side. There is a solution for the import but it requires a good number of clicks and it is unlikely that users could figure it out by themselves. How do you think we could simplify? Should we add a color node selector to the qSlicerSegmentationsIOOptionsWidget for reading?
Maybe a common solution for both import and export would be to make it easier to create custom terminologies or improve color nodes so that they can contain standard terminologies. We could then use these to map label values to/from segment names and terminology.