Administration > Menu reference > Administration > Codelists

The table manager is used to:

•Create and edit mappings between the external object code (field code) of the measurement objects to be imported and the internal object type subtype. The mapping is performed in the Object mapping /GEO_OBJECT_MAP table.

•Create and edit mappings between measurement data attributes and dpSpatial attributes, which is controlled from the database table GEO_ATTRIBUTE_MAP.

To use the Table Manager, the user must have the managecodelists database role:

grant managecodelists to USERNAME;

All codelist owners must grant insert and update rights to managecodelists in order for users with this role to be able to edit the content of the codelists. These rights are granted by the code list owner according to the syntax:

grant insert, update on CODELIST to managecodelists;

Add a new mapping

In order to insert mappings, you must know the object types, subtypes and component types of the measurement objects to be loaded.

Use the Object metadata reader tool in the Administration menu to find the appropriate object types, subtypes and component types.

As a suggestion, the administrator produces and maintains code lists of field codes with appropriate mappings to internal objects in dpPower. The field codes can be supplemented with instructions to personnel who handle measurements in the field about how field objects should be coded and which coordinate system should be used.

1.Select Administration > Codelists > Table manager.

2.In the Table owner field, select the database user who created the table.

3.In the Table field:

oGEO_ATTRIBUTE_MAP - The mapping between measurement data attributes and dpSpatial attributes. Attribute mapping is used when importing and exporting, among other things, Geodata with attributes (*.dpt)

oGEO_OBJECT_MAP - Manages object mapping during import and export.

4.Press Add . A form for entering mapping values to the current table opens.

5.Fill in the desired mapping values. Pink fields with an asterisk (*) are mandatory. At the bottom of the form, a short description of the input field that is currently in focus is displayed.

6.Press Save. The form closes and the new mapping with the entered values is added to the database.

7.To be sure that the change has taken effect, press Update server in the main window of the tool.

Press to copy the values in a row.

Press to edit a row.

Press to delete a row.

Press to assign all the empty display flags with values from the sequence.

Table fields

GEO_OBJECT_MAP

Here follows a description of the fields used in the object mapping table. Please note that several fields are mandatory - they must be filled in for the mapping to be valid and for import or export to be possible. In addition to the mandatory fields, usually only the Graphic or Symbol field will be filled in. This can of course vary depending on the type of file and the choice of imported objects.

Field	Description
Field code	External object code in the measurement file. Primary key. (text string) Mandatory value.
Object type	The internal object type (in dpSpatial). Mandatory value.
Sub type	The internal subtype. Mandatory value.
Graphics	Component type for graphics component.
Symbol	Component type for symbol component.
Pnr text	Text component type to be mapped to "Point number" in the measurement file.
Pnr field	Field name in the database to be replaced by the values in the "Point number" field in the measurement file.
Pnr offset X	Offset of point number-text in X direction (cm) when drawing in the map view.
Pnr offset Y	Offset of point number-text in Y direction (cm) drawing in the map view.
Code text	Text component type to be mapped against "Field code" in the measurement file.
Code field	Field name in the database to be replaced by the values in the "Field code" field in the measurement file.
Code offset X	Offset of object code-text in X-direction (cm) drawing in the map view.
Code offset Y	Offset of object code-text in Y direction (cm) drawing in the map view.
Free text	Text component type for free text. Applies to mapping against measurement files of extended Marit format.
Free text field	Database fields for free text.
Free text offset X	Offset of free text in X-direction (cm) drawing in the map view.
Free text offset Y	Offset of free text in Y direction (cm) drawing in the map view.
State	The state the object shall get
Height text offset X	Displacement of height text in X-direction (cm)
Height text offset Y	Displacement of height text in Y-direction (cm)
Height text	Text component type for height
Text trigger type	Text trigger type that should be used through configuration for type

GEO_ATTRIBUTE_MAP

The field ext_otype is mandatory and must therefore be filled in for a mapping to be valid. The other fields must contain names of the database fields in the data table for dpSpatial's equivalent to ext_otype for the attributes you want to map and the component types for the components to which the attributes belong.

Field	Description
Field code	External object code in the measurement file.
Component 1	Component type for attribute field 1.
Attribute field 1	Database field for Attribute 1.
Component 2	Component type for attribute field 2.
Attribute field 2	Database field for Attribute 2.
...	...
Component 10	Component type for attribute field 10.
Attribute field 10	Database field for Attribute 10.