Digitization alphabet

This section explains how the scanner captures an object's shape using a laser beam, what a point cloud is, and how the process of collecting spatial data works.

Here we explore the main types of scanners—mobile, stationary, with or without color capture—and which tasks each is best suited for.

This section covers how to determine the number of scan positions, what to consider when placing equipment, and how to avoid data gaps.

Georeferencing is like giving your model a real-world address. Imagine you’ve created a perfect 3D model of a monument, but it’s just floating in space — with no idea where it actually exists. To make it useful not only visually but spatially, you need to anchor it to a coordinate system. In Ukraine, the official system for this is USK-2000.

Why does this matter? Because once your data has proper coordinates, you can combine it with other sources — architectural drawings, cadastral maps, or online geoportals. It also allows you to come back in a year and re-scan in the exact same system to see what’s changed. To do this, you place control points on site (GCPs), and use GNSS receivers or total stations.

And it’s not just a “nice-to-have” — it’s the law. According to a government resolution (№1259 from 2004), all spatial data projects in Ukraine must be done using USK-2000. So if you want your data to “live” in the right spot, this is the system to use.

This section explains how to merge scans into a single model, clean up noise and unnecessary elements, and prepare the data for further processing.

In this section, we’ll show you what to do with all your data after the scanning is complete — how to store, process, share, or archive it in a convenient way. You’ll learn how not to get lost in folders, which formats to choose, and how to organize your files so others can easily work with them. It’s all about giving your data a second life — clear, structured, and useful.

EXPORT AND FORMATS

A point cloud can be:

Structured — includes data about scanning station positions. This is a complete copy of the scan with positioning metadata. These files should always be saved, even if not used daily. To minimize risk of file corruption, we recommend exporting each scan station as a separate file.

Example filenames:

Lviv_Castle_2024_Station_001.e57

Lviv_Castle_2024_Station_002.e57

Lviv_Castle_2024_Block01.e57 (multiple stations in one file — not recommended)

Unstructured — used for processing, archiving, or publishing. This is a simplified cloud without individual scan station data. It’s often decimated to 5 mm or 10 mm accuracy and split into zones: exterior/interior, by floor, etc. These files are lighter, easier to work with, and typically stay under ~5 GB.

Example filenames:

Odesa_Opera_2023_Outside_Level1_5mm.e57

Odesa_Opera_2023_Inside_Level2_10mm.e57

Common formats:

E57 — universal, supports color, coordinates, and metadata

LAS/LAZ — good for geodesy, archives, and lightweight delivery

RCP/RCS — convenient for Autodesk environments

For BIM/CAD — use RCP or processed E57
For archiving — E57 or LAS

DATA ORGANIZATION

Organize folders by object, date, and data type

Use clear filenames: Kyiv_Sophia_2024_Inside_Scan01.e57

Add a README file with content description, coordinate system, units, authorship, and license

Include a GCPs file listing ground control points. This helps engineers verify the correct spatial alignment of the model. In the GCP file, specify the coordinate system — for example, EPSG:556… for Ukraine’s USK-2000. This makes the data clearer for international collaborators too.

SHARING AND PUBLICATION

In the future, our platform will support uploading and sharing your point cloud with other users. This will make it easier to publish digital data and open it to a wider audience.

For sharing — use ZIP archives with organized folders

Always include licensing information (Creative Commons, copyright)

This section is about making sure your data not only survives, but becomes useful for others.