Skip to content

As-built FKB Workflow

Workflow

This chapter describes a step-by-step recommended workflow for creating and exporting FKB data in Gemini Terrain:

Step 1. Create application layer for FKB

The option to create new FKB application layers can be found in the context menu in the vertical list field for application layers.

For FKB we use Create...

When creating application layers for FKB, we use templates. Several templates have been prepared for projects where we need to deliver FKB data, which are included with the program. Product specifications can be found on the Norwegian Mapping Authority's website: www.kartverket.no

The latest applicable templates that have been created (always check the Norwegian Mapping Authority's pages for any new versions of the product specifications):

FKB 5.0x

  • FKB501_Naturinfo.aly
  • FKB501_Bane.aly
  • FKB502_Arealbruk.al_
  • FKB502_Lufthavn.al_
  • FKB503_Høydekurve.al_

FKB 5.1

  • FKB51_AR5.al_
  • FKB51_BygnAnlegg.al_
  • FKB51_Bygning.al_
  • FKB51_Ledning.al_
  • FKB51_Tiltak.aly
  • FKB51_TraktorvegSti.aly
  • FKB51_Vann.aly
  • FKB51_Veg.aly

Step 2. Import from field / copy geometry from models

As-built road data for FKB can come from various sources, such as measurements and theoretical models like SFI models, etc.

It may be beneficial to import measurements to a draft layer and then distribute them to their respective FKB application layers.

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

Step 3. Edit geometry if necessary and add properties

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

Step 4. Export to SOSI

We refer to the section on SOSI export.

Step 5. Check the file in SOSI control

We refer to the section on SOSI control.