I've been looking through the documentation and still haven't found where this went:
Hi,
To answer your questions:
1. Real world units can be enabled in the layer properties. Right click layer > Properties > Display tab
2. There's a couple different workflows you can try
a. In the Symbology pane click the burger button > Match layer symbology to a style
Run this tool
b. Another option is to convert the symbology of your old preset layer to the unique value renderer. From there you can run the Apply Symbology From Layer geoprocessing tool on the new layer with the symbology from the old layer.
Hopefully one of these options will work well for your data. In a future release, one of the teams is working on a similar UI that will streamline this process a bit more.
thanks,
Andrew
I reached out to another team to get clarification on this and they confirmed that the core styles use the common name and not the genus. The match layer symbology to a style will always use the symbol name so in this case it will only work with common name. If you only had data with genus you could create a new style where the symbol name of the realistic tree matches the genus and then in that case it would work to use the match layer symbology to a style but it sounds like it will still work for you to use common name moving forward.
Preset layers have been deprecated. This has been documented on the main help topic as well as release notes for 3.0
https://pro.arcgis.com/en/pro-app/latest/help/mapping/layer-properties/preset-layers.htm
https://pro.arcgis.com/en/pro-app/latest/get-started/release-notes.htm
Technical article: https://support.esri.com/en/technical-article/000027469
Wow, what a bummer. Maybe I did see that and ended up in denial since I was hoping I could help users visualize tree planting plans. So I would have to hang onto Pro 2.9 indefinitely to create attribute driven realistic tree models? Do you have a suggestion for a workaround? Curious as to the reasoning behind the decision to deprecate this.
Here are some details that will hopefully explain this better:
It’s never easy to remove something that has been in the software for years but based on the previous points multiple teams in coordination with product management made the decision to deprecate this.
While the UI is not there the same behavior can be achieved in 3.0 using the out of the box system styles for 3D thematic and realistic vegetation. Leverage these styles with attribute-driven symbology and you will have the same output. Additionally, we have added new ready-to-use OSM realistic and thematic trees that can be accessed from ArcGIS Online. I have placed some links below for the various workflows.
Attribute-driven symbology
https://pro.arcgis.com/en/pro-app/latest/help/mapping/layer-properties/attribute-driven-symbology.htm
ArcGIS Pro system styles
https://esri-styles.maps.arcgis.com/home/item.html?id=6b9ad70589bb42788251b465487a6ac0
Add System styles
https://pro.arcgis.com/en/pro-app/latest/help/projects/connect-to-a-style.htm#GUID-F0F6BA63-F617-4ADA-B153-428A809942B5
OSM trees
https://www.esri.com/arcgis-blog/products/arcgis-living-atlas/mapping/new-osm-3d-scene-layers/
Thanks, Andrew. I'm most of the way there but I must be missing something in attribute driven symbology. I've added the 3D Vegetation - Realistic style and enabled attribute driven symbology on my feature layer. I've set Unique Values based on the genus field in my attribute table. Is the functionality that reads the genus field and automatically selects the tree model based on the field gone? I'm having to select the tree model myself. Also, once I select a tree model for each unique value, I'm only presented with points (pt) for trre height and crown width when I need real world units like preset trees used to allow. Is this possible?
I was just starting down the road to match layer as you were writing this! I got no matches from my genus field so I wondered if it wanted common name based on the symbol selector names.
I'll keep at it with your other recommendations as I would like to demo this in a couple weeks. Thanks.
Common named worked to match symbology. The only other thing I was wondering about was having to set up each unique tree symbol's attribute fields to get my height and width, a process presets did for all symbols at once at the very beginning.
As long as you have crown height and width for each tree in the attribute table then you can set this at the layer level using the vary symbology by attribute
Thanks. This ended up working for me and the results look as good as they did with presets. I look forward to the streamlined process for this.
Though I like using the common name for the trees, any idea why genus finds no matches against the realistic trees style? This is a very minor issue since I have my solution. I appreciate your help with this.
This is what I gathered from this topic: https://pro.arcgis.com/en/pro-app/2.8/help/mapping/layer-properties/supported-tree-genus-types.htm
Supported tree genus names are listed, sorted by common name. Data with matching genus names is drawn with the corresponding tree model. Data with an unknown or undefined genus is drawn with the Generic Tree symbol, unless the data value corresponds, at least partially, to a Common Name listed below
In the old preset you had the generic tree symbol when it was undefined but that's not the case in the new workflow. Hopefully that answers your question.
Andrew, that is the text that I've relied on for past versions of Pro and gives rise to my question since genus no longer seems to work. Is genus not working because it is not included in the name field shown below? Is this what my field is being matched against? If so, it makes sense that only common name in my attached shapefile would work. I checked an older version of Pro (2.9) and the properties look exactly the same for this tree, yet it can match using genus field or combined genus/species field. Version 3.0 only works using the common name field.
I also noticed the Match Layer Symbology to Style doesn't open the dialog to do this, so I end up running the GP tool from the toolbox.
Would you be willing to test this using the attached shapefile?
sure, i'll take a look.
Thanks again
@Andrew--Johnson would crown width be same as crown diameter considering that the crown is circular?
yes, that's correct
I'm dealing with the same issue i.e. trying to replicate the same workflow of assigning a realistic tree shape to a point dataset with accurate tree height and canopy width measurements. I have made it up until this point, however, when I open the size dropdown after having allowed symbol property connections I am only given one field to edit the symbol and do not have the option of adjusting feature height and width separately? I was wondering if this option has also been deprecated or if I am going about the process incorrectly?
Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
