I am working on a map of different types of transportation plans in Virginia localities (324 records) and I have hit a roadblock in the most efficient way to display the data. The layer I have created is a polygon layer of locality boundaries and the additional features/attribute fields I would like to display are:
want to display each of these fields as a unique point symbol in each locality for which the respective field is non-null
I plan to provide a legend for the symbolized attributes as well as configure pop-ups for each locality with specific data from the attribute table.
So far, I have come up with the following methods for symbology:
Create individual layers for each plan type and symbolize by single symbol, unique to each layer/plan type -- layers created from Plans by Locality using select by attribute where respective field values are not null.
I would have to offset the symbology of each layer to avoid obscurity
Ideally, I would like to contain this data in a single layer but am not opposed to a layer package if necessary as I am unsure of the feasibility in having unique point symbols within a polygon layer.
Other considerations:
Using ArcPro Version 2.9
The data in this layer originated from a standalone attribute table/csv which I joined to a polygon feature layer of Virginia localities. There may be a workaround to displaying the attribute data spatially, but I am unsure of how to do this without compromising the connection between the localities and the plans which cover them.
Solved! Go to Solution.
Oof, let's try making this a bit easier for you.
We're going to use attribute-driven symbology to make this work.
if ($feature.Bike_Plans== null){
return 0
}
So, what we did was say "If this field is empty, make the symbol size 0". When the field is not empty, it will match whatever size you normally have in the size field.
Taking this, we can go back to the wrench tab and duplicate this symbol layer
and change the symbol and the field we're checking each time.
And then we get this as the output
Be careful if doing random points to change the seed value each time, and change the spacing in general, or else they all end up on top of each other.
Now.
This is going to look awful in your legend.
There are other ways to do this, but I'd suggest making a dummy point feature class with a name field and 5 points.
Hope this helps!
Oof, let's try making this a bit easier for you.
We're going to use attribute-driven symbology to make this work.
if ($feature.Bike_Plans== null){
return 0
}
So, what we did was say "If this field is empty, make the symbol size 0". When the field is not empty, it will match whatever size you normally have in the size field.
Taking this, we can go back to the wrench tab and duplicate this symbol layer
and change the symbol and the field we're checking each time.
And then we get this as the output
Be careful if doing random points to change the seed value each time, and change the spacing in general, or else they all end up on top of each other.
Now.
This is going to look awful in your legend.
There are other ways to do this, but I'd suggest making a dummy point feature class with a name field and 5 points.
Hope this helps!
This is amazing! Thank you so much for working through my chaos haha, I figured I was making this a bit too difficult for myself.
It's one of my favorite capabilities in Pro. You can do a lot of cool stuff with it.