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; } } }

Symbology Created in AGOL works in ArcGIS Pro but not when Saving the Web Map in Pro

CarsonG

I was testing symbology to see what the complexity for lines are available now in the Map Viewer and Field Maps.

As none of the symbols I created in Pro first, worked in AGOL or in Field Maps I started testing the symbols in AGOL. They can be seen in the image below. These symbols also work in Field Maps.

I opened the WebMap in Pro and the symbology as expected, stayed as is as shown below.

I tried changing some of the colors and then saving the Pro Map as a Web Map using the share Save As Web Map tool.

When I opened the new map in Viewer, the symbology had downgraded.

Why is this occurring?

Najděte více příspěvků označených jako

Accepted answers

RussRoberts

The sharing of a web layer that creates a hosted feature layer item and storing the complex symbology that only newer clients like Map Viewer, Experience Builder or Dashboards would read. Map Viewer Classic and other 3.x clients will downgrade to a simple default symbol.

All comments

RussRoberts

When you are doing the Save in Pro you need to make sure you uncheck this box on the Save panel

CarsonG

Thanks Russell, that did it. Think I figured that out before but forgot lol.

CarsonG

Hey @RussRoberts ,

Thought this was resolved.

I saved the symbology I created from AGOL inside Pro. Leaving the option of symbol compatibility unchecked worked for the other map that was created in AGOL.

When I tried using the saved symbology in Pro to Publish a Web Layer, it is downgrading the symbology. There is no option when publishing a Web Layer for symbol compatibility.

When I tried to share the layers as a web map it says the symbols will be downgraded. The symbol compatibility check box for Sharing As Web Map is unchecked. They are still downgrading.

RussRoberts

This is currently not supported for writing these symbols out at the item level. Map Viewer can save the symbols back to the item and with the Pro 3.1 release this will be supported.

CarsonG

Which/what will be supported in 3.1?

RussRoberts

CarsonG

Will Field Maps be able to read the complex symbology as created in Pro 3.1? The complex symbology I created in AGOL in the first image on my original post was viewable in Fields Maps but only when it was created in AGOL. Will ArcPro 3.1, Map Viewer and Field Maps all be compatible with each other as far as the complex symbology is concerned?

RussRoberts

The Pro and Map Viewer complex symbols should both work in Field Maps. Those symbols are just writing CIM ( the symbol spec) into the web map. We dont reference any of the web styles after the symbol has been applied so the symbols are safe if a web style was ever to be deleted the layer renderer would not break.

Scoth

I would be nice if there was an easy way to tell which symbols will transfer nicely. Instead I find myself doing random guess and check... this square uploads fine, but this diamond does not, etc. I've spent more time dealing with symbol incompatibility than almost anything else. In the end I just accept blurry looking symbology online.

Připojte se ke konverzaci

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.