Note on Level Runs Without Benchmarks

If a level data file you are importing includes a level run that does not include a benchmark, the software will attempt to use a computed value for the first point in that run. It does this by locating the most recent point ID in a preceding run that matches the first point ID in the run that is missing a benchmark. If it finds a matching point ID, it copies the elevation from that point to the first point ID in the run that is missing a benchmark as a computed elevation.

For example, if the first point ID in the run that is missing a benchmark is 100, and the most recent previous instance of a point ID of 100 is found at the end of the preceding run, the elevation for point 100 in the preceding run is copied to the elevation for point 100 in the run that is missing a benchmark as a "Computed" value. In this case, you may not need to merge the runs.