CTDOT CONNECT DDE GUIDE VOLUME 4 - OPENROADS DESIGNER SURVEY


Module 4 - Processing Survey Data


Description

In this Module, you will learn how to import an ASCII survey data file and edit the imported data.

Objectives
  • Learn how to Import Field Data (ASCII data file).

  • To become familiar with the available tools and dialog boxes.

  • To become proficient editing the imported field data.

Quick Steps
Step 1 - Review and Edit Data Files
Step 2 - Create Field Book
Step 3 - Rename the Field Book
Step 4 - Import Field Data
Step 5 - Address Duplicate Points
Step 6 - View Options
Step 7 - Process Survey Data

 

Before attempting to open or create DGN files users should make sure the following is in place:

Step 1 - Review and Edit Data Files

Raw data and coordinate files should be reviewed and can be edited before the import in to OpenRoads. One option is to edit field files via a text editor before loading them into the field book.

Numerical order is irrelevant. The important thing is the order in how link codes define the shape.

  

Additional points (i.e. Stored Points) can be entered, but ensure that they stand out from actual shots taken (i.e. Observation Points.) ORD will resolve double link codes by using an underbar and number suffix (e.g. 1018_1) so a good practice is to use a letter suffix.

 

String SubstitutionsORD no longer uses multiple Linking Codes; however, double coded shots such as “st pc” are automatically converted through String Substitutions (e.g. “startPC”.) CTDOT has added “pt cl” to simply “cl” behind the scenes. This allows field personnel to continue using familiar InRoads coding for the time being.

 

 

Click here for a listing of Linking and Control Survey Codes.

Step 2 - Create Field Book

1. From the Explorer interface, select the Survey group. Note: The model name, “Default” is listed as the default under Survey Data – not the design file name. This could be renamed to something more relevant such as: Terrain, Ground File, Annotation, etc.

2. Expand the model tree.

3. Right-click on Field Books to review the menu options.

  • Create Terrain Model From Field Book Selection Set Depending on your system configuration Terrain Models can be created dynamically. The benefit to this is you can see how edits affect the Terrain Model in real time (we will use this functionality later in this course). Also any additional data collected is added to the Terrain Model automatically. If you elect to turn this functionality off however, it’s a simple matter to create a Terrain Model using this menu choice. You may also notice that it will use a selection set, this might be highly useful if you need a specialized Terrain Model made from certain data types or Feature Codes.
  • New This menu choice creates a new Field Book. As noted before it’s entirely up to you how many (or few) Field Books you utilize in your projects.
  • Properties Properties will display all of the properties of a survey feature.
  • Zoom Zoom will allow you to zoom into a specific area of data in your project. Within a large project (with several Field Books) it may be beneficial to be able to Zoom into a specific data collection session.
  • Isolate and Clear Isolate This will modify the display to highlight specific collection sessions. Useful if you have several Field Books.

4. In the Survey panel, right-click on Field Books and select New...

5. On the Selecting Settings dialog select Accept. Note that a new drop-down arrow appears as a Field Book is added.

5. Expand Field Books.

When a new Field Book is created, it will be created under the Field Books folder with a default name of Field Book 1. To view the newly created field book you must expand the Field Books folder using the drop-down arrow next to Field Books in the Survey pane

6. Expand the newly created Field Book 1additional Survey information will appear once data has been imported. 

Under Field Books is where the survey data you import is stored. You can create the data structure to fit your operational needs.

  • Do you need a single “Job” where all the collected field data is stored? You can do that.
  • Do you need to separate each and every collection into it’s own book? That’s easy as well.

Basically, it is up to you to decide what a “Field Book” contains.

 

Step 3 - Rename the Field Book

1. Click Field Book 1 in Explorer to select its properties as shown in the previous image.

2. Using the Properties (Survey) interface, rename Field Book 1 to something more appropriate if desired.


 

Step 4 - Import Field Data

All project field data should be stored in the COMPASS Project folder with the ground file. OpenRoads can import multiple files at once.

1. From the Explorer Survey group, right click the new field book to Import> File…

 
2. Browse to the field data folder in your COMPASS Project.

3. First select a control file if present.

4. Click OK.

Files with an asc extension will not work.

 

For *.txt, use …code or …code, code?

 

5. Continue to import multiple field files to Field Book 1You can Add them or simply click OK.

At this point it’s important to mention that all of the resulting survey data is contained within the DGN file. There are no external files and no need to ensure synchronization between the “data” and the resulting graphics or terrain. The resulting graphic elements contain the “intelligence” and “know” certain survey properties such as Terrain Model attribute (Spot, Break, None) how they should display and other properties that used to be controlled by multiple external files. As you will shortly see this is very powerful and makes editing data very intuitive and the resulting changes are seen in real-time as the graphics update. However, sometimes this does necessitate a different mindset. Such as, to make changes to the Terrain Model best practice would be to edit the terrain properties of the point rather than the resulting “Triangles”.

6. Review the imported survey data. Use the Fit View tool to see the results.

Step 5 - Address Duplicate Points

Address duplicate points using the “Differences” tab if necessary.

NOTE: I have been selecting the “Skip” option, but this may need to be addressed further. In this example, the Control file information was brought in first and should take precedence.

Apply All.

The field book tree is now populated.

 

Step 6 - View Options
« Examine Survey Features

In this section, you will examine Survey Features.

1. Fit View. All Observations and Triangles are displayed by default.

2. You may toggle off All Observations through Explorer if desired.

3. Zoom into the view.

4. Use Element Selection to click and highlight the Terrain Model outer boundary.

5. Toggle displays such as Triangles by double clicking the Off or On through Properties. The display immediately changes.

« Decorations

In this section, you will become familiar with decorations. Decorations provide surveyors a quick display tool to access vital survey point information. They can be utilized during the quality control process and differ from the annotation tools which place permanent labels in the project.

 

1. Change the active tab from Home to Analyze.

Note the Decorations section of the menu, these tools control the display of survey data such as the survey point Names, Field Codes, Elevations, Descriptions, Setups, Observations and Icons. All of these tools function as ON/OFF display toggles.

2. In the Decorations section of the ribbon, left-click on the Names tool and notice that the point names disappear. Left-click on Names again and the display returns.

3. Display the Field Codes and Elevations.

In the Decorations section of the ribbon, left-click Field Codes to display the feature codes.

Left-click Elevations, to display the elevations of the survey points.

The display properties of the Decorations can be configured from the Back Stage view.

4. Select File to get to the back stage and then select Settings > User > Preferences > View Options - Civil > Survey Decorators. The Colors have been set up to follow standards and should not be changed.

Click OK to accept any changes and return to the drawing view and note the changes.

Step 7 - Process Survey Data

Be aware that any editing after this point will become self-contained in the MicroStation file, and there presently is not an option to export the edited field book.

« Survey Details Reminder

1. Display Survey Details if not already.

2. Click All Observations to list them.

 

« Review Flags and Messages

Points in question are also flagged by a Survey Locator.

Re: NTC – it’s CASE SENSITIVE – see substitutions email!

 

1. Hover over one of the points to display information about it.

2. Click the Message Center tab to view notifications.

3. Right click the far left empty column or double click within each field of the row of the Survey Details to Edit selected items.

 

« Heads-Up Editing

1. Use Element Selection to select feature.

2. Hover over the selection for the Heads-up Tools to appear.

 

3. Move the cursor over the Heads-up Tools to select a tool.

Point feature tool choices are as follows:

  1. Properties
  2. New Point Feature
  3. Turn on/off All Annotations
  4. Report
  5. Create Control Point
  6. Edit Observations
  7. Delete

 

Linear feature tool choices are as follows:

  1. Properties
  2. Append Point In Linear Feature
  3. Move Point Along Linear Feature
  4. Insert Point In Linear Feature
  5. Close Linear Feature
  6. Break Linear Feature
  7. Transpose Linear Feature – Changes linestyle direction
  8. Move Linear Feature
  9. Report
  10. Convert to Point List Linear Feature
  11. Manage Point List
  12. Edit Point Features
  13. Delete

 

« Survey Codes

Linking Codes - Linking Codes is a way to connect features in the field. They are placed after Feature Codes. Some have been customized to avoid conflicts with feature codes.

 

Control Codes - Control Codes can be used to draw additional planimetrics for circles, rectangles, and lines; and can also modify a location.

You are able to use a JPT code from a line see below.

You are able to use a JPT code from a line but not from a pc see below.

 

The following demonstrates results from each of these examples: