Revit Tip: Crop point clouds to optimize Revit performance

Point clouds are essential for as-built accuracy, but they can overwhelm Revit views. Strategic crop regions are the quickest way to boost performance without sacrificing fidelity where you need it.

• Link, don’t import: Use Insert > Link Point Cloud (RCP/RCS). Keep the source in a controlled folder. If you need software or guidance on licensing, connect with NOVEDGE.
• Put the cloud on its own workset: Create a “Point Cloud” workset so you can toggle or unload it in heavy views. This pairs well with view templates.
• Crop in 3D with a Section Box: In a 3D view, enable Section Box and tighten it around the area you’re modeling. This dramatically reduces the visible point count and GPU load.
• Crop per-view in 2D: In plans, sections, and elevations, select the point cloud and use the contextual Crop tools. Draw a polygonal crop to isolate just the working zone. Use Invert to keep outside areas when needed, and Reset when you change scopes.
• Drive consistency with Scope Boxes: Assign a Scope Box to 3D views to standardize the Section Box extents across multiple coordination views.
• Template it: Create view templates that lock point cloud display settings (visibility, color mode, density). Apply the template to production vs. coordination views for predictable performance.
• Tune display for speed: In the point cloud’s Properties, use a simple color mode (Single Color or Intensity) and lower Density for navigation views. Save higher density settings for detail checks.
• Coordinate first, then crop: Align the cloud using Shared Coordinates so crops are meaningful across disciplines and linked models. Once registered, your crops will remain consistent project-wide.
• Break up mega-clouds: If the source is massive, split regions in Autodesk ReCap before linking. Smaller, task-based RCS files—then cropped in Revit—perform best. If you need ReCap or add-ons, check out NOVEDGE.
• Use view purpose: Keep cropped, lightweight clouds in documentation views; reserve uncropped or higher-density versions for dedicated coordination views.
• Print/export only what’s needed: Revit prints and exports what’s visible. Cropping the cloud cuts down on raster time and file size.
• QA pass: Periodically audit views for oversized crops. Tighten them as the modeling focus shifts to keep navigation snappy.

Pro workflow:

• Start with a dedicated 3D “Coordination – Cloud” view (Scope Box + Section Box).
• Create floor plan templates with point cloud visibility On but density reduced and tightly cropped.
• Build detail verification views with higher density and micro-crops around critical elements.

Common pitfalls to avoid:

• Assuming crops are global—point cloud crops are view-specific.
• Leaving clouds visible at full density in sheeted views.
• Skipping worksets, making unload/reload management painful.

Bottom line: Crop early, crop often. Pair crops with templates, scope boxes, and disciplined display settings for smooth navigation and clean sheets. For tools, licensing, and expert advice across BIM workflows, visit NOVEDGE.