Preserving Hex Code Color Symbology when publishing web service

262
4
10-20-2021 05:41 PM
Labels (3)
JustinOdell
Occasional Contributor III

Hi all,

I have an ArcGIS Pro project with some features symbolised based on a hex color code attribute value. I did this by varying the symbology by attribute, then allowing symbol property connections as per this instruction: https://support.esri.com/en/technical-article/000024233

What I wish to do now is publish my Map as a Feature Service and preserve the hex code colors symbology. When I publish the service however, the hex code colors are lost in the symbology. What is the best way to publish my service whilst preserving the hex color symbology?

Thanks.

0 Kudos
4 Replies
ABishop
Regular Contributor

@JustinOdell 

In my past experience with symbology and published services, I have learned to wait to customize the layers' symbology in the web map.  I believe there is a hex code option when choosing colors.

Amanda Bishop, GISP
0 Kudos
JustinOdell
Occasional Contributor III

Thanks @ABishop

Is there a way to automatically apply the hex code colors based on an attribute within ArcGIS Pro? I have several hundred features, so not really in the business of manually configuring them. The process I have tried in my original post works, but is not preserved when service is published.

E.g. is there a preconfigured hexadecimal style file?

0 Kudos
ABishop
Regular Contributor

@JustinOdell 

Honestly, I am not sure if that is possible in a web map symbology configuration.  But sounds like a great idea!   Maybe post it as an idea on the idea page?  If it isn't already available, ESRI might implement it!

Amanda Bishop, GISP
0 Kudos
JustinOdell
Occasional Contributor III

Found another post which is useful and related to this task:

https://community.esri.com/t5/arcgis-pro-blog/setting-up-the-attribute-driven-color-in-symbology/ba-...

I note there is a BUG logged in support of this capability:

https://support.esri.com/en/bugs/nimbus/QlVHLTAwMDEwNDMxNg==

At this time there is no solution or work around to this issue.

 

0 Kudos