I am published reference map image services to be added to a web map, using Enterprise 11.3 (an HA system, if that is relevant).
When I publish reference map services, they are presented in two 'layers': the 'parent', which has the name I give in the 'Share As Web Layer' properties in Pro, and the 'child', which keeps the layer name as it is given in the Pro project's table of contents. I am not sure if there is a better name for this relationship. (maybe the service and the layer?)
So the user has to drill down into the layer to see its symbology, and there are two visibility checkboxes:
This is more annoying when trying to group these layers. Then, there are three levels to view:
If I try to publish a layer that is in a group layer in Pro, it's even more confusing (I won't bother to show this). I had to ungroup all my groups in the Pro project.
This is not the case with hosted feature layers, which behave the way i prefer:
So if I am creating a group layer with both hosted and map image layers, I have a mix of levels for the user to navigate, which I know the client will not like.
Is there any way around this?
I assume this is the way map image layers are designed. I seem to keep finding ways that reference layers do not behave the same way as hosted feature layer in Enterprise, usually not as well.
Accepted Solutions
My teammate just showed me an easy (and somewhat obvious) workaround.
Instead of browsing layers from Enterprise content, in the web map, choose 'Add layer from URL' using the REST endpoint, making sure to add the layer number:
My teammate just showed me an easy (and somewhat obvious) workaround.
Instead of browsing layers from Enterprise content, in the web map, choose 'Add layer from URL' using the REST endpoint, making sure to add the layer number:
