nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Remove duplicate labels from multiple classes

MathiasBerlin

Sometimes you have a feature labelled in different label classes, for instance a certain class for large areas (larger font, higher weight etc) and another class for smaller areas for the same reason. It is not possible now to remove duplicates between different layers and label classes. That would be a huge improvement to the labeling in our maps.

Find more posts tagged with

Annotation & Labeling

Status: Open

Comments

williamscraigm

Remove duplicates does work across label classes and layers but it's limited to prevent accidental removals. Currently only labels from the same feature type (point, line, polygon etc.) and in label classes with the same font and size will be considered duplicates as documented here. You're requesting unlimited removal for any matching text string?

MathiasBerlin

Hi!
Thank you for the clarification on duplicate removal. Yes, I would suggest that you could choose from wich classes duplicates should be removed, therefore you could also specify which class should be regarded as "base" vs "candidate". Imagine a river narrowing from a polygon to a line (nice to be able to remove line labels and keep polygon labels when too close etc).

Currently we have to do a lot of data editing to work around some of these issues, I think it would be a nice enhancement to an otherwise great labelling engine.

jetemple

Just stumbled on this thread after jumping into an APRX to update a map, and got very confused as to why I had a load of duplicate labels where I didn't previously...

This 'same font, same size' rule seems to have been added in 3.4 - I'd updated Pro since the original APRX was created - and for me it'd be really useful to essentially disable/revert this so that it would remove based on text string alone, as I frequently use varying label text size to give a sense of importance or weight (excuse the pun) to certain label classes.