Creating dynamic blocks with attributes from excel spreadsheet data for trees
@MMStaake wrote:
I am looking for an efficient way to create a dynamic block or point which needs to include data imported from excel for trees (species, trunk diameter, native, demo/protect in place, health, tree label number). I'm thinking dynamic blocks with attributes? I have to do this for over 1,000 trees, so I'm not sure what the best way to go about this is. The parts I'd like to be dynamic are the trunk size based off of the spreadsheet data and the tree label number. I do have cogo points for the locations, but all of this information will eventually be exported as a shapefile for GIS. Thanks!
you want the symbol to be dynamically sized from trunk?
You can create User Defined Property (UPD) to add more labeling to you cogo point that can be exported to GIS.
If dynamic you want the attributes to have various content the that is simply a block with attributes.
your spread sheet would need the coordinates of each tree, then you would need to create a script file that inserts, rotates and scales and fills the fields. ... not impossible but UPD would IMHO be the easy way out
Joe Bouza
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
<<...I'm not sure what the best way to go about this is.>>
<<The parts I'd like to be dynamic are the trunk size based off of the spreadsheet data and the tree label number.>>
<<I do have cogo points for the locations...>>
<<... all of this information will eventually be exported as a shapefile for GIS.>>
If you already have a spreadsheet that has both the x/y-coordinates and trunk diameter for each individual tree then you may not even need cogo points. It all depends on your spreadsheet and whether or not the Excel data needs to be combined with the x/y coordinates of the cogos. Civil3D is capable of creating shapefile that can include tree label and trunk diameter as Data Attributes in the database file (dbf). Creating a shapefile will eliminate the dynamic block altogether. The time and energy you spend linking the dynamic block to the spreadsheet can be easily be replaced by creating the shapefile yourself.
BTW, the shapefile's database is editable so if a trunk diameter was recorded incorrectly by the field crew it can be changed and the tree's appearance will reflect the new diameter automatically.
If you are willing to share a sample of your trees, say a 10% sample, a step-by-step procedure (or a screen cast) can be provided for you.
Chicagolooper
Your path is described here. Property Set Data is the Way! Some things may need to be controlled by description keys (size)
Working with Property Set Data in Civil 3D - YouTube
You'll need the Shape Import/Export Utilities.
Rick Jackson
Survey CAD Technician VI
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
@MMStaake wrote
<<...Internally we don't use GIS, but the files will need to be exported for our sub- they use GIS, not AutoCad. ...>>
If you are planning to 'export' at a later date for your sub, it would be better to create the shapefile now. Otherwise ignoring the shapefile creation right now will be a big issue, huge issue.
Right now you can do both, Civil AND shapefile. If you only do Civil now it's on you. Totally on you.
Instead of asking the forum, ask your sub what they think. In them in your discussion!
Chicagolooper
