RR - aDesignToField - UserGuide - EN

System 1200 Data Import Guide Design to Field User Manual
2-1
Design To Field
Guide to importing data into System1200
Leica Geo Office - Version 4.0

English
GRKE1205 Doc.Version 1.0

System 1200 Data Import Guide Design to Field 2-2
Table of Contents
1. Introduction .............................................................................................................................................................. 2-6

1.1 Overview ............................................................................................................................................................. 2-7
1.2 Available data converters.................................................................................................................................... 2-8
2 Installing the data converters ................................................................................................................................2-10
2.1 Prerequisites ......................................................................................................................................................2-11
2.2 Installing the converter package ........................................................................................................................2-11
2.3 Updating an existing converter...........................................................................................................................2-13
2.3.1 Downloading the converter .........................................................................................................................2-13
2.3.2 Registering the converter in LGO ...............................................................................................................2-13
3 Converting Points, Lines and Area data ...............................................................................................................3-15
3.1 Overview ............................................................................................................................................................3-16
3.2 How to create a points, lines and areas job .......................................................................................................3-16
3.2.1 Defining the file to import ............................................................................................................................3-16
3.3 Graphical Data Viewer .......................................................................................................................................3-18
3.3.1 Viewer Layout .............................................................................................................................................3-18
3.3.2 Zoom/Pan Tools .........................................................................................................................................3-19
3.3.3 Layer Tool...................................................................................................................................................3-19
3.3.4 Graphical Settings ......................................................................................................................................3-20
3.3.5 Saving the data...........................................................................................................................................3-21
3.4 Creating the on-board files.................................................................................................................................3-22
3.5 Importing LandXML data....................................................................................................................................3-23
3.5.1 Supported LandXML entities.......................................................................................................................3-23
3.6 Importing DXF data............................................................................................................................................3-25
3.6.1 Supported DXF entities...............................................................................................................................3-26
3.6.2 Treatment of DXF Layers............................................................................................................................3-30
4 Converting Digital Terrain Model data ..................................................................................................................4-32
4.1 Overview ............................................................................................................................................................4-33
4.2 How to create a DTM job ...................................................................................................................................4-33

4.5 Importing GSI data.............................................................................................................................................4-37
5 Converting Road Data ............................................................................................................................................5-38
5.1 Overview ............................................................................................................................................................5-39
5.2 How to create a road job ....................................................................................................................................5-40
5.3 Connection Editor ..............................................................................................................................................5-42
5.3.1 Layout .........................................................................................................................................................5-43
5.3.2 Layer Tool...................................................................................................................................................5-44
5.3.3 Navigation Tools .........................................................................................................................................5-45
5.4 Connection Tools ...............................................................................................................................................5-47
5.4.1 Connect / Disconnect a vertex ....................................................................................................................5-47
5.5 Creating the on-board database files .................................................................................................................5-48
5.6.1 Horizontal alignment ...................................................................................................................................5-50
5.6.2 Profile (Vertical Alignment) .........................................................................................................................5-53
5.6.3 Prof example...............................................................................................................................................5-53
5.6.4 Cross-sections ............................................................................................................................................5-55
5.6.5 Stringlines ...................................................................................................................................................5-56
5.7 Importing Bentley® LandXML data ....................................................................................................................5-56
5.8 Importing GSI data.............................................................................................................................................5-58
5.8.1 Horizontal Alignment...................................................................................................................................5-58
5.8.2 Vertical Alignment .......................................................................................................................................5-59
5.8.3 Cross-sections ............................................................................................................................................5-60
5.8.4 Cross-section assignment...........................................................................................................................5-62
5.10 Importing data in the MX Genio format ..............................................................................................................5-65
5.11 Importing data in the Avance format ..................................................................................................................5-67
5.11.2 Vertical alignment file..................................................................................................................................5-68
5.11.3 Cross-section file ........................................................................................................................................5-69

5.12 Importing data in the REB format.......................................................................................................................5-70
5.13 Importing data in the Cartomap format ..............................................................................................................5-72
5.14 Importing data in the Clip format ........................................................................................................................5-74
5.15 Importing data in the InRoads format.................................................................................................................5-76
5.16 Importing data in the Ispol format.......................................................................................................................5-78
5.17 Importing data in the Modelo Digital format........................................................................................................5-81
5.18 Importing data in the Multipiste format ...............................................................................................................5-82
5.19 Importing data in the SDR format.......................................................................................................................5-83
5.19.1 Horizontal and vertical alignment................................................................................................................5-83
5.20 Importing data in the SierraSoft format ..............................................................................................................5-84

5.20.1 Horizontal and vertical alignment................................................................................................................5-84
5.21 Importing data in the TCP format .......................................................................................................................5-86
5.22 Importing data in the Trazado format .................................................................................................................5-87
5.23 Importing data in the VIPS format ......................................................................................................................5-88
1. Introduction
In this chapter
1.1 Overview
1.2 Available data converters
1.1 Overview
Design to Field is the name of a software component contained within the Leica Geo Office (LGO) application that allows data to be imported for
use on-board System 1200 GPS and TPS sensors.
Design to Field allows many different data types to be imported for use on board a System 1200 sensor. These data types include control points,
background maps, digital terrain models and road, rail and tunnel design data for use with the RoadRunner suite of applications,
Data may be imported using industry standard data formats such as LandXML, DXF and GSI or from a number of additional formats using
converters that are available in the downloads area of the Leica Geosystems website.
Data converters are available for the following System 1200 job types:
Points, Lines and Area (PLA) job:

The entities (points, lines and areas) imported into this type of job may be displayed as a background map or may be staked out on-board a
System 1200 sensor
DTM job:
DTM jobs store a digital terrain model on board a System 1200 sensor. Each digital terrain model may be made up of one or more surfaces or
layers.
Road job:
Road jobs store a collection of two or three dimensional lines, known as stringlines, that define a road project for use with the System 1200
RoadRunner application. In many cases road projects are defined, in addition to their horizontal and vertical alignments, by cross-sections instead
of stringlines. In this case, Design to Field converts the cross-sections to stringlines based on the parameters set by the user before storing the
data on-board the sensor.
Rail job:
Rail jobs are used in conjunction with the System 1200 RailRunner application. Design to Field allows the horizontal and vertical alignments of
each track to be defined as well as the superelevation or cant for each track.
Tunnel job:
Tunnel jobs are used in conjunction with the System 1200 RoadRunner Tunnel application (only available in certain countries, check for availability
with your local Leica Geosystems representative). Design to Field allows the horizontal and vertical alignments of the tunnel to be defined as well
as the design profiles of the tunnel.
1.2 Available data converters
The data converters may be installed using the LGO installation CD or downloaded from the Leica Geosystems web page at the following URL:
http://www.leica-geosystems.com/s-e/en/downloads/lgs_page_catalog.htm?cid=3291
At the time of writing the following converters are available:
Job Type Format converter available for the following formats:
PLA
(Points, Lines LandXML, DXF
and Areas)
DTM LandXML, DXF (3D Face entities), GSI
Road LandXML (stringlines and cross-sections), Bentley LandXML (surfaces), Avance, Cartomap, Clip, InRoads/InRail, Ispol,
Modelo Digital, SDR Varin/Map, SierraSoft, TCP, REB, Multipiste, MX GenI/O, VIPS, DXF
Rail LandXML, Avance, Cartomap, Clip, InRoads/InRail, Ispol, Modelo Digital, SDR Varin/Map, SierraSoft, TCP, REB, Multipiste,
MX GenI/O, VIPS
Tunnel LandXML, Avance, Cartomap, Clip, InRoads/InRail, Ispol, Modelo Digital, SDR Varin/Map, SierraSoft, TCP, REB, Multipiste,
MX GenI/O, VIPS
The data converters are packaged into one installation package that may be downloaded from the \Road Converters section of the Leica
Geosystems website or directly from the LGO v4.0 installation CD. Select the DesignToField Converter Install Application and save the file. In
addition to the install application, for updating converters that are already installed and in order to reduce the size of the download, the converters
may also be downloaded one at a time from the web page.
Important Note: If any of the converters in the above table are to be used, the installation package must have been run on each PC on which the
converter will be used. If an individual converter (*.rri file) is downloaded from the web page and registered in Design to Field without having run
the installation package previously, the data conversion will fail.
The individual converters should only be downloaded to update an existing converter that has been installed using the installation program.
2 Installing the data converters

In this chapter
2.1 Prerequisites
2.2 Installing the converter package
2.3 Updating an existing converter
2.1 Prerequisites
Before installing the additional data converters it is required that at least version 4.0 of the Leica Geo Office application be installed.
In order to guarantee compatibility of the converters and the Leica Geo office application, it is recommended that the latest version of LGO be
installed.
For more information on purchasing the LGO application or updates, contact your local Leica Geosystems representative.
Important Note: If it is required to install the data converters to create tunnel jobs, the file Road Runner Formats.tnl must be in the same folder as
the file Design To Field Importers.exe before running the installation. Contact your local Leica Geosystems representative for information on how
to access the file Road Runner Formats.tnl.
2.2 Installing the converter package
The installation file Design To Field Importers.exe may be executed directly from the Windows® Explorer or from the Start menu.
- Press the Start button on the taskbar and select the option Run.
- In the dialogue box, select the button Browse and browse to the folder
where the file DesignToField Importers.exe has been saved.
- Once the file has been selected, press the OK button and the
installation procedure will commence.
- The converters are available in four languages: English, French,

German and Spanish. Select the language for the installation procedure
and press the Next button.
- Select the default folder for installing the converters or browse to a new
folder using the Change button.
- A tree containing the available converters will appear. The

converters are divide into four groups: Points, Lines and Area
Importers, Road Importers, Rail Importers and DTM Importers.
Note: Road and Tunnel jobs are created with the same Road
Importers.
- By default all of the data formats will be selected.
- If all of the additional data converters are not required, deselect

those that will not be used before pressing the Next button.
- The selected importers will be installed and registered automatically within the LGO application. The next time the LGO application is run,
the installed converters will be available for use.
2.3 Updating an existing converter
The converters may be updated at any time according to changes in the definition of each format, due to routine maintenance or due to the
addition of new functionality. The latest version of the converters is always available on the Downloads page of the Leica Geosystems website.
http://www.leica-geosystems.com/s-e/en/downloads/lgs_page_catalog.htm?cid=3291
2.3.1 Downloading the converter
It is not necessary to reinstall the entire installation package in order to update an individual converter. The individual converter may be
downloaded from the downloads page and registered manually within LGO.
Note: Individual converters may only be downloaded by registered web site

users. In order to register, follow the instructions in the Downloads area of the
web site.
- Browse to the required converter on the web page and press the
Download button.
- Browse to a folder and save the file.
2.3.2 Registering the converter in LGO
Once the converter has been saved, it needs to be registered within the LGO application. To register the converter within LGO:
- Run LGO and select the Tools/Design to Field option.

- Press the Manage button. A list of the importers that have already been
registered will be shown.
- Select the existing version of the importer that will be updated and press
the > button. The importer will be moved to the Not Used list.
- Press the Register button and select the new converter file.
- Note: Converter files use the following naming conventions:
File extension: *. rri
Prefix: PLA file have the prefix PLA, e.g PLA_DXF-Importer.rri

DTM files have the prefix DTM, e.g. DTM_DXF-Importer.rri
Road and rail importers have the prefix RR, e.g. RR_Road_Clip.rri
Additional Prefix: Road and Rail importers have the additional prefix, Road or Rail, e.g. RR_Rail_InRoads.rri
- Once the converter file has been selected, it will be registered in LGO. Press the OK button to return Design to Field, the registration of
the converter is now complete.
3 Converting Points, Lines and Area data

In this chapter
3.1 Overview
3.2 How to create a points, lines and area job
3.3 Graphical Data Viewer
3.4 Creating the on-board files
3.5 Importing LandXML data
3.6 Importing data in DXF format
3.1 Overview
The Design to Field points, lines and area converters allow these graphical entities to be imported to System 1200. The imported data may be
used as a background map (e.g. for updating purposes) or for staking out.
The information imported from each data format is format dependent as not all formats store the same data.
3.2 How to create a points, lines and areas job
The generic process of creating a PLA job is described in this section, the actual screens may vary depending on the information available in the
imported data format. Any additional screens are explained in the section relating to each particular format.
3.2.1 Defining the file to import
- To create a PLA job using the Design to Field component select the Tools/Design to Field option of the
Leica Geo Office PC application.
- Select the import type Points, Lines & Areas
- Select the design format of the data file from the Importer drop-down list.
Additional format converters may be added using the Manage button.
- To read the file containing the data to import, press the Import button and browse to the file.
- Once the data file to import has been defined, the data will be displayed graphically for review or edition before creating the on-board file.
3.3 Graphical Data Viewer
The graphical data viewer is used to review and edit the data that has been imported.
3.3.1 Viewer Layout

3.3.2 Zoom/Pan Tools
The zoom and pan tools may be found in the toolbar.
Zoom in
Zoom out
Zoom all
If a zoom tool is selected, it is possible to pan around the data using the scroll bars of the graphical window.
If the zoom tool is not selected, it is possible to pan around the window by clicking the mouse at a selected point and dragging the mouse in the
desired direction.
If a mouse with a scroll-wheel is being used, the scroll-wheel may also be used to zoom in and zoom out of the window.
3.3.3 Layer Tool
The Layer tool may be used to turn-on or turn-off layers in the plot window, to include or exclude layers from the export to the System
1200 database and also to view a single layer of the data.
When the layer button is pressed, a menu is opened where all of the layers of imported data may
be viewed.
Turn-on / turn-off the layer in the plot view.
This button is only used for visualisation purposes, it does not affect whether the data from this layer will be exported to the System
1200 job.
Export / do not export the data in the selected layer to the System 1200 job.
View only the selected layer. All layers in the job will be turned-off except for the selected layer.
This button is only used for visualisation purposes, it does not affect whether the data from this layer will be exported to the System 1200 job.
3.3.4 Graphical Settings
This button allows the graphical settings parameters to be configured.
3.3.4.1 General Settings
Scale: View the scale bar
3.3.4.2 Points
Name: View the point ID

Code: View the point Code
Height: View the height of the point
Description: View the point description

3.3.4.3 Alignments
Name: View the name of the alignment elements

Start Element: View the Start Chainage
Chainage text: View the chainage of the alignment tangent points
3.3.4.4 Areas
Name: Name of the area
3.3.5 Saving the data
If modifications are made to the data, for example by deselecting layers of data, the changes may be saved using the Save
button.
Browse to the required folder and enter a filename where the data will be saved. The modified data will be saved to a file in
LandXML format. The file may be loaded at a later date should it be necessary to create a new on-board database.
Note that the original data files will not be modified by saving the data.
3.4 Creating the on-board files
Once any modifications have been made to the data, the files to be used on-board the measurement sensor may be created by
pressing the Export button.
A new dialog will be shown where it is necessary to give a name to the job that will be used on-board the sensor and to select the folder where the
on-board files will be stored.
Name: Enter a name for the job to store.
Browse to the folder where the job will be stored.
Location Name of the folder where the job will be stored.

LandXML is a format that was designed to model and transfer Land Planning, Civil Engineering and Survey data between software applications. It
is now used as a standard data transfer format between most of the major software suppliers in the geomatics field. More information about
LandXML format may be found at the LandXML website: http://www.landxml.org
3.5.1 Supported LandXML entities
The Design to Field PLA LandXML importer imports the following LandXML entities:
Points
Points contained in the <CgPoints> section of a LandXML file are imported as points to the System 1200 database. An example of the CgPoints
section of a LandXML file that may be imported follows:
<CgPoints>
<CgPoint name="PtID1" oID="Pk436" code="" desc="">4600896.000 308783.000 740.000</CgPoint>
<CgPoint name="PtID2" oID="0001" code="" desc="">4600776.019 308740.897 740.501</CgPoint>
<CgPoint name="PtID3" oID="0002" code="" desc="">4600776.019 308740.897 740.501</CgPoint>
</CgPoints>
Lines
The following LandXML entities are imported as lines to the System 1200 database from the <CoordGeom> section of the LandXML file:
<Line>, e.g.
<Line staStart="5704.481000">
<Start>674066.231000 329437.258000</Start>
<End>674311.422000 329511.122000</End>
</Line>
<IrregularLine> e.g.
<IrregularLine>
<Start>187241.2000 278792.0500</Start>
<End>187246.3500 278783.4500</End>
<PntList2D>187241.2000 278792.0500 187242.2500 278790.3000 187246.3500 278783.4500 </PntList2D>
</IrregularLine>
LandXML <Curve> elements are imported as arcs in the System 1200 database, e.g.
<Curve staStart="6045.683000" rot="cw" crvType="arc" radius="600.000000">

<Start>674392.309000 329537.591000</Start>
<Center>674178.960144 330098.378184</Center>
<End>674495.830000 329588.875000</End>
</Curve>
3.6 Importing DXF data
DXF is perhaps the most widespread formats used for interchanging geomatics data until the present time. It is a format that is based on co-
ordinate geometry elements rather than survey related entities and as such has many limitations. The most important limitation when importing
DXF data for use on a survey sensor is the lack of a point ID for point elements. Although many solutions have been implemented in various
survey software, no generic solution is available to solve this problem. For this reason, points and lines are automatically assigned a point ID when
imported from a DXF file based on the position of the entity in the DXF file.
After selecting the DXF file to import, the user may select how the
DXF information should be imported:
Select Layers to import

This selection box allows the user to select which elements should
be imported from which layers of the DXF file. A full list of the DXF
entities supported by the points, lines and area DXF importer may
be found in §3.6.1.
DXF File Linear Units

The majority of DXF files do not contain information regarding the
linear units of the file. Given that this information is required in the
System 1200 database it is necessary to select the units in which
the DXF file was written.
Point ID prefix
As stated previously, no generic method of naming points is
available in the DXF format definition. The points, lines and area
importer numbers the points sequentially in the System 1200
database starting with the number 1 and incrementing each point by
1. In addition, a prefix may be added to each point number if
required.
Line ID prefix
Lines imported from the DXF do not have identifiers. The points, lines and area importer numbers the lines sequentially in the System 1200
database starting with the number 1 and incrementing each line by 1. In addition, a prefix may be added to each line number if required.
Import Points on lines and polylines as separate entities

Each line or polyline in a DXF file is made up of a series of points. It may interest the user to create these points in the System 1200 database
(e.g. to stake out the points) or not (e.g. if the DXF data is to be used simply as a background map).
If the checkbox Import Points on lines and polylines as separate entities is selected, points will be created at the vertex of all lines in the DXF
file. If the checkbox is not selected, no points will be selected.
The difference may be seen in the following screenshots:
Import Points on lines and polylines as separate entities selected Import Points on lines and polylines as separate entities not selected
3.6.1 Supported DXF entities
The Design to Field DXF points, lines and area importer imports the following DXF elements:
Points
The following DXF entities are imported as points in the System 1200 job:
POINT
The co-ordinates of a DXF POINT entity are imported to the System 1200 database as a point. The point ID of each point is assigned
automatically based on the order of the POINT entities in the DXF file. Point ID’s may be assigned a prefix during the conversion if required.
Each point is given a point code with the same name as the DXF layer from which it was imported.
The POINT entity in the DXF file resembles the following excerpt. The layer and attributes for each point may change with respect to the example:
0
2
POINT
70
64
10
0.0
20
0.0
30
0.0
3
BLOCK
DXF BLOCK entities are often used in DXF files to contain symbol information, given that this information is normally superfluous in the field and
would interfere with the selection of points and lines on the sensor screen, only the insertion point of the BLOCK entity is imported into the System
1200 database. The point ID of each point is assigned automatically based on the order of the BLOCK entities in the DXF file.
Each System 1200 point imported from a DXF BLOCK is given a point code with the same name as the BLOCK. The point code is included in a
point group with the same name as the DXF layer of the BLOCK. The point code description of every DXF BLOCK imported into System 1200 is
set to the text DXF Block.
In the following example, the DXF BLOCK would be imported with the point code BENCHM. This point code would be placed in the point code
group HEIGHTINFO.
0
BLOCK
8
HEIGHTINFO
2
BENCHM
70
64
Lines
The following DXF entities are imported as lines in the System 1200 job:
LINE
A DXF LINE entity is imported to the System 1200 database as a line. The line ID of each line is assigned automatically based on the order of the
LINE entities in the DXF file. Line ID’s may be assigned a prefix during the conversion if required.
Each line is given a line code with the same name as the DXF layer from which it was imported.
The LINE entity in the DXF file resembles the following excerpt. The layer and attributes for each line may change with respect to the example:
0
LINE
8
0
10
-0.193702
20
0.00637
30
0.0
11
0.231854
21
0.00637
31
0.0
ARC
A DXF ARC entity is imported to the System 1200 database as a line with an arc flag. Each arc will be drawn as such on-board the System 1200
sensor. The line ID of each line is assigned automatically based on the order of the ARC entities in the DXF file. Line ID’s may be assigned a
prefix during the conversion if required.
The ARC entity in the DXF file resembles the following excerpt. The layer and attributes for each line may change with respect to the example:
0
ARC
8
0
10
5.485202
20
8.804875
30
0.0
40
4.597739
50
217.066148
51
56.595122
POLYLINE / LWPOLYLINE
A DXF POLYLINE or LWPOLYLINE entity is imported to the System 1200 database as a line. The treatment of an LWPOLYLINE is exactly the
same as a normal polyline during import. The importer takes into account any arcs that may be defined within the polyline and draws them as arcs
on-board the System 1200 sensor. Closed polylines and lwpolylines are also imported.
The line ID of each line is assigned automatically based on the order of the LINE entities in the DXF file. Line ID’s may be assigned a prefix during
the conversion if required.
The POLYLINE entity in the DXF file resembles the following excerpt. The layer and attributes for each line may change with respect to the
example. The LWPOLYLINE is virtually identical to the POLYLINE definition:
POLYLINE
8
G8010035
66
1
70
0
0
VERTEX
8
G8010035
.
.
3.6.2 Treatment of DXF Layers
DXF files are normally divided into layers that allow different parts of the same job to be viewed or edited in the original application.
System 1200 allows the same layers to be maintained by assigning all DXF entities in the same layer the same code group. This allows code
groups to be turned on and off on-board the sensor using the System 1200 filtering functionality in much the same way as layers can be turned on
and turned off in a CAD application.
This functionality may be seen in the following example:
Visualisation of all layers / code groups in CAD program and System 1200
Visualisation of the same data after turning off a layer in the CAD application and the corresponding code group on the System 1200 sensor
4 Converting Digital Terrain Model data

In this chapter
4.1 Overview
4.2 How to create a DTM job
4.5 Importing data in GSI format
4.1 Overview
Digital terrain models may be imported to System 1200 for use with the RoadRunner suite of applications or with the Stakeout application. A
System 1200 DTM job may be created for each digital terrain model file. Each DTM may contain one or more layers on-board the System 1200
sensor.
4.2 How to create a DTM job
The generic process of creating a DTM job is described in this section, the actual screens may vary depending on the information available in the
imported data format. Any additional screens are explained in the section relating to each particular format.
To create a DTM job using the Design to Field component select the Tools/Design to Field option of the Leica Geo
Office PC application.
- Select the import type DTM Data
- Select the design format from the Importer drop-down list, additional format
converters can be added using the Manage button.
- To read the file containing the data to import, press the Import button and browse to the file.
- Once the data file to import has been defined, the data will be displayed graphically for review or edition before creating the on-board file.
See §3.3 and §3.4 for more information on how to use the graphical viewer and create the on-board files.
The Design to Field DTM LandXML importer imports the digital terrain models in triangular format contained in the <Surfaces> section of a
LandXML file.
A single DTM job is created for each LandXML file but a separate surface is created in the System 1200 job for each <Surface> in the <Surfaces>
section.
An example surface imported by the LandXML DTM importer is given below:
<Surface name="OTRA"> <!- - Surface name - ->

<Definition surfType="TIN">
<Pnts> <!- - List of coordinates - ->
4478409.3940 447171.3450 654.3630
4478415.7820 447168.4900 654.6290
4478409.4370 447171.2810 654.4690
4478382.4190 447143.7010 655.3650
4478384.6360 447142.9310 655.1490
4478384.5900 447142.8620 655.2830
4478386.4610 447142.0530 655.1500
4478386.5500 447141.9590 655.2570
4478409.4370 447171.2810 654.4690
4478394.1060 447138.5250 655.2670
4478394.0290 447138.5640 655.1360
</Pnts>
<Faces> <!- - List of triangles - ->
<F>1 2 3</F>
<F>4 5 6</F>
<F>6 7 8</F>
<F>9 10 11</F>
</Faces>
</Definition>
</Surface>
Triangular digital terrain models may be imported to System 1200 from DXF files. The triangles in the DXF file should be defined by the 3DFACE
DXF entity.
After defining the DXF file containing the digital terrain model the importer
scans the DXF file and presents a list of all of the layers that contain
3DFACE entities.
For each selected DXF layer, a separate surface is created in the System
1200 DTM job.
It is also necessary to define the linear units of the DXF file so that the
information is stored correctly on the System 1200 sensor.
An excerpt of a DXF file containing 3DFACE entities is shown below:
0 Start of record.
3DFACE Record is a 3D face entity.
TRIANGLE 3D face type.
10 X coordinate, first point.
723573.984000 X value.
20 Y coordinate, first point.
7663192.178000 Y value.
30 Z coordinate, first point.
23.383000 Z value.
11 X coordinate, second point.
723576.998000 X value.
21 Y coordinate, second point.
7663191.120000 Y value.
31 Z coordinate, second point.
23.029000 Z value.
12 X coordinate, third point.
723572.684000 X value.
22 Y cordinate, third point.
7663189.966000 Y value.
32 Z coordinate, third point.
24629.000 Z value.
0 End of record.
4.5 Importing GSI data
Digital terrain models in GSI format may be used on previous generations of Leica Geosystems sensors. The same GSI files can be imported for
use on System 1200 sensors using the GSI DTM importer.
DTM models in GSI format may only contain one DTM surface.
It is not possible to import a standard GSI points file as a DTM, the data must be arranged in triangles and conform to the GSI DTM format
definition. An example of GSI DTM data is given:
*41....+00000CHARRON2003 42....+00000000DTMNTWRK 43....+00000000DTMCOORD 44....+0000000000000000 45....+0000000000000000

*11....+0000000000003076 71....+TRI0000000000001 81..10+0000000305426640 82..10+0000005049311074 83..10+0000000000005663
*11....+0000000000003077 71....+TRI0000000000001 81..10+0000000305425426 82..10+0000005049311546 83..10+0000000000005696
*11....+0000000000004299 71....+TRI0000000000001 81..10+0000000305428849 82..10+0000005049312771 83..10+0000000000006347
*11....+0000000000003077 71....+TRI0000000000002 81..10+0000000305425426 82..10+0000005049311546 83..10+0000000000005696
*11....+0000000000003076 71....+TRI0000000000002 81..10+0000000305426640 82..10+0000005049311074 83..10+0000000000005663
*11....+0000000000003082 71....+TRI0000000000002 81..10+0000000305419640 82..10+0000005049313345 83..10+0000000000005603
*11....+0000000000004299 71....+TRI0000000000003 81..10+0000000305428849 82..10+0000005049312771 83..10+0000000000006347
*11....+0000000000003077 71....+TRI0000000000003 81..10+0000000305425426 82..10+0000005049311546 83..10+0000000000005696
*11....+0000000000004306 71....+TRI0000000000003 81..10+0000000305424385 82..10+0000005049313713 83..10+0000000000006107
WI41 Job identification, maximum 8 characters, may be defined by user.

WI42 Identification of DTM file, may not be changed by user. This entry must be +DTMNTWRK.
WI43 Identification of principal point type, may not be changed by user. This entry must be +DTMCOORD.
WI44 Optional easting offset. May be defined by user.
WI45 Optional northing offset. May be defined by user.
WI11 Point identification, ignored by the application.

WI71 Triangle number, indicates triangle the coordinates belong to.
WI81 Easting of the triangle vertex.
WI82 Northing of the triangle vertex.
WI83 Elevation of the triangle vertex.
5 Converting Road Data

In this chapter
5.1 Overview
5.2 How to create a road job
5.4 Importing data in GSI format
5.1 Overview
Road projects are generally defined by an horizontal and a vertical alignment. The rest of the project may be defined by cross-sections at given
intervals along the horizontal alignment or by a series of longitudinal line known as stringlines.
Design to Field can import both types of road definition, cross-sections and stringlines. Cross-section data is converted to stringlines during the
import process since data is stored on-board the System 1200 sensor in stringline format only.
Cross-section
Stringlines are thee-dimensional lines that define an edge of the road vertex
model. A stringline model is created from a collection of cross-sections by
joining the vertices of each cross-section to the preceding and following
Stringline
cross-section.
Given that a cross-section may have more or less points than the adjacent
cross-sections, conflicts may arise when generating stringlines from cross-
section data. These conflicts need to be solved before a stringline model
can be produced. Design to Field uses a software component called the
Possible conflict
Connection Editor to solve these conflicts.
When cross-section data is imported from the original data files, the cross-section vertices are joined together by the Connection Editor in order to
create stringlines using a series of criteria such as the distance of the vertex from the centreline and the relative position of the vertex along the
cross-section. The user should then review the connections before creating the on-board files to ensure that the conflicts have been resolved
adequately and to modify any of the connections, if required.
5.2 How to create a road job
The generic process of creating a road job from imported cross-section is described in this section, the actual screens may vary depending on the
information available in the imported data format. Any additional screens are explained in the section relating to each particular format. The
process for importing stringline data is similar but does not involve use of the Connection Editor.
- To create a road job using the Design to Field component select the Tools/Design to Field option of the
Leica Geo Office PC application.
- Select the Importer Type Road Data.
- Select the design format from the Importer drop-down list,

additional format converters can be added using the Manage
button.
- To start the conversion, press the Import button.
- Browse to the files containing the horizontal alignment, vertical

alignment and cross-sections and press the Next button. Note that it
is not required to work with a vertical alignment or cross-sections if
these data are not available.
- Enter the job details and press the Next button. These details are stored
in the System 1200 job and may be used to identify the data and the
creator on-board the sensor.
- Enter the checking tolerances and press the Next button. When importing data,
Design to Field checks that the data is coherent before writing it to the road job.
If a difference greater than the defined horizontal and vertical tolerances is found
in the data, an error is generated and the user is advised where in the data the
error has occurred. In this case the data should be verified and the import
process restarted.
- Once the data has been read successfully, a summary of the data is shown. The
Finish button should be pressed to close the import wizard. The data will now be
displayed in the graphical viewer for review and modification before creating the on-
board files.
- At this stage the data has been read from the file and the vertices of each cross-section have been joined to the vertices in the preceding
and following cross-section automatically. It is now required to check the connections and modify them should the algorithm that connects
the vertices use different criteria from the required ones. This may be done using the Connection Editor.
5.3 Connection Editor
The Connection Editor allows cross-section based road data to be converted to three-dimensional lines (stringlines) for use on-board System
1200.
When cross-section data is imported from the original data files, the cross-section vertices are joined together in order to create stringlines using a
series of criteria such as the distance of the vertex from the centreline and the relative position of the vertex along the cross-section.
The stringlines may be viewed and, if required, edited using the Connection Editor. The Connection Editor may be accessed using the icon.
Note: The Connection Editor may only be accessed when importing cross-section based data.
5.3.1 Layout
The Connection Editor is divided into three panels:
Plan View (a), Cross-section View (b), Cross-section Data (c)

At any one time, three cross-sections are displayed. Only cross-sections at chainages that are contained in the original data file are displayed.
5.3.1.1 Plan View
The perspective of the Plan View of the data may be thought of as looking down on the road design from above where all of the curves in the
alignment have been taken away. This view allows a plan perspective of how the vertices of the cross-sections have been joined to create
stringlines.
The zoom and pan tools function in this view in the same way as in the Viewer application with the exception that the vertical axis of the window is
not scaled.
Any cross-section vertex may be selected with a mouse click. The corresponding vertex will also be highlighted in the Cross-Section View.
5.3.1.2 Cross-section View
The cross-section view allows the cross-section data to be viewed at the chainages that were contained in the original data.
The zoom and pan tools function in this view in the same way as in the Viewer application in all three cross-section views.
Any cross-section vertex may be selected with a mouse click. The corresponding vertex will also be highlighted in the Plan View.
5.3.1.3 Cross-section Data
The numeric values of the cross-section data may be viewed in this section. The chainage of the cross-section together with the distance from
centreline and absolute height of the selected vertex may be viewed.
5.3.2 Layer Tool
The Layer Tool is similar in operation to the Layer Tool in the Viewer.
When the layer button is pressed, a menu is opened where all of the layers of imported data may be
viewed.
Turn-on / turn-off the layer in the plot view.
This button is only used for visualisation purposes, it does not affect whether the data from this layer will be exported to the System
1200 job.
Join / do not join vertices in the cross-section across the centreline.
View only the selected layer. All layers in the job will be turned-off except for the selected layer.
5.3.3 Navigation Tools
The navigation tools allow each of the cross-sections in the job to be viewed.
Go to the first cross-section in the job
Go to the last cross-section in the job
Go to the previous cross-section in the job
Go to the next cross-section in the job
The Play and Stop buttons allow the cross-sections throughout the job to be viewed continuously one after the other. The Play
button starts the sequence and the stop button stops the sequence.
The Chainage field in the cross-section data panel may also be used to display a cross-section at a given
chainage. Enter the chainage of the cross-section to be displayed and press the arrow key.
5.3.3.1 Selecting a vertex
A vertex may be selected in any of the three panels (Plan View, Cross-Section View, Cross-section data).
To select a vertex graphically in the plan view or the cross-section view, simply click on the vertex, the corresponding vertex will be shown in the
other view and the centreline offset and the height of the point will be shown in the cross-section data panel.
To navigate across the section, use the arrow keys in the cross-section data panel.
To move to a given chainage, type the chainage into the chainage field and press the arrow button.
5.4 Connection Tools
The connection tools may be used to connect or disconnect points in the cross-section should they have been connected erroneously.
5.4.1 Connect / Disconnect a vertex
To disconnect two vertices in adjacent cross-sections, select the required vertex in the middle cross-section and the corresponding vertex
in the preceding or following cross-section. If the two selected vertices are connected, the disconnect button will be enabled. Click on the
disconnect button to disconnect the two vertices.
To connect two vertices in adjacent cross-sections, select the required vertex in the middle cross-section and the corresponding vertex in
the preceding or following cross-section. If the two selected vertices are disconnected, the connect button will be enabled. Click on the
connect button to connect the two vertices.
5.4.1.1 Continue / Discontinue a vertex
In some cases it is required to continue a stringline to the next cross-section instead of joining the vertex to another vertex.
In the following example, the vertices 1, 2 and 4 are connected to the corresponding vertex in the next cross-section whereas the vertex 3 is
continued at the same distance and height offset from the centreline.
To continue a vertex until the next cross-section, the vertex must be disconnected from all other vertices. Select the vertex in the middle
cross section and press the continue button.
To discontinue a vertex that has been continued until the next cross-section, select the vertex in the middle cross section and press the
discontinue button.
5.5 Creating the on-board database files
Once all of the connections have been verified, the on-board database may be created on returning to the graphical viewer and using the Export
button.
Name: Enter a name for the job to store.
Browse to the folder where the job will be stored.
Location Name of the folder where the job will be stored.
Allow chainages greater than 214000.0m
If chainages greater than 214000m are to be used on the job, this

checkbox should be selected.
Chord-Curve Tolerances
Given that stringlines are lines described by a collection of three-dimensional points, a sufficient number of points along the stringline must be
stored so that the stored line is a close representation of the original data. On the other hand, the larger the number of points stored on-board the
sensor, the more performance is affected. In order to strike a balance between the true representation of the design model and the size of the on-
board database, it is possible to enter a maximum tolerance value that ensures that stored model will not deviate from the original model by more
than the stipulated value. Separate tolerance values may be specified for
horizontal and vertical values.
Stringline
Point
The maximum horizontal tolerance is the value applied to the stringline furthest
a from the centreline. Using the diagram as a reference, the horizontal chord-
curve difference that will be checked during conversion will be the value a.
b
Stringline
Point
Centreline
Outermost It should be noted that the outermost stringline always has the maximum
Stringline horizontal chord-curve difference (a) and that the innermost stringlines will
always have a chord-curve difference less than this maximum value (i.e. a will
always be greater than b).
- Once all conflicts have been solved, press the OK button to create the on-board data.
- If the path of the folder used for the new job was not the CF card used by the sensor, copy the newly created files to the DBX folder of the
CF card of the sensor.
The Design to Field LandXML road data importer imports data in both stringline and cross-section format. The definition for the horizontal and
vertical alignments is identical for both types of road model.
The horizontal and vertical alignments are contained in the <Alignment> section of the LandXML file which has the following format:
<Alignment name="Centerline" length="619.253000" staStart="100.000000">

<CoordGeom>
<Profile>
</Alignment>
The horizontal alignment is contained in the <CoordGeom> section and the vertical alignment is contained in the <Profile> section.
5.6.1 Horizontal alignment

It is possible to define the horizontal alignment with the following LandXML entities:
– Line
– Curve
– Spiral
5.6.1.1 Line
The Line element defines the make up of a straight component in the stringline. The attribute staStart can be written to the element. This is the
start station (chainage) of the element.
For each Line element the following sub-elements are required:
– Start (2D coordinate defining the beginning of the line)

– End (2D coordinate defining the end of the line)
5.6.1.2 Line example

A line element should look like:
<Line staStart="0.000000">
<Start>2000.000000 6000.000000</Start>
<End>2186.841000 6068.005000</End>
</Line>
5.6.1.3 Curve
The Curve element is used to define curves in the horizontal alignment of a stringline.
For each Curve element the following sub-elements are required:
– Start (2D coordinate defining the beginning of the curve)

– Center (2D coordinate defining the center of the curve)
– End (2D coordinate defining the end of the curve)
The following attributes are required for the Curve element:
– rot (rotation; can have the values “cw” or “ccw”)

– radius
The following optional attributes are also supported:
– staStart
– crvType (Should be entered as “arc”)
5.6.1.4 Curve example

A curve element should look like:
<Curve staStart="348.832000" rot="cw" crvType="arc" radius="100.000000">

<Start>2307.751000 6150.344000</Start>
<Center>2218.672427 6195.786357</Center>
<End>2304.071000 6247.816000</End>
</Curve>
5.6.1.5 Spiral
The element Spiral is used to define any spiral in the horizontal alignment.
For each Spiral element the following sub-elements are required:
– Start (2D coordinate defining the beginning of the spiral)

– PI (2D coordinate defining the “Point of Interest” of the spiral)
– End (2D coordinate defining the end of the spiral)
The PI (Point of Interest) is related only to the spiral element.
PI
End
Start
The following attributes are required when defining a Spiral element:
– Length (length of the curve)

– RadiusStart
– radiusEnd
– rot
– spiType (“clothoid”, “bloss” and “cubic” are supported)
The following optional attributes are also supported:
– staStart
– desc
– constant
“INF” is used to define a tangent (radius = infinity). The “rot” attribute defines whether the arc travels clockwise or counter-clockwise from the Start
to End point. The “constant” attribute can store the spiral constant. If the constant cannot be provided (through calculations or input or due to the
spiType) then the attribute value should be left blank.
5.6.1.6 Spiral example

This example is for a curve to tangent clothoid spiral:
<Spiral staStart="450.724000" desc="CurveToTangent" length="100.001000" radiusStart="99.999000" radiusEnd="INF" rot="cw" spiType="clothoid" constant="100">

<Start>2304.071000 6247.816000</Start>
<PI>2286.304084 6276.978259</PI>
<End>2227.794000 6310.759000</End>
</Spiral>
This example is for a cubic parabola Spiral:
5.6.2 Profile (Vertical Alignment)

The element Prof must contain only one sub-element ProfAlign. Within this sub-element the vertical alignment is defined.
5.6.3 Prof example

<Profile>
<ProfAlign name="VERTICAL ALIGNMENT">
</ProfAlign>
</Profile>
5.6.3.1 ProfAlign
The ProfAlign element contains the definition of the vertical alignment of the stringline.
There must be at least on sub-element in the ProfAlign. The ProfAlign element must contain one of the sub-elements:
– PVI (Point of Vertical Interest)

– CircCurve (Circular Curve)
– ParaCurve (Parabolic Curve)
5.6.3.2 ProfAlign example

This example contains the three supported elements:
<ProfAlign name="VERT">
<PVI>0.000000 0.000000</PVI>
<PVI>25.000000 5.000000</PVI>
<CircCurve length="15.047489" radius="100.000000">32.462310 6.065348</CircCurve>
<PVI>40.000000 6.000000</PVI>
<PVI>60.000000 6.500000</PVI>
<ParaCurve length="150.0000" desc="-2225.000000">110.000000 7.748596</ParaCurve>
<PVI>160.000000 6.750000</PVI>
</ProfAlign>
5.6.3.2.1 PVI (Point of Vertical Interest)

The PVI point represents the start or end point of any straight, circular curve, parabolic curve or any point on the vertical alignment. The PVI
contains a space delimited station (chainage) of the stringline and elevation.
5.6.3.2.2 PVI example

In this example the PVI elements act as the start and end points for a straight running between station (chainage) 0.000 and 25.000.
<ProfAlign name="VERT">
<PVI>0.000000 0.000000</PVI>
<PVI>25.000000 5.000000</PVI>
</ProfAlign>
5.6.3.2.3 CircCurve
The CircCurve element represents part of what is needed to define a circular curve. The start and end coordinates are included in PVIs.
The CircCurve element requires the attributes:
– length (length of the curve) The length is defined by the chainage difference between the start PVI point and end PVI point.
– Radius
A typical vertical circular curve would be defined by:
CircCurv
PVI PVI
5.6.3.2.4 ParaCurve
The ParaCurve represents a point of vertical interest that is used to define a vertical parabolic curve.
The ParaCurve element requires the attributes:
– Length (The length is defined by the chainage difference A to B)
A typical ParaCurv would be defined in a similar way to the CircCurve.
ParaCurv
PVI PVI
5.6.4 Cross-sections
Cross-section data may be imported using the LandXML <CrossSects> entity.
An example of a LandXML cross-section follows. A layer is created in the System 1200 database for each unique <CrossSectSurf> in the
LandXML file. The name of the layer on-board is the same as the <CrossSectSurf > name attribute (Layer 4 in the example).
<CrossSects>
<CrossSect sta="11270.000000">
<CrossSectSurf name="Layer 4">
<PntList2D>-3.500000 509.024000 0.000000 509.148000 6.949000 509.287000</PntList2D>

</CrossSectSurf>
</CrossSect>
</CrossSects>
5.6.5 Stringlines
Each stringlines in the LandXML file is stored as an <Alignment> with the following format:
<Alignment name="RL01" length="12684.981550" staStart="0.000000">
<CoordGeom>
<IrregularLine staStart="0.000000">
<Start>383106.333122 335289.793813</Start>
<End>389361.759948 345490.807029</End>
<PntList2D></PntList2D>
</IrregularLine>
</CoordGeom>
<Profile>
<ProfAlign name="RL01">
</ProfAlign>
</Profile>
</Alignment>
The horizontal part of the alignment consists of a two dimensional list of points and the vertical part of the stringline is stored as <Profile>. On-
board the System 1200 sensor, the stringline is given the same name as the corresponding <Alignment> in the LandXML file.
Note: A LandXML “add-on” software component is available for that may be embedded in 3rd party road design software. This component reads a
LandXML file and converts the data to the System 1200 on-board format. A more comprehensive description of the LandXML format used by
Design to Field is included with the add-on. Contact your local Leica Geosystems representative for more information.
5.7 Importing Bentley® LandXML data
Depending on the version of each application, LandXML data exported by Bentley software products (MX, InRoads / InRail and GeoPak) may use
different LandXML entities to describe road elements.
In all cases the horizontal alignment and vertical alignment files are exported in the format described in the preceding section but the surface
model of the project is described using breaklines in a separate LandXML file.
The LandXML file containing the surface model should have the following format:
<SourceData>
<Breaklines>
<Breakline brkType="standard" name="Eje" desc="Creado por el Modelador de Trazados1">
<PntList3D>
4600572.087899168 308587.997311171 704.890027935 4600574.229364767 308589.287320895 704.866653808 4600576.264023327 308590.512990516
704.844445482 4600576.370830366 308590.577330619 704.843279681 4600578.512295965 308591.867340343 704.819905554 4600580.653761564
308593.157350067 704.796531427 4600580.770998568 308593.227973138 704.795251784 4600582.795227164 308594.447359792 704.773157300
4600584.936692762 308595.737369516 704.749783173 4600587.078158361 308597.027379240 704.726409046 4600589.219623961 308598.317388964
</PntList3D>
<Feature code="Breakline">
<Property label="guid" value="c87fb2fc-fb56-42e3-87a7-5f823ad2d5cb"/>
<Property label="style" value="MOD EJE"/>
<Property label="triangulate" value="true"/>
<Property label="pointDensity" value="0.000000000"/>
</Feature>
</Breakline>
</Breaklines>
</SourceData>
Data files using these LandXML entities should be imported using the LandXML -Bentley converter instead of the standard LandXML converter.
5.8 Importing GSI data
Road data in GSI format may be used on previous generations of Leica Geosystems sensors. The same GSI files can be imported for use on
System 1200 sensors using the GSI road importer.
Road models in GSI format may only contain one layer per cross-section.
5.8.1 Horizontal Alignment

The following geometric elements are supported:
Tangent point: Station, Beginning (X,Y) "STRAIGHT"

Circular curve: Station, Beginning of arc (X,Y), Radius, "000CURVE"
Spiral in: Station, Beginning of curve (X,Y), A-Parameter (A= √LxR) "00SPIRIN"
Spiral out: Station, Beginning of curve (X,Y), A-Parameter (A= √LxR) "0SPIROUT"
Curve in: Station, Beginning of curve (X,Y), Radius 1, Radius 2 "0CURVEIN"
Curve out: Station, Beginning of curve (X,Y), Radius 1, Radius 2 "CURVEOUT"
End of Project: Station, Coordinates (X,Y) "00000EOP"
Header of the Horizontal Alignment File:
41....+000JOBID 42....+HZALIGNM 43......+STACOORD
WI 41 Job-Identification. Max. 8 ASCII-characters, may be defined by user.

WI 42 Identification of Horizontal Alignment file. May not be changed by user.
WI 43 Identification of principal point type file. May not be changed by user.
Data block
11....+KILOMETR 71....+0NEXTGEO 72....+0NEXTRAD 73....+0TEMPLNR 81..10+00000000 82..10+00000000
WI 11 Station (chainage) of the point.

WI 71 Type of the following geometric element.
WI 72 Radius of the next horizontal geometric element, Radius 1 for a compound curve, or the A-Parameter for spirals.
WI 73 Number of a cross-section (Template) assigned to the next geometric element.
WI 74 Radius 2 for compound curves.
WI 81 E-Coordinate of the point.
WI 82 N-Coordinate of the point.
Note:
- The header consists of a single block at the start of a data file.
- Tangents and the EOP contain “00000NON” in WI72
- Data units and decimal places in WI’s 11, 72 and 74 are defined by WI81 and WI82.
- If the radius point for a curve (circular or spiral) is to the left of the alignment (looking in the direction of increasing stations) the radius is
negative.
- If the radius point for a curve (circular or spiral) is to the right of the alignment (looking in the direction of increasing stations) the radius is
positive.
- A cross section (Template) may be assigned to more than one location.
- An alignment file must contain at least two elements. The last element must be "EOP".
- There is no limitation on the size of the Hz-alignment file. If a file is created/edited using the program "ROAD+FILE EDITOR" on the
TPS1100, there is a limitation of 200 data blocks.
5.8.1.1 Horizontal Alignment example
*41....+000000000000A6-B 42....+00000000HZALIGNM 43....+00000000STACOORD

*11....+0000000094562793 71....+00000000000CURVE 72....-0000000010200000 73....+0000000000000NON 81..10+0000000521157487 82..10+0000000494803311
*11....+0000000095222400 71....+00000000STRAIGHT 72....+0000000000000NON 73....+0000000000000NON 81..10+0000000521767106 82..10+0000000495054894
*11....+0000000095629192 71....+0000000000SPIRIN 72....+0000000000350000 73....+0000000000000NON 81..10+0000000522137922 82..10+0000000495222153
*11....+0000000095751692 71....+00000000000CURVE 72....+0000000001000000 73....+0000000000000NON 81..10+0000000522250574 82..10+0000000495270222
5.8.2 Vertical Alignment
Tangent point: Station, H "STRAIGHT"

Circular curve: Station, Radius, H "000CURVE"
Parabola: Station, Parabola parameter, H "0PARABOL"
End of Project: Station, H "00000EOP"
Header of the Horizontal Alignment File:
41....+000JOBID 42....+0VALIGNM 43......+STACOORD

WI 41 Job-Identification. Max. 8 ASCII-characters, may be defined by user.

WI 42 Identification of Vertical Alignment file. May not be changed by user.
WI 43 Identification of principal point type file. May not be changed by user.
Data block
11...+KILOMETR 71...+0NEXTGEO 72...+0NEXTRAD 83..10+00000000

WI 11 Station (chainage) of a vertical alignment point
WI 71 Type of the following geometric element
WI 72 Radius of the following geometric element or parabola parameter
WI 83 Elevation of the point block.
Note:
- Tangents and the EOP contain “00000NON” in WI72
- Data units and decimal places in WI’s 11 and 72 are defined by WI83.
- Tangent and arc lengths are calculated from the stationing.
- The stationing is projected onto a horizontal plane.
- If the curve radius point lies above the centerline, the radius is positive.
- If the curve radius lies beneath the centerline, the radius is negative.
- An alignment file must contain at least two elements.
5.8.2.1 Vertical Alignment example
41....+0example 42....+0VALIGNM 43....+STACOORD

11....+00000000 71....+STRAIGHT 72....+00000NON 83..10+00400000
11....+00300000 71....+0PARABOL 72....-01142932 83..10+00422500
11....+00500000 71....+STRAIGHT 72....+00000NON 83..10+00420000
11....+00550000 71....+0PARABOL 72....+02091126 83..10+00415000
11....+00850000 71....+STRAIGHT 72....+00000NON 83..10+00406522
11....+01127904 71....+00000EOP 72....+00000NON 83..10+00418605
5.8.3 Cross-sections
Height difference: Height difference from the vertical alignment

Horizontal distance: Distance from the horizontal alignment.
Cross section type: Differentiate between CUT and FILL cross sections
Slope: Slope ratio
Header of the cross-section file:
41....+00JOB_ID 42....+TEMPLATE
WI 41 Job identification. Max. 8 ASCII characters, user definable.

WI 42 Template file identification. May not be changed by user.
Data block
11....+0PROF_NR 35..10+DISTANCE 36..10+000HDIFF 71....+0000FILL 72....+00002000
WI 11 The cross section number.

WI 35 Horizontal distance from the centerline.
WI 36 Height difference from the centerline.
WI 71 Cross section type.
WI 72 Slope ratio.
Note:
- All data blocks having the same cross section number (WI11) belong together.
- All data blocks belonging to a cross section must be consecutive in the file to minimize file access.
- The data blocks for a cross section must be sorted from left to right across the section.
- Data units defined by WI 35+36.
- Cross-sections do not have to be sorted by number.
- A negative distance (WI35) indicates a point to the left of the centerline.
- A positive distance (WI35) indicates a point to the right of the centerline.
- The entries for cross section type and slope are optional.
- The non-zero slope entry must be attached only to the last point on each side of the cross section.
- A negative height difference (WI36) indicates a point below the centerline.
- A positive height difference indicates a point above the centerline.
- A cross-section may contain up to 48 points.
- A template file must contain at least one cross-section.
5.8.3.1 Cross-section example
41....+0EXAMPLE 42....+TEMPLATE
11....+QP000123 35..10-00013000 36..10-00003000
11....+QP000123 35..10-00010000 36..10-00005000
11....+QP000123 35..10-00004000 36..10-00000100
11....+QP000123 35..10+00004000 36..10+00000100
11....+QP000123 35..10+00010000 36..10-00006000
11....+QP000123 35..10+00013000 36..10-00003500
11....+QP000124 35..10-00012000 36..10-00002000
11....+QP000124 35..10-00011000 36..10-00004000
11....+QP000124 35..10-00004000 36..10+00000100
11....+QP000124 35..10+00004000 36..10-00000100
11....+QP000124 35..10+00011000 36..10-00005000
11....+QP000124 35..10+00012000 36..10-00002500
11....+QP000125 35..10-00012000 36..10-00002000
11....+QP000125 35..10-00011000 36..10-00002500
11....+QP000125 35..10-00004000 36..10-00000070
11....+QP000125 35..10+00004000 36..10-00000070
11....+QP000125 35..10+00011000 36..10-00002500
11....+QP000125 35..10+00012000 36..10-00002000
11....+TEMPLATE 35..41-00002000 36..11+00000000 71....+0000FILL 72....+00002000
11....+TEMPLATE 35..41-00000500 36..11+00000000 71....+0000FILL 72....+00000000
11....+TEMPLATE 35..41+00000000 36..11+00000000 71....+0000FILL 72....+00000000
5.8.4 Cross-section assignment
Cross Section number: The number or identifier of the cross section

Chainage: The chainage from which the cross section is applied must have a corresponding cross-section file.
Header of the cross-section assignment file:
410001+000ASKER 42..10+ASSIGNMT 43....+CRSASKER
WI41 Job identification. Max. 8 ASCII characters, user definable.

WI42 Cross section assignment file identification. May not be changed by user. Data units are defined by characters 6+7 of WI42.
WI43 Name of the corresponding cross section file.
Data block:
110002+0000NORM 71....+00382000
WI 11 The cross section number or identifier

WI 71 Start chainage for that cross section
Note:
- A cross section assignment file must have a corresponding cross section file.
- A cross section remains valid until a new cross section is assigned.
- A given cross section may be assigned more than once.
- The units for station (chainage) are defined in WI 42 in the file header.
5.8.4.1 Cross-section assignment example
410001+000asker 42..10+ASSIGNMT 43....+CRSASKER

110002+0000NORM 71....+00382000
110003+0000NORM 71....+00552000
110004+00000568 71....+00568000
110005+000568.1 71....+00568100
110006+000585.1 71....+00585100
110007+000585.2 71....+00585200
110008+0000NORM 71....+00611000
110009+0000NORM 71....+00775000
110010+00000811 71....+00811000
110011+000826.9 71....+00826900
110012+00000827 71....+00827000
110013+00000827 71....+00844000
110014+000826.9 71....+00844100
110015+00000860 71....+00860000
Although the DXF format does not directly support road alignments, many infrastructure projects (e.g. housing estates) may be designed in CAD
programs that export DXF files with the aim of staking out the linear entities (e.g. walls, kerbs etc.) that the project contains. For this reason, it is
possible to read a DXF file and stakeout the linear entities of the DXF file using the RoadRunner Individual Stringline function.
The Design to Field DXF road data importer converts the following DXF entities into stringlines:
LINE
ARC
POLYLINE
LWPOLYLINE
For a more detailed description of these entities, see §3.4.
After defining the DXF file to import, a list of the layers in the DXF file
that contain polylines is displayed.
Select the layers to import

Select the layers to export to the System 1200 job. A layer will be
created in the System 1200 job with the same name as the DXF
layer and will contain all of the polylines that correspond to that layer.
DXF File Linear Units

The majority of DXF files do not contain information regarding the
linear units of the file. Given that this information is required in the
System 1200 database it is necessary to select the units in which the
DXF file was written.
Line ID prefix
Lines imported from the DXF do not have identifiers. The points, lines
and area importer numbers the lines sequentially in the System 1200
database starting with the number 1 and incrementing each line by 1.
In addition, a prefix may be added to each line number if required.
5.10 Importing data in the MX Genio format
The MX Genio format is a stringline based format thus no conversion from cross-sections to stringlines is necessary.
All data, horizontal alignment, vertical alignment and all stringlines are contained within the same data file.
After selecting the MX Genio data file, it is necessary to select the

horizontal alignment from the stringlines in the file.
Centreline
The horizontal and vertical alignment is generally not flagged in an MX
Genio file. It is necessary therefore to select one of the stringlines in
the file as the centreline.
Choose from
Any stringline may selected as the centreline but in order to simplify
the choice when a file contains many strings, it is possible to filter the
stringlines by displaying the M strings, the G strings and the co-
ordinate strings or any combination of these strings using the
corresponding check boxes.
When the centreline has been selected, press the Next button.
Any combination of stringlines may be exported from the MX Genio

file. The Sort and select stringlines dialog allows the strings to be
exported to the System 1200 sensor to be selected.
Note:
There are some differences in the way the RoadRunner and MX handle stringlines. Users should be aware of these differences when making a
conversion from an MX/Moss file in GENIO format:
- Only one instance of a stringline can be used in RoadRunner. The stringline may have gaps and appear and disappear throughout the job but
the relative position of the stringline in the design cannot change. In MX it is possible for a stringline with the same name to appear in an infinite
number of positions in the design.
- In MX a stringline may crossover itself (e.g. an exit ramp), if the exact chainage where this occurs is selected in the RoadRunner application, the
relative order of the stringlines may not be maintained.
- MX allows different stringlines to cross over each other, if the exact chainage where this occurs is selected in the RoadRunner application, the
relative order of the stringlines may not be maintained.
5.11 Importing data in the Avance format
The horizontal alignment data should be separated by spaces.
Element_Number Chainage Eastings Northings Bearing Radius Parameter Length
Element_Number (Integer) : Correlative number of element within file. Should start with 1 and increment in steps of 1.
Chainage (Double) : Chainage at start of element
Eastings (Double) : Eastings ordinate at start of element
Northings (Double) : Northings ordinate at start of element
Bearing (Double) : Bearing of alignment at start of element
Radius (Double) : Radius of curvature of element.
Parameter (Double): The value of the clothoide parameter (always positive)
Length (Double): The length of the element.
Note:
- If the curve is towards the left in the direction of increasing chainage, the radius is negative.
- If the element is a straight the radius is 0.
- If the element is the start of a clothoide (spiral) whose radius is infinite at the start of the element, the radius should have a value of 0.001
if it turns to the right and -0.001 if it turns left.
- If the element is the start of a clothoide (spiral) whose radius is a known value, the known radius at the start of the clothoide should be
used.
1 0.000 501972.519 792983.872 226.6746 -400.000 0.000 55.290

2 55.290 501953.581 792931.973 217.8750 -400.000 -130.002 42.251
3 97.541 501943.311 792890.995 214.5127 0.000 0.000 199.169
4 296.710 501898.299 792696.979 214.5127 0.001 130.000 60.357
5 357.067 501882.564 792638.741 221.3742 280.000 0.000 329.687
6 686.755 501634.316 792451.458 296.3333 280.000 -130.000 60.357
7 747.112 501573.996 792452.318 303.1948 0.000 0.000 159.764
8 906.876 501414.433 792460.332 303.1948 0.001 120.000 40.000
5.11.2 Vertical alignment file
The vertical alignment data should be separated by spaces.
Element_Number Chainage Height Slope Parameter Length
Element_Number (Integer) : Correlative number of element within file. Should start with 1 and increment in steps of 1.
Chainage (Double) : Chainage at start of element
Height (Double) : Height at start of element
Slope (Double) : Slope in %, positive if element rises, negative if element falls
Parameter (Double) : Parabolic parameter (kV)
Length (Double): The length of the element.
Note:
- If the element is a straight, the parameter has a value of 0
- If the element is a parabola, the sign of the parameter is given by subtracting the entry slope from the exit slope (p1 – p2). If the result of
the subtraction is negative, the value of the parameter will also be negative.
1 1000.000 146.933 0.004994 0.000 21.914

2 1021.914 147.042 0.004994 -15065.000 49.486
3 1071.400 147.208 0.001709 0.000 31.626
4 1103.026 147.262 0.001709 3003.000 19.496
5 1122.522 147.359 0.008203 0.000 26.613
6 1149.135 147.577 0.008203 -1000.000 88.200
7 1237.335 144.411 -0.080006 0.000 19.019
8 1256.354 142.889 -0.080006 900.000 72.098
9 1328.452 140.009 0.000107 0.000 1.234
10 1329.686 140.009 0.000107 0.000 0.001
5.11.3 Cross-section file
For each cross-section the following data is required:
Cross-section chainage
Distance_to_CL Height
.
..
…
Empty line
Cross-section chainage: Chainage at which cross-section starts in format xxx+xxx.xx

Distance_to_CL: Distance from point to centre line, negative if to left.
Height: Absolute height of point
400+100.00
-5.650 922.000
-4.500 930.100
-3.500 931.100
-2.500 931.180
3.000 931.280
4.500 931.490
5.000 931.700
6.000 931.700
400+200.00
-5.650 938.000
-4.500 990.100
-3.500 921.100
-2.500 926.180
3.000 931.280
4.500 931.490
5.000 931.700
6.000 931.700
5.12 Importing data in the REB format
The REB format is a cross-section based format that allows the import of cross-sections in layers. Up to 99 layers may be imported. A layer is
created in the System 1200 database for each layer in the REB cross-section file.

The horizontal alignment file should have the extension *.040 or *.d40
040 1 412.697 0.000 0.0000 0.000 184.0374948 3504880.526 5373134.370

040 1 437.810 25.113 0.0000 500.000 184.0374948 3504886.757 5373110.043
040 1 637.810 200.000 -1250.0000 0.000 178.9445367 3504941.513 5372917.744
040 1 696.516 58.706 -1250.0000 -500.000 175.9546517 3504961.874 5372862.687
040 1 896.516 200.000 0.0000 440.000 170.8616935 3505045.413 5372681.032
040 1 1090.116 193.600 1000.0000 0.000 177.0241729 3505125.283 5372504.764
040 1 1256.392 166.276 825.0000 0.000 187.6095874 3505170.824 5372345.046
040 1 1768.629 512.237 825.0000 -400.000 227.1368911 3505112.577 5371844.374

The vertical alignment file should have the extension *.021 or *.d21
021 0 649219 61791 0

021 0 825607 62827 176470
021 0 1587709 62129 214020
021 0 1900000 58582 0

The cross-section alignment file should have the extension *.055, *.d55, *.066 or *.d66
The cross-section file may contain layers. It is possible to export any number of layers from the REB file.
D66 format:
66 20 780000 1 -5500 62587 -4000 62534 0000 62394 4000 62254

66 20 780000 2 5500 62202
66 20 800000 1 -5500 62650 -4000 62598 0000 62458 4000 62318
66 20 800000 2 5500 62265
66 20 820000 1 -5500 62706 -4000 62653 0000 62513 4000 62373
66 20 820000 2 5500 62321
66 20 840000 1 -5500 62754 -4000 62701 0000 62561 4000 62421
66 20 840000 2 5500 62369
D55 format:
055-1 810.000 0.00 42.62 2.63 42.55 4.37 42.51

055 1 810.000 0.00 42.62 1.38 42.65 3.27 42.57
055-1 820.000 0.00 42.60 2.63 42.53 4.37 42.49
055 1 820.000 0.00 42.60 1.38 42.63 3.27 42.56
055-1 830.000 0.00 42.58 2.63 42.51 4.37 42.47
055 1 830.000 0.00 42.58 1.38 42.61 3.27 42.54
055-1 840.000 0.00 42.56 2.63 42.49 4.37 42.45
055 1 840.000 0.00 42.56 1.38 42.59 3.27 42.52
055-1 850.000 0.00 42.53 2.63 42.47 4.37 42.42
055 1 850.000 0.00 42.53 1.38 42.57 3.27 42.49
5.13 Importing data in the Cartomap format
The Cartomap format is a cross-section based format that allows the import of cross-sections in layers. A layer is created in the System 1200
database for each layer in the Cartomap cross-section file.
Cross-section layers are available from Cartomap v5.0 onwards, the Cartomap road data importer also accepts data files from previous versions
of Cartomap.

definição do traçado em planta de: Eje_1
P.K. X Y Cota Rumo Comprimento Tipo raio Parâmetro

0+000.000 6196.694 7591.315 804.494 76.6817 247.281 Recta
0+050.000 6243.377 7609.222 800.569 76.6817
0+062.125 6254.698 7613.565 799.122 76.6817
0+100.000 6290.061 7627.130 795.446 76.6817
0+101.790 6291.732 7627.771 795.339 76.6817
0+150.000 6336.744 7645.037 790.425 76.6817
0+200.000 6383.427 7662.944 789.697 76.6817
0+216.423 6398.761 7668.826 790.923 76.6817
0+247.281 6427.571 7679.878 791.960 76.6817 108.000 Clotóide -300.000 180.000
0+250.000 6430.110 7680.852 791.943 76.6744
0+265.644 6444.705 7686.484 792.583 76.3504

definição do traçado em alçado de: Eje_1
P.K. Cota terreno RASANTE EJE_1 Dif. Cotas Inclinação Kv Cota vértice
0+000.000 804.494 802.085 -2.409 -4.770000
0+050.000 800.569 799.700 -0.869 -4.770000
0+062.125 799.122 799.122 -0.000 -4.770000
0+100.000 795.446 797.315 1.869 -4.770000
0+101.790 795.339 797.230 1.891 -4.770000 1900.858
0+150.000 790.425 795.545 5.120 -2.233778 1900.858
0+200.000 789.697 795.085 5.388 0.396613 1900.858
0+216.423 790.923 795.222 4.299 1.260616 1900.858

0+247.281 791.960 795.861 3.901 2.883942 1900.858
0+250.000 791.943 795.941 3.999 3.027003 1900.858
0+265.644 792.583 796.479 3.896 3.850000 1900.858

pontos singulares da secção tipo: Eje_1
P.K. Nivel X Y distância Cota terreno Cota secção Dif. cotas

0+000.000 Nivel 1 6193.539 7599.539 -8.809 803.573 801.494 -2.079
6193.784 7598.901 -8.125 803.629 801.153 -2.476
6194.142 7597.967 -7.125 803.744 801.153 -2.591
6194.321 7597.501 -6.625 803.796 801.403 -2.394
6194.724 7596.450 -5.500 803.915 801.965 -1.950
6194.903 7595.983 -5.000 803.968 801.985 -1.983
6195.440 7594.583 -3.500 804.126 802.015 -2.111
6196.694 7591.315 0.000 804.494 802.085 -2.409
6197.948 7588.047 3.500 804.863 802.015 -2.848
6198.485 7586.647 5.000 805.021 801.985 -3.036
6198.664 7586.180 5.500 805.074 801.965 -3.109
6199.067 7585.129 6.625 805.192 801.403 -3.790
6199.246 7584.663 7.125 805.245 801.153 -4.092
6199.604 7583.729 8.125 805.350 801.153 -4.198
6199.849 7583.091 8.809 805.422 801.494 -3.928
Nivel 2 6194.329 7597.481 -6.604 803.799 801.413 -2.386
6194.508 7597.014 -6.104 803.851 801.663 -2.188
6196.694 7591.315 0.000 804.494 801.785 -2.709
6198.880 7585.616 6.104 805.137 801.663 -3.474
6199.059 7585.149 6.604 805.190 801.413 -3.777
Nivel 3 6194.321 7597.501 -6.625 803.796 801.403 -2.394
6196.694 7591.315 0.000 804.494 801.535 -2.959
6199.067 7585.129 6.625 805.192 801.403 -3.790
0+050.000 Nivel 1 6240.227 7617.436 -8.797 800.254 797.569 -2.684
5.14 Importing data in the Clip format
The Clip format is a cross-section based format that allows the import of cross-sections in layers. A layer is created in the System 1200 database
for each layer in the Clip cross-section file.
*PLT1
Eje Nueva Carretera.Tronco
0.0000 , 441000.0100 , 4453916.6870 , 99.0251 , 0.0000 , 0.0000
494.4770 , 441494.4290 , 4453924.2590 , 99.0251 , 0.0000 , 0.0000
574.4770 , 441574.4011 , 4453923.3511 , 104.1181 , 500.0000 , 200.0000
1254.0872 , 442036.6960 , 4453497.5778 , 190.6487 , 500.0000 , 0.0000
1334.0872 , 442044.1674 , 4453417.9503 , 195.7417 , 0.0000 , 200.0000
1430.6586 , 442052.8339 , 4453321.7891 , 191.3503 , -700.0000 , 260.0000
2381.9624 , 442693.2885 , 4452718.6216 , 104.8333 , -700.0000 , 0.0000
2478.5338 , 442789.7963 , 4452715.7319 , 100.4420 , 0.0000 , 260.0000
Variante de la C-736.Claznica 23-05-2000 P g. 1
LISTADO DE VERTICES
N§ P.K. TE Cota TE pE(%) Longi. Kv

Cota TS Cota TS pS(%) Flecha Theta(%)
=== =========== =========== ======== ======== ======== ========
1 700.000
634.567 700.000 634.567 6.0000
2 1082.017 800.767 640.613 6.0000 562.500 -7500

657.488 1363.267 653.269 -1.5000 -5.273 -7.5000
3 2769.005 2494.006 636.308 -1.5000 549.998 25000

632.183 3044.004 634.108 0.7000 1.512 2.2000
C-736.Calznica. 23-05-2000 P g. 1
LISTADO DE PUNTOS DE PERFILES TRANSVERSALES
P.K. 1100
COTA RASANTE C.D. 652.598
COTA RASANTE C.I. 652.598
ÄÄÄÄÄÄÄÄTALUDESÄÄÄÄÄÄÄÄÄ ÄÄÄÄÄÄPLATAFORMAÄÄÄÄÄÄÄ ÄÄÄSUBRASANTEÄÄÄ

Dist. Cota Talud Dist. Cota Pend. Dist. Cota
======= ======== ======= ======= ======== ====== ======= ========
-25.89 647.123
-17.90 652.450 -1.500 -17.90 652.450
-16.00 653.718 -4.00
-15.00 653.758 8.00
-12.50 653.558 8.00 -12.50 652.558
-5.50 652.998 8.00
-4.50 652.918
0.00 651.323
4.50 652.278
5.50 652.198 -8.00 5.50 651.198
12.50 651.638 -8.00
15.00 651.438 -8.00
16.00 651.358 -8.00
17.71 650.221 17.71 650.221
23.24 646.533 -1.500
P.K. 1120
COTA RASANTE C.D. 652.973
COTA RASANTE C.I. 652.973
ÄÄÄÄÄÄÄÄTALUDESÄÄÄÄÄÄÄÄÄ ÄÄÄÄÄÄPLATAFORMAÄÄÄÄÄÄÄ ÄÄÄSUBRASANTEÄÄÄ

Dist. Cota Talud Dist. Cota Pend. Dist. Cota
======= ======== ======= ======= ======== ====== ======= ========
-27.19 646.633
-17.90 652.825 -1.500 -17.90 652.825
5.15 Importing data in the InRoads format
The InRoads format is a cross-section based format that allows the import of cross-sections in layers. A layer is created in the System 1200
database for each layer in the InRoads cross-section file. The data exported from the InRail application is exported in the same format as InRoads.
* BENTLEY HORIZONTAL ALIGNMENT TO ASCII

*
* Nombre de la alineación: leica
* Descripción de la alineación:
* Estilo de alineación: default
*
{ TYPE STATION RADIUS X_CRD Y_CRD DIRECTION SPI_LENGTH
LIN 0+000.000 0.000 521173.471 4716474.259 292.09 0.000
SPI 0+081.530 0.000 521092.570 4716464.154 292.09 15.000
CIR 0+096.530 75.000 521077.639 4716462.792 298.46 0.000
SPI 0+131.801 0.000 521043.466 4716470.107 328.39 15.000
LIN 0+146.801 0.000 521030.400 4716477.462 334.76 0.000
* BENTLEY VERTICAL ALIGNMENT TO ASCII

*
* Nombre de la alineación: rasante
* Descripción de la alineación:
* Estilo de alineación: default
*
{ TYPE STATION ELEVATION SLOPE VC_LENGTH
LIN 0+002.821 619.746 -0.144 0.000
PAR 0+029.766 615.867 -0.144 50.000
LIN 0+079.766 613.524 0.050 0.000
LIN 0+139.197 616.510 -0.080 0.000
Date: miércoles, 18 de abril de 2001 11:14:12

Surface Name: FIRME1
Alignment Name: EJE-1
0+100,00 -30,650 922,000
0+100,00 -18,500 930,100
0+100,00 -17,500 931,100
0+100,00 -16,500 931,180
0+100,00 -14,000 931,280
0+100,00 -10,500 931,490
0+100,00 -7,000 931,700
0+100,00 -6,000 931,700
0+100,00 10,500 932,460
0+100,00 14,000 932,670
0+100,00 16,500 932,570
0+100,00 17,500 932,490
0+100,00 18,500 931,490
0+100,00 34,670 924,160
0+120,00 -31,040 921,700

0+120,00 -18,500 930,050
0+120,00 -17,500 931,050
5.16 Importing data in the Ispol format
The Ispol format is a cross-section based format that allows the import of cross-sections in layers. A layer is created in the System 1200 database
for each layer in the Ispol cross-section file.
ispol-V.7.08 3 Oct 2001 15:57 612 pagina 1

PROYECTO : TG405L 3. JUNIO-2001 TODOS LOS EJES JUNTOS
EJE : 27: Enlace T672. Ramal 1.
============================================
* * * LISTADO DE LAS ALINEACIONES * * *
============================================
DATO TIPO LONGITUD P.K. X TANGENCIA Y TANGENCIA RADIO PARAMETRO AZIMUT Cos/Xc/Xinf Sen/Yc/Yinf
---- ----- --------- ------------ ------------ ------------ ------------ ------------ ------------ ------------ ------------
1 RECTA 1.671 0.000 450686.112 4473164.070 135.0241 0.8524422 -0.5228215
2 CIRC. 143.204 1.671 450687.536 4473163.196 1500.000 135.0241 449903.304 4471884.533
3 CIRC. 132.107 144.875 450805.853 4473082.617 -1500.000 141.1019 451708.402 4474280.701
4 RECTA 67.700 276.982 450914.731 4473007.874 135.4951 0.8485509 -0.5291137

=================================================
*** ESTADO DE RASANTES ***
=================================================
PENDIENTE LONGITUD PARAMETRO VERTICE ENTRADA AL ACUERDO SALIDA DEL ACUERDO

(%) (m) ( kv ) p.k. cota p.k. cota p.k. cota

------------ ------------ ------------ ------------ ------------ ------------ ------------ ------------ ------------
0.002 648.977
-2.022805 76.710 7500.000 199.334 644.945 160.979 645.721 237.690 644.562
-1.000000 77.575 6000.000 276.763 644.171 237.975 644.559 315.550 643.282
-2.292914 159.291 10000.000 703.743 634.381 624.098 636.207 783.389 633.823
-0.700000 127.300 1900.000 1035.627 632.058 971.977 632.503 1099.277 635.877
6.000000 198.750 3750.000 1222.923 643.295 1123.548 637.333 1322.298 643.991
0.700000 180.000 15000.000 1678.081 646.481 1588.081 645.851 1768.081 646.031
-0.500000 126.207 20000.000 1915.489 645.294 1852.386 645.610 1978.593 645.377

****************************************************
* * * SECCION TRANSVERSAL COMPLETA ***
****************************************************
P.K. Inicial : 0.000

P.K. Final : 2320.000
Intervalo : 0.000
---------------- PUNTOS DE CONTROL EN ALZADO---------------------
pk: 0.000 BANDAS BLANCAS EJES DE GIRO
------------------------------- --------------------------------
X: 450686.112 Dist.: 0.000 Cota: 648.977 Dist.: 0.000 Cota: 648.978
Y: 4473164.070 Dist.: 0.000 Cota: 648.977 Dist.: 0.000 Cota: 648.978
Az: 135.0241
TALUDES CUNETAS SUBRASANTE RASANTE

---------------------- ---------------- ------------------------------- -------------------------------
Dist. Cota Talud Dist. Cota Dist. Cota Cod Pend% Dist. Cota Cod Pend%
------- -------- ----- ------- -------- ------- -------- ----- ------ ------- -------- ----- ------
-21.01 639.415
2.00
-3.00 648.417
2.00
-2.00 648.917
-3.00 648.417 100.0 -2.00 648.917 50.0
2.00 4.00
-1.00 648.458 11.0 -1.00 648.958 11.0
2.00 2.00
0.00 648.477 1.0 0.00 648.977 1.0
-2.00 -2.00
3.50 648.407 2.0 3.50 648.907 2.0
-2.00 -2.00
6.00 648.357 11.0 6.00 648.857 11.0
-1.99 -3.99
8.00 648.318 100.0 7.00 648.818 50.0
7.00 648.818
2.00

pk: 0.000
8.00 648.318
2.00
24.94 639.846

****************************************************
* * * SECCION TRANSVERSAL COMPLETA ***
****************************************************
P.K. Inicial : 0.000

P.K. Final : 2320.000
Intervalo : 0.000
5.17 Importing data in the Modelo Digital format
The Modelo Digital format is a cross-section based format that allows the import of cross-sections in layers. Up to 4 layers may be imported. A
layer is created in the System 1200 database for each layer in the Modelo Digital cross-section file.

1 0 476472.034 4480056.675 74.4488 0 0 378.541099999973

2 378.5411 476820.493 4480204.559 74.4488 -0.001 1826.2 460.000800000038
3 838.5419 477241.9955 4480388.7262 72.4292 -7250 0 4024.48099999997
4 863.0229 480253.3366 4482980.3717 37.0904 -7250 1826.2 460.000900000043
5 5323.0238 480498.2422 4483369.7341 35.0707 0 0 612.517999999982
6 5935.5418 480818.862 4483891.6357 35.0707 0.001 1826.2 460.000899999985
7 6395.5427 481063.7675 4484280.9982 37.0904 7250 0 1146.60499999998
8 7542.1477 481767.5662 4485184.6753 47.1586 7250 1826.2 460.000800000038
9 8002.1485 482085.0947 4485517.4779 49.1783 0 0 3.89500000001863
10 8006.0435 482087.8131 4485520.2674 49.1783 0 0 0.001

1 0.000 121.090 -0.01 0 1000.0
2 1000.000 111.090 0 0 10000.0
3 11000.000 111.090 0 0 1000.0
4 12000.000 111.090 0 0 500

0.000
-40.146 629.781
-30.786 629.596
-12.549 629.218
-7.203 629.397
-7.000 628.990 628.990
-6.315 628.175 628.175
-6.250 628.490
-6.037 629.435
-5.500 628.990 628.990
5.18 Importing data in the Multipiste format
The Multipiste format is a cross-section based format that allows the import of cross-sections without layers.

D;AO= 0.000;L= 494.477;X= 441000.010;Y= 4453916.687;G= 99.0251
A;AO= 494.477;L= 80.000;X= 441494.429;Y= 4453924.259;G= 99.0251;R= -0.000;A= -200.000
C;AO= 574.477;L= 679.610;X= 441574.401;Y= 4453923.351;G= 104.1181;R= -500.000
A;AO= 1254.087;L= 80.000;X= 442036.696;Y= 4453497.578;G= 190.6487;R= -500.000;A= 200.000
A;AO= 1334.087;L= 96.571;X= 442044.167;Y= 4453417.950;G= 195.7417;R= 0.000;A= 260.000
C;AO= 1430.659;L= 951.304;X= 442052.834;Y= 4453321.789;G= 191.3503;R= 700.000
A;AO= 2381.962;L= 96.571;X= 442693.289;Y= 4452718.622;G= 104.8333;R= 700.000;A= -260.000

D:S=700.000;SL= 100.767;Z= 634.567;P= 6.0000
P:S=800.767;SL= 562.500;Z= 640.613;P= 6.0000;RP= -7500.000;SJ=1250.767;ZJ=654.113
D:S=1363.267;SL= 1130.739;Z= 653.269;P= -1.5000
P:S=2494.006;SL= 549.998;Z= 636.308;P= -1.5000;RP= 25000.000;SJ=2869.006;ZJ=633.496
D:S=3044.004;SL= 621.327;Z= 634.108;P= 0.7000
P:S=3665.331;SL= 619.986;Z= 638.457;P= 0.7000;RP= -40000.000;SJ=3945.331;ZJ=639.437
D:S=4285.317;SL= 945.132;Z= 637.992;P= -0.8500

P;L=GAUCHE;PMDEV=1100.000;TPC=non;D1=4.500;P1=7.111;D2=1.000;P2=8.000;D3=7.000;P3=8.000;D4=2.500;P4=8.000;D5=1.000;P5=-4.000;N= 5
P;L=DROITE;PMDEV=1100.000;TPC=non;D1=4.500;P1=-7.111;D2=1.000;P2=-8.000;D3=7.000;P3=-8.000;D4=2.500;P4=-8.000;D5=1.000;P5=-8.000;N= 5
5.19 Importing data in the SDR format
Horizontal and vertical alignment s may be imported from files in the SDR Varin / Map format. This format uses a single file to define both the
horizontal and vertical alignment.
5.19.1 Horizontal and vertical alignment
5.19.1.1 Horizontal and vertical Alignment example

00NMSDR33 V04-030000 2-FEB-01 16:32 213121
28KIbaranbio 1
06NM1.00000000
29NM15720.000 313.8178999999994814.765 2328.828
32NM209.570 400.000
33NM73.333 400.000
31NM353.0076561446470.000
32NM248.663 1500.000
31NM363.5612416417300.000
33NM92.045 -550.000
32NM421.525 -550.000
33NM92.045 -550.000
31NM304.1160022790350.000
33NM101.250 500.000
32NM338.141 500.000
33NM101.250 500.000
31NM370.6657455681550.000
33NM88.889 -450.000
32NM494.312 -450.000
33NM82.735 -450.000
31NM288.5949880514950.000
32NM685.605 -6500.000
31NM281.8800696048160.000
31NM283.030899999999125.042
32NM157.108 5000.000
31NM285.0312611839410.000
34NM16578.429 94.457
36NM18372.227 79.313 217.211
36NM19239.833 109.679 300.003
36NM19636.659 99.758 175.005
37NM20193.656 105.328
5.20 Importing data in the SierraSoft format
The SierraSoft format is a cross-section based format that allows the import of cross-sections. The horizontal and vertical alignments are exported
in the same file.
5.20.1 Horizontal and vertical alignment
5.20.1.1 Horizontal and vertical Alignment example

AXIS
NAME "Eixo 0"
VISIBLE TRUE
ACTIVE TRUE
LOCK FALSE
START STATION 0.000
HORIZONTAL_ALIGNMENT
0,248417.213,151769.600,163.6459,17.881,0.000,0.000;
1,248426.878,151754.556,163.6459,73.481,40.000,0.000;
0,248405.230,151694.779,280.5971,37.699,0.000,0.000;
1,248369.268,151683.466,280.5971,31.985,-150.000,0.000;
0,248340.007,151670.700,267.0171,30.784,0.000,0.000;
1,248313.263,151655.455,267.0171,68.325,40.000,0.000;
0,248256.319,151675.340,375.7702,13.802,0.000,0.000;
1,248251.192,151688.154,375.7702,44.629,-40.000,0.000;
END HORIZONTAL_ALIGNMENT
VERTICAL_ALIGNMENT
0,0.000,224.999,0.000;
0,8.626,225.551,0.000;
2,8.708,225.556,700.000;
0,74.406,226.671,0.000;
0,74.436,226.670,0.000;
0,111.765,225.550,0.000;
2,111.801,225.549,-4000.000;
0,191.747,223.950,0.000;
0,191.767,223.950,0.000;
0,344.610,222.422,0.000;
END VERTICAL_ALIGNMENT

#SEZ 1 0.000 0.000 0.000 224.599 248417.213 151769.600
#COD PRO 0
0.000 224.349 0 0
-3.673 224.257 0 0
-3.870 224.102 0 0
#COD PRO 0
-3.870 224.102 0 0
-3.673 224.257 0 0
#COD PRO 0
-3.870 224.102 0 0
-3.870 224.102 0 0
-4.200 223.772 0 0
-4.200 223.772 0 0
-4.680 224.102 0 0
-4.680 224.102 0 0
#COD PRO 0
-4.680 224.102 0 1
#COD PRO 0
0.000 224.349 0 0
3.673 224.257 0 0
3.870 224.102 0 0
#COD PRO 0
3.870 224.102 0 0
3.673 224.257 0 0
#COD PRO 0
3.870 224.102 0 0
3.870 224.102 0 0
4.200 223.772 0 0
4.200 223.772 0 0
4.680 224.102 0 0
4.680 224.102 0 0
#COD PRO 0
4.680 224.102 0 1
5.21 Importing data in the TCP format
The TCP format is a cross-section based format that allows the import of cross-sections.

0.000 517074.576 4151633.92 106.1004 0.000 0.000
71.228 517145.478 4151627.11 106.1004 75.00 100.000
127.478 517200.526 4151616.55 124.0054 0.000 100.000
232.701 517262.707 4151537.68 190.9925 50.00 0.000
257.701 517264.159 4151512.74 198.9503 0.000 0.000
263.562 517264.255 4151506.88 198.9503 25.00 -100.000

0.000 466.306 0.000 0.000 0.000
421.191 532.524 1000.000 144.969 10.508
868.541 473.151 1200.000 144.128 8.655
1213.935 510.277 0.000 0.000 0.000

0.000 -7.230 656.396 99
0.000 -7.010 656.176 59
0.000 -6.010 655.676 58
0.000 -5.010 656.176 20
0.000 -3.010 656.216 19
0.000 -3.000 655.966 18
0.000 0.000 656.026 0
0.000 3.000 655.966 18
0.000 3.010 656.216 19
0.000 5.010 656.176 20
0.000 6.344 655.287 50
10.000 -6.670 656.507 99
10.000 -6.669 656.507 59
10.000 -6.010 656.178 58
5.22 Importing data in the Trazado format
Horizontal and vertical alignment s may be imported from files in the Trazado format

Fichero: C:\TEMP\COR\WIN\V1-2801
Título: v1-2801
Fecha: 28/01/2003 19:04:08
ALIN TIPO P.K. LONGITUD X Tang. Y Tang. AZIMUT RADIO

XC o I YC o I PARAMETRO
1 RECTA -248.631 283.216 495697.785 4393751.138 132.6287 0.000

0.000 0.000
2 CIRC. 34.585 30.200 495944.609 4393612.253 132.6287 -500.000

496189.802 4394048.006
3 RECTA 64.785 7.062 495971.360 4393598.247 128.7836 0.000

0.000 0.000

Nombre del fichero del alzado : C:\TEMP\COR\WIN\V1-2801
Título: V1-2801
Fecha/hora última modificación: 11/11/2002 20:38:08
NR P.K. COTA PENDIENTE%/PARAMETRO
P.K. INICIO -500.0000 84.7370 -1.0680
TANGENTE ENTRADA -252.6782 82.0956 -1.0680

1 VERTICE -198.8937 81.5212 11116.0000
TANGENTE SALIDA -145.1091 81.4672 -0.1003
5.23 Importing data in the VIPS format
Horizontal and vertical alignment s may be imported from files in the VIPS format

10 1.000 0.000 0.000 0.000 0.000 0.000
10 266531.655 -51813.887 266531.742 -51750.228 63.660 0.000
10 2.000 63.660 25.000 25.000 0.000 0.000
10 266531.742 -51750.228 266530.114 -51741.320 72.765 0.000
10 3.000 72.765 0.000 0.000 0.000 0.000
10 266530.114 -51741.320 266521.390 -51718.339 97.346 0.000

0.0000 10.0000 85.1000
0.0000 212.6300 0.0000
44.1600 214.1891 350.0000
85.1630 213.2000 0.0000

RR - aDesignToField - UserGuide - EN

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RR - aDesignToField - UserGuide - EN

Uploaded by

Copyright:

Available Formats

System 1200 Data Import Guide Design to Field User Manual

Leica Geo Office - Version 4.0

GRKE1205 Doc.Version 1.0

1. Introduction .............................................................................................................................................................. 2-6

4.2 How to create a DTM job ...................................................................................................................................4-33

5.11.3 Cross-section file ........................................................................................................................................5-69

5.20 Importing data in the SierraSoft format ..............................................................................................................5-84

Points, Lines and Area (PLA) job:

1.2 Available data converters

At the time of writing the following converters are available:

Job Type Format converter available for the following formats:

DTM LandXML, DXF (3D Face entities), GSI

2 Installing the data converters

2.2 Installing the converter package

- The converters are available in four languages: English, French,

- A tree containing the available converters will appear. The

- By default all of the data formats will be selected.

- If all of the additional data converters are not required, deselect

2.3 Updating an existing converter

2.3.1 Downloading the converter

Note: Individual converters may only be downloaded by registered web site

- Browse to a folder and save the file.

2.3.2 Registering the converter in LGO

- Run LGO and select the Tools/Design to Field option.

- Note: Converter files use the following naming conventions:

File extension: *. rri

Prefix: PLA file have the prefix PLA, e.g PLA_DXF-Importer.rri

3 Converting Points, Lines and Area data

3.2 How to create a points, lines and areas job

3.2.1 Defining the file to import

- Select the import type Points, Lines & Areas

3.3 Graphical Data Viewer

3.3.1 Viewer Layout

3.3.2 Zoom/Pan Tools

The zoom and pan tools may be found in the toolbar.

3.3.3 Layer Tool

Turn-on / turn-off the layer in the plot view.

3.3.4 Graphical Settings

This button allows the graphical settings parameters to be configured.

3.3.4.1 General Settings

Scale: View the scale bar

Name: View the point ID

Description: View the point description

Name: View the name of the alignment elements

Name: Name of the area

3.3.5 Saving the data

3.4 Creating the on-board files

Name: Enter a name for the job to store.

Browse to the folder where the job will be stored.

Location Name of the folder where the job will be stored.

3.5 Importing LandXML data

3.5.1 Supported LandXML entities

<Curve staStart="6045.683000" rot="cw" crvType="arc" radius="600.000000">

3.6 Importing DXF data

Select Layers to import

DXF File Linear Units

Import Points on lines and polylines as separate entities

The difference may be seen in the following screenshots:

3.6.1 Supported DXF entities

3.6.2 Treatment of DXF Layers

This functionality may be seen in the following example:

4 Converting Digital Terrain Model data

4.2 How to create a DTM job