This thread and the work around (placing unwanted levels in a separate workset to control visibility) is very useful and addresses the over-abundance-of-levels enthusiasm that seems to affect early revit projects. A must read. thanks!
|
|
|
This thread and the work around (placing unwanted levels in a separate workset to control visibility) is very useful and addresses the over-abundance-of-levels enthusiasm that seems to affect early revit projects. A must read. thanks!
This thread brings up bad memories of ugly Revit models and days and days of workset cleanup and level issues, lol...
LOL! Same here After all this time, I still don't have set rules as to how many. As long as you have a good reason for creating a level, it's fine to do that. But try to keep them to a minimum. It's really all about anticipating how the project might change during design; about managing change. If a certain building block might need to move due to the structure getting deeper etc., than it makes sense to create a few extra levels so you can make changes easily by moving the level up and any plan views with that associated level keep on working as before (which wouldn't be the case if things move upwards and now your cut plane is too low!). Another example of a good reason to create extra levels is managing parapet heights.
If you are using "phantom" levels for reference or to attach things to you might want to consider using reference planes instead. Elements can be attached or aligned & locked to the ref planes and you won't end up with as many superfluous levels to manage.