Trying to import a LiDAR scan into Revit, but the file is massive. It’s slowing everything down!
Handling large LiDAR files in Revit or AutoCAD can be challenging, but there are a few techniques to make it more manageable. We typically decimate point clouds before importing, which helps reduce the file size without compromising accuracy. Segmenting the scan into smaller zones also makes it easier to work with, especially when collaborating across teams. Another useful approach is cloud storage—we utilize BIM 360 and Autodesk Cloud to store and process large files efficiently without overloading local systems. For a recent MEP project, we converted the scan into Revit meshes and parametric models, making the integration seamless and lightweight. What’s your current workflow? We’d love to help you streamline it!
Comments
-
Totally agree that handling large LiDAR files can be a bottleneck if not managed properly. We've found similar success with decimating point clouds prior to import; it really helps balance performance and accuracy, especially on larger industrial or MEP projects.
Segmenting the scans by zones is also something we use frequently, particularly when different teams are working on separate floors or systems. It keeps file sizes in check and improves collaboration efficiency.
One additional technique we've implemented is using Leica Cyclone REGISTER 360 for preprocessing and clean-up before bringing the data into Revit or AutoCAD. It helps us align scans properly and export in optimized formats like RCP or RCS for smoother performance.
For Revit integration, we often convert high-density scan areas into parametric families or 3D solids only where needed, while keeping the rest as lightweight point cloud references. This hybrid approach gives us flexibility without bogging down the model.
We’re also exploring automation tools and Dynamo scripts to further streamline workflows like clash detection and element extraction.
Thanks,
Matt0
