As-built NVDB Excel Spreadsheet

Using Field Code XREF Spreadsheet

Property values can be entered via the property list or in the horizontal list field (object list), or by using the Replace... function.

You can also use the field code XREF spreadsheet (cross-reference spreadsheet) to cross-link properties. The field code XREF spreadsheet is an Excel spreadsheet. The advantage of using Excel is that it's a program many people are familiar with and have access to. With the field code XREF spreadsheet, we can support multiple tasks, including allowing non-Gemini Terrain users to enter codes for attributes, such as material managers or equipment suppliers.

The field code XREF spreadsheet supports two tasks:

• Import attributes using field code XREF
• Distribute objects using field code XREF

The linking key between Gemini Terrain and the field code XREF spreadsheet is the field code attribute. This can be found under Project Settings - Field Codes in the Gemini Terrain Settings dialog on the tools menu.

The functions for creating field code XREF spreadsheets and cross-linking properties can be found under Tools - Cross-reference attributes with Excel in the context menu in the vertical list field for application layers.

For both tasks, we must first create a field code XREF spreadsheet from one or more application layers in Gemini Terrain. We do this with the option Export Field Code XREF Spreadsheet...

Once this is done, we can enter codes/select from dropdown menus in the Excel spreadsheet and then import this into Gemini Terrain.

Using Field Code XREF Spreadsheet in NVDB Deliveries

An example where the field code XREF spreadsheet is useful is for NVDB deliveries.

Example of a selection of NVDB application layers

At the start of the project, we create NVDB layers for all road objects that are part of the delivery.

We can then create a field code XREF spreadsheet by selecting all the layers and choosing Export Field Code XREF Spreadsheet.... The Excel spreadsheet will contain a worksheet for each object type with field code attributes in the application layers.

Example where the attribute S_FIELDCODE is selected as the field code in the project.

Once this is done, the field code XREF spreadsheet is ready to be filled in. Properties with predefined values also have dropdown menus for this in the Excel spreadsheet.

When the field code XREF spreadsheet is filled in, it can be used in two XREF functions:

• Import Attributes Using Field Code XREF... This imports the attributes in the Excel spreadsheet to the application layer(s) with the same name as in the Excel spreadsheet

• Distribute Objects Using Field Code XREF... This imports the attributes from the Excel spreadsheet and distributes the objects in an application layer to the application layer(s) with the same name as in the Excel spreadsheet

The dialog help of these functions describes the operation in more detail: * Import Attributes Using Field Code XREF... * Distribute Objects Using Field Code XREF...

Log

After performing one of the tasks, a log appears. It will contain descriptions of any errors that occurred during the operation.

Below are some of the most common error messages and their meanings.

1. Field code not cross-linked, missing in Excel sheet: "nnnn"
   This message appears if objects in Gemini Terrain have field codes that don't exist in the Excel spreadsheet.

2. Field code not cross-linked due to incorrect application layer name in sheet: "nnnn"
   If we've checked Import only if the field code in the Excel sheet matches the name of the target application layer, cross-linking is only performed if these application layer names in Gemini Terrain and Excel are identical.

For example, there might be a point with field code 8250 Manhole on the application layer NVDB_xxxx_nn (P) in Gemini Terrain, while in the Excel spreadsheet the code is on NVDB_Manhole_83 (P).

1. Warning: Field code "nnnn" has different description in field code list for application layer: "mmmm.aly"
   This message appears if a field code has one description in Excel and another in the application layer (metadata).