Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
there is something annoying that makes many of my colleagues create a "legend" phase for just for legend purpose.
For instance, we can tag material and layers on a wall composition , but why couldn't we dimension the overall width or even tag the typeMark of the wall?
Tags cannot be exposed unless you have an element to tag. As a BIM manager, I want to see all my tags without bringing in useless elements in my standards file. More importantly, we want to show tags in our legends without having to manually duplicate and maintain as up to date symbols.
To achieve a proper smart BIM workflow, I propose the two following capabilities:
Allow us to place tags in Legend views
Allow us to easily maintain a relationship between tags and their respective symbols.
Perhaps every tag is automatically converted as a symbol or there is a functions to do so.
If we could place tags in legends, we would probably not really need the symbol version except for old users who still think in CAD and use symbols to hide all the CAD mistakes they did in Revit.
It is amazing how little code is required to implement this, AutoDesk should fire a strategist and hire a coder to work on little stuff like this, they could knock out implementation of ideas like this at a rate of a couple a week (including setting up unit tests) and end up with annual releases that we look forward to rather than have to buy only because we're on subscription and can't save down.
Also I was able to extend the original idea to aggregate data from all instances and their hosts so I can tag my doors and windows on a legend sheet with a list of fire ratings of the walls they are in.
Text boxes are just not BIM. Why have the possibility to drag a family as a representation in a legend when you can't tag that representation. Quite non-intuitive if you ask me.
When using legend components to document your design: You cannot dimension to host components, such as walls, ceilings, and floors. This needs to be made available.
This has to be the biggest overlooked development opportunity in Revit so far regarding architects at least. And specifically door/window drawings.
Archicad seems less typebased and thus slightly better in earlier phases of a project. As the project develops Revit pulls comfortably ahead expect on one thing. Revit has a great type system but cannot document the types properly.
Looking at this very rationally and professionally, during the last 10 years, deciding not develop the ability to document types is just an error of jugdement. Simple as that. You have Assemblies but those are unusable for Door/Window drawings for a number of reasons. (One being they disappear when the last instance is removed)
Legend components is the logical choice but you cannot tag the information they have.
So the core of the issue is to create type drawings incl type data.
Seems so obvious right ?
Except using Revit you cannot do it.
Archicad can do it and is very very good at it.
Putting a normal Door tag on a Door component in a legend view seems to be one logical path forward.
Creating Assemblies directly from a type (no instance involved) could also do it i suppose.
But seriously come on, something needs to happen here.
Just want to add some more information to my original post here.
Here is a few examples on whats needed from electrical and architectural. All disciplines need it in some way.
Example using Lines, Legend Components and Text.
(It could have been just one Tag getting the information.)
Then you might say.."hey what i minute we can do that with the Type Image parameter in a schedule". We tried that and even made a function to update those images. But its not usable because you cant align the text vertically to the image. (vertical middle) This is how a Revit schedule will look today with the Type Image parameter:
Then you have architects who needs Door/Window Drawings. Which can look like this but can have numerous layouts. (Which a Door Tag will solve) Again - this could be a Door Tag - just let us tag it.
We have been using secondary design options sometimes to make those. Design Option because you can use tags. Secondary because they dont show in regular schedule quanitites.
So another idea is to make the "secondary design option functionality" available as something else. Like a category-specific virtual design / documentation space with an API that to support it. (Currently there is no API support for Design Options.)
This is low hanging fruits with large benefits.
More or less use what you have with some changes.
So all in all four ideas that will get us closer to doing this:
1. Standard category tags in legend views.
2. Create Assemblys directly from Type geometry. (No instance involved)
3. Vertically align text in a schedule (wont solve everything but its a good start)
4. Secondary design option-ish documentation space incl API support.
