You are on page 1of 88

System 1200 Data Import Guide

Design To Field
Guide to importing data into System1200

Leica Geo Office - Version 4.0
English

GRKE1205 Doc.Version 1.0

Design to Field

2-1
User Manual

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

System 1200 Data Import Guide

Design to Field

2-3

4.2
How to create a DTM job ...................................................................................................................................4-33
4.3
Importing LandXML data....................................................................................................................................4-35
4.4
Importing DXF data............................................................................................................................................4-36
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
Importing LandXML data....................................................................................................................................5-50
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.9
Importing DXF data............................................................................................................................................5-64
5.10 Importing data in the MX Genio format ..............................................................................................................5-65
5.11 Importing data in the Avance format ..................................................................................................................5-67
5.11.1 Horizontal alignment ...................................................................................................................................5-67
5.11.2 Vertical alignment file..................................................................................................................................5-68

System 1200 Data Import Guide

Design to Field

2-4

5.11.3 Cross-section file ........................................................................................................................................5-69
5.12 Importing data in the REB format.......................................................................................................................5-70
5.12.1 Horizontal alignment ...................................................................................................................................5-70
5.12.2 Vertical alignment file..................................................................................................................................5-70
5.12.3 Cross-section file ........................................................................................................................................5-70
5.13 Importing data in the Cartomap format ..............................................................................................................5-72
5.13.1 Horizontal alignment ...................................................................................................................................5-72
5.13.2 Vertical alignment file..................................................................................................................................5-72
5.13.3 Cross-section file ........................................................................................................................................5-73
5.14 Importing data in the Clip format ........................................................................................................................5-74
5.14.1 Horizontal alignment ...................................................................................................................................5-74
5.14.2 Vertical alignment file..................................................................................................................................5-74
5.14.3 Cross-section file ........................................................................................................................................5-75
5.15 Importing data in the InRoads format.................................................................................................................5-76
5.15.1 Horizontal alignment ...................................................................................................................................5-76
5.15.2 Vertical alignment file..................................................................................................................................5-76
5.15.3 Cross-section file ........................................................................................................................................5-77
5.16 Importing data in the Ispol format.......................................................................................................................5-78
5.16.1 Horizontal alignment ...................................................................................................................................5-78
5.16.2 Vertical alignment file..................................................................................................................................5-78
5.16.3 Cross-section file ........................................................................................................................................5-79
5.17 Importing data in the Modelo Digital format........................................................................................................5-81
5.17.1 Horizontal alignment ...................................................................................................................................5-81
5.17.2 Vertical alignment file..................................................................................................................................5-81
5.17.3 Cross-section file ........................................................................................................................................5-81
5.18 Importing data in the Multipiste format ...............................................................................................................5-82
5.18.1 Horizontal alignment ...................................................................................................................................5-82
5.18.2 Vertical alignment file..................................................................................................................................5-82
5.18.3 Cross-section file ........................................................................................................................................5-82
5.19 Importing data in the SDR format.......................................................................................................................5-83
5.19.1 Horizontal and vertical alignment................................................................................................................5-83

..3 Cross-section file ..................................................21....................22..........20 Importing data in the SierraSoft format ..........2 Vertical alignment file..............................................23 Importing data in the VIPS format ..............1 Horizontal alignment ............System 1200 Data Import Guide Design to Field 2-5 5..1 Horizontal and vertical alignment..........21.......................................5-84 5...........22 Importing data in the Trazado format ............2 Cross-section file ......22..............................21.....................................................................................................5-86 5..........................................................................................................................................1 Horizontal alignment ..........................................................................5-84 5............20......................................................................5-86 5....................5-87 5.........................21 Importing data in the TCP format .5-88 5..........................................................................................5-87 5....................1 Horizontal alignment ......................................2 Vertical alignment file........................................................................................................5-86 5..........................................................................................................5-88 ...............................................20...................................................................................................................................................................23.............................2 Vertical alignment file.....5-87 5.........................23..............................5-88 5........................................................................5-86 5.............................................................5-85 5.................................................................................................................................................

System 1200 Data Import Guide 1.1 Overview 1.2 Available data converters Design to Field 2-6 . Introduction In this chapter 1.

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. by cross-sections instead of stringlines. In this case.System 1200 Data Import Guide Design to Field 2-7 1. check for availability with your local Leica Geosystems representative). in addition to their horizontal and vertical alignments. Data converters are available for the following System 1200 job types: 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. Data may be imported using industry standard data formats such as LandXML. 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. known as stringlines. Road job: Road jobs store a collection of two or three dimensional lines. Rail job: Rail jobs are used in conjunction with the System 1200 RailRunner application. Each digital terrain model may be made up of one or more surfaces or layers. rail and tunnel design data for use with the RoadRunner suite of applications.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. Design to Field allows the horizontal and vertical alignments of the tunnel to be defined as well as the design profiles of the tunnel. background maps. Lines and Area (PLA) job: The entities (points. Tunnel job: Tunnel jobs are used in conjunction with the System 1200 RoadRunner Tunnel application (only available in certain countries. These data types include control points. digital terrain models and road. . that define a road project for use with the System 1200 RoadRunner application. In many cases road projects are defined. DXF and GSI or from a number of additional formats using converters that are available in the downloads area of the Leica Geosystems website.

MX GenI/O. Lines and Areas) LandXML. Clip. GSI Road LandXML (stringlines and cross-sections).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. Modelo Digital. Cartomap. REB. Bentley LandXML (surfaces). SDR Varin/Map. SierraSoft. Clip. SierraSoft. MX GenI/O. TCP. 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. . Ispol. Multipiste. Clip. TCP.0 installation CD. Multipiste.leica-geosystems. Select the DesignToField Converter Install Application and save the file.System 1200 Data Import Guide Design to Field 2-8 1. Avance. Modelo Digital. DXF (3D Face entities).htm?cid=3291 At the time of writing the following converters are available: Job Type Format converter available for the following formats: PLA (Points.com/s-e/en/downloads/lgs_page_catalog. InRoads/InRail. InRoads/InRail. REB. SDR Varin/Map. SierraSoft. SDR Varin/Map. Avance. MX GenI/O. the converters may also be downloaded one at a time from the web page. for updating converters that are already installed and in order to reduce the size of the download. Ispol. DXF DTM LandXML. Avance. Cartomap. InRoads/InRail. Cartomap. Modelo Digital. DXF Rail LandXML. TCP. In addition to the install application. VIPS. VIPS Tunnel LandXML. Ispol. REB. Multipiste.

.rri file) is downloaded from the web page and registered in Design to Field without having run the installation package previously.System 1200 Data Import Guide Design to Field 2-9 Important Note: If any of the converters in the above table are to be used. the data conversion will fail. If an individual converter (*. The individual converters should only be downloaded to update an existing converter that has been installed using the installation program. the installation package must have been run on each PC on which the converter will be used.

3 Updating an existing converter Design to Field 2-10 .1 Prerequisites 2.System 1200 Data Import Guide 2 Installing the data converters In this chapter 2.2 Installing the converter package 2.

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

Note: Road and Tunnel jobs are created with the same Road Importers. Rail Importers and DTM Importers.System 1200 Data Import Guide - Design to Field 2-12 Select the default folder for installing the converters or browse to a new folder using the Change button. . Road Importers. The next time the LGO application is run. The selected importers will be installed and registered automatically within the LGO application. - A tree containing the available converters will appear. deselect those that will not be used before pressing the Next button. - - By default all of the data formats will be selected. Lines and Area Importers. the installed converters will be available for use. The converters are divide into four groups: Points. - If all of the additional data converters are not required.

due to routine maintenance or due to the addition of new functionality. - Browse to a folder and save the file. - Browse to the required converter on the web page and press the Download button. The latest version of the converters is always available on the Downloads page of the Leica Geosystems website.htm?cid=3291 2. it needs to be registered within the LGO application.3 Updating an existing converter The converters may be updated at any time according to changes in the definition of each format. In order to register. The individual converter may be downloaded from the downloads page and registered manually within LGO.leica-geosystems. . Note: Individual converters may only be downloaded by registered web site users. follow the instructions in the Downloads area of the web site. http://www.1 Downloading the converter It is not necessary to reinstall the entire installation package in order to update an individual converter.2 Registering the converter in LGO Once the converter has been saved. 2. To register the converter within LGO: - Run LGO and select the Tools/Design to Field option.System 1200 Data Import Guide Design to Field 2-13 2.3.com/s-e/en/downloads/lgs_page_catalog.3.

rri Road and rail importers have the prefix RR.g. RR_Road_Clip. e.rri DTM files have the prefix DTM. DTM_DXF-Importer. the registration of the converter is now complete. .g.rri Once the converter file has been selected. Road or Rail. RR_Rail_InRoads. The importer will be moved to the Not Used list.g. - Press the Register button and select the new converter file. Press the OK button to return Design to Field. e.rri Additional Prefix: Road and Rail importers have the additional prefix.System 1200 Data Import Guide - - Design to Field 2-14 - Press the Manage button. e. Note: Converter files use the following naming conventions: File extension: *. rri Prefix: PLA file have the prefix PLA. e.g PLA_DXF-Importer. it will be registered in LGO. - Select the existing version of the importer that will be updated and press the > button. A list of the importers that have already been registered will be shown.

System 1200 Data Import Guide 3 Converting Points. lines and area job 3.6 Importing data in DXF format Design to Field 3-15 .1 Overview 3.2 How to create a points. Lines and Area data In this chapter 3.4 Creating the on-board files 3.5 Importing LandXML data 3.3 Graphical Data Viewer 3.

for updating purposes) or for staking out. Lines & Areas - Select the design format of the data file from the Importer drop-down list.2 How to create a points.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. 3. 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. 3.g. the actual screens may vary depending on the information available in the imported data format. .2. The information imported from each data format is format dependent as not all formats store the same data. Additional format converters may be added using the Manage button. Select the import type Points.System 1200 Data Import Guide Design to Field 3-16 3. Any additional screens are explained in the section relating to each particular format.1 Overview The Design to Field points. lines and areas job The generic process of creating a PLA job is described in this section.

- 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. press the Import button and browse to the file.System 1200 Data Import Guide Design to Field 3-17 - To read the file containing the data to import. .

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-18 .System 1200 Data Import Guide Design to Field 3.

3. . If the zoom tool is not selected. When the layer button is pressed. the scroll-wheel may also be used to zoom in and zoom out of the window. it is possible to pan around the data using the scroll bars of the graphical window. 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.System 1200 Data Import Guide Design to Field 3-19 3. Zoom in Zoom out Zoom all If a zoom tool is selected.2 Zoom/Pan Tools The zoom and pan tools may be found in the toolbar.3 Layer Tool The Layer tool may be used to turn-on or turn-off layers in the plot window.3.3. a menu is opened where all of the layers of imported data may be viewed. to include or exclude layers from the export to the System 1200 database and also to view a single layer of the data.

3. it does not affect whether the data from this layer will be exported to the System 1200 job.4. This button is only used for visualisation purposes.4. 3.4 Graphical Settings This button allows the graphical settings parameters to be configured. it does not affect whether the data from this layer will be exported to the System 1200 job. View only the selected layer. Export / do not export the data in the selected layer to the System 1200 job. This button is only used for visualisation purposes.1 General Settings Scale: View the scale bar Name: Code: Height: View the point ID View the point Code View the height of the point 3.System 1200 Data Import Guide Design to Field 3-20 Turn-on / turn-off the layer in the plot view.3.3.2 Points . 3. All layers in the job will be turned-off except for the selected layer.

the changes may be saved using the Save button. . Browse to the required folder and enter a filename where the data will be saved.4. The modified data will be saved to a file in LandXML format.3.System 1200 Data Import Guide Description: Design to Field 3-21 View the point description 3.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.4.5 Saving the data If modifications are made to the data. The file may be loaded at a later date should it be necessary to create a new on-board database. for example by deselecting layers of data.4 Areas Name: Name of the area 3.3. Note that the original data files will not be modified by saving the data.3.

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.System 1200 Data Import Guide Design to Field 3-22 3. . Name: Enter a name for the job to store. Location Name of the folder where the job will be stored. Browse to the folder where the job will be stored.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.

501</CgPoint> <CgPoint name="PtID3" oID="0002" code="" desc="">4600776.019 308740.0500 187242. <IrregularLine> <Start>187241.897 740.2000 278792.000 308783. An example of the CgPoints section of a LandXML file that may be imported follows: <CgPoints> <CgPoint name="PtID1" oID="Pk436" code="" desc="">4600896. <Line staStart="5704.5.3000 187246.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>.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.019 308740.g.3500 278783. More information about LandXML format may be found at the LandXML website: http://www.122000</End> </Line> <IrregularLine> e.2000 278792.000 740.4500</End> <PntList2D>187241.000</CgPoint> <CgPoint name="PtID2" oID="0001" code="" desc="">4600776.System 1200 Data Import Guide Design to Field 3-23 3.258000</Start> <End>674311. e.5 Importing LandXML data LandXML is a format that was designed to model and transfer Land Planning.481000"> <Start>674066.231000 329437.0500</Start> <End>187246.897 740.4500 </PntList2D> </IrregularLine> .landxml. 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.422000 329511.3500 278783.2500 278790.org 3.g.

683000" rot="cw" crvType="arc" radius="600.000000"> <Start>674392.309000 329537.378184</Center> <End>674495. e.960144 330098.830000 329588.591000</Start> <Center>674178.System 1200 Data Import Guide Design to Field LandXML <Curve> elements are imported as arcs in the System 1200 database. <Curve staStart="6045.875000</End> </Curve> 3-24 .g.

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.System 1200 Data Import Guide Design to Field 3-25 3. It is a format that is based on coordinate geometry elements rather than survey related entities and as such has many limitations. 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.6. The points. . Although many solutions have been implemented in various survey software. Line ID prefix Lines imported from the DXF do not have identifiers. In addition. The points. 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. lines and area importer numbers the lines sequentially in the System 1200 database starting with the number 1 and incrementing each line by 1. For this reason. In addition. Point ID prefix As stated previously. no generic method of naming points is available in the DXF format definition. no generic solution is available to solve this problem. a prefix may be added to each point number if required. DXF File Linear Units The majority of DXF files do not contain information regarding the linear units of the file. a prefix may be added to each line number if required. lines and area DXF importer may be found in §3.1. The most important limitation when importing DXF data for use on a survey sensor is the lack of a point ID for point elements.6 Importing DXF data DXF is perhaps the most widespread formats used for interchanging geomatics data until the present time. A full list of the DXF entities supported by 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.

points will be created at the vertex of all lines in the DXF file.6.g. to stake out the points) or not (e. if the DXF data is to be used simply as a background map). It may interest the user to create these points in the System 1200 database (e. If the checkbox is not selected.System 1200 Data Import Guide Design to Field 3-26 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. lines and area importer imports the following DXF elements: Points The following DXF entities are imported as points in the System 1200 job: POINT .g. no points will be selected. If the checkbox Import Points on lines and polylines as separate entities is 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.1 Supported DXF entities The Design to Field DXF points.

0 20 0. Each point is given a point code with the same name as the DXF layer from which it was imported.0 3 BLOCK DXF BLOCK entities are often used in DXF files to contain symbol information. the DXF BLOCK would be imported with the point code BENCHM. The POINT entity in the DXF file resembles the following excerpt. The point code is included in a point group with the same name as the DXF layer of the BLOCK.System 1200 Data Import Guide Design to Field 3-27 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 BLOCK entities in the DXF file. The layer and attributes for each point may change with respect to the example: 0 2 POINT 70 64 10 0. The point ID of each point is assigned automatically based on the order of the POINT entities in the DXF file. In the following example. Each System 1200 point imported from a DXF BLOCK is given a point code with the same name as the BLOCK. This point code would be placed in the point code group HEIGHTINFO. Point ID’s may be assigned a prefix during the conversion if required.0 30 0. only the insertion point of the BLOCK entity is imported into the System 1200 database. The point code description of every DXF BLOCK imported into System 1200 is set to the text DXF Block. 0 BLOCK 8 HEIGHTINFO 2 BENCHM 70 64 . given that this information is normally superfluous in the field and would interfere with the selection of points and lines on the sensor screen.

The line ID of each line is assigned automatically based on the order of the ARC entities in the DXF file.0 11 0. The layer and attributes for each line may change with respect to the example: 0 LINE 8 0 10 -0. The layer and attributes for each line may change with respect to the example: 0 .00637 31 0. The line ID of each line is assigned automatically based on the order of the LINE entities in the DXF file. Each line is given a line code with the same name as the DXF layer from which it was imported.System 1200 Data Import Guide Design to Field 3-28 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. Each arc will be drawn as such on-board the System 1200 sensor. The ARC entity in the DXF file resembles the following excerpt.0 ARC A DXF ARC entity is imported to the System 1200 database as a line with an arc flag.231854 21 0.193702 20 0. Line ID’s may be assigned a prefix during the conversion if required.00637 30 0. The LINE entity in the DXF file resembles the following excerpt. 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.

System 1200 Data Import Guide Design to Field 3-29 ARC 8 0 10 5.0 40 4. Closed polylines and lwpolylines are also imported. 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.066148 51 56. Each line is given a line code with the same name as the DXF layer from which it was imported. The POLYLINE entity in the DXF file resembles the following excerpt. Line ID’s may be assigned a prefix during the conversion if required.595122 POLYLINE / LWPOLYLINE A DXF POLYLINE or LWPOLYLINE entity is imported to the System 1200 database as a line. .597739 50 217. The treatment of an LWPOLYLINE is exactly the same as a normal polyline during import.804875 30 0.485202 20 8. The line ID of each line is assigned automatically based on the order of the LINE entities in the DXF file. The LWPOLYLINE is virtually identical to the POLYLINE definition: POLYLINE 8 G8010035 66 1 70 0 0 VERTEX 8 G8010035 . The layer and attributes for each line may change with respect to the example. .

System 1200 allows the same layers to be maintained by assigning all DXF entities in the same layer the same code group.System 1200 Data Import Guide Design to Field 3-30 3. This functionality may be seen in the following example: Visualisation of all layers / code groups in CAD program and System 1200 . 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.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 Data Import Guide Design to Field 3-31 Visualisation of the same data after turning off a layer in the CAD application and the corresponding code group on the System 1200 sensor .

1 Overview 4.System 1200 Data Import Guide 4 Converting Digital Terrain Model data In this chapter 4.5 Importing data in GSI format Design to Field 4-32 .4 Importing data in DXF format 4.2 How to create a DTM job 4.3 Importing LandXML data 4.

additional format converters can be added using the Manage button.2 How to create a DTM job The generic process of creating a DTM job is described in this section. 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. - Select the import type DTM Data - Select the design format from the Importer drop-down list.1 Overview Digital terrain models may be imported to System 1200 for use with the RoadRunner suite of applications or with the Stakeout application. the actual screens may vary depending on the information available in the imported data 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. 4. Any additional screens are explained in the section relating to each particular format.System 1200 Data Import Guide Design to Field 4-33 4.

. - Once the data file to import has been defined. press the Import button and browse to the file.4 for more information on how to use the graphical viewer and create the on-board files.3 and §3. See §3. the data will be displayed graphically for review or edition before creating the on-board file.System 1200 Data Import Guide Design to Field 4-34 - To read the file containing the data to import.

4370 447171.5500 447141.5900 447142.2570</P> <P id="9">4478409.-> .4190 447143.-> <!.5250 655.4900 654.3940 447171.List of coordinates .9310 655.3650</P> <P id="5">4478384.4610 447142.4690</P> <P id="10">4478394.7820 447168.2810 654.3450 654.1060 447138.0530 655.1500</P> <P id="8">4478386.2810 654. 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..System 1200 Data Import Guide Design to Field 4-35 4.5640 655.7010 655..3 Importing LandXML data The Design to Field DTM LandXML importer imports the digital terrain models in triangular format contained in the <Surfaces> section of a LandXML file.2830</P> <P id="7">4478386.6290</P> <P id="3">4478409.6360 447142.Surface name . An example surface imported by the LandXML DTM importer is given below: <Surface name="OTRA"> <Definition surfType="TIN"> <Pnts> <P id="1">4478409.9590 655.-> <!.8620 655.2670</P> <P id="11">4478394.List of triangles .3630</P> <P id="2">4478415..1360</P> </Pnts> <Faces> <F>1 2 3</F> <F>4 5 6</F> <F>6 7 8</F> <F>9 10 11</F> </Faces> </Definition> </Surface> <!.4370 447171.0290 447138.1490</P> <P id="6">4478384.4690</P> <P id="4">4478382.

Z value. 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. The triangles in the DXF file should be defined by the 3DFACE DXF entity. Z coordinate.4 Importing DXF data Triangular digital terrain models may be imported to System 1200 from DXF files. .System 1200 Data Import Guide Design to Field 4-36 4. Z value. Y cordinate.178000 30 23. 3D face type. X value. Z coordinate.383000 11 723576. Y value. second point. X coordinate. X value. X coordinate. third point. End of record. third point. An excerpt of a DXF file containing 3DFACE entities is shown below: 0 3DFACE TRIANGLE 10 723573. second point.998000 21 7663191. Z coordinate. Y coordinate. Y value. a separate surface is created in the System 1200 DTM job. first point.966000 32 24629. Record is a 3D face entity.029000 12 723572. second point.684000 22 7663189. third point.000 0 Start of record. X coordinate. first point. Z value.984000 20 7663192. Y coordinate. For each selected DXF layer. Y value.120000 31 23. X value. first point. 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.

System 1200 Data Import Guide

Design to Field

4-37

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
*11....+0000000000003076
*11....+0000000000003077
*11....+0000000000004299
*11....+0000000000003077
*11....+0000000000003076
*11....+0000000000003082
*11....+0000000000004299
*11....+0000000000003077
*11....+0000000000004306

42....+00000000DTMNTWRK
71....+TRI0000000000001
71....+TRI0000000000001
71....+TRI0000000000001
71....+TRI0000000000002
71....+TRI0000000000002
71....+TRI0000000000002
71....+TRI0000000000003
71....+TRI0000000000003
71....+TRI0000000000003

43....+00000000DTMCOORD
81..10+0000000305426640
81..10+0000000305425426
81..10+0000000305428849
81..10+0000000305425426
81..10+0000000305426640
81..10+0000000305419640
81..10+0000000305428849
81..10+0000000305425426
81..10+0000000305424385

44....+0000000000000000
82..10+0000005049311074
82..10+0000005049311546
82..10+0000005049312771
82..10+0000005049311546
82..10+0000005049311074
82..10+0000005049313345
82..10+0000005049312771
82..10+0000005049311546
82..10+0000005049313713

45....+0000000000000000
83..10+0000000000005663
83..10+0000000000005696
83..10+0000000000006347
83..10+0000000000005696
83..10+0000000000005663
83..10+0000000000005603
83..10+0000000000006347
83..10+0000000000005696
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.

System 1200 Data Import Guide

5 Converting Road Data
In this chapter
5.1 Overview
5.2 How to create a road job
5.3 Importing LandXML data
5.4 Importing data in GSI format
5.5 Importing data in DXF format

Design to Field

5-38

System 1200 Data Import Guide

Design to Field

5-39

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
vertex

Stringlines are thee-dimensional lines that define an edge of the road
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
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 crosssection data. These conflicts need to be solved before a stringline model
can be produced. Design to Field uses a software component called the
Connection Editor to solve these conflicts.

Stringline

Possible conflict

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.

System 1200 Data Import Guide

Design to Field

5-40

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.

These details are stored in the System 1200 job and may be used to identify the data and the creator on-board the sensor. - - 5-41 Enter the job details and press the Next button. Enter the checking tolerances and press the Next button. 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. - Browse to the files containing the horizontal alignment. The data will now be displayed in the graphical viewer for review and modification before creating the onboard files. Note that it is not required to work with a vertical alignment or cross-sections if these data are not available. When importing data. . press the Import button. - Once the data has been read successfully.System 1200 Data Import Guide Design to Field - To start the conversion. vertical alignment and cross-sections and press the Next button. The Finish button should be pressed to close the import wizard. a summary of the data is shown. If a difference greater than the defined horizontal and vertical tolerances is found in the data. Design to Field checks that the data is coherent before writing it to the road job.

5. edited using the Connection Editor. 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. This may be done using the Connection Editor. if required. 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. When cross-section data is imported from the original data files. The stringlines may be viewed and. The Connection Editor may be accessed using the Note: The Connection Editor may only be accessed when importing cross-section based data. . icon.System 1200 Data Import Guide - Design to Field 5-42 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.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.

Cross-section Data (c) Design to Field 5-43 .System 1200 Data Import Guide 5. Cross-section View (b).1 Layout The Connection Editor is divided into three panels: Plan View (a).3.

Any cross-section vertex may be selected with a mouse click.1. When the layer button is pressed. The corresponding vertex will also be highlighted in the Plan View. 5.1. 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.3.3.3. .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. Only cross-sections at chainages that are contained in the original data file are displayed. The chainage of the cross-section together with the distance from centreline and absolute height of the selected vertex may be viewed.3. 5. Any cross-section vertex may be selected with a mouse click. The zoom and pan tools function in this view in the same way as in the Viewer application in all three cross-section views. 5.System 1200 Data Import Guide Design to Field 5-44 At any one time. The corresponding vertex will also be highlighted in the Cross-Section View. three cross-sections are displayed.2 Layer Tool The Layer Tool is similar in operation to the Layer Tool in the Viewer.1.3 Cross-section Data The numeric values of the cross-section data may be viewed in this section. 5.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. a menu is opened where all of the layers of imported data may be viewed. This view allows a plan perspective of how the vertices of the cross-sections have been joined to create stringlines.

System 1200 Data Import Guide Design to Field 5-45 Turn-on / turn-off the layer in the plot view. . Join / do not join vertices in the cross-section across the centreline. 5.3 Navigation Tools The navigation tools allow each of the cross-sections in the job to be viewed. View only the selected layer. 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. it does not affect whether the data from this layer will be exported to the System 1200 job. This button is only used for visualisation purposes.3. The Play button starts the sequence and the stop button stops the sequence. All layers in the job will be turned-off except for the selected layer.

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.1 Selecting a vertex A vertex may be selected in any of the three panels (Plan View. To move to a given chainage. Cross-section data). Enter the chainage of the cross-section to be displayed and press the arrow key.System 1200 Data Import Guide Design to Field 5-46 The Chainage field in the cross-section data panel may also be used to display a cross-section at a given chainage. To select a vertex graphically in the plan view or the cross-section view. 5. Cross-Section View. type the chainage into the chainage field and press the arrow button.3. .3. To navigate across the section. simply click on the vertex. use the arrow keys in the cross-section data panel.

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. the vertices 1. If the two selected vertices are connected.4. select the required vertex in the middle cross-section and the corresponding vertex in the preceding or following cross-section.4 Connection Tools The connection tools may be used to connect or disconnect points in the cross-section should they have been connected erroneously. select the required vertex in the middle cross-section and the corresponding vertex in the preceding or following cross-section. Click on the disconnect button to disconnect the two vertices. . To connect two vertices in adjacent cross-sections. 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. 5. 5. Click on the connect button to connect the two vertices.4. the connect button will be enabled. In the following example.1.System 1200 Data Import Guide Design to Field 5-47 5.1 Connect / Disconnect a vertex To disconnect two vertices in adjacent cross-sections. If the two selected vertices are disconnected. the disconnect button will be enabled.

System 1200 Data Import Guide Design to Field 5-48 To continue a vertex until the next cross-section. Location Name of the folder where the job will be stored. Browse to the folder where the job will be stored. the vertex must be disconnected from all other vertices. 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.5 Creating the on-board database files Once all of the connections have been verified. To discontinue a vertex that has been continued until the next cross-section.0m If chainages greater than 214000m are to be used on the job. Allow chainages greater than 214000. this checkbox should be selected. 5. select the vertex in the middle cross section and press the discontinue button. Select the vertex in the middle cross section and press the continue button.

Separate tolerance values may be specified for horizontal and vertical values. On the other hand. 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. - If the path of the folder used for the new job was not the CF card used by the sensor. In order to strike a balance between the true representation of the design model and the size of the onboard database.e. the larger the number of points stored on-board the sensor. the more performance is affected. a sufficient number of points along the stringline must be stored so that the stored line is a close representation of the original data. press the OK button to create the on-board data. . Stringline Point The maximum horizontal tolerance is the value applied to the stringline furthest from the centreline. a will always be greater than b). a b Stringline Point Centreline Outermost Stringline It should be noted that the outermost stringline always has the maximum horizontal chord-curve difference (a) and that the innermost stringlines will always have a chord-curve difference less than this maximum value (i. copy the newly created files to the DBX folder of the CF card of the sensor. - Once all conflicts have been solved.System 1200 Data Import Guide Design to Field 5-49 Chord-Curve Tolerances Given that stringlines are lines described by a collection of three-dimensional points. the horizontal chordcurve difference that will be checked during conversion will be the value a. Using the diagram as a reference.

System 1200 Data Import Guide Design to Field 5-50 5.6. 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.1 Horizontal alignment It is possible to define the horizontal alignment with the following LandXML entities: – – – Line Curve Spiral 5.6.6 Importing LandXML data The Design to Field LandXML road data importer imports data in both stringline and cross-section format.253000" staStart="100.1.1 Line The Line element defines the make up of a straight component in the stringline.000000"> <CoordGeom> <Profile> </Alignment> The horizontal alignment is contained in the <CoordGeom> section and the vertical alignment is contained in the <Profile> section. 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) . The definition for the horizontal and vertical alignments is identical for both types of road model. This is the start station (chainage) of the element. The attribute staStart can be written to the element. 5.

4 Curve example A curve element should look like: <Curve staStart="348.786357</Center> <End>2304. 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.6.6.6.2 Line example A line element should look like: <Line staStart="0.000000 6000.816000</End> </Curve> 5-51 .System 1200 Data Import Guide Design to Field 5.751000 6150.005000</End> </Line> 5.1.000000"> <Start>2307.071000 6247.3 Curve The Curve element is used to define curves in the horizontal alignment of a stringline.672427 6195.841000 6068.1.832000" rot="cw" crvType="arc" radius="100.000000</Start> <End>2186.344000</Start> <Center>2218.1. can have the values “cw” or “ccw”) radius The following optional attributes are also supported: – – staStart crvType (Should be entered as “arc”) 5.000000"> <Start>2000.

“bloss” and “cubic” are supported) The following optional attributes are also supported: – – – staStart desc constant Design to Field 5-52 .1.5 Spiral The element Spiral is used to define any spiral in the horizontal alignment.System 1200 Data Import Guide 5.6. PI Start End The following attributes are required when defining a Spiral element: – – – – – Length (length of the curve) RadiusStart radiusEnd rot spiType (“clothoid”. 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.

3.794000 6310.6.978259</PI> <End>2227.304084 6276. The “constant” attribute can store the spiral constant.759000</End> </Spiral> This example is for a cubic parabola Spiral: 5.System 1200 Data Import Guide Design to Field 5-53 “INF” is used to define a tangent (radius = infinity).2 Profile (Vertical Alignment) The element Prof must contain only one sub-element ProfAlign. Within this sub-element the vertical alignment is defined. 5.071000 6247. If the constant cannot be provided (through calculations or input or due to the spiType) then the attribute value should be left blank. 5.816000</Start> <PI>2286.001000" radiusStart="99.6 Spiral example This example is for a curve to tangent clothoid spiral: <Spiral staStart="450. The ProfAlign element must contain one of the sub-elements: – – – PVI (Point of Vertical Interest) CircCurve (Circular Curve) ParaCurve (Parabolic Curve) .999000" radiusEnd="INF" rot="cw" spiType="clothoid" constant="100"> <Start>2304. There must be at least on sub-element in the ProfAlign.1 ProfAlign The ProfAlign element contains the definition of the vertical alignment of the stringline.724000" desc="CurveToTangent" length="100.6. The “rot” attribute defines whether the arc travels clockwise or counter-clockwise from the Start to End point.3 Prof example <Profile> <ProfAlign name="VERTICAL ALIGNMENT"> </ProfAlign> </Profile> 5.6.1.6.

System 1200 Data Import Guide Design to Field 5-54 5.748596</ParaCurve> <PVI>160.000000 7. The start and end coordinates are included in PVIs.6.000000">110.462310 6. 5.6.000000 5. The PVI contains a space delimited station (chainage) of the stringline and elevation.3 CircCurve The CircCurve element represents part of what is needed to define a circular curve.000000 0.000 and 25.2.000000</PVI> <PVI>60. parabolic curve or any point on the vertical alignment.000000 0. <ProfAlign name="VERT"> <PVI>0.3.3.000000 6.000000</PVI> <PVI>25.750000</PVI> </ProfAlign> 5. 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.000000</PVI> <PVI>25.2.065348</CircCurve> <PVI>40.047489" radius="100. circular curve.000.6. Radius A typical vertical circular curve would be defined by: CircCurv PVI PVI .2.000000">32.0000" desc="-2225.6.000000 5.1 PVI (Point of Vertical Interest) The PVI point represents the start or end point of any straight.3.500000</PVI> <ParaCurve length="150.2 ProfAlign example This example contains the three supported elements: <ProfAlign name="VERT"> <PVI>0.000000</PVI> </ProfAlign> 5.3.000000 6.000000 6.000000</PVI> <CircCurve length="15.2 PVI example In this example the PVI elements act as the start and end points for a straight running between station (chainage) 0.

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.4 ParaCurve The ParaCurve represents a point of vertical interest that is used to define a vertical parabolic curve.4 Cross-sections Cross-section data may be imported using the LandXML <CrossSects> entity.6.2.System 1200 Data Import Guide Design to Field 5. ParaCurv PVI PVI 5. <CrossSects> <CrossSect sta="11270.000000"> <CrossSectSurf name="Layer 4"> 5-55 .3.6. 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).

148000 6.333122 335289. 5. the stringline is given the same name as the corresponding <Alignment> in the LandXML file. 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.System 1200 Data Import Guide Design to Field 5-56 <PntList2D>-3. A more comprehensive description of the LandXML format used by Design to Field is included with the add-on.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. LandXML data exported by Bentley software products (MX.949000 509. Note: A LandXML “add-on” software component is available for that may be embedded in 3rd party road design software.500000 509.6.000000 509.000000"> <Start>383106.7 Importing Bentley® LandXML data Depending on the version of each application.000000"> <CoordGeom> <IrregularLine staStart="0.287000</PntList2D> </CrossSectSurf> </CrossSect> </CrossSects> 5. InRoads / InRail and GeoPak) may use different LandXML entities to describe road elements. This component reads a LandXML file and converts the data to the System 1200 on-board format. .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>.793813</Start> <End>389361.024000 0. Onboard the System 1200 sensor. Contact your local Leica Geosystems representative for more information.759948 345490.

264023327 308590.737369516 704.370830366 308590.512990516 704.795227164 308594.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.219623961 308598.773157300 4600584.997311171 704.229364767 308589.087899168 308587.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.936692762 308595.027379240 704.447359792 704.System 1200 Data Import Guide Design to Field 5-57 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.795251784 4600582.866653808 4600576.749783173 4600587.726409046 4600589.843279681 4600578.844445482 4600576.078158361 308597.512295965 308591.867340343 704.819905554 4600580.227973138 704.890027935 4600574.770998568 308593. .287320895 704.653761564 308593.577330619 704.157350067 704.796531427 4600580.

Y)... A-Parameter (A= √LxR) "0SPIROUT" Station. WI 42 Identification of Horizontal Alignment file. Beginning of curve (X. WI 72 Radius of the next horizontal geometric element. may be defined by user..+0NEXTGEO 72. 8 ASCII-characters. Beginning of curve (X.. Coordinates (X..+000JOBID 42. WI 81 E-Coordinate of the point.Y)...10+00000000 WI 11 Station (chainage) of the point. The same GSI files can be imported for use on System 1200 sensors using the GSI road importer...8.+0NEXTRAD 73.Y). "000CURVE" Station... Radius 1 for a compound curve.. May not be changed by user.. Radius 1.. WI 74 Radius 2 for compound curves.. Radius.+HZALIGNM 43. Radius 2 "0CURVEIN" Station. WI 71 Type of the following geometric element.. Data block 11.+STACOORD WI 41 Job-Identification..System 1200 Data Import Guide Design to Field 5-58 5. Beginning (X.Y).. ...10+00000000 82. Max. or the A-Parameter for spirals..+0TEMPLNR 81.Y) "STRAIGHT" Station. WI 43 Identification of principal point type file. Radius 2 "CURVEOUT" Station.8 Importing GSI data Road data in GSI format may be used on previous generations of Leica Geosystems sensors. A-Parameter (A= √LxR) "00SPIRIN" Station. Road models in GSI format may only contain one layer per cross-section. May not be changed by user..+KILOMETR 71. Beginning of arc (X.1 Horizontal Alignment The following geometric elements are supported: Tangent point: Circular curve: Spiral in: Spiral out: Curve in: Curve out: End of Project: Station. Radius 1. WI 73 Number of a cross-section (Template) assigned to the next geometric element... Beginning of curve (X.Y) "00000EOP" Header of the Horizontal Alignment File: 41. 5.Y).. Beginning of curve (X.

.+00000000000CURVE 72.+0000000001000000 73.+0000000095751692 71...+0000000000000NON 81.. If a file is created/edited using the program "ROAD+FILE EDITOR" on the TPS1100..+00000000000CURVE 72.10+0000000522137922 82.+0000000000000NON 81.........+0000000000000NON 73..+0000000095629192 71....+0000000000350000 73.... 5....... Tangents and the EOP contain “00000NON” in WI72 Data units and decimal places in WI’s 11....8. H "0PARABOL" Station. There is no limitation on the size of the Hz-alignment file.8...-0000000010200000 73. H "00000EOP" Header of the Horizontal Alignment File: 41... 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.+STACOORD ..10+0000000495222153 *11.10+0000000495270222 5...+0000000095222400 71.2 Vertical Alignment The following geometric elements are supported: Tangent point: Circular curve: Parabola: End of Project: Station.System 1200 Data Import Guide Design to Field 5-59 WI 82 N-Coordinate of the point. An alignment file must contain at least two elements.. The last element must be "EOP".... 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.10+0000000521767106 82.+0000000000000NON 81..+00000000STACOORD *11. A cross section (Template) may be assigned to more than one location.....1 Horizontal Alignment example *41.....10+0000000495054894 *11..+0VALIGNM 43.+0000000000SPIRIN 72.. Radius.+0000000094562793 71... there is a limitation of 200 data blocks...........+000000000000A6-B 42.10+0000000521157487 82.1....... H "STRAIGHT" Station...+000JOBID 42.10+0000000522250574 82.. Note: - The header consists of a single block at the start of a data file. 72 and 74 are defined by WI81 and WI82.. Parabola parameter.10+0000000494803311 *11..+0000000000000NON 81. H "000CURVE" Station..+00000000HZALIGNM 43..+00000000STRAIGHT 72.

..10+00400000 11.+0PARABOL 72..+STRAIGHT 72. WI 43 Identification of principal point type file. Note: - Tangents and the EOP contain “00000NON” in WI72 Data units and decimal places in WI’s 11 and 72 are defined by WI83...+0example 42..+01127904 71... May not be changed by user.... If the curve radius point lies above the centerline.+0VALIGNM 43......+00000000 71.+00000EOP 72.. An alignment file must contain at least two elements....+00000NON 83.+STRAIGHT 72..+00000NON 83.. 5...+00300000 71....+STACOORD 11.2.... the radius is negative.10+00406522 11. If the curve radius lies beneath the centerline.+KILOMETR 71. WI 42 Identification of Vertical Alignment file. 5-60 .....+0NEXTGEO 72..3 Cross-sections The following geometric elements are supported: Height difference: Horizontal distance: Height difference from the vertical alignment Distance from the horizontal alignment...+STRAIGHT 72..8...+00000NON 83..10+00415000 11...8..10+00422500 11.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..+02091126 83.1 Vertical Alignment example 41..10+00418605 5.+00550000 71.. The stationing is projected onto a horizontal plane.+0NEXTRAD 83. Data block 11....10+00420000 11.. Tangent and arc lengths are calculated from the stationing..... may be defined by user.System 1200 Data Import Guide Design to Field WI 41 Job-Identification.+00500000 71... the radius is positive.+00850000 71.. 8 ASCII-characters..-01142932 83.. May not be changed by user..+0PARABOL 72....... Max.....+00000NON 83......

Data block 11. user definable... A cross-section may contain up to 48 points.+0000FILL 72. All data blocks belonging to a cross section must be consecutive in the file to minimize file access. A negative distance (WI35) indicates a point to the left of the centerline. Cross-sections do not have to be sorted by number.. WI 36 Height difference from the centerline..... WI 42 Template file identification. 5-61 .System 1200 Data Import Guide Cross section type: Slope: Design to Field Differentiate between CUT and FILL cross sections Slope ratio Header of the cross-section file: 41. The non-zero slope entry must be attached only to the last point on each side of the cross section. WI 72 Slope ratio.. A positive distance (WI35) indicates a point to the right of the centerline.10+000HDIFF 71.+TEMPLATE WI 41 Job identification.. May not be changed by user. A template file must contain at least one cross-section. Data units defined by WI 35+36.10+DISTANCE 36... A positive height difference indicates a point above the centerline. A negative height difference (WI36) indicates a point below the centerline. Max.... WI 35 Horizontal distance from the centerline.+00002000 WI 11 The cross section number.. WI 71 Cross section type. 8 ASCII characters. The data blocks for a cross section must be sorted from left to right across the section.+0PROF_NR 35.. Note: - All data blocks having the same cross section number (WI11) belong together.. The entries for cross section type and slope are optional.+00JOB_ID 42.

.+QP000125 35.....10-00000070 11.....10-00005000 11.41-00002000 36..10+00012000 36...10-00002000 11.10+00000100 11..10-00006000 11.+QP000125 35.. .10+00011000 36..41+00000000 36..+TEMPLATE 35.10+00004000 36..10-00002000 11.....+QP000124 35....10-00000100 11.. Max...10-00011000 36.3.10-00011000 36....+QP000125 35..10-00004000 36...+QP000123 35....+QP000123 35. 8 ASCII characters.+QP000125 35.....10+00011000 36..+0000FILL 72.10-00004000 11........11+00000000 71.10+00012000 36.10-00000100 11...+00000000 11..+QP000124 35.10-00003500 11..+TEMPLATE 11..10-00005000 11.....10-00012000 36.10-00012000 36. Header of the cross-section assignment file: 410001+000ASKER 42.....11+00000000 71.+TEMPLATE 35.......10-00002500 11..10-00002000 11.....10-00002500 11..+QP000124 35...10+00004000 36.10-00010000 36........+QP000124 35..+QP000125 35....+QP000125 35.......+QP000123 35.+QP000123 35.+QP000124 35.....8.8.......10-00000070 11...11+00000000 71.+0000FILL 72..+TEMPLATE 35..10+00000100 11..+00000000 5...41-00000500 36..10-00004000 36..10+00013000 36...10+00010000 36.10+00004000 36...+00002000 11.System 1200 Data Import Guide Design to Field 5-62 5..1 Cross-section example 41..10-00004000 36......10+ASSIGNMT 43.+CRSASKER WI41 Job identification.....+0000FILL 72.10-00003000 11..4 Cross-section assignment The following geometric elements are supported: Cross Section number: Chainage: The number or identifier of the cross section The chainage from which the cross section is applied must have a corresponding cross-section file.10-00002500 11...+QP000123 35.+0EXAMPLE 42....10-00013000 36. user definable.+QP000123 35.+QP000124 35..

. 5.+00844000 110014+000826.....+00568100 110006+000585... The units for station (chainage) are defined in WI 42 in the file header.....+CRSASKER 110002+0000NORM 71.+00568000 110005+000568. A given cross section may be assigned more than once.9 71.+00552000 110004+00000568 71.+00811000 110011+000826..+00844100 110015+00000860 71..1 Cross-section assignment example 410001+000asker 42.......+00827000 110013+00000827 71.1 71. A cross section remains valid until a new cross section is assigned....+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....4. Data block: 110002+0000NORM 71....10+ASSIGNMT 43.. Data units are defined by characters 6+7 of WI42.System 1200 Data Import Guide Design to Field WI42 Cross section assignment file identification...+00775000 110010+00000811 71. WI43 Name of the corresponding cross section file....+00585100 110007+000585.9 71....... May not be changed by user.1 71.+00382000 110003+0000NORM 71.+00860000 5-63 ....+00585200 110008+0000NORM 71.+00826900 110012+00000827 71....+00611000 110009+0000NORM 71.8...2 71..

kerbs etc.System 1200 Data Import Guide Design to Field 5-64 5. a prefix may be added to each line number if required. . Select the layers to import Select the layers to export to the System 1200 job.4.g. In addition. lines and area importer numbers the lines sequentially in the System 1200 database starting with the number 1 and incrementing each line by 1. a list of the layers in the DXF file that contain polylines is displayed. The points. walls. it is possible to read a DXF file and stakeout the linear entities of the DXF file using the RoadRunner Individual Stringline function. After defining the DXF file to import. many infrastructure projects (e. DXF File Linear Units The majority of DXF files do not contain information regarding the linear units of the file.) that the project contains.9 Importing DXF data Although the DXF format does not directly support road alignments. 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.g. housing estates) may be designed in CAD programs that export DXF files with the aim of staking out the linear entities (e. For this reason. 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. 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. Line ID prefix Lines imported from the DXF do not have identifiers.

5-65 . it is necessary to select the horizontal alignment from the stringlines in the file.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. After selecting the MX Genio data file. When the centreline has been selected. 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. vertical alignment and all stringlines are contained within the same data file.System 1200 Data Import Guide Design to Field 5. All data. the G strings and the coordinate strings or any combination of these strings using the corresponding check boxes. 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. horizontal alignment. press the Next button.

the relative order of the stringlines may not be maintained.System 1200 Data Import Guide Design to Field 5-66 Any combination of stringlines may be exported from the MX Genio file. the relative order of the stringlines may not be maintained. The stringline may have gaps and appear and disappear throughout the job but the relative position of the stringline in the design cannot change. Note: There are some differences in the way the RoadRunner and MX handle stringlines.In MX a stringline may crossover itself (e. . . Users should be aware of these differences when making a conversion from an MX/Moss file in GENIO format: . .MX allows different stringlines to cross over each other. if the exact chainage where this occurs is selected in the RoadRunner application. The Sort and select stringlines dialog allows the strings to be exported to the System 1200 sensor to be selected.Only one instance of a stringline can be used in RoadRunner. In MX it is possible for a stringline with the same name to appear in an infinite number of positions in the design. if the exact chainage where this occurs is selected in the RoadRunner application.g. an exit ramp).

433 792460.519 792983. the radius is negative.System 1200 Data Import Guide Design to Field 5-67 5. the known radius at the start of the clothoide should be used.357 357. 5.316 792451.1948 0.872 226.000 329.876 501414.002 42. Should start with 1 and increment in steps of 1.741 221.000 0.000 159.000 60.000 55.290 501953.299 792696.979 214.001 if it turns left.000 501972.3742 280.3333 280. the radius should have a value of 0.000 0.995 214.000 40.332 303.1 Horizontal alignment The horizontal alignment data should be separated by spaces.5127 0.5127 0.001 if it turns to the right and -0.251 97. If the element is the start of a clothoide (spiral) whose radius is a known value.318 303.000 .001 120.000 0.11.290 55.6746 -400.000 60.996 792452.1 Horizontal Alignment example 1 2 3 4 5 6 7 8 0.000 -130.11 Importing data in the Avance format 5.764 906.112 501573. : Chainage at start of element : Eastings ordinate at start of element : Northings ordinate at start of element : Bearing of alignment at start of element : Radius of curvature of element.973 217.067 501882.11.001 130.000 0. 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.8750 -400.564 792638. If the curve is towards the left in the direction of increasing chainage.1948 0.169 296.1.541 501943.458 296.311 792890.710 501898. The value of the clothoide parameter (always positive) The length of the element.687 686.000 199.000 -130.581 792931. Element_Number Chainage Eastings Northings Bearing Radius Parameter Length Element_Number (Integer) Chainage (Double) Eastings (Double) Northings (Double) Bearing (Double) Radius (Double) Parameter (Double): Length (Double): Note: - : Correlative number of element within file.357 747.755 501634.

000 -0. 5.000 0.613 88.000107 0.1 Vertical Alignment example 1 2 3 4 5 6 7 8 9 10 1000.914 1071.452 1329.522 1149.486 31. Element_Number Chainage Height Slope Parameter Length Element_Number (Integer) Chainage (Double) Height (Double) Slope (Double) Parameter (Double) Length (Double): Note: - : Correlative number of element within file.000 0.686 146.496 0.234 0.135 1237.11.577 144.889 140.335 1256.009 140.200 19.008203 0.001709 0.001709 3003.000 0.026 1122.2.11.System 1200 Data Import Guide Design to Field 5-68 5. If the element is a straight.208 147.000 1021. positive if element rises.933 147.098 1.042 147.000 0. If the result of the subtraction is negative.000 21.411 142.2 Vertical alignment file The vertical alignment data should be separated by spaces.354 1328.008203 -1000.359 147. : Chainage at start of element : Height at start of element : Slope in %. the sign of the parameter is given by subtracting the entry slope from the exit slope (p1 – p2).009 0. the value of the parameter will also be negative.400 1103.000 -0.004994 0.262 147. Should start with 1 and increment in steps of 1.626 26.000 0.000107 0.000 19.000 0.001 . the parameter has a value of 0 If the element is a parabola. negative if element falls : Parabolic parameter (kV) The length of the element.080006 0.914 49.019 72.004994 -15065.080006 900.

100 -3.000 931.3.System 1200 Data Import Guide Design to Field 5.700 6.1 Cross-section example 400+100.500 926.000 931.000 931.280 4.180 3.11.700 5-69 .3 Cross-section file For each cross-section the following data is required: Cross-section chainage Distance_to_CL Height .500 931.000 931.500 931.180 3. … Empty line Cross-section chainage: Distance_to_CL: Height: Chainage at which cross-section starts in format xxx+xxx.xx Distance from point to centre line..000 -4.500 921.500 930.490 5.000 931.280 4. negative if to left.700 6.650 922.500 931.00 -5.100 -2.500 990.490 5.11.100 -3. .00 -5.650 938. Absolute height of point 5.500 931.100 -2.000 931.000 -4.700 400+200.

0000 -400.1 Horizontal Alignment example 040 1 040 1 040 1 040 1 040 1 040 1 040 1 040 1 412.874 5372862.1 Horizontal alignment The horizontal alignment file should have the extension *.000 184.276 825.516 200.3 Cross-section file The cross-section alignment file should have the extension *.2 Vertical alignment file The vertical alignment file should have the extension *.d40 5.000 170.0374948 3504880.687 896. 5.12.043 637.370 437.629 512.513 5372917.824 5372345.374 5. A layer is created in the System 1200 database for each layer in the REB cross-section file.413 5372681.116 193.1368911 3505112.6095874 3505170. Up to 99 layers may be imported.600 1000.000 184.9546517 3504961.040 or *.000 187.392 166.0000 0.066 or *.9445367 3504941.0000 -500.000 177.021 or *.12.2.516 58. *.0000 0.032 1090.113 0.283 5372504.764 1256.744 696.055.8616935 3505045.1 Vertical Alignment example 021 0 649219 61791 0 021 0 825607 62827 176470 021 0 1587709 62129 214020 021 0 1900000 58582 0 5.000 175.d66 The cross-section file may contain layers.237 825.d21 5.046 1768.526 5373134.0000 0.12. . It is possible to export any number of layers from the REB file.000 0.0000 500. *.System 1200 Data Import Guide Design to Field 5-70 5.810 200.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.577 5371844.757 5373110.0000 0.1.000 0.0241729 3505125.d55.12.810 25.0374948 3504886.706 -1250.0000 440.000 227.000 -1250.000 178.697 0.12.

47 42.00 42.000 830.00 0.56 42.49 5-71 .000 820.63 1.27 4.60 42.37 3.59 42.63 1.38 2.57 42.56 42.System 1200 Data Import Guide Design to Field 5.00 0.53 42.55 42.63 1.49 42.000 810.53 42.27 4.38 2.000 820.37 3.000 850.62 42.00 0.58 42.63 1.00 0.1 Cross-section example D66 format: 66 66 66 66 66 66 66 66 20 20 20 20 20 20 20 20 780000 1 780000 2 800000 1 800000 2 820000 1 820000 2 840000 1 840000 2 -5500 5500 -5500 5500 -5500 5500 -5500 5500 62587 62202 62650 62265 62706 62321 62754 62369 -4000 62534 0000 62394 4000 62254 -4000 62598 0000 62458 4000 62318 -4000 62653 0000 62513 4000 62373 -4000 62701 0000 62561 4000 62421 D55 format: 055-1 055 1 055-1 055 1 055-1 055 1 055-1 055 1 055-1 055 1 810.38 2.00 0.000 850.37 3.49 42.42 42.3.57 4.53 2.47 42.58 42.12.62 42.000 0.00 0.27 4.52 42.27 4.38 42.63 1.000 830.51 42.51 42.00 0.54 42.27 42.000 840.63 42.37 3.00 0.37 3.56 42.60 42.61 42.000 840.00 0.38 2.45 42.65 42.

6744 76.130 7627.698 6290.000 0+265.6817 76.000 0+050.944 7668.583 Comprimento Tipo raio Parâmetro 76. the Cartomap road data importer also accepts data files from previous versions of Cartomap.281 Recta 76.1 Vertical Alignment example definição do traçado em alçado de: Eje_1 P.858 -2.644 Y 6196.061 6291.388 Dif.2.770000 -4.943 792.125 0+100.13.222 7613.K.230 1.694 6243.770000 1900.000 0+062.858 Cota vértice .569 799.697 790.6817 76.700 -0.770000 -4. A layer is created in the System 1200 database for each layer in the Cartomap cross-section file.122 0+100.484 Rumo 804.K.771 7645.869 799.000 0+200.339 0+150.339 790.6817 76.000 804.446 795.446 0+101.571 6430.427 6398.000 797. Cota terreno 0+000.6817 76.732 6336.409 799.494 800.0 onwards.13. 5.790 0+150.110 6444.494 0+050.744 6383.891 795.315 1.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.923 791.1 Horizontal Alignment example definição do traçado em planta de: Eje_1 P.826 7679.6817 76.System 1200 Data Import Guide Design to Field 5-72 5.000 0+101.423 0+247.13.000 789.761 6427.120 795.000 Clotóide -300. Cross-section layers are available from Cartomap v5.125 799.13.6817 76.869 797. X 0+000.3504 5.697 RASANTE EJE_1 802.1 Horizontal alignment 5.705 Cota 7591.1.790 795.425 789.770000 -4.233778 1900.000 0+216.2 Vertical alignment file 5.569 0+062.770000 -4.085 -2.565 7627. Cotas Inclinação Kv -4.878 7680.6817 108.377 6254.425 0+200.000 800.545 5.6817 76.122 -0.000 180.6817 247.122 795.085 5.000 76.000 790.000 795.037 7662.281 0+250.858 0.396613 1900.852 7686.315 7609.960 791.

724 6194. cotas 5-73 .350 801.13.850000 Design to Field 1900.625 -5.790 -4.000 5.149 7597.591 -2.500 5.625 7617.848 -3.959 -3.583 7591.067 6199.000 0+265.000 -3.474 -3.915 801.245 801.13.K.500 -5.104 0.153 805.500 6.192 801.968 801.644 790.928 -2.047 7586.858 5.663 7583.729 7583.125 -6.967 7597.111 -2.440 6196.901 7597.709 -3.903 6195.180 7585.604 6199.000 6.948 6198.663 805.198 -3.403 804.000 6.784 6194.539 -8.027003 3.851 801.036 -3.494 801.583 795.983 -2.985 804.000 Nivel 2 Nivel 3 0+050.569 -2.321 6194.315 7585.299 3.386 -2.858 1900.494 -2.950 -1.246 6199.535 805.092 -4.091 7597.965 805.422 801.883942 3.403 -8.861 795.192 801.190 801.923 791.000 X Nivel 1 6193.059 6194.777 -2.941 796.694 6199.896 1.684 Dif.500 0.137 801.797 800.985 805.109 -3.863 802.153 803.625 7.880 6199.3 Cross-section file 5.125 8.694 6197.809 803.188 -2.281 0+250.315 7588.260616 2.796 801.573 803.000 3.481 7597.744 801.222 795.329 6194.3.085 804.694 6198.625 0.501 7596.858 1900.494 803.785 805.126 802.629 801.321 6196.129 6240.494 801.125 -7.796 801.394 -2.960 791.403 805.413 803.450 7595.104 6.604 -6.227 distância 7599.485 6198.790 797.413 803.015 804.129 7584.799 801.153 803.983 7594.015 805.315 7585.074 801.014 7591.539 7598.067 Nivel 1 Y 6193.849 6194.079 -2.1 Cross-section example pontos singulares da secção tipo: Eje_1 P.508 6196.809 -6. Nivel 0+000.616 7585.System 1200 Data Import Guide 0+216.403 803.153 805.943 792.494 802.501 7591.965 803.664 6199.409 -2.858 1900.394 -1.476 -2.663 804.436 Cota terreno -8.125 8.647 7586.142 6194.999 3.423 0+247.021 801.901 3.479 4.604 -6.254 Cota secção 801.

System 1200 Data Import Guide Design to Field 5-74 5. 2478.3503 . 200. A layer is created in the System 1200 database for each layer in the Clip cross-section file.Tronco 0. 441494. 200.7891 .0251 .14.0000 5. 4453923. 1 LISTADO DE VERTICES N§ P.500 -7500 657.998 25000 632. 4453497. 441000.0000 . 104.2885 .Claznica 23-05-2000 P g.5000 3 2769. 0. Kv Cota TS Cota TS pS(%) Flecha Theta(%) === =========== =========== ======== ======== ======== ======== 1 700. 441574. 442789. 260.14.000 634.K.567 700.0872 .4011 .7963 .7319 .567 6.14.0000 500.1 Horizontal alignment 5. 4453916.1 Horizontal Alignment example *PLT1 Eje Nueva Carretera.9503 .0000 -700. 0. 195.1181 . 99. 1334. 0.0000 . 5.6586 .8333 .5778 .267 653.0000 0.0872 .017 800.7417 . 4453321.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. 191.4770 .0000 .488 1363.2000 . 1430.0000 .14.1.004 634. 0.4770 .0000 562. 4453924.0100 .3511 . 442044.0000 . 104.6870 .613 6.273 -7.0000 -700. 2381. 442052. 494. 4453417. 100. 260.7000 1.767 640.9624 .5000 549.512 2.4290 .8339 . TE Cota TE pE(%) Longi.6216 . 0.005 2494.4420 . 4452715.0251 .0000 .308 -1.5000 -5.0000 .269 -1.108 0.6960 . 442693.0000 0.2 Vertical alignment file 5.0000 500.000 634. 442036.6487 .2. 190.0000 . 4452718.0000 0. 99.0000 .1 Vertical Alignment example Variante de la C-736.5338 . 574.006 636.2590 .0000 2 1082.1674 .183 3044. 1254.

90 652.558 -5.24 646. 1100 COTA RASANTE C.221 23.00 651.1 Cross-section example C-736.00 5.3 Cross-section file 5.50 652. Cota Pend.89 647. 652.00 653.825 5-75 .50 652.D.I.90 652. 652.918 0.90 652.500 -17.450 -1. 652.633 -17.50 652.00 651.00 -12.50 652.K.500 P.3.533 -1. Dist.198 12.50 651.00 16.438 -8. Cota ======= ======== ======= ======= ======== ====== ======= ======== -25.638 -8.323 4.19 646.71 650.973 COTA RASANTE C.00 -15.598 ÄÄÄÄÄÄÄÄTALUDESÄÄÄÄÄÄÄÄÄ ÄÄÄÄÄÄPLATAFORMAÄÄÄÄÄÄÄ ÄÄÄSUBRASANTEÄÄÄ Dist.00 -4.00 15.123 -17.50 651.Calznica.00 651.825 -1.D.00 653.50 652.System 1200 Data Import Guide Design to Field 5.278 5. Cota ======= ======== ======= ======= ======== ====== ======= ======== -27.K.998 8. Cota Talud Dist.718 -4.90 652.500 -17.I.198 -8.598 COTA RASANTE C. Dist. 23-05-2000 P g. 652.71 650.00 -12.358 -8. 1120 COTA RASANTE C.50 653.221 17.450 -16.00 17. Cota Pend.758 8.14.973 ÄÄÄÄÄÄÄÄTALUDESÄÄÄÄÄÄÄÄÄ ÄÄÄÄÄÄPLATAFORMAÄÄÄÄÄÄÄ ÄÄÄSUBRASANTEÄÄÄ Dist.558 8. 1 LISTADO DE PUNTOS DE PERFILES TRANSVERSALES P. Cota Talud Dist.14.

000 0.154 292.144 0.000 15.766 615.050 0.080 0.000 521030.259 292.15.000 0.570 4716464.15.1 Vertical Alignment example * 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.000 LIN 0+079.2.1 Horizontal Alignment example * 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.System 1200 Data Import Guide Design to Field 5-76 5.746 -0.510 -0.107 328.197 616.000 0.000 15.766 613.792 298. The data exported from the InRail application is exported in the same format as InRoads.09 CIR 0+096.466 4716470.39 LIN 0+146.1.000 521092.000 LIN 0+139.15.000 PAR 0+029.462 334.471 4716474.000 521043.2 Vertical alignment file 5.801 0.400 4716477.000 0.09 SPI 0+081.000 521077.639 4716462. A layer is created in the System 1200 database for each layer in the InRoads cross-section file.15.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.1 Horizontal alignment 5.821 619.46 SPI 0+131.000 .76 5.867 -0. 5.801 0.000 521173.530 0.524 0.144 50.530 75.

500 932.000 932.570 0+100.500 931.000 931.280 0+100.00 -31.00 -18.490 0+100.1 Cross-section example Date: miércoles.3.040 921.000 0+100.00 -7.700 0+100.3 Cross-section file 5.490 0+100.00 -30.460 0+100.00 34.00 17.100 0+100.00 16.700 0+100.050 Design to Field 5-77 .00 -10.670 924.00 -17.500 931.160 0+120.500 930.00 -16.050 0+120.650 922.500 931.00 14.500 932.500 931.00 -18.500 930.00 -14.490 0+100.000 931.500 932.System 1200 Data Import Guide 5.00 10.00 18.700 0+120.180 0+100.00 -17.100 0+100.00 -6.500 931. 18 de abril de 2001 11:14:12 Surface Name: FIRME1 Alignment Name: EJE-1 0+100.15.000 931.670 0+100.15.

08 3 Oct 2001 15:57 612 PROYECTO : TG405L 3.5291137 5. 143.000 141.System 1200 Data Import Guide Design to Field 5-78 5.196 1500.700 276.K.204 1.0241 0.982 450914.-----------.402 4474280.0241 449903.112 4473164. pagina 1 TODOS LOS EJES JUNTOS ============================================ * * * LISTADO DE LAS ALINEACIONES * * * ============================================ DATO TIPO LONGITUD P.874 135.8524422 -0.2 Vertical alignment file 5.1.08 3 Oct 2001 15:57 612 PROYECTO : TG405L 3. Ramal 1.8485509 -0.536 4473163.7. 5.16. 132.853 4473082.000 135. X TANGENCIA Y TANGENCIA RADIO PARAMETRO AZIMUT Cos/Xc/Xinf Sen/Yc/Yinf ---.4951 0.000 450686.16.107 144.304 4471884. JUNIO-2001 EJE : 27: Enlace T672.671 0.16. Ramal 1.-----------.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. pagina 1 TODOS LOS EJES JUNTOS ================================================= *** ESTADO DE RASANTES *** ================================================= PENDIENTE LONGITUD PARAMETRO VERTICE ENTRADA AL ACUERDO SALIDA DEL ACUERDO .-----------.-----------1 RECTA 1.533 3 CIRC.-----------.671 450687. JUNIO-2001 EJE : 27: Enlace T672.1019 451708.731 4473007.-----------.1 Horizontal alignment 5.875 450805. A layer is created in the System 1200 database for each layer in the Ispol cross-section file.701 4 RECTA 67.7.--------.070 135.----.-----------.2.1 Vertical Alignment example ispol-V.5228215 2 CIRC.617 -1500.16.-----------.1 Horizontal Alignment example ispol-V.

000 Cota: 648.PUNTOS DE CONTROL EN ALZADO--------------------0.08 3 Oct 2001 15:57 612 PROYECTO : TG405L 3.098 636.481 1588.022805 76. JUNIO-2001 EJE : 27: Enlace T672.000 ---------------.978 135.058 971.977 Dist.000 2320.K.00 -2.721 237.503 1099.081 645.0 Pend% 5-79 .: 0.743 634.00 -1.975 644.070 Dist.: 0. Ramal 1. Cota Dist.277 635.-----------.207 783.------------------------------Dist.00 4.000 0.0 -1.923 643.690 644.282 -2.000000 198.081 646.000 199.-----------0.00 648.002 648.562 -1.------21.500000 126.7.081 646.0241 TALUDES CUNETAS SUBRASANTE RASANTE ---------------------.0 -2.System 1200 Data Import Guide Design to Field (%) (m) ( kv ) p.750 3750.977 -2.K.-----------.417 100.-------------------------------450686.-----------. cota p.16.: 0.-----------.000 Cota: 648.851 1768.575 6000.------.k.------------------------------.298 643.458 11.------.-------.710 7500.00 -3.00 648. Cota Cod Pend% Dist.k.945 160.1 Cross-section example ispol-V.000 Cota: 648.627 632.-----------.031 -0.823 -0.----.000 703.548 637.291 10000.: 0.991 0.386 645.700000 180.978 4473164. cota -----------.700000 127.207 20000.417 2.415 2.000 1915. cota p.977 632.00 648.559 315.-------.---------------.381 624.334 644.917 -3.----.000 1678.610 1978.389 633.333 1322.16.877 6.000 1222.958 11.300 1900.0 2.01 639.00 648. Final : Intervalo : pk: X: Y: Az: 0.112 Dist.00 648.489 645.763 644.k.000000 77.00 648. Cota Talud Dist.377 5.917 50.979 645.------.----.171 237. Cota Cod ------.294 1852.000 Cota: 648.550 643.000 1035.3 Cross-section file 5.593 645.292914 159.000 BANDAS BLANCAS EJES DE GIRO ------------------------------.3.977 Dist. Inicial : P.-------.-----.-----------.000 15000.295 1123.-------. **************************************************** * * * SECCION TRANSVERSAL COMPLETA **************************************************** pagina 1 TODOS LOS EJES JUNTOS *** P.000 276.-----------.

K.0 11.00 648.00 648.000 8.7.477 1.0 -2.System 1200 Data Import Guide 2.318 2.K.0 2.000 pagina 1 TODOS LOS EJES JUNTOS *** 5-80 .00 648.00 648. JUNIO-2001 EJE : 27: Enlace T672.00 648.50 648. JUNIO-2001 EJE : 27: Enlace T672.94 639.000 2320.318 100.407 2.977 -2.00 0.818 1.00 3.00 6.7.0 7.000 0. Ramal 1.00 3.907 -2.08 3 Oct 2001 15:57 612 PROYECTO : TG405L 3. pagina 1 TODOS LOS EJES JUNTOS pk: 0.00 ispol-V.818 2.99 8.846 ispol-V. Inicial : P.0 -2.857 -3.00 648.00 24.0 Design to Field 2. Ramal 1.00 648.357 11. Final : Intervalo : 0.00 0.0 50.50 648.99 7. **************************************************** * * * SECCION TRANSVERSAL COMPLETA **************************************************** P.00 6.08 3 Oct 2001 15:57 612 PROYECTO : TG405L 3.0 -1.00 648.

990 628.60499999998 8 7542. Up to 4 layers may be imported.5427 481063.203 -7.1783 0 0 0.0904 -7250 1826.034 4480056.1 Vertical Alignment example 1 2 3 4 0.000 -6.5419 477241.1 Horizontal alignment 5.2 460.2 460.3366 4482980.541099999973 2 378.781 629.146 -30.7675 4484280.4488 0 0 378.090 -0.090 0 12000.2 460.517999999982 6 5935.System 1200 Data Import Guide Design to Field 5-81 5.175 628.000 121.000 111. A layer is created in the System 1200 database for each layer in the Modelo Digital cross-section file.8131 4485520.9982 37.3 Cross-section file 5.4779 49.17.250 -6.0 10000.3717 37.001 1826.0904 7250 0 1146.000 -40.559 74.000800000038 9 8002.218 629.0707 0 0 612.2.4292 -7250 0 4024.3.000899999985 7 6395.500 629.435 628.0435 482087. 5.493 4480204.1485 482085.1586 7250 1826.0229 480253.090 0 0 0 0 0 1000.17.090 0 11000.990 628.175 628.6753 47.17.001 1826.48099999997 4 863.6357 35.7341 35.1.000 111.2674 49.7262 72.1477 481767.786 -12.397 628.0 500 5.9955 4480388.000800000038 3 838.990 628.990 .490 629.17.17.5418 480818.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.862 4483891.2422 4483369.2 460.2 Vertical alignment file 5.675 74.17.89500000001863 10 8006.0707 0.5662 4485184.0 1000.0238 480498.0947 4485517.4488 -0.596 629.1 Cross-section example 0.001 5.1783 0 0 3.549 -7.000900000043 5 5323.5411 476820.315 -6.1 Horizontal Alignment example 1 0 476472.000 111.01 1000.037 -5.

P1=3.Z= 634.L=DROITE.D5=1.18.000.P= 6.D1=4.D4=2.P3=-3.000 C.400.N= 5 P.000.L= 494.PMDEV=1240.P1=-6.SL= 619.P4=1.P1=7.400.D3=7.RP= -40000.500.L=GAUCHE.567.G= 104.789.D1=4.Y= 4453923.111.267.622.000.400.000.AO= 494.D4=2.000.TPC=non.400.D3=7.000.D5=1.327.A= 200.986.L=DROITE.000.X= 441000.000.D5=1.D2=1.000 A.A= -200.D2=1.000.N= 5 P.500.G= 99.000.834.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.SL= 1130.D2=1.500.D5=1.259.440.500.X= 441574.P3=5.PMDEV=1100.7000.RP= -7500.006.P2=-8.R= 700.1 Cross-section example P.P1=6.P2=5.000.000.000.R= -500.P2=-3.000.400.111.2.108.800.000.500.AO= 2381.500.500.5000.000.N= 5 P.006.500.000.PMDEV=1260.SL= 562.244.000.G= 104.000.P2=-1.D3=7.400.571.Z= 636.SJ=1250.X= 442044.PMDEV=1300.P3=-8.P3=8.D1=4.000.477.500.610.1 Horizontal alignment 5.767.R= 700.P3=1.457.Y= 4453497.D2=1.P1=-7.3503.D2=1.087.687.D2=1.P2=8.800.000.000.G= 195.P4=8.SL= 100.G= 191.000.000.000 A.000.000.D4=2.000.000.P4=-5.L=DROITE.331.767.962.D4=2.000.000.400.000 C.000.L= 679.1.8500 5.Z= 640.400.000.TPC=non.D1=4.L= 96.429.351.P= 6.N= 5 P.18.000.D2=1.R= -0.P1=-3.500.696.L=GAUCHE.000.000.N= 5 P.414.D1=4.R= 0.000.000.044.L=DROITE.000.500.Y= 4453916.000.1181.P1=-4.000.440.000.500.Z= 637.D3=7.571.331.113 D:S=1363.P4=-7.L=DROITE.N= 5 5-82 .System 1200 Data Import Guide Design to Field 5.TPC=non.PMDEV=1260.P5=-8.000.400.ZJ=633.000.P4=-8.0251 A.P5=-4.X= 442052.TPC=non.D2=1.P1=7.SL= 621.D4=2.P3=-5.N= 5 P.500.PMDEV=1280.L=GAUCHE.P3=-7.000.P1=-1.N= 5 P.D4=2.000.P5=-7.167.000.P= -1.P3=3.000.132.D1=4.992.000.PMDEV=1240.AO= 1254.AO= 574.500.P2=8.Z= 638.D3=7.P4=3.D2=1.6487.L=GAUCHE.D4=2.500.0000.000.P5=-4.739.P2=-5.L= 80.767.N= 5 P.P= -1.P5=-8.500.R= -500.L= 951.000.P4=7.D5=1.D4=2.400.111.P5=-4.P5=-4.Z= 634.D2=1.A= -260.3.P4=-8.P2=-7.P1=1.SL= 945.D3=7.D3=7.000.000.Y= 4452718.401.000.N= 5 P.613.P= 0.D4=2.ZJ=654.087.500.P1=-7.7000 P:S=3665.P= -0.P2=1.TPC=non.000.578.SJ=3945.D4=2.P4=-1.G= 99.L=GAUCHE.P3=7.289.P3=8.N= 5 P.P3=-1.P1=4.1 Horizontal Alignment example D.000.D3=7.L= 96.400.P2=3.P5=-5.TPC=non.D3=7.400.18.D5=1.400.000.L= 80.500.P4=-3.RP= 25000.D2=1.500.000.AO= 1430.5000 P:S=2494.000.950.ZJ=639.D1=4.400.SJ=2869.414.000.414.578.000.D1=4.Y= 4453417.P3=-8.600.D5=1. 5.P5=-4.PMDEV=1300.400.000.111.400.500.3 Cross-section file 5.P4=5.TPC=non.TPC=non.000.000.1 Vertical Alignment example D:S=700.500.414.AO= 1334.8333.000.000.500.477.500.000.308.010.400.000.D3=7.D5=1.000.496 D:S=3044.000.000.TPC=non.477.004.D1=4.000.PMDEV=1320.D3=7.SL= 549.998.L=GAUCHE.18.437 D:S=4285.000.267.D1=4.P4=8.000.000.18.L=DROITE.TPC=non.022.2 Vertical alignment file 5.000.317.D1=4.P5=-4.000.414.D4=2.N= 5 P.000.7417.P2=7.D5=1.500.000.D4=2.A= 260.P= 0.D1=4.0251.D2=1.TPC=non.P2=-8.P5=-4.Y= 4453321.D5=1.X= 442693.000.G= 190.AO= 0.Z= 653.000 A.X= 441494.D5=1.X= 442036.659.440.269.000.Y= 4453924.18.000.PMDEV=1280.TPC=non.0000 P:S=800.400.PMDEV=1320.500.D5=1.D3=7.304.P5=-4.PMDEV=1100.000 5.

663 1500.758 175.000 33NM88.0076561446470.8800696048160.1 Horizontal and vertical alignment 5.6657455681550.429 94.659 99.000 32NM248.000 31NM285.045 -550.000 313.679 300.000 31NM363.000 33NM101.000 31NM304.19 Importing data in the SDR format Horizontal and vertical alignment s may be imported from files in the SDR Varin / Map format.765 2328.141 500.889 -450.000 31NM353.000 32NM685.000 33NM82.735 -450.000 34NM16578.828 32NM209.042 32NM157.045 -550.605 -6500.457 36NM18372.000 33NM92. 5.0312611839410.227 79.000 32NM421.000 33NM73.313 217. This format uses a single file to define both the horizontal and vertical alignment.000 31NM283.656 105.250 500.030899999999125.570 400.833 109.003 36NM19636.1.000 31NM370.8178999999994814.005 37NM20193.525 -550.108 5000.000 33NM101.211 36NM19239.5949880514950.000 32NM338.250 500.System 1200 Data Import Guide Design to Field 5-83 5.312 -450.19.1160022790350.000 33NM92.000 32NM494.328 .000 31NM281.19.5612416417300.000 31NM288.00000000 29NM15720.333 400.1 Horizontal and vertical Alignment example 00NMSDR33 V04-030000 2-FEB-01 16:32 213121 28KIbaranbio 1 06NM1.

151769.629.000.0.878.000.0.375.0.0. 0.248256.610.8. 0.007.802.-4000.191.0.267.225.466.0171. 2.000. 0.700.-40.8.0.151655.626.268.000.000.248426.0.222.73.985.0. 0.000 HORIZONTAL_ALIGNMENT 0.0.44.0.747.550.225.267.225.1 Horizontal and vertical Alignment example AXIS NAME "Eixo 0" VISIBLE TRUE ACTIVE TRUE LOCK FALSE START STATION 0.319.551.000.223.151683.000. 5.213.000.340. The horizontal and vertical alignments are exported in the same file.154.226.000.151754.163.191.30.111. 0.7702. 1.0.0. 0.151670.999.5971.0. 0.74.000.0.248405.000.0.000.68.0171. 1.20.481.31.000.000.20.000.6459.40.556.422.40.248340.784.226. 0.248369.000.670.000.230.0.455.280.1.600.000.556.000.708.671.000.20 Importing data in the SierraSoft format The SierraSoft format is a cross-section based format that allows the import of cross-sections.765.151688.System 1200 Data Import Guide Design to Field 5-84 5.37.0.-150.344. 0.436.375.248313.000.248417.699. 1.151675.13.000.5971. 1.000.6459.0.280.325.700.224.767.549. 0.000.950.163.223. END VERTICAL_ALIGNMENT .7702.000.801.0.406.881.000.0. 2.950.74.248251.111.151694.17.0.1 Horizontal and vertical alignment 5.000.263. END HORIZONTAL_ALIGNMENT VERTICAL_ALIGNMENT 0.225.192.779.

680 1 PRO 224.102 224.102 224.102 PRO 224.102 PRO 224.870 #COD 3.870 3.000 -3.257 224.200 4.102 PRO 224.102 223.2 Cross-section file 5.772 224.349 224.870 4.870 3.772 224.870 #COD -3.349 224.200 -4.257 PRO 224.000 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0.772 223.680 -4.680 #COD 0.1 Cross-section example #SEZ #COD 0.102 224.000 224.102 224.680 4.599 248417.102 224.870 -4.680 #COD -4.102 PRO 224.870 -3.20.673 #COD -3.772 223.673 #COD 3.102 0.102 224.2.673 -3.680 #COD 4.000 3.257 PRO 224.102 223.870 -3.20.System 1200 Data Import Guide Design to Field 5.673 3.200 -4.600 5-85 .257 224.200 4.000 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 1 0.213 151769.102 PRO 224.

670 656.000 0.344 655.478 4151627.701 517262.000 0.3 Cross-section file 5.026 0 3.000 10.216 19 -3.1 Horizontal Alignment example 0.010 656.9925 50.178 58 5-86 .230 656.000 0.576 4151633.88 198.1 Vertical Alignment example 0.000 0.System 1200 Data Import Guide Design to Field 5.707 4151537.21.000 0.526 4151616.21.655 1213.701 517264.21.000 0.68 190.176 20 -3.255 4151506.000 0.010 655.000 0.000 144.176 20 6.1.524 1000.277 0.1 Cross-section example 0.000 0.000 127.000 421.935 510.21.396 99 -7.176 59 -6.676 58 -5.159 4151512.55 124.966 18 0.507 99 -6.000 655.010 656.000 655.1 Horizontal alignment 5.000 0.000 0.000 10.2 Vertical alignment file 5.128 8.478 517200.507 59 -6.92 106.010 656.000 0. 5.191 532.000 466.000 263.306 0.00 -100.0054 0.287 50 -6.21.1004 0.541 473.562 517264.010 656.000 257.00 100.000 0.000 0.000 -7.000 5.969 10.669 656.000 656.000 232.74 198.000 100.11 106.000 71.000 10.966 18 3.9503 25.000 517074.1004 75.508 868.216 19 5.21.000 144.21 Importing data in the TCP format The TCP format is a cross-section based format that allows the import of cross-sections.000 0.228 517145.151 1200.000 0.010 656.010 656.00 0.2.3.000 5.9503 0.

0680 TANGENTE ENTRADA -252.0000 TANGENTE SALIDA -145.22.000 P.216 495697. LONGITUD X Tang.000 0.7836 0.609 4393612.4672 -0.6782 82.138 132.6287 -500.22. 3 RECTA 34.K.000 0.2 Vertical alignment file 5.000 5-87 .631 283.585 30.22.22.1 Vertical Alignment example 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 0.5212 11116.0000 PENDIENTE%/PARAMETRO 84.000 5.247 128. AZIMUT XC o I YC o I PARAMETRO RADIO 1 RECTA -248.785 4393751.062 495971.253 132.1003 0.7370 -1.0680 1 VERTICE -198.1. Y Tang.1 Horizontal alignment 5. INICIO -500.006 64.000 2 CIRC.2.K.200 495944.802 4394048.K.000 496189.1 Horizontal Alignment example Fichero: C:\TEMP\COR\WIN\V1-2801 Título: v1-2801 Fecha: 28/01/2003 19:04:08 ALIN TIPO P.22 Importing data in the Trazado format Horizontal and vertical alignment s may be imported from files in the Trazado format 5.785 7.360 4393598. COTA P.6287 0.System 1200 Data Import Guide Design to Field 5.1091 81.0956 -1.8937 81.

228 63.1630 213.0000 0.000 0.000 0.000 0.000 10 266531.000 0.390 -51718.000 0.1 Vertical Alignment example 0.339 97.23.346 5.000 0.655 -51813.2000 0.23 Importing data in the VIPS format Horizontal and vertical alignment s may be imported from files in the VIPS format 5.1 Horizontal alignment 5.000 5-88 .660 10 2.0000 85.320 72.114 -51741.000 10 266530.660 25.765 0.23.000 0.23.000 72.1 Horizontal Alignment example 10 1.0000 44.228 266530.000 10 266531.320 266521.000 0.0000 10.000 25.000 0.1000 0.1891 350.887 266531.2 Vertical alignment file 5.2.000 63.742 -51750.742 -51750.0000 85.000 0.23.6300 0.765 10 3.0000 212.000 0.000 0.System 1200 Data Import Guide Design to Field 5.1600 214.114 -51741.1.