Cross Section Viewer

Import Survey Data

Survey data can be imported into either a new or existing survey. The data must be in a comma separated value (CSV) plain text format that contains a single header row of column names ([] sample below)](#sample-csv-file). Different fields are required depending on method used to identify cross sections in the current database.

Import Survey Data Menu

The CSV data must contain the station (distance along the cross section) as well as the vertical elevation of each survey point. These values must be in the same units as the datase into which the data are being imported. Moreover the elevation values must also use the same vertical datum as the database. Refer to the [database information(/Online_Help/File_Menu/#database-information) screen if you are unsure.

In the current version ofthe software, the columns in the text file must be separated by commas (not tabs etc). Strings should not be wrapped in quotes.

Note that when a database uses IDs to indentify cross sections, that the CSV file can only include cross sections that are already defined in the database. The CSV importer will fail if the CSV file contains cross section IDs that are not already defined in the current database.

Import Survey

Required Fields

The fields that are required in the CSV file depend on the way in which cross sections are defined in the current database:

CSV Column Data Type Cross Sections Idenfitied By ID Cross Sections Identified by River Distance Cross Sections Identified by Stationing
Cross Section ID Int64 Mandatory NA NA
River Distance Double NA Mandatory NA
River Station String NA NA Mandatory
Station Index Int64 Mandatory Mandatory Mandatory
Station Double Mandatory Mandatory Mandatory
Elevation Double Mandatory Mandatory Mandatory
Offset Double Optional Optional Optional
Easting Double Optional Optional Optional
Northing Double Optional Optional Optional
Survey Date DateTime Optional Optional Optional
Vertical Uncertainty Double Optional Optional Optional
Survey Point Code Text Optional Optional Optional

Cross Section ID

This is the integer identifier that uniquely identifies each cross section. The integers in the CSV must already exist in the database or an error will be reported. This column is not needed if the database identifies cross sections by river distance or stationing.

River Distance

This is the river distance of the cross section for which the survey points apply. Unlike with CrossSectionID, if a cross section at the specified river distance is not already defined in the database then a new cross section is defined using the river distance value from the CSV file.

River Station

This is the text label that defines each cross section. Each label in the CSV file must already be associated with a cross section defined in the database or an error will be reported.

Station Index

This integer defines the sequence of survey points along a cross section. Each survey point must have a unique integer value, but they need not start with 1 for each cross section.


This is the horizontal distance along the cross section for a particular cross section. The units must be the same as the elevation units defined in the cross section database. Refer to the database information screen if you are unsure.


The elevation of each survey point. The units and vertical datum must be the same as those defined in the database.


This optional value can be used to store the Euclidean distance of the surveyed point from the theoretical line that represents the monumented cross section.


This optional value can be used to store either the geographic (unprojected) longitude or the cartesian (projected) map easting of the survey point.


This optional value can be used to store either the geographic (unprojected) longitude or the cartesian (projected) map northing of the survey point.

Survey Date

This optional value can be used to store the date on which a cross section was surveyed. Note that the only the survey date of the first record for each cross section is stored. Subsequent survey dates are ignored. In other words, each cross section is assumed to be surveyed in its entirity on a single date. Use the survey date format property to define the way in which dates are represented in the CSV file. All dates MUST confirm with this format or an error will be reported.

Vertical Uncertainty

This optional value can be used to define the vertical uncertainty with each survey point. The main cross section plot can represent this value as error bars when it is present.

Survey Point Code

Include miscellaneous text pertaining to each point using the survey point code column. This can be used for point quality information or other descriptors such as “edge of water” etc. Be sure not to include any commas in the text! Currently this survey point codes do not appear anywhere in the software, but they are included in the cross section export when data are exported from the database.

Sample CSV File

The following is a sample CSV file for three cross sections on the Missour River near Kansas City, US.