Skip to content

Measurement data and application layer

Creating field codes

It is common to use field codes when we measure data. It has proven more efficient to connect properties to the field code afterward when we return to the office. For example, you can use the object list in manual V770 as a field code list. This object list should contain all objects included in all disciplines when designing roads. The objects should also be coordinated with the process codes. In addition, it will specify which objects should be delivered as documentation to NVDB and FKB.

When the field codes are determined, we need to create these in Gemini Terrain.

Procedure

  1. Select the icon for Gemini Terrain Settings... and then Project - Field Codes
  2. Check Use field codes
  3. Click Edit in Excel.... This opens the file FieldCodes.txt
  4. Enter all field codes with descriptions
  5. Save and close FieldCodes.txt

When the coding system is ready, surveyors need to be instructed on how to code data in the field.

Tip

The program contains several predefined system properties for the application layer. One of them is S_FIELDCODE. By adding this property to the different object types in the application layer (line, point, and polygon), we get a list of the field codes from the FieldCodes.txt file.

Importing contract posts

As mentioned in the introduction, we can import the contract posts from the tendering program used for the job. To make the connection between a contract post and a measured object (point, line, polygon), the property S_CONTRACTPOST must be defined for the object types.

In Gemini Terrain, we activate the use of contract posts in the dialog Gemini Terrain Settings... - Project - Contracts.

When working in a cloud project, the contract can be easily imported via Gemini ProAdm or directly in Gemini Connected Web. When working in local projects, you can perform a simpler import under Gemini Terrain Settings... - Project - Contracts.

Attribute for contract posts

Attribute for contract posts shown in horizontal list field.

Procedure

  1. Select the icon for Gemini Terrain Settings... - Project - Contracts
  2. Check Use contracts
  3. Select the desired method, Gemini Connected or Local contract
  4. Click OK to confirm the settings

Importing measurement data

As previously mentioned, we store measured data in gmi layers. For these layers, we have good functions for importing and exporting various external formats and all field books on the market.

Info

Traceability is important in relation to data. In Gemini Terrain, we can add the properties S_IMPORTFILE and S_IMPORTDATE. These properties are automatically filled out by the program when we import data to the application layer.

Properties for traceability of imported data

It can be beneficial to import measurement data to a draft layer first.

Import to draft layer

Import to draft layer

Tip

By using draft layers, we can perform quality control of the data, for example, check if the same data has been measured multiple times. When this quality control is completed, we can copy the data to the final layer.

For large projects, it might be beneficial for each user to have their own draft layer.

Connecting contract posts to measurement data

After the data is imported and verified, we can connect contract posts to the measured data.

Example of connecting contract post to measurement data

When this is done, we can easily generate reports on measured quantities linked to contract posts.