As best as possible I try to enable Element Tracking so that I can keep a link between Rhino and Revit. But there are times when I need to make a wholesale replacement of a lot of geometry across several categories. It’s common that I have added a lot of dimensions and tags to on sheets. In order to preserve dimensions I typically do NOT add a dimension directly to an object but to a separate Reference Plane or Detail Line.
However, when it comes to tags things get a bit harder. Can you suggest a workflow that would allow me to quickly ‘re-tag’ items in Views? For example, if I had all my columns tagged in a plan view then I replace all of those columns with nearly identical (or identical but with different parameters and a new GUID) geometry in the same place, is there a way to say “ok, there was an object in this space that was tagged in this view before so I’m going to tag this new object that now occupies this space”.
Thanks for this, it will be useful to know what elements are tagged. But is there also a way that I could expand on this to tag ‘future’ objects that occupy the same space?
I am working with the Reference Annotations component and noticed that the Dimensions output always seems to be empty. I’m wondering if this is expected behavior or if I might be missing something in my workflow.
Here’s what I’ve tried so far:
Selected elements with associated dimension annotations in Revit.
Connected these elements to the Reference Annotations component.
Checked that other outputs of the component work correctly, but the Dimensions output remains empty.
Am I misunderstanding how the component works, or is there a limitation I should be aware of? Any guidance or clarification would be greatly appreciated!
Have you noticed, In the output, the dimension results appear to be calculated based on the total number of faces of the geometry, rather than being limited to the referenced faces. Additionally, upon inspecting the referenced faces, I observed that the ID assigned to all faces remains identical, which may lead to confusion or misinterpretation of the references.
I’ll see if we can get that refined, what is the desired workflow with those particular faces? The Element ID is going to be from the parent, the sub-element faces don’t have an ElementID.