STAR*NET V6 - Circe

Chapter 5 Preparing Input Data
When building “Relative” and “Positional Tolerance Checking” lists, the methods shown
in the previous example are usually all you need. However, the “/CONNECT” keyword
is available to provide an additional method for generating connection lists.
Use the “/CONNECT” keyword to specify a list of station names that you want the
program to exhaustively create connections between. In the data below, connections are
created exhaustively between all 10 points for a “positional tolerance checking” list.
These two lines will create a total of 45 connections: 51-52, 51-55, 51-60, 51-65, etc.
.PTOL /CON 51 52 55 60 65 66 71 #Total 10 points
.PTOL /CON 43 43 47
Use the “/CONNECT=GroupName” keyword when you want the program to
exhaustively create connections in separately named groups. A group name, just like a
point name, can be up to 15 characters. In the data below, connections are created by
exhaustively connecting points separately in each group.
.PTOL /CON=North 71 72 78 81 82 #Total 7 point in group North
.PROL /CON=North 81 85
.PTOL /CON=South 127 155 164 #Total 4 points in Group South
.REL /CON=South 177
Note that a “named” connection group can be shared by both types of lists. So in the case
of the last two lines above, both the “positional tolerance checking” and the “relative”
lists will have connections added by exhaustively connecting 4 points. To keep named
connection groups unique between the two lists, simply use unique group names.
You can use any combination of the techniques shown to create a “Relative” or a
“PTolerance” list of connections. Connections created by all techniques are simply
combined into a single list. Any duplicated connections are ignored.
For small networks, you may wish to create a connection between “every” point in your
project rather than using the techniques above. Simply use the “/EVERY” keyword. The
example below creates a “Relative” list containing every connection.
.REL /EVERY #Creates an exhaustive list connecting every point
Caution – The “/EVERY” keyword causes matrix operations performed during an
adjustment to become more laborious, and in a large network, processing time can
increase dramatically! This keyword is not generally useful for typical survey work. It is
particularly useful for specialized projects such as deformation studies where complete
covariance information is required for additional analysis. “/EVERY” provides the
means to compute a full covariance matrix which can be exported by the “Dump File”
facility described in the “Other Files” project options settings.
87