also is there any way to relocate the tag locations so they do not clash between each other in the view at scale in sheet? it is hard to know how they would look based on the drawing scale, text size and length in sheet/paper
thanks, I am aware of them but the only thing I do not like is that I need to specify the location point of all of the tags which I do not have idea, but I want to see tags attached to the elements in views and perhaps relocate them later once I know what annotative elements are in the views
in this case the location of the elements to tag are a point, so you suggest to get those points and place the tag type maybe some fixed distance above the location points for example?
is there any way to relocate the tag locations so they do not clash between each other in the view? it is hard to know how they would look based on the drawing scale, text size and length in sheet/paper
Yes - and likely several other object type exceptions and zero visibility/zero geometry exceptions as well. For sketch based I would use the center of the bounding box generally.
I saw this some time ago I believe it uses packages of DynaShape, VASA, Generative Design or more, what I believe is doing is taking all the elements geometry projection in 2D in a sheet with the drawing scale applied, and find a white space where there is no geometry within the viewcrop region on sheet.
If this needs to take all the elements geometry I think I can start to cry by waiting the script to run successfully, because getting elements geometry in dynamo is soooo slow.
maybe VASA package interpreted the view drawing as a projected image with colours so it can find where is the white space colour?
That’s not really what it is doing, but I guess close enough. The Vasa conversion shouldn’t take long for most views; more likely the delay is in Dynashape.
Keep in mind that you are trying to solve a very complicated problem which is geometric by nature. Many others have tried with AI tools being the most successful I have seen so far.
If speed is the only concern you could reduce calculation time by sticking to the Revit API and building an add-in, but that is a different forum. You might also get sufficient results using just VASA and a nearest neighbor exploration, removing the need for DynaShape. I imagine many views would calculate this way and you might even be able to remove generative design from the mix if you can live with a bit of action during QA (which should be budgeted for even with the most restrictive of toolsets).