Point Cloud Data
Best Point Cloud File Formats
Compare point cloud file formats—E57, LAS/LAZ, RCS/RCP, PTS, and native vendor files—for Scan to BIM exchange, archiving, and Revit workflows.
BimzstudioJun 25, 202512 min
file-formatsE57
Point Cloud Data
Compare point cloud file formats—E57, LAS/LAZ, RCS/RCP, PTS, and native vendor files—for Scan to BIM exchange, archiving, and Revit workflows.
Choosing a point cloud format is a project decision with cost and risk attached. The wrong choice creates broken Revit links, multi-day file transfers, lost intensity data, or archives nobody can open in five years. This article compares the formats Scan to BIM teams actually use—E57, LAS/LAZ, PTS/XYZ, Autodesk RCS/RCP, and vendor natives from Leica, Faro, and Trimble—and recommends when each belongs in a Europe or USA project pipeline.
Pair with Point Cloud to Revit Workflow Explained for the Autodesk modeling path.
Point clouds are big. Formats exist to balance interoperability, compression, structure, attributes, and software performance. Problems arise when:
| Need | Better format tendency |
|---|---|
| Open exchange between firms | E57, LAS/LAZ |
| Autodesk Revit / ReCap performance | RCS + RCP |
| GIS / wide-area LiDAR | LAS/LAZ |
| Quick ASCII debug | PTS/XYZ (small sets) |
| Vendor advanced workflows | Native Cyclone/SCENE/RealWorks |
| Long-term archive | Open format + documented CRS |
There is no single “best” format—only best for a stage.
Ecosystem lock-in. Teams live inside one vendor’s tools and treat natives as deliverables.
Email-era habits. People still try to send giant clouds like PDFs.
Attribute ignorance. Intensity, RGB, classification, and GPS time matter differently to different users; formats handle them unevenly.
Version drift. ReCap project files reference RCS paths that break when folders move.
Compression myths. “Lossless” and “good enough for modeling” are different conversations.
Spec laziness. Contracts say “provide point cloud” without naming format, structure, or metadata.
EU multi-party renovation (architect DE, MEP NL, surveyor PL). E57 used as contractual exchange; each party converted to working formats (RCS for Revit shops, vendor natives for survey QA). Avoided forcing one commercial license on all.
US DOT-adjacent building + site. LAS/LAZ for exterior corridor tied to civil; RCS for interior Scan to BIM. Dual delivery matched two industries’ norms.
Hospital FM archive in Sweden. After modeling, client stored LAZ + E57 plus metadata JSON for CRS and registration report—not only the RVT. Future re-modeling possible without original SCENE license.
Retail rollout USA. Central ReCap cloud (RCP) shared via Autodesk ecosystem for speed; E57 still required at handover for non-Autodesk stakeholders.
Industry-neutral exchange widely supported. Stores points and often imagery/attributes in a structured way. Excellent for contractual delivery between organizations. Not always the fastest working format inside Revit—convert/index for production modeling.
Use when: multi-vendor exchange, archive, specification compliance.
ASPRS LAS is the workhorse of airborne and many terrestrial GIS pipelines. LAZ compresses LAS efficiently. Classification fields are first-class. Great for large outdoor sets and civil coordination. Building interior Scan to BIM teams use it less as a daily Revit link format, more as exchange/archive.
Use when: civil/GIS interoperability, compressed archives, classification workflows.
RCS = indexed point cloud engine file. RCP = project file referencing one or more RCS. Revit links these efficiently. This is the practical production format for Autodesk-centric Scan to BIM.
Use when: Revit/Navisworks production; Autodesk collaboration.
Watch-outs: Keep relative paths intact; deliver RCP with all RCS; version carefully.
ASCII or simple formats. Universal but bulky and slow. PTX may preserve scanner station structure useful for some registration forensics. Fine for small clips, teaching, or debugging—poor as primary delivery for whole buildings.
Leica Cyclone / LGSx ecosystems, Faro SCENE projects, Trimble RealWorks, etc., preserve setup hierarchy, targets, and processing history. Best for registration QA and resurvey. Poor as the only deliverable if the client lacks licenses.
Some teams exchange pods, RCP unlocked packages, or proprietary streaming formats for web viewers. Treat viewers as communication layers; keep an open archival format underneath.
Regardless of extension, document:
buildingSMART and ISO 19650 thinking applies: the information container needs context, not only bytes.
| Format | Interoperability | Revit speed | Compression | Best role |
|---|---|---|---|---|
| E57 | High | Medium (after convert) | Moderate | Exchange/archive |
| LAS | High (esp. GIS) | Low–Med | Low | Exchange |
| LAZ | High | Low–Med | High | Archive/exchange |
| RCS/RCP | Autodesk-centric | High | Engine-optimized | Production |
| PTS/XYZ | Universal | Poor | Poor | Debug/small |
Project_Floor_Zone_v03.rcs patterns.Who opens the cloud? Revit modelers, civil GIS, owner FM, future unknown?
Field native → registered master → exchange → production index → archive.
Often vendor tools or specialized register packages. Export a master.
E57 and/or LAZ with attributes retained. Verify unit scale with a known distance.
Import to ReCap, region by floor, save RCP/RCS for Point Cloud to Revit work.
Noise reduction on copies (Noise Reduction Techniques). Bump versions.
Folder structure, hashes if required, QA PDF, coverage maps.
Open in Revit, Navisworks, and one non-Autodesk tool if E57 was promised.
Confirm all RCS present, paths relative, metadata complete.
Store open + native + reports. Do not rely on a single cache disk.
Project: Courthouse renovation, US Northeast
Stakeholders: County survey GIS group (LAS-centric), architect (Revit), specialty steel detailer (Navisworks), owner archive.
Initial failure: Survey uploaded only SCENE project to a portal. Architect could not open it. Two weeks lost arguing licenses.
Fix: Contract addendum required:
Outcome: Modeling started within days of re-delivery. Steel detailer used Navisworks with the same RCP. Three years later, a new elevator study reopened the E57 successfully without SCENE.
Format planning was cheaper than the delay.
Ask four questions in order:
E57 remains the practical open exchange for building reality capture. It can carry structured scan data and imagery depending on exporter settings. Always verify units after import (a classic failure point), whether images were included when the contract required them, that the registered assembly—not raw unaligned stations—was exported, and file integrity via size sanity checks and opening in a second tool.
LAS/LAZ excel when classification and GIS workflows matter. For interiors, they work but may feel unnatural to building teams used to station-based projects. LAZ compression makes overnight transfers feasible. Preserve intensity when metal QA or AI classification is planned. Confirm whether your pipeline writes LAS 1.2 vs 1.4 fields your consumers expect.
Autodesk ReCap indexes clouds for performance. RCP is the project glue. Delivery mistakes to avoid: sending RCS files without the RCP, breaking relative paths by flattening folders, forgetting support files after zipping, and mixing unlocked/legacy formats without testing the client's Revit version. Create floor/zone regions so modelers can isolate worksets of reality. That is often a bigger productivity win than changing format again.
Leica, Faro, and Trimble native projects preserve targets, setups, and processing history better than flattened exchange files. Keep them even when the client never opens them. Future dispute resolution and partial re-registration depend on that history. Contractually, natives can remain surveyor-held while E57/RCP are client deliverables.
Budget storage early. A hospital campaign can exceed several hundred GB across raw, registered, and indexed derivatives. Policies that keep only RCP without open archive create future lock-in. Policies that keep every intermediate without naming authority create confusion about which file is truth. One accepted registered release plus raw archive plus production indexes is a sane default.
Cloud streaming and reality-capture platforms will reduce local file anxiety, but contractual archives will still need open formats. Expect wider LAZ and E57 retention even when daily work happens in vendor clouds. AI pipelines will demand consistent attribute schemas—intensity, normals, confidence—pushing teams to stop discarding fields during conversion.
OpenBIM programs will keep asking for IFC models; clouds will remain companion evidence. Format literacy stays a core Scan to BIM skill.
Format conversions are where silent unit and CRS errors appear. After every major export/import, measure a known baseline in the destination software. If a 10 m corridor becomes 10,000 mm incorrectly labeled—or becomes 32.8 ft without anyone noticing—the rest of the project inherits the lie. Keep a conversion log: source format, tool, version, units in, units out, CRS statement, operator, date.
Watch for clipped regions that disappear during conversion, intensity stripped to save space, and RGB present while geometry was decimated. When delivering to Autodesk ecosystems, open the RCP on a machine that is not the authoring workstation. When delivering E57, open it in a second vendor tool or CloudCompare. When delivering LAZ to GIS stakeholders, confirm the EPSG code loads correctly in their environment.
Finally, teach project managers that “the point cloud” is a package, not a single attachment. A zip that breaks relative RCS paths is a failed delivery even if every byte arrived. Pair this discipline with the modeling workflow in Point Cloud to Revit Workflow Explained.
RCP/RCS via ReCap is the practical best for performance and linking.
E57 is the usual open choice; LAZ is strong when GIS/classification matters and size is critical.
It works, but many building workflows prefer E57 exchange + RCS production. LAS shines outdoors/civil.
Only if visualization or certain classification methods need it. Geometry QA often uses intensity/mono.
Conversions should preserve coordinates; verify with check distances. Poor settings can resample or clip.
Fine as working caches inside a tool. Pair with open archive for handover.
No. IFC carries modeled BIM. Clouds remain the evidence. See also Complete Guide to Scan to BIM.
Clean before final exchange when possible; document filters applied so others do not double-process destructively.
For a typical Autodesk-centric renovation in Europe or the USA, a robust default stack is:
Deviate from this stack only with a written reason (for example, pure civil corridor with no Revit scope). Defaults prevent the most expensive format fights: the ones that start after modeling has already begun.
<!--expand17-formats-->Choosing a format is necessary but not sufficient—packaging discipline is what keeps Scan to BIM schedules predictable.
The best point cloud file format depends on the stage: natives for registration depth, E57/LAZ for open exchange and archive, RCS/RCP for Autodesk production speed. Specify dual deliveries, document CRS and residuals, and test-open packages before you call the survey complete. That discipline prevents the most expensive “format problems”—which are usually planning problems in disguise.
Bimzstudio consumes production-ready clouds and delivers accurate Scan to BIM models with QA/QC and LOD 100–500 clarity for EU and USA clients. If your files are ready for modeling—or you need help defining deliverable packages—see Point Cloud to BIM and Point Cloud to Revit.
Continue with the related service, or request a scoped proposal if you already have a brief.
Point Cloud to Revit Workflow Explained
A production Point Cloud to Revit workflow—from ReCap linking and shared coordinates to modeling, QA, and clash-ready exports for as-built BIM.
LOD 100 to 500 Explained: How to Specify BIM Detail That Teams Can Deliver
LOD 100 to 500 explained for owners and BIM teams: what each level means, how to specify tolerances, Scan to BIM implications, and QA/QC acceptance criteria.
Scan Registration Challenges
Solve scan registration challenges—drift, weak overlap, hybrid TLS/mobile seams, and QA—for accurate point clouds and Scan to BIM success.
| Native vendor | Low–Med | N/A | Varies | Registration QA |
Owner-confirmed studies that already list this service — visual delivery evidence, not invented metrics.
1105 Lakewood
A Point Cloud → BIM comparison of 1105 Lakewood. The scan and the BIM model share the same viewpoint so the existing condition can be read against the modeled geometry.
18 Grand Avenue
Residential Scan-to-BIM work for 18 Grand Avenue. Cutaway and plan views compare existing-condition scan data with the BIM model. Exterior stills are shown independently and are not used as a slider pair.
Foyer Soleil – Résidence Les Marronniers
Residential BIM for Foyer Soleil – Résidence Les Marronniers. A plan-view scan overlay can be compared with the BIM layout. Exterior elevations are shown as BIM drawings, not as a point-cloud slider.
Telecom Infrastructure As-Built Modeling
As-built BIM for a building with rooftop telecom equipment. The axonometric pair compares an existing-condition capture with the BIM model of the same volume. Façade stills are shown independently.
Language
