Description keys
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.
Description keys won't hatch a buffer.
Besides, if your gonna write desc keys, you may as well create shapefile cuz the shapefile will allow you to create fill (or hatch inside a closed polyline.)
Jus sayin'.
Chicagolooper
You are my hero 👍
I do think description keys can do this
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.
No but a scaled back will.
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.
Yes - description keys will handle this for the know sizes and can be updated if the tree survey adds or changes the any size.
I did pretty much the same as @samir_rezk did except I merged the recomment-treeID-buffer in the raw description. since there are only 10-12 different buffer size creating the keys is not very onerous. Once imported if the arborist changes hi mind on P or R communication of tree# or giS overlay can easily solve the alteration.
For this exercise I did not bother creating UDP but they can easily be added too. I also just used to OOTB blocks to demonstrate
all you need to do is change th R or P and APPLYDESCKEYS
Thank you @samir_rezk for kick starting me
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.
