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 inconsistency when adding data in Pro 3.0

ThomasHoman

I just noticed a inconsistency in Pro 3.0 when features are being added to a map.

I have 3 feature classes in a feature dataset that have symbology already applied via the source data - a feature I really appreciate by the way - that display differently depending on how the data is added to the map.

As a slight backstory, these 3 feature classes are generated via modelbuilder from the master parcel features as part of our 300ft notification process for Community Development.

Case 1 in attached image - Features were added to the Map retaining existing symbology

Case 2 in attached image - Features were added to the Map via right clicking on the feature dataset and selecting 'Add To Current Map.' With this method it appears the selected color palette is used for symbology as opposed to stored symbology.

My Idea - review UI so that symbology of added features is applied consistently. There may be other cases/methods of adding data to a map (arcpy, ...) that I have not checked.

Regards,

Tom

UIInconsistency.jpg

Find more posts tagged with

Map Authoring

Implemented

Status: Implemented

Comments

AmeliaBradshaw

This Idea has been implemented in ArcGIS Pro 3.1. Please see the What's New documentation for more new features in Pro 3.1.

KoryKramer

We were able to figure out a scenario to reproduce the described behavior, so we're re-opening this for now.

KoryKramer

@ThomasHoman would you be able to share the feature class with the stored symbology so we can examine the issue? You could send a zipped file gdb to kkramer@esri.com

Thank you

ThomasHoman

@wayfaringrob - I am not sure where the symbology is stored. What I am seeing in behavior where when I bring in a previously created layer they symbology is already set to what I want.

@JonathanNeal @KoryKramer - Not knowing the source of the symbology I think Jonathan's comments could easily be the source. It would just be nice to have symbology applied consistently via the multiple ways data can be added to the map.

Respectfully,

Tom

KoryKramer

Setting this to Needs Clarification for now. @ThomasHoman can you clarify what you mean by the feature classes having "symbology already applied via the source data"?

Are you talking about representation mentioned by Jonathan, or something else?

JonathanNeal

@wayfaringrob The symbology can be stored in the data souce. Details: https://pro.arcgis.com/en/pro-app/latest/help/mapping/layer-properties/draw-layers-with-representations.htm

I think this is probably going to be a bug/enhancement that when you add a dataset to the map it should look for these symbologies before going with the default. (Checking with the team now)

wayfaringrob

In case 1, how were they added to the map? Also, by 'stored symbology' - what are you referring to? Where is this stored?