Skip to content

Workflow for NVDB in Gemini Terrain

Overview

The workflow in Gemini Terrain is done in four steps:

  1. Enter NVDB username and password
  2. Create NVDB application layer
  3. Enter NVDB data
  4. Send data to Datafangst

These steps are described in more detail below.

Detailed Workflow

1. Enter NVDB Username and Password

Enter your NVDB username and NVDB password.

The option for this is found under Personal Settings - NVDB Authentication in the Gemini Terrain Settings dialog on the tool menu.

2. 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 As-built 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.

3. 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.

4. Send Data to Datafangst

We have 4 operation types in Datafangst:

  1. Create
    Creates new road objects
  2. Correct
    Changes the properties of an existing road object version. Typically used when there are incorrectly registered property values.
  3. Update
    Creates a new version of an existing road object. Typically used when observable changes have occurred to a road object along the road.
  4. Close
    Sets end data on an existing road object. Typically used when a road object has been removed from the road.

Note

The default choice is Create. If we send data with Correct, Update, or Close, we must also include the ID of the objects in NVDB, NVDB_ID.

NVDB_ID can be retrieved via the NVDB client application layer for existing road objects (which uses the READ API).

The option for NVDB delivery, Export As-built 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. Road objects will not be duplicated in Datafangst; already submitted road objects will be updated. Furthermore, new objects in the application layer are added, and deleted objects in the application layer are removed.

Tip

Another useful function is that the data manager and other project participants have the ability to add comments on all road objects and road object types in Datafangst. The option Get Status from Datafangst..., which we find in the context menu in the vertical list field for application layers, will retrieve any comments on the road objects and put them in the property S_COMMENT.

Note

Note that the NVDB id will be retrieved for objects that are approved and created in the NVDB database.

In Gemini Terrain, we find this information, among other places, in the property list.