Importing and Processing Measured Data

Overview

In road projects, the surface generator (build engine) uses the layer number of the layers. Data for terrain surface and layers in the ground must be placed on the correct physical layers for the surface generator's building rules to function as intended.

In Gemini Terrain, we have the following predefined layers:

Predefined layers in Gemini Terrain, A = Vegetation, B = Topsoil, C = Replacement materials, D = Soil, E = Rock

We see that the terrain surface can in principle contain data for all these layers. This is not a problem since the build engine in Gemini Terrain handles partially defined physical layers.

In traditional surveying, it is time-saving to code data for the terrain surface (virgin terrain) and ground layers (after uncovering) correctly in the field.

Surveying of terrain surface

Planning of Measurement and Coding in the Field

For surveying physical layers in road projects, we must plan measurement and coding in the field, and it's advantageous to have codes for all the predefined layers:

• Vegetation
• Topsoil
• Replacement materials
• Soil
• Rock

We can import data from various external formats or directly from the field book.

In addition to coding which layer the data should be placed on, it may also be useful to survey the boundary contours that mark the transition between different types of layers.

For the terrain surface, land type boundaries may also be relevant to use as boundary contours. This is perhaps especially relevant when scanning the terrain surface.

Distribution of Terrain Data

We distribute terrain data to application layers based on which layer they belong to.

Distribution of terrain data to application layers

Surveyed points and lines must be triangulated before they can form a layer (terrain model). Point clouds can be triangulated, but they can also form a layer without triangulation.

Application layers and triangulation are described in more detail in the section Application Layers.