Point Cloud File Formats Explained: E57, RCP/RCS, and LAS/LAZ

If your BIM coordinator just received a hard drive from a field capture crew and your Autodesk Revit modelers cannot link the raw scan files before a design development deadline, the deliverable was exported in the wrong point cloud format. Request RCP and RCS files when your design team works inside Autodesk Revit, AutoCAD, or Navisworks Manage, specify ASTM E57 when you need a vendor-neutral archive or work across platforms like Leica CloudWorx, and ask for LAS or LAZ when your civil engineers need classified terrain data in AutoCAD Civil 3D. Specifying the file extension and internal scan structure before capture prevents days of conversion delays.

When should you request E57 instead of proprietary formats?

Request the ASTM E57 format whenever you need a vendor-neutral master archive, work in non-Autodesk software, or require spherical panoramic imagery alongside 3D geometry. Standardized under ASTM E2807, E57 is a compact, open file structure supported by almost every terrestrial laser scanning and BIM platform.

When FieldScan captures a commercial building with a Leica RTC360 at +/-2 mm accuracy and registers the dataset in Cyclone REGISTER 360, exporting a structured E57 preserves each tripod setup location, laser intensity values, RGB color, and high-dynamic-range panoramic photos. Keeping station positions intact is necessary if your drafters use Leica CloudWorx for Revit to view crisp 360-degree photographs while tracing overhead conduits and piping. On sites with reflective glass curtain walls or wet polished concrete floors, laser multipathing creates stray noise points that appear to float behind the glass surface. Having a structured E57 allows a modeling engineer to isolate and toggle off specific tripod setups where a reflection occurred, rather than deleting clean geometry from adjacent rooms. Because ASTM E2807 is non-proprietary, storing an E57 copy on your server ensures you can reopen the project years later without maintaining a specific software subscription.

Why do Autodesk Revit and Navisworks teams prefer RCP and RCS files?

You should request Autodesk ReCap formats (RCP and RCS) when your architects and MEP engineers link point clouds directly into Autodesk Revit, AutoCAD, or Navisworks Manage without third-party plugins. Native Autodesk tools cannot link an E57 or LAS file directly into a model without first indexing the data through Autodesk ReCap, a conversion step that ties up an engineering workstation for hours on a large commercial floor plate.

A ReCap deliverable consists of two linked components that must stay in the same folder hierarchy: a lightweight RCP project file and an adjacent support folder containing the heavy RCS scan files. The RCP file acts as an XML pointer storing coordinate systems, limit boxes, and scan regions, while the RCS files hold the spatial point octrees and RealView panoramic bubbles. Along long office corridors with uniform drywall and acoustical tile ceilings, registration drift can accumulate if scans lack tight overlap and target constraints. In Cyclone REGISTER 360 PLUS, we verify loop closure before exporting the native RCP dataset so your Revit team never has to re-index drifting walls. In the office, the most common handover failure happens when someone copies the small RCP file alone without the adjacent support folder of RCS files, causing Revit to display an unresolved path error.

RCP and RCS files are the wrong choice as your sole archive or when sharing data with subcontractors running Archicad, Tekla, or Bentley software, because the proprietary wrapper locks out non-Autodesk tools. Send us your CAD and BIM software list along with your floor plans, and we will configure our 3D laser scanning deliverables so your team can link the point cloud the morning it arrives.

When are LAS and LAZ the right choice for site and civil work?

Ask for LAS or its lossless compressed counterpart, LAZ, when your civil engineers are importing aerial LiDAR, photogrammetry, or outdoor topography into AutoCAD Civil 3D or GIS platforms. Maintained by the American Society for Photogrammetry and Remote Sensing (ASPRS), the LAS specification stores point classification tables that interior architectural formats ignore, separating bare-earth ground points (ASPRS Class 2) from vegetation, vehicles, utility lines, and building roofs. When we run FAA Part 107 compliant operations for drone surveying and inspection using DJI Enterprise drones and Pix4Dmapper over sloped parcels, dense coastal scrub or tree cover in San Diego canyons often hides the true grade. Classifying the LAS dataset lets civil engineers turn off the vegetation layer in AutoCAD Civil 3D to generate an accurate surface tin from the remaining ground returns. Because uncompressed LAS files occupy significant disk space, requesting LAZ provides the same coordinate precision and classification tables in a smaller file package that transfers quickly and opens directly in modern civil platforms.

How do structured and unstructured point clouds change your modeling workflow?

Beyond the three-letter file extension, deciding whether the exported point cloud is structured (gridded by setup) or unstructured (unified into one cloud) dictates both workstation speed and whether your drafters can view 360-degree site photographs. When a terrestrial scanner like the Leica RTC360 or Leica BLK360 captures a mechanical room from twenty tripod positions, adjacent scans overlap and record the same pipe walls multiple times.

• Structured point clouds (setups retained): Preserves the spherical scanner grid from each tripod position, retains panoramic photo bubbles, and allows selective hiding of individual setups, resulting in larger files with overlapping points on shared walls.
• Unstructured or unified point clouds (merged grid): Fuses all tripod setups into a single homogeneous cloud and applies spatial decimation (such as a 3 mm or 5 mm point spacing grid) to remove duplicate points, keeping Revit viewports responsive on mid-range computers while stripping out station photography.

If your team is modeling a complex central plant in Autodesk Revit 2025 or 2026, request both versions. Drafters load the lightweight unified RCS file for fast geometric tracing while keeping the structured E57 or RCP open on a second monitor to inspect panoramic photos of valve tags and hanger connections.

When should you skip raw point cloud files and order a BIM model instead?

Ordering raw E57, RCP, or LAZ point clouds is the wrong choice when your architectural or engineering staff lacks high-RAM workstations, dedicated solid-state storage, or daily experience modeling against dense LiDAR data. Even a unified point cloud for a 50,000 square foot (4,645 sq m) commercial building requires dozens of gigabytes of local drive space and a dedicated graphics card to pan and slice smoothly. Above-ceiling plenums on renovation sites often have partial occlusion from insulation batts or tight ductwork where the laser beam only hits the bottom half of a pipe. An inexperienced drafter tracing an unfamiliar point cloud can misinterpret shadow gaps or pipe insulation thickness, introducing dimensional errors into the permit set.

When your design team needs clean parametric geometry ready for construction documents rather than millions of raw coordinates, skipping the point cloud handover in favor of our scan-to-BIM modeling services removes the hardware bottleneck. We convert the registered LiDAR dataset directly into native Autodesk Revit models at LOD 200 through LOD 500 using Leica CloudWorx for Revit and Navisworks Manage, delivering verified models in two to four weeks for typical mid-rise commercial buildings. FieldScan captures existing conditions across Southern California, serving all of San Diego County, with projects across Orange County, Riverside County and the Inland Empire. Send us your building address, approximate square footage, and target design software, and we will reply with a capture plan and the exact deliverable formats your project requires.