NVDB workflow¶
Workflow¶
Working with the Norwegian Public Roads Administration as a client is relatively extensive regarding SOSI deliveries. The object list for completed road data for maps and the National Road Database (NVDB) shows that some object types should go to FKB and NVDB, some only to FKB, and some only to NVDB.
The following sections describe a suggested workflow.
1. Create application layer for NVDB¶
The option to create new NVDB application layers can be found in the context menu in the vertical list field for application layers. For NVDB, we use Create/update NVDB-as-built-applayer...
For NVDB application layers, we don't use templates in the same way as for FKB. The program uses the same template, NVDB.al_, for all application layers, but the user doesn't 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 own.
Info
NVDB's REST-API gives us access to all road objects stored in NVDB with associated attributes and codes.
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.
Tip
On the Norwegian Public Roads Administration's website, you can also find the complete data catalog for NVDB.
2. Import from field / copy geometry from models¶
Completed road data for NVDB can come from several sources, such as measurements and theoretical models like SFI models.
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.
3. Edit geometry and enter properties¶
We refer to the chapter on editing data in application layers. Properties can be entered in the horizontal list field with Replace... or directly in the property list.
Info
If we have used field codes, we can cross-link properties with Excel forms for field codes. Excel forms for field codes are described in more detail in a separate section.
4. Export to SOSI¶
We refer to a separate section on SOSI export.
5. Import into Datafangst for verification¶
To verify data before delivery, you can import the SOSI file into the Norwegian Public Roads Administration's Datafangst system.
Tip
It is always recommended to check SOSI files before final delivery to ensure that all geometry and properties are correct.