Select to view content in your preferred language

Symbology downgraded when publishing from Pro to Portal

1800
5
07-25-2022 07:36 AM
Labels (1)
by Anonymous User
Not applicable

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. “

WendyConibear_1-1658759617090.png

WendyConibear_2-1658759631880.png

 

 

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

 

Tags (3)
5 Replies
NatalieScott_HVP
Emerging Contributor

I would definitely like this; this would save a lot of trial and error to find compatible symbology. It would be good to also include compatibility with ArcGIS Pro (as this will update more frequently than Portal).

0 Kudos
Scott_Tansley
MVP Regular Contributor

I think this comes down to how you're drawing the data.  You mention map and feature services.  They are very different things, even though they have the same start point.

A Map Service (or Map Image Layer) is a type of service that provides an image to the end user.  Literally, when you pan and zoom in the map, the request says "go get the data and then send me a JPEG or PNG" back.  The ArcGIS Server has all the power and drawing ability of ArcGIS Pro, because all 'the code' is there to render that image.

If you add an individual layer from a map service, then you're actually doing something very different.  You're running a query (not an export image).  It's like saying "select * where everything is in this map view".  And the response is actually 'text (JSON or PBF)' not an image.  That text then has to be drawn by your browser.  Literally the map in the browser is presented with a long list of attributes and vertices, and it starts drawing.  But your browser is not ArcGIS Pro, it can do simple lines but not cartographic lines.

https://developers.arcgis.com/rest/services-reference/enterprise/map-service.htm

A feature service works in the same way as an individual layer.  We only ever get text from a feature service, and so the ability to draw it is as advanced as your browser can handle, and so not cartographic standards.

If you need to show the cartographic detail then you need to add it to your map in the form of:

https://maps.myserver.com/arcgis/rest/services/helloworld/mapserver

rather than:

https://maps.myserver.com/arcgis/rest/services/helloworld/mapserver/1

or

https://maps.myserver.com/arcgis/rest/services/helloworld/featureserver/1 

 

This decisions point determines if the data is drawn (nicely) by the server, or basically by the browser.

Sorry, very complex subject and hard to demonstrate in text.  But have a play with the URLs you add in your Portal map and see what different results you get.

Scott Tansley
https://www.linkedin.com/in/scotttansley/
NatalieScott_HVP
Emerging Contributor

Hi Scott,

Thanks for the detailed response. I had noticed that the behaviour was different depending on map/feature service usage, but your explanation made it much clearer. I'm sure I'll be able to develop a solution that works based on these parameters.

However... It would still probably be nice to be able to determine, in ArcGIS Pro, which symbology will be able to be consistently drawn across platforms. One for the wishlist 🙂

Thanks

Natalie

 

 

0 Kudos
Scott_Tansley
MVP Regular Contributor

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.

Scott Tansley
https://www.linkedin.com/in/scotttansley/
0 Kudos
by Anonymous User
Not applicable

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.

 

0 Kudos