Skip to content

Workflow for NVDB in Gemini Terrain

Overview

The workflow in Gemini Terrain consists of several steps:

  1. Create NVDB application layer
  2. Enter NVDB data
  3. Send data to Datafangst

These steps are described in more detail below.

Detailed Workflow

1. Create NVDB Application Layer

The options for creating new application layers are found in the context menu in the vertical list field for application layers. For NVDB, we use Create/Update NVDB Asbuilt Application Layer.... We create an application layer for each road object type. We can also choose to create application layers with only required properties (properties with importance Required and Conditional). The column for attributes will show either All attributes or Required attributes. This can be changed before you click Create....

Note

The program uses the same template, NVDB.al_, for all application layers, but the user does not see this during the process of creating the NVDB layer. Note that it can be customized, for example, with regard to extra properties that should be included in addition to NVDB's.

Beyond this, NVDB's API gives us access to all road objects stored in NVDB with associated attributes and codes.

On the Norwegian Public Roads Administration's website, we also find the complete data catalog for NVDB.

2. Enter NVDB Data

Completed road data for FKB can come from several sources, such as surveys and theoretical models like SFI models, etc. It may be appropriate to import measurements into a draft layer and then distribute them to their respective application layers.

We often use theoretical data if these are performed within the tolerance requirements (documented with geometric control). In such cases, we need to copy 3D lines from theoretical road models to application layers. Since the 3D lines that go to FKB should not contain curves, these are split into many small straight line segments. There are requirements for point density in these cases, i.e., requirements for arrow height in plan and height (deviation between the straight line course between the points and the actual line course).

Tip

We can enter properties in the horizontal list field with Replace... or directly in the property list. If we have used field codes, we can cross-link properties with an Excel sheet for field codes. Excel sheets for field codes are described in more detail in a separate section.

We also refer to the chapter on editing data in application layers.

3. Send Data to Datafangst

The option for NVDB delivery, Export Asbuilt to Datafangst..., is found in the context menu in the vertical list field for application layers. When we export to NVDB, the data is sent directly to Datafangst via the API. We can send the same application layer multiple times to NVDB.

During export, we choose how the objects in the layer are handled. There are four options:

  • Export only new objects
  • Update existing and export new objects
  • Update existing objects only
  • Export all objects again

Info

See the dialog Export Asbuilt to Datafangst for a more detailed description of the four options.