Technical field notes / plain languageRESOURCES / 10
Understand the data before you scope the work.
Original guides for teams that need to commission, receive, or use reality-capture information without treating scanner marketing as a project specification.
Editorial standard
Direct answers, visible limits, practical next steps.
Each note separates capture, registration, review, format, and derived deliverables so project teams can ask better questions.
01 / LIBRARY
Core concepts
Start with the decision closest to your project.
E57 vs. RCP/RCS: choose for the receiving workflow
A practical comparison of E57 point-cloud exchange and Autodesk RCP/RCS indexing, including coordinates, scan structure, imagery, compatibility, and handoff testing.
Read technical note ↗02 / Project planningHow to plan a 3D laser scanning project
A pre-mobilization checklist for capture boundaries, access, safety, coordinates, QA, deliverables, receiving software, and project responsibility.
Read technical note ↗03 / Quality assuranceRegistered point clouds: what the approval should mean
An explanation of point-cloud registration methods, review evidence, control, local fit, and why one mean error value cannot prove a dataset is project-ready.
Read technical note ↗04 / FundamentalsWhat is 3D laser scanning?
A project-focused explanation of terrestrial 3D laser scanning, what it records, how point clouds are created, and what the technology does not establish by itself.
Read technical note ↗Next coordinatePROJECT / SCOPE
Turn the question into a defined project brief.
Tell us what your team needs to decide, the conditions you need documented, and the software the information must enter.