How does Closure work?
Closure is designed to do most of the misclosure checking work
automatically! Simply select your survey data file, and define the lines
you want to check for large misclosures, and let this tool do the rest.
You can limit the closure calculations to selected measurement types and
you can even prioritize them.
Closure Features Summary
Closure has the following powerful features to make the calculation and
viewing of closures easy for you:
- There are no limitations on the number of points or measurements in a traverse or network.
- You can calculate vertical, horizontal, and 3D
misclosures.
- You can easily import traverse or network data
from any file format handled by GeoLab.
- You can load GeoLab IOB files directly.
- You can easily create line definitions for
misclosure calculations using a built-in Lines Editor.
- The Lines Editor will automatically scan your
network input file and create lines and closed loops for you with
the click of a button.
- It's easy to save closure reports as text files,
and you can print them too.
- You can easily select the measurement types you
wish to limit the closure calculations to, and you can even
prioritize them simply by moving them up or down in a list.
- All GeoLab capabilities are automatic when
loading your traverse or network data in GeoLab's IOB format,
including automatic coordinate generation, and geoid file loading.
- And much more!
The Closure Lines Editor
The Lines Editor is a dialog that helps you create and edit the
"lines files" used by Microsearch Closure. A "lines file" is a
specially-formatted (see below) simple text file that contains
definitions of the lines you wish to use in computing closures.
Note that Closure can generate most of the lines information you
will need, but you can also manually edit those definitions to
handle your specific needs.
Please click the Lines Editor image on the right to see a larger
screenshot.
|
 |
Understanding the Lines File Format
A "lines file" is a simple text file used by Microsearch Closure to save
line definitions in. A line is defined completely by a set of point
(station) names.
Note that the Lines Editor can be used to create and edit lines files,
so it is never really necessary to manually edit them directly. The
details of the format for these files is given here for completeness
only.
A lines file is in a special CSV (Comma-Separated Variables) text
format. All lines must be no longer than a maximum of 8192 characters.
All blank lines, and all lines beginning with a semicolon (';')
character are ignored. Other lines in a lines file are as follows:
"LINE START","LineName"
This line must always be used to start defining a new line, and
specifies the name of the line to be defined by lines following this
line.
"LINE","Point name 1","Point name 2", ... "Point name n"
Any number of lines of this form are used to define the point names for
the line, and must be found after a "LINE START" line and before a "LINE
END" (see below) line. Note that the maximum number of characters per
line is 8192, so if all the point names for a line will not fit on one
line, multiple lines must be used (see the example below).
"LINE END"
This line must always be used to end the definition of a line, and must
be preceded by a "LINE START" line and one or more "LINE" lines.
Example Lines File
The following lines give an example of the lines in a valid lines file:
"LINE START","L1"
"LINE","P1","P2","P3"
"LINE","P4","P5","P6","P7"
"LINE END"
"LINE START","L2"
"LINE","A1001","A1002","A1005"
"LINE","A1020","A1021","A1032","A1099"
"LINE END"
|
