Symbology downgraded when publishing from Pro to Portal

Question

Hello all,

Publishing our map services as map images, using Pro to Portal, we have encountered numerous layers where the symbology has been downgraded for Portal. Although this is expected behaviour, e.g. line layers, simple line symbols are supported. If other symbols are used, the feature service converts them to a simple line symbol that best represents the original symbol, I would be interested to find out other's experiences with downgraded symbology.

For example, a cartographic line symbol in the map document may be drawn as a simple solid line in a feature service client. If a line symbol is complex or has multiple layers, the feature service downgrades the line to best represent the original line symbol. “

This has been problematic as some symbology is nationally recognised for example Public Rights of Way and can no longer be represented in Portal if we publish as a registered feature layer/map image.

It would be really helpful if in Pro when selecting a symbology, there was an option for "Portal only symbology" so we knew what symbology supports, instead of receiving a message at the point of publishing the data that it will be downgraded.

I would be interested to know others experiences of downgraded symbology when publishing map images or registering feature layers in Portal.

Many thanks

Capture.PNG

openclosed.gif

JasonFitzsimmons · Answer

Thank you @Scott_Tansley , I was having this problem and your answer was helpful.

In my Web map, I specifically added  layers within the services by using 'Add Layer from URL' rather than 'Browse Layers'   (even if there was only one layer) so that in the table of contents in the Web Map (and subsequently in Experience Builder), I see only that single layer, rather than the map service with the layer embedded within it, requiring a button click to open the service (see screenshot).

Most of the time I have added layers using the URL and layer number with no changes to the symbology,  but I had the same problem the poster above had for one layer with a bit more complex symbology.

Do you have any suggestions for how I can get around this small but annoying issue? Our clients always complain when we have these embedded table of contents items that don't appear to serve any purpose on the front end (as opposed to an intentional group layer). I understand this is a bit cosmetic but we do like our apps to be as clean and streamlined as possible.

Anonymous User · Answer

Thanks Scott, that's helpful and yes I appreciate the differences between a map and feature service now I have investigated this further. Your explanation makes it very clear - thank you. When we are publishing data as a map service, we need to be aware that the symbology may be downgraded (I think you now have a warning message which is also helpful).  I'll check out the links in your email above.

Scott_Tansley · Answer

That's quite an easy one.  Your limitation is the styles that are available in the Portal Web Map.  If it's in the web map options then you can draw that in the browser.

You may also want to read:  https://pro.arcgis.com/en/pro-app/latest/help/projects/styles.htm

And review "web styles".  ArcMap used to have something called optimised styles, I haven't found an equivalent in Pro, but I don't spend a lot of time there any longer.