Filtering Filters in Revit

The term "Filter" is much used in Revit - and it means different things in different situations.  Filters also follow varied and confusing rules depending on what you are doing.  Below are some of the rules and exceptions:

Coffee Filters

The 'Filter' icon in Revit probably makes good sense to most Americans, but others around the world might be a bit puzzled - it is a historical image, much like the Floppy Disk for 'Save'.

In the USA, coffee filters are still quite common:

Many American restaurants have a coffee filter machine, with a pot of brown liquid sitting on a hot-plate for hours after it has been dripped through a paper filter.

 

In Europe you might find various different machines for making coffee - plungers (French Press) used to be quite popular:

In Greece or Turkey, traditional coffee was made in copper pots.  now of course, there are updated electric versions available.

In Australia coffee-plungers are now a rarity, while filters can only be found in antique and junk shops.  Nothing less than a full-on espresso machine will do in even the smallest cafe.  A restaurant with a coffee filter would be laughed out of town:

There ends the 'Filter' icon history lesson.  I have to say that I do like the coffee filter as an icon because it is neat and distinctive - but it might puzzle the younger generation.  I can't see an espresso machine making a good icon.

Jeff has pointed out that the filter icon is probably derived from laboratory funnel filters - probably true, and much more logical than my coffee filter theory!

Selection Filters

When you select a number of elements in Revit, two Selection Filters icons are activated:

Status Bar Filter Icon

The Status Bar icon (lower right of screen) shows the number of selected elements; and the coffee filter icon, which gives you access to the Selection Filter dialog box.

 

Ribbon Selection Filter Commands

Ribbon Selection Filter commands allow you to:

• Save, Load or Edit element selections
• access to the Selection Filter dialog box

 

This is an invaluable (but underused) tool for filtering down your selection

It is really important to check the selection filter to make sure that you have not accidentally selected partially hidden items (eg. floors, section lines) before you delete, modify or copy them.

View Filters

View filters are created and saved in each project, and can be applied to:

• individual views
• multiple views or
• view templates

View filter rules allow AND and/or OR

• OR filter capability was added to Revit in v2019, which made our lives so much easier
  
• OR filter rules are pure gold (as the French would say)
  

View filters can be used to:

• Hide/show elements (Visibility) or 
• To override their appearance

 Filter Overrides are not part of the View Filter:

• Overrides are part of the view definition - meaning they are tricky to maintain or duplicate
• Overrides can be part of a View Template
  

• One of the annoying restrictions in View Filters is that Shared Parameters created in loadable Families are not available for use in View filters - unless you also add them as Project Parameters - refer to this blog post
  

More on View Filters in another blog post . . . .

Schedule Filters

Schedule Filters are quite different to View Filters in many ways:

• Schedule Filters are an integral part of each schedule - they cannot be separately applied to other similar schedules - this is entirely different and inconsistent to View filters
• However, Schedule Filters can now be included in View Templates that are then applied to multiple schedules (since v2017).
• Be warned that if you create a complex filter as part of a schedule, then apply a view template, your filter could be overridden by whatever is in the template - never to be retrieved.
  

• There is a huge list of system parameters that are not available for use in Schedule Filters - way too many to list here.  Autodesk are slowly adding new ones with each release, but it is a very slow feed, rather like an old-fashioned coffee filter that is clogged up with coffee grounds.
  

• Shared Parameters created in loadable Families are available for use in Schedule filters - this is a good thing (but not consistent with View Filters).

• Schedule Filters do not allow an 'OR' rule - this is a really bad thing (and not consistent with View Filters);  they only allow 'AND' rules.
  

• Schedule Filters have a fixed number of 'AND' rules - currently 7 (this was increased to 7 a few years back).

 

More on Schedule Filters in another blog post . . . .

Browser Filters

Project Browser has its own filtering system:

• It is limited to 3 'AND' rules, which includes some System Parameters and Shared Parameters
  

• A few years back Autodesk added "Family" and "Type" as separate parameters for filtering, which is much better

• Unfortunately the default filter "all" is by the combined "Family and Type" parameter, which cannot be edited - I would prefer the "all" filter to be by "Family" and "Type" as two separate rules.
  

Parameter Search Filters

A few years back (v2017) Autodesk added a new filtering function to a couple of dialog boxes.  They referred to them as "Search" capabilities but really they are just filters - which adds to the confusion.

Global Parameters Dialog Box

There is a 'Search parameters' box at the top of the dialog.

If you type in a word or part of a word, it does not search for parameters containing that (part)word.  What it does is to filter the parameters in the dialog so that it only displays those containing the (part)word in any of the columns (parameter, value or formula);

• Any parameters not matching the filter are hidden
  

I seldom use this capability - partly because the way it was implemented is quite confusing.  No doubt there are people out there who love it!

It can catch the unsuspecting user out - if you don't realise that the focus is in that Search box, and you type something in (say a value that you are trying to input in a parameter), then all your parameters may disappear.  This could be very disconcerting.

I think it would have been easier to understand if the Parameter grouping titles did not get hidden.

Family Types Dialog Box

The same capability is also available in the Family Types dialog in the Family editor (since v2017).

The same gotcha/confusion is also available in the Family Types dialog in the Family editor.

 

 

Shared Parameters in Revit View Filters

Here is another Revit Gotcha for young and old: 

Family Editor Shared Parameters

If you add a new Shared Parameter in the family editor, you might expect that parameter to be available in a project in all situations.  You would be wrong!

Shared Parameters created in the family editor, and then loaded into a project have two entirely different (inconsistent) behaviours:

• In Schedules, the shared parameters will automatically be available to add as fields

• In View Filters, the family shared parameters will not be available to add as fields

This is quite confusing and inconsistent.  It can also catch you out, however experienced with Revit you might be - as I recently discovered when demonstrating how to create View Filters to a client

Schedules

If you create a new schedule  for the category of the recently loaded family, the Shared Parameter is automatically available in the list of available fields - as you might expect:  it is one of their mystical powers.

View Filters

Try the same trick with View Filters and you will probably get a nasty surprise

 

 Workaround

To make the shared parameters available for use in View Filters, you have to add them (again) as Project Parameters.

 

  

 

View Filter

If you go back to the View Filter definition, you will see that the Shared Parameter is now available as a field to be added.

As a BIM Manager, I would once have known about this Revit inconsistency - but I just plain forgot!  There is no way we can remember all of the inconsistencies.  And why should we have to?

Fortunately, Autodesk are slowly addressing some of these irritations - but it is such a laborious process.

Stair Section Detail Level in Revit

Here is yet another problem with Revit Stairs that really needs to be fixed by Autodesk:  

The view 'Detail Level' display in section is not consistent between walls, floors and stairs (not to mention ramps!):

View Detail Level

When a view is set to Medium or Fine detail level, sections of most categories display the correct materials:

When the View detail level is set to 'Coarse', the cut hatching display of some elements is overridden by the Type properties 'Coarse Scale Fill Pattern'

This capability is available only for certain categories - meaning that the display of stairs is pretty hopeless at Coarse scale

 

Workarounds

What to do about this?  There are several possible ways to resolve this lack in Revit, but none is very good!

Visibility Graphics

You can over-ride the cut pattern of stairs - but this requires several steps (excuse the pun) on top of just changing one View Detail Level setting:

Due to the fiddly nature of changing this in the view (similar settings may need to be applied to other categories), you would certainly need to include this as part of a View Template - so it could be applied or removed at the flick of a switch.

Filters

You could also try using a View Filter, as it could potentially be applied to multiple categories

This has an advantage in that it is more "discoverable" than searching through all the category overrides - unless you have a gazillion filters applied!

Another advantage in Revit 2021 is the ability to "Enable" or "Disable" the filter without losing the override settings - a very useful new enhancement for Filters.

Downsides

The View Detail Level is very easy to switch on/off - and it affects all categories that have the built-in Coarse Scale override capability.  If you set the view back to Medium, the 'by category' cut pattern overrides get left behind - so you would need another operation to remove those (hence the need to use View Templates).

Another problem with the Visibility Graphics workarounds is what happens when you choose anything other than black solid fill as your hatching override:

If you make it grey . . .

 

The Stairs will show the joint lines between different materials - you may or may not want this, but it is clearly different behaviour to the Coarse Detail Level control that hides the material join lines and treats it as one material, for a nice clean look.

Of course, this is not helped by the inability to join walls/floors to Stairs !!  You still get the joint lines between those.  Refer to Stair Joint Lines

The Worst Workaround

Filled Regions are extremely useful for patching up Revit's inadequacies, but they are not popular with BIM & Model Managers because they cause so many other problems as soon as a model changes.

Filled Regions allow you to make the hatching look exactly how you want, because they allow some of their edges to be "Invisible Lines" - thus they can appear to join with adjacent "real' cut hatching.

Filled regions are placed per view, so if you have multiple sections cutting through the same or similar parts of the model you may end up with many filled regions.

One possible method to manage that problem is to include them in 'Detail Groups' - but they are also problematic to manage, not to mention a major shortcoming of really slowing down your Revit model if you have too many of them.

Conclusion

Whichever workaround you use the most important thing to do is to follow company standard procedures - and be consistent.  Agree with your workmates on which dodgy workaround to use, and stick to it.  This will make it so much easier to come back to make changes when the model is updated.

Slanted Wall Joins in Revit 2021

Following on from my Analysis of Slanted Walls in Revit 2021, and Analysis of Slanted Walls and Rooms in Revit 2021 let us see how it handles slanted wall joins in plan.

Mysterious Behaviour

I have not yet figured out the rule for this, but it seems that slanted walls sometimes join properly in plan and sometimes not . . .

The failure of wall layers to join seems to occur at varying wall angles and different view range cut heights.

At gently slanting angles the problem does not manifest itself:

• At 25 degrees (or less) with a standard wall cut height of 1200mm (or 4 ft for the imperialists), the wall joins ok
  

• Bump the slant angle up to 30 degrees and it fails
• In this example the base offset of the wall is raised 900mm above the Level that it is hosted on - that causes all kinds of issues, but it is not the problem here

• Change the 'View Cut Plane Height' to 1000mm, and it works again - but of course the cut location of the wall changes

• Change the angle to 45 degrees and it breaks again
• It seems that the base height of the wall has no influence on this (providing it is below the cut height).
  

There must be some mysterious formula that combines the cut plane height with the wall slant angle that makes it work or fail!

Of course it should not fail at all - why doesn't it just work as expected?

Talking of "Course", this problem doesn't show up in Coarse views - only Fine and Medium detail levels.

Which Kind of Callout to Use in Revit

Previously I have written about some of the limitations and inconsistencies with Revit Callouts:

• Weird rules for 'Reference Other View' Callouts
  

• Weird rules for Real Callouts

• Callout Crop-Boundary Mismatch

• Detail Plan Callout Views & Stair Path Arrows

• 3D Stair Plans in Detail Views

• Reference Label

There are some strange and frustrating restrictions, which mean you need to carefully plan how to manage Callouts.

Here I am going to describe the different ways to make Callouts in Revit, and propose a method of working that is different to the way Revit was designed, and probably different to how you use them.

Which Kind of Callout to Use?

1. Real Callout

The standard ‘Callout’ command places a rectangle defining the callout view extents. This will create a new view, and place the view reference rectangle on the active view. For reasons listed below, this method is not preferred.

• You cannot change the reference.

• You cannot move the callout to a different parent view.

• You cannot change the callout view family between Plan/Detail (Plans only).

• The callout rectangle can be stretched or rotated in the parent view – this will make the same change of extents or rotation to the callout view itself, which is not always desirable.

• You cannot have the callout extents slightly different on the parent view (to make callouts readable) - they have to match the view cropping exactly.  Refer to Callout Crop-Boundary Mismatch.

• If you copy and paste a Callout it creates an entirely new view with a different reference.

For more information see rules for Real Callouts

2. Reference Other View

Reference Other View Callouts can be created by:

• Create a view to be referenced by the callout – eg. duplicate another view and crop it

• Make sure the view is cropped (unless it is a drafting view).
  

• On the view to place the callout, select the ‘Callout’ command, then select ‘Reference Other View’, and select a relevant view name from the drop-down menu

This method has many advantages:

• Callouts can be moved to another view
• Callout references can be changed to refer to different view
• References will update if the view/sheet number is changed
  
• Callouts can be copied to another parent view

It also has a few disadvantages:

• It is possible for the user to select the wrong view in the list - there is no automatic check for this.
  
• If you want to have "Sim" showing on a callout for similar details on multiple callouts, that is a Type property of the view being referred to, not a property of the callout symbol. 
  
• That means it is all or nothing - ie. all instances of the callout must have "Sim" or not. 
  
• It also changes the view type so it may move in your project browser, depending on your browser organistion.
• You have to manually create each callout view (by Duplicate or Duplicate Dependent); then crop that view - this is a small price to pay for the benefits.
• You could probably automate this using Dynamo.
  

For more information see rules for 'Reference Other View' Callouts

3. Intersecting Views

Section callout symbols can be created automatically by Revit in section views – this occurs when one section has its extents completely within the larger section (both crop boundaries and clipping extents).
I would not recommend trying to use this method:

• It is very confusing for users - it is better to stick with one Callout method for consistency.
  

• Such callout sections may appear/disappear as view extents change

4. Fake Callouts 

Last and very much least, is a method that you should never, never use - but I've seen it often.

Fake (or dummy) view callout references can be made out of detail components or detail lines and text. This is very bad practice:

• These may look like genuine Callouts, so people may not check the references. 
  

• References will not update if view/sheets are changed.

• This is totally against everything that Revit is trying to do!

Workflow Opinions

The following are my recommendations for working with Callouts in Revit.  Please note that these are opinions only - it is up to you to look at all the reasons I have given, and make up your own mind about this.  I accept no blame if it does not work for you.

One: All Callouts by 'Reference Other View'

Use method 2 (Reference Other View) for every single callout in your project.

If you never use methods 1 (Real Callouts), 3 (Intersecting Views), 4 (Fake Callouts), you will ensure consistency and will avoid most of the problems related to Callouts.

Two: Do Not Use Detail Views

Avoid using the Revit view family of 'Detail Views' - these have so many limitations and quirks, it is just not worth it.  Always use Plan views or Section views.  Refer to Detail Plan Callout Views

NB. If you follow the first recommendation above, this will not be an issue because it is only possible to create new detail views by Real Callouts.

Three: No Fakes

Never, never, never, never, never, never, never, never, never, never use method  4 (Fake/dummy Callouts).  It is much quicker and safer to use 'Reference Other View' callouts.

Anyone who does this in Revit should not be using Revit at all !

Reference Label

There is one problem with using only 'Reference Other View' - refer to 'Reference Label'

Feedback

I would be very interested to hear whether anyone has different (or the same) opinions about using Callouts - feel free to comment.