The short comparison
E57 is commonly used as a vendor-neutral exchange container for 3D imaging data. RCP/RCS is Autodesk’s indexed point-cloud ecosystem: an RCP project can reference one or more RCS files prepared for supported Autodesk applications.
Neither label completely describes the handoff. A receiving team still needs to know the coordinate basis, units, structure, imagery, segmentation, file size, software version, and how the export was tested.
When E57 is useful
E57 is often selected when data must move between different vendors or remain less dependent on one authoring platform. Depending on the source and exporter, an E57 may carry point coordinates, intensity, color, scan poses, and other structured information.
Practical advantages can include:
- a broadly recognized exchange path;
- preservation of individual scan structure in supported exports;
- movement between processing, visualization, and authoring tools;
- a useful archival or intermediary handoff when the project defines what must be retained.
The format name does not guarantee that every exporter and importer handles every field the same way. Test representative data when scan origins, imagery, normals, intensity, classifications, very large coordinates, or other attributes matter.
When RCP/RCS is useful
RCP/RCS is often selected when the recipient works in Autodesk software that can attach or consume ReCap-indexed data. Indexing can improve the receiving workflow and package one or more scan files through a project reference.
Important distinctions:
- an RCP is a project file that can reference scans and project organization;
- an RCS is an indexed scan file;
- the package may contain multiple files and dependencies;
- behavior depends on the Autodesk application and version receiving it.
Do not assume that sending a lone RCP file sends the referenced data. Deliver and test the complete agreed package.
Coordinates can be the real problem
Format conversion does not solve an undefined coordinate system. Large geospatial coordinates may challenge some modeling tools. Moving data closer to a local origin without a documented transformation can make the model easier to navigate while severing the agreed spatial relationship.
Before export, confirm:
- source and target units;
- local, project, or geospatial coordinate basis;
- orientation, vertical basis, and origin;
- transformations or offsets;
- whether the recipient needs absolute position, relative fit, or both;
- how the receiving application manages shared coordinates.
Unified cloud or structured stations?
Some workflows need individual scan positions and panoramic navigation. Others need a unified, cleaned, or segmented point cloud. Reducing everything to one cloud can simplify use but may remove station-level organization or scanner-view functionality. Preserving every station can add volume and complexity the recipient does not need.
Make that decision from the intended use, not from a default export setting.
Density, clipping, and compression
More points are not automatically more useful. Excessive density can make transfer, indexing, navigation, and coordination slower. Excessive decimation can remove edges or small features important to the decision.
Agree on any clipping, segmentation, filtering, decimation, noise removal, or compression. Keep an appropriate source record when later re-export may be required. LAZ can provide lossless compression for LAS-type point records, but it is a different ecosystem and does not replace all structured-scan needs.
Imagery and appearance
Colorized points, panoramic imagery, and intensity are distinct information types. A colored cloud does not guarantee that panoramic images or station navigation are included. Lighting changes, moving objects, parallax, privacy edits, and exposure can also affect appearance even when geometry is sound.
If imagery is required, state whether the project needs point RGB values, panoramas, blur/redaction, web viewing, or another specific experience.
Use a representative handoff test
The safest compatibility check is a small, representative dataset opened in the recipient’s real environment. Verify:
- coordinates, units, and orientation;
- visible extent and clipping;
- expected scan or region organization;
- point color and intensity;
- performance and practical navigation;
- attachment path in the authoring or coordination tool;
- package completeness after transfer to another machine.
Autodesk maintains current ReCap product and support information. Confirm version-specific import and attachment behavior in the recipient’s supported documentation rather than relying on a generic format assumption.
A better request than “send the point cloud”
Specify: “Provide the approved registered dataset in E57 and/or a complete RCP/RCS package, in the agreed coordinates and units, organized by the defined zones, with the stated imagery treatment, tested in the named receiving application and version.” Then list exclusions and required review evidence.