Data Import from Leica DBX

Description

Import data from Leica equipment that uses the Leica DBX format, including Leica System 1200, Leica Viva and Leica Nova sensors.

Access

Home / Data / Import / Leica DBX

Requirements

Xchange Leica Survey module
Point Cloud module (for the import of point clouds)

Options

The following properties allow control of the import.

General	Description
Content	Displayed - Only objects that are Visible will be imported. All - All objects are imported regardless of whether they are Visible or not.
Import Measurements	Select to import raw total station measurements and GNSS measurement data.
Import Attributes	Select to import attributes.
Import Images	Select to import images.
Import Point Clouds	Select to import point clouds / scans.
Measurement Date Attribute	Enter a name for the attribute that will hold the measured date and time for imported points.
Geoid Model Folder	Select the folder where the geoid model used on-board is located.
CSCS Folder	Select the folder where the CSCS grid transformation file used on-board is located.
Coding	Description
Process Codes	Select the checkbox to process feature codes, control codes and string numbers to create lines and polygons. Note: When line objects are created using code processing, the line inherits the attributes of the first point in the line. If the data file uses free codes to enter control codes then the free code must precede the point that requires the control code.
Join Consecutive Points	Select the checkbox to join all points with the same code that are measured consecutively. Note: Points with the same code are joined when the layers Intended Use is set to Lines or Polygons providing the point is not already part of a line sequence created from control codes or string numbers.
Control Codes	Select the control code table to be used to process control codes.
String Number Attribute	Enter the name of the attribute (maximum 16 characters) that contains the string number used during feature code processing. Note: Point codes with string attributes are joined regardless of the layers Intended Use for the line.
Transformation	Description
Apply Transformation	Do one of the following: Select Yes (Scaled) to compute a scaled transformation using points with the same name and apply it to all points in the imported file. Select Yes (Unscaled) to compute an unscaled transformation using points with the same name and apply it to all points in the imported file. Select No to import the points in the file without a transformation. Note: A 2D Conformal with Height transformation is computed if at least one matched point pair has known heights. A 2D Conformal transformation is computed if all matched point pairs have at least one unknown height. Transformations are computed and applied only when measurements are imported. Point name matching is performed prior to re-naming.
Save Transformation	Select the checkbox to save the computed transformation to the project. Note: The name of the saved transformation file is included in the import report.
Points	Description
Name Format	Add a prefix or suffix to rename points imported from the file. Note: {0} represents the current point name. Type a character before {0} to add a prefix. Type a character after {0} to add a suffix.
Name Offset	Add a numeric offset to the numeric component of the names of imported points.
Adopt Existing	Do one of the following to manage points with the same name: Select the checkbox to adopt a point in the project in preference to importing a point from the file when points with the same name are encountered. Clear the checkbox to import all points from the file. Points with the same name may be created in the project.
Lookup Tables	Description
Layer	Select the Layer lookup table to be used during the import.
Attribute Definition	Select the Attribute Definition lookup table to be used during the import.
Line Style	Select the Line Style lookup table to be used during the import.
Fill	Select the polygon Hatch lookup table to be used during the import.

A blank selection for a lookup table indicates that no lookup will be performed.

Notes

When importing a DBX job database, Point, Line, Alignment and Area objects, as well as their associated attributes, are imported.
Curves are imported as 2D circular arcs with heights in a line object.
Transition curves are imported as transition curves in a line object.
Point clouds are only imported if the Import Point Clouds option is active and the Point Cloud module is included in the licence.
A new layer is created with the name of the point cloud and placed in the layer group specified for the layer template.
Individual scans within in the Dbx file will be imported as separate point clouds.
Each Code in a Codelist is imported as a layer along with its attribute definitions.
Attribute definitions with the name specified in String Number Attribute are not imported.
If the geoid model referenced in the DBX job cannot be found, you will be prompted for the location of the geoid model. If you cannot locate the geoid model, the Default Geoid Undulation specified in the projects coordinate systems Earth Constants is used.
The location of the previously used geoid models is saved for future imports.
If the DBX job does not reference a geoid model, the geoid model specified in the projects coordinate system will be used in preference to the Default Geoid Undulation.
To import a line as a breakline, prior to import, for the layer the line will be placed on, in the layers General tab, set Breakline to Yes.
A check point measurement is assigned a 'Measurement Purpose' of Check. The measurement is used for check purposes only.
A total station setup summary displays when TPS measurements are imported. Differences larger than the allowable tolerance display in red.
All models contained in a DBX DTM Job database are imported as separate terrain models.
Lines and alignments contained in a DBX Road Job database that do not have a code are imported to the active layer.
Centrelines in a DBX Road Job are imported as alignments.

Possible errors

Error or Warning	Description
The input coordinate system '%1' does not match the project coordinate system '%2'.	The coordinate system name referenced in the imported data file has a different name to the coordinate system configured for the project. Ensure the coordinate systems are equivalent.
Geoid file '%1' not found.	The geoid file referenced in the imported data file was not located. Set the location of the geoid model file in the Import options, or navigate to the files location when the open dialog displays prompting you for the geoid models location.
Default geoid separation used for point '%1'.	The geoid file referenced in the imported data file was not located. The default geoid separation will be used.
The input geoid model '%1' does not match the project geoid model '%1'.	The geoid file referenced in the imported data file was located however it has a name and file name that is different to the geoid model specified for the project. If the two geoid models are equivalent then ignore the message.You should ensure that the geoid model you select for the projects coordinate system is equivalent to the geoid model used to collect your data.