Setting Out Data - Road and Railway

Tip: This specific type of export is only available from Novapoint 21.FP2 and onwards. In Novapoint 20 and earlier, the same results can be exported from the Road task > Design > Setting Out Data.

To get setting out data with the necessary topology to be readable in total stations the export need to be set up in a specific way.

The export needs to include the alignment used for the road task, and the road task itself. In addition, you need to use the correct conversion file to assemble the exported file the correct way.

In short, you need to:

• Add the road task to be exported (only one road task can be picked for this export format because of limitations set by the receiver).
  If not all road task result features are needed for the export, then pick the correct stringlines to export.

• Be aware that most machine control systems can only handle one road surface in one file. Use the selection dialog to select the correct layer for one export

• Add the alignment used for this specific road task (machine control needs the centerline in the same LandXML file as the rest of the road surface layer)

• Set chainage limitations (if needed)

• Use the conversion file 'Irregular Lines'

Note: Multiple conversion files for Irregular Lines might be available, so make sure to pick the correct one for your export.

This type of export will only export the road task string lines as so-called “irregular lines” to LandXML for use with Leica RoadRunner or import it to Trimble Business Center for further export to Trimble equipment or use the Trimble File Flipper to make machine control files directly.

Using templates

Exporting the road model stringlines can be made simpler through the use of export templates.

1. Select Output > Export.

2. Pull down the Template menu on the far left (note that templates are only available when creating the task, not when editing).

3. Pick the appropriate template to use (f.ex. 'StakeOutLines_Road Surface').

4. A wizard starts and lets you pick the road task to export. Press Next, and the road alignment belonging to this road will be picked automatically.

5. Define the from-to chainage to use if there is a need to export a shorter length of the road. Press Finish.

6. Set the appropriate conversion file (f.ex. 'Irregular Lines', will work with Leica and Trimble. ‘InfraBIM Breakline”, will work for Trimble, Novatron, and others).

7. Press OK on the export task to complete.

8. Set a file name to the exported files.

Examples

Using Templates

When exporting, there are possibilities to pick just the stringlines you need and push them to a LandXML-file with topology for use on the total station.

'StakeOutLines_Road All Layers'

This template has already picked all the typical road surfaces including all stringlines for the road surface and pavement layers. Check the query set in the 'Selection' for the task.

Template with edits

The template 'StakeOutLines_Road All Layers' makes sure the user picks one task to export including the correct alignment. It is however still possible to edit the query in the 'Selection' for the task. De-select or change the selection as needed. For further information see the 'Manual selection'-part on this page.

Manual selection

Editing a template selection or making a selection from 'scratch' can be done in many ways. Here we show some examples.

Remember that to get the content in the export file correct with the use of topology needed for 'Irregular Lines', you need to:

• • Pick ONLY one road task to export.

  • Pick the correct line task for this road.

  • Pick the 'Irregular Lines' conversion file.

In the query for 'Selection', the objects picked will determine what gets exported.

Note: No selection = All objects are selected.

Warning: When starting to select objects, remember to also include the alignment (object type = LinearElement)

• All road surface strings - Pick the object type for 'StakeOutStringTopLevel'.

• All pavement layers - Pick the object type for 'StakeOutStringStructure'.

• A specific pavement layer only  -Stinglines for the pavement layers related to the Base Course. Pick the object type for 'StakeOutStringStructure'.

We would in this case like to have only the stringlines for the Base Course layers. These stringlines have an attribute 'layerName' with unique text values that you can use.

All the Base Course layers will have a text including 'PAVEMENT_BASE_COURSE' with some more information at the end. We can use this now and get the stringlines that contain this information.

Add a filter for the attribute 'layerName'.

Note: We are also here allowing ourselves to be inaccurate in cases when using CONTAINS (not case-sensitive). 'base_course' and 'Base_COURSE' are handled equally.

Tip: To pick only the Base Course 1, then filter for 'BASE_COURSE_1' instead of just 'BASE_COURSE'.

Multiple pavement layers

Use the filter when picking one pavement layer and add another filter.

Complex selections

The dynamic query can have more complex selections and filter on different attributes at the same time. Make sure you have used the correct operator for AND/OR when combining selections like this.

Tip: For even more complex selections that we do not handle, consider having the separate selections grouped in 'Collection tasks' and use them as a task selection in the dynamic query instead. Then the objects with the correct filter should be set in those 'Collection tasks'.

Next topic: SOSI