STAR*NET V6 - Circe

More documents

Recommendations

Info

Chapter 5 Preparing Input Data INLINE OPTION: .ELLIPSE Station Names By default, when you run an adjustment with error propagation, error ellipses are generated at all stations. These ellipse ellipses will be shown in your listing and plot. But if you wish to show error ellipse information only for specific stations, include one or more “.ELLIPSE” inline options in your data file. Each line should contain one or more station names separated by commas or spaces. This allows you to generate error ellipse listing information and error ellipse plots only for critical stations in a network. #List of specific ellipses to show in listing and plot results .ELL 1 4 6 77 76 74 35 A202 A203 R60 .ELL A207 132 133 153 INLINE OPTION: .RELATIVE Connection List Specifications .PTOLERANCE Connection List Specifications By default, when you run an adjustment with error propagation, relative error ellipses are generated between all station pairs connected by observations, and output for these ellipses are shown in your listing and plot. Also, when the “Positional Tolerance Checking” feature in the Project Options/Special Settings dialog is selected, the same relative ellipses are used to create the tolerance checking report. But you may wish relative error ellipse information listed and plotted only between specific station pairs in the network (whether or not they are connected by observations). Likewise, you may wish Positional Tolerance Checking performed only between specific station pairs in the network. You can include one or more “.RELATIVE” and/or “.PTOLERANCE” inline option lines in your data file to create separate lists that control what output of each type is generated by the adjustment. Each line should contain one or more dash delimited station name pairs separated by commas or spaces. If you want either list to also contain all the station pairs connected by observations, add a “.REL” or “.PTOL” line with a single “/OBSERVATIONS” keyword. The example below illustrates creating two connection lists, one of each type. #List of connections for relative ellipse listing and plotting .REL 4-35 4-53 77-A203 133-134 133-138 124-152 124-155 .REL 125-160 155-170 156-174 .REL /OBS #List of connections for tolerance checking .PTOL 5-155 22-173 133-184 .PTOL /OBS 86
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
Page 1 and 2:
STAR*NET V6 Least Squares Survey Ad
Page 3 and 4:
TABLE OF CONTENTS Chapter 1 OVERVIE
Page 5:
10.9 Entering a Geoid Height and Ve
Page 8 and 9:
Chapter 1 Overview 4. Survey planni
Page 10 and 11:
Chapter 2 Installation 2.3 Starting
Page 12 and 13:
2.7 The Registry Chapter 2 Installa
Page 14 and 15:
3.3 The Menu System Chapter 3 Using
Page 16 and 17:
3.8 Checking the Error File Chapter
Page 18 and 19:
Chapter 3 Using STAR*NET 3.12 Displ
Page 20 and 21:
Chapter 4 Options 4.2 Changing Proj
Page 22 and 23:
Option Group: Units Chapter 4 Optio
Page 24 and 25:
General Options Chapter 4 Options T
Page 26 and 27:
Chapter 4 Options Option Group: Dis
Page 28 and 29:
Chapter 4 Options What standard err
Page 30 and 31:
Chapter 4 Options The default metho
Page 32 and 33:
Option Group: Adjusted Contents Cha
Page 34 and 35:
Other Files Options Chapter 4 Optio
Page 36 and 37:
Chapter 4 Options Creating a Ground
Page 38 and 39:
Special Options Chapter 4 Options T
Page 40 and 41:
4.5 Company Options Chapter 4 Optio
Page 42 and 43: Chapter 4 Options Note that any dat
Page 44 and 45: Chapter 4 Options When the Instrume
Page 46 and 47: Using the Input Data Files Dialog C
Page 48 and 49: Chapter 5 Preparing Input Data 5.5
Page 50 and 51: Station Names Chapter 5 Preparing I
Page 52 and 53: Chapter 5 Preparing Input Data Zeni
Page 54 and 55: Point Descriptors Chapter 5 Prepari
Page 56 and 57: Example 1: (2D Data) Chapter 5 Prep
Page 58 and 59: Chapter 5 Preparing Input Data The
Page 60 and 61: Chapter 5 Preparing Input Data SING
Page 62 and 63: The “V” Code: Vertical Observat
Page 64 and 65: Chapter 5 Preparing Input Data Samp
Page 66 and 67: Example 2: (2D Data) Chapter 5 Prep
Page 70 and 71: Chapter 5 Preparing Input Data TRAV
Page 72 and 73: Chapter 5 Preparing Input Data Exam
Page 74 and 75: The “TE” Code: Ending a Travers
Page 80 and 81: Chapter 5 Preparing Input Data LEVE
Page 82 and 83: Chapter 5 Preparing Input Data SIDE
Page 84 and 85: Chapter 5 Preparing Input Data Usin
Page 86 and 87: INLINE OPTION: .DELTA ON/OFF Chapte
Page 88 and 89: INLINE OPTION: .SCALE Value Chapter
Page 90 and 91: Chapter 5 Preparing Input Data INLI
Page 98 and 99: Chapter 5 Preparing Input Data Lega
Page 106 and 107: How do I weight observations? Chapt
Page 108 and 109: Chapter 5 Preparing Input Data 102
Page 110 and 111: Chapter 6 Running Adjustments The S
Page 112 and 113: 6.5 Preanalysis Chapter 6 Running A
Page 114 and 115: Chapter 6 Running Adjustments 108
Page 116 and 117: Chapter 7 Viewing and Printing Outp
Page 118 and 119: 7.4 Viewing the Error File Chapter
Page 124 and 125: Chapter 8 Analysis of Adjustment Ou
Page 142 and 143:
Chapter 8 Analysis of Adjustment Ou
Page 144 and 145:
To run the utility, follow these st
Page 146 and 147:
Chapter 9 Tools As discussed above,
Page 148 and 149:
Chapter 9 Tools A few words should
Page 150 and 151:
Chapter 9 Tools The settings select
Page 152 and 153:
Chapter 10 Adjustments in Grid Coor
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
APPENDIX A - TOUR OF THE STAR*NET P
Page 170 and 171:
Appendix A STAR*NET Tutorial Exampl
Page 172 and 173:
Appendix A STAR*NET Tutorial 4. Rev
Page 174 and 175:
Appendix A STAR*NET Tutorial 7. Fin
Page 176 and 177:
Appendix A STAR*NET Tutorial 12. To
Page 178 and 179:
Appendix A STAR*NET Tutorial Take a
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Appendix A STAR*NET Tutorial Before
Page 188 and 189:
Example 5: Resection Appendix A STA
Page 190 and 191:
Page 192 and 193:
Example 7: Preanalysis Appendix A S
Page 194 and 195:
188
Page 196 and 197:
Appendix B References 6. Mikhail, E
Page 198 and 199:
Appendix C Additional Technical Inf
Page 200 and 201:
Appendix C Additional Technical Inf
Page 202 and 203:
Appendix D Error and Warning Messag
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Data Lines, General Content Data Ty
Page 210 and 211:
Index Installation Installing, 3 Se
Page 212:
STARPLUS SOFTWARE, INC.
show all

STAR*NET V6 - Circe

Create successful ePaper yourself

Delete template?

Save as template?