Trimble JobXML

Use this dialog to import a Trimble JobXML file containing measured points and associated attributes.

Where to find the dialog

On the toolbar, select Application Layer - Import/export - Trimble JobXML.

Schema interpretation

Gemini Terrain performs schema interpretation if the schema is available online. If access to the schema is missing, you will receive a warning, but you can still proceed with the import.

A Trimble JobXML file contains measured points with associated attributes.

Example of JobXML format

<point>
    <name>p2</name>
    <code>8100</code>
    <attribute>Hello</attribute>
    <attribute>Hi</attribute>
    <method>GpsRTKQuickMark</method>
    <surveyMethod>NetworkRTK</surveyMethod>
    <classification>Normal</classification>
    <deleted>false</deleted>
    <fieldbook>
        <row>
            <attribute>
                <name>Measurement method</name>
                <value>96 GPS kinematic (Real time kinematic)</value>
                <source>Menu</source>
                <order>66</order>
            </attribute>
        </row>
    </fieldbook>
</point>

Attribute library

To import the file correctly, you must also have access to the attribute library, the fxl file. This file contains information about which codes are lines and which codes are points.

Example of fxl format

<library>
    <codegroup>
        <name>Measurement method</name>
        <description>
            10 Terrain measured
            11 Terrain measured: Total station
            12 Terrain measured: Theodolite with electronic distance meter
            13 Terrain measured: Theodolite with tape measure
            14 Terrain measured: Orthogonal method
            15 Staked out:
        </description>
    </codegroup>
</library>

Normally, the JobXML file contains a reference to the attribute library used in the measurement job. If this reference is missing, you will be prompted to specify the location and fxl file.

Warning

If you do not provide an fxl file, everything will be interpreted as points.

Double coding of points

The import interprets double coding under certain conditions. With double coding, the first code can be a line point. If this is the case, the second code becomes a single point. Additionally, you can have a third code (control code) as described in the section below.

Example of double coding

<point>
    <name>p3</name>
    <code>8100 8191</code>
    <attribute>Test1</attribute>
    <attribute>Test2</attribute>
    <method>GpsRTKQuickMark</method>
    <surveyMethod>NetworkRTK</surveyMethod>
    <classification>Normal</classification>
    <deleted>false</deleted>
    <fieldbook>
        <row>
            <attribute>
                <name>Measurement method</name>
                <value>96 GPS kinematic (Real time kinematic)</value>
                <source>Menu</source>
                <order>66</order>
            </attribute>
        </row>
    </fieldbook>
</point>

Line interpretation and codes

When you measure on a line code, the line is split at the point by adding or changing an attribute value. A typical example is measuring VA. If the diameter changes along the way, the line is split at the point where the new diameter is registered.

If you measure on a line and change the code, for example from pipe to manhole, the line is broken (meaning no line is drawn to the new code).

Note

You start the line again if you switch back to the same code with the same attribute values.

In addition to the automation, you can add control codes as a supplement. For example, you can override the automation by specifying start and stop lines manually.

Control codes

Gemini Terrain supports the following control codes (KOF standard):

• 91 Start line
• 96 Stop and close line
• 99 Stop line