- Privacy Policy
- Data Processing Agreement
- Data Security Policies
- Terms of Use
- Site Map
- ©2023 Ideate Software
Support
- Ideate Automation
- Ideate BIMLink
- Getting Started
- Using Ideate BIMLink
- Working in Excel
- How to...
- Create NEW Elements
- Manage Sheets and Revisions
- Create a Model Health Check
- Use Ideate BIMLink for Quality Control
- Manage Key Schedule Data
- Manage Project Standards
- Set Up Projects
- Utilize Type Swapping
- Manage Calculated Values
- Leverage Linked File Data
- Assign Space Types
- Construction Tasks
- Use Ideate Sticky with Ideate BIMLink
- Export Links Into the Same Excel File
- Video Examples
- Customization
- Automation
- Troubleshooting
- Ideate Explorer
- Ideate Sticky
- IdeateApps
- Getting Started
- Ideate ReNumber
- Ideate QuickSelect
- Ideate SmartDelete
- Ideate XRay
- Ideate SpellCheck
- Ideate Annotate
- Ideate Sheet and View Tools
- Customization
- Troubleshooting
- Automation
- Ideate StyleManager
- Getting Started
- Using Ideate StyleManager
- How To...
- Automation
- Troubleshooting
- Ideate Software Platform
- Licensing
- Download Latest
How to Use Ideate Annotate for Revit
Topics in this Section
Manage Clashes ▲ ▼
Clash Sensitivity
Annotation Clash issues reported within the Review tab of Ideate Annotate represent conditions when various Revit annotation elements such as Tags and Text or Text and Dimensions overlap. The Clash Sensitivity setting controls the degree to which the bounding boxes of these elements overlap. When the slider option is set to 100, which is at the right edge, the clash must be 100%, meaning the one element must be fully within the other element. This setting would result in the fewest number of clash results. When the slider is all the way to the left the elements only need to have more than a 0% overlap to be considered a clash. This setting will result in the most results, many of which may not seem valid as shown between these two text boxes.
The size of the bounding box is often determined by the overall size of all elements within a custom annotation family, including elements that may not be visible (reference lines)
Avoid Tagging Nested Families ▲ ▼
The sample tag rule called Structural_Foundations is designed to avoid tagging any nested families. The out-of-the-box Revit Tag All is shown below in black, with all pile caps also being tagged.
The Ideate Annotate method only tags the cap, and not the piles-resulting in a cleaner outcome.
In this rule there are two filters, one called Is Nested and another for the Phase sequence. Use Is Nested=False to avoid tagging any shared/nested family content. If you use more than one filter you should also review the Elements Must Pass All Filters checkbox, as shown in yellow. Typically this should be checked to ensure that all listed filters must be true.
Learn more: Customizing Tag Rules
Top of Page ▲