View Imported Level Data in Project Explorer

Each imported or keyed-in level data file displays as an expandable node located beneath the Imported Files node in Project Explorer (select Project Explorer in Home > Data). The way level data is displayed beneath the level data file node depends on whether the Allow Network Adjustment or Prevent Further Adjustment option was selected in the Level Editor dialog.

For the following examples, assume the file being imported is named "test.dat" and contains one level run. The run began on BM1 and ended on BM2. In addition to the benchmarks, the surveyor specified three control points: 1, 2, and 100. The survey went in the direction of 1 toward 2 with 100 as an IS point between 1 and 2.

Note: You can right-click the Imported Files node in the Project Explorer and select to sort the imported files either by their name or by the order in which they were imported, providing two options to more easily locate any imported file.

Example 1: Allow Network Adjustment option selected in Level Editor dialog

This option should have been selected if you want all elevations of interest to be left as delta elevation observations and, therefore, adjusted as part of a network adjustment. The data would display in Project Explorer as follows:

Node type example	Description
Imported Files	This is the Imported Files node.
Test.dat or Keyed-In File	This is an imported leveling data file. The icon is followed by the name of the file. This is a keyed-in leveling data file. The icon is followed by the name "Keyed-In File." A project can include only one Keyed-In File node.
BM1	This is a coordinate node from a benchmark. The icon is followed by a coordinate point ID. To preserve the integrity of raw field data, you cannot edit coordinate properties for an imported coordinate.
BM2	This is a coordinate node from a benchmark.
BM1-BM2 (H1)	This is a run node. The icon is followed by the run's first coordinate point ID, a dash, and the last coordinate point ID. This is followed by an "H" number in parenthesis that identifies the run. Observation nodes are nested beneath it in chronological order. The data file can include multiple run nodes.
BM1-1 (E1)	This is a delta elevation observation node, which represents the change of elevation between two control points. The icon is followed by the backsight point ID, a dash, and the foresight or side shot point ID. This is followed by an "E" number in parenthesis that identifies the observation.
1-100 (E2)	This is a delta elevation observation node.
1-2 (E3)	This is a delta elevation observation node.
2-BM2 (E4)	This is a delta elevation observation node.

Example 2: Prevent Further Adjustment option selected in Level Editor dialog

This option should have been selected if you want all elevations of interest to be converted from delta elevation observations into coordinates and, therefore, not adjusted as part of a network adjustment. The data would display in Project Explorer as follows:

Node type example	Description
Imported Files	This is the Imported Files node.
Test.dat or Keyed-In File	This is an imported leveling data file. The icon is followed by the name of the file. This is a keyed-in leveling data file. The icon is followed by the name "Keyed-In File." A project can include only one Keyed-In File node.
BM1	This is a coordinate node from a benchmark. The icon is followed by a coordinate point ID. Note: To preserve the integrity of raw field data, you cannot edit coordinate properties for an imported coordinate.
BM2	This is a coordinate node from a benchmark.
BM1-BM2 (H1)	This is a run node. The icon is followed by the run's first coordinate point ID, a dash, and the last coordinate point ID. This is followed by an "H" number in parenthesis that identifies the run. Observation nodes are nested beneath it in chronological order. The data file can include multiple run nodes.
1	This is a coordinate node from an adjustment. The icon is followed by the point ID.
100	This is a coordinate node from an adjustment.
2	This is a coordinate node from an adjustment.