Symbology in Sub-type group layer behaves differently compared to a non-subtype group layer.

[gis_KIWI4]

It looks like the labels just display with overlap. 
Whereas with the non-subtype group layer it may only show one label and hide the rest, making it appear cleaner.

The display scale is set correctly because in the sparsely populated areas of the network it conveys the information needed but in crowded areas it just doesn't work as well as it should.

We are currently on 11.3, looking to upgrade to 11.5. I wonder if that adds better labelling support for subtype group layers in webmaps and ExB apps. 

[RobertKrisher]

Can you show more details about how your labels are configured in both scenarios? In particular, it looks like with your subtype layers you have the "Never remove (place overlapping)" option selected, which is not enabled by default.

[gis_KIWI4]

@RobertKrisher  - I don't think I looked at that option in ArcGIS Pro partly because Labelling settings don't really transfer well to the MapViewer. 

And in the MapViewer this option doesn't exist on subtype group layers. 

But that being said, I just checked the map that was used to publish and it does have the option set to remove overlapping labels.  

[RobertKrisher]

ok, I missed that from the first post. the labelling in experience builder / web maps don't look as good as they do in ArcGIS Pro. At least part of it looks like its because it doesn't support not placing overlapping labels. The map in ArcGIS Pro looks reasonable.

So this is more of a question of the map viewer and its support for subtype group layers, as opposed to the Utility Network or anything ArcGIS Pro related (like I was expecting).

[gis_KIWI4]

Yes, that is correct.
Even though it's not a UN question, I was hoping to get an answer here as subtype group layers are the recommended way of adding data to the map.

[gis_KIWI4 · Accepted solution]

Published the same map on AGOL and I can see it's more what I would have expected. It's doesn't place overlapping labels. 

I am thinking this is Enterprise MapViewer issue that will be fixed in 11.5 upgrade.