STAR*NET V6 - Circe

More documents

Recommendations

Info

Chapter 5 Preparing Input Data Using Inline Options The inline option is a very powerful feature in the <strong>STAR*NET</strong> program. Using inline options allow you control many aspects of your data. For example, if units setting on your Project Options is set to meters, the program will output results in meters, and it will also expect input data to be entered in meters. But if part of your observations are measured in feet, perhaps supplied to you by another surveyor, you can simply use the “.UNITS” inline to tell the program that those observations are in feet. The program does the conversion to meters automatically! Example use of the “.UNITS” inline option to change units of input data: # Default units are FeetUS as set in the Project Options M 24-23-25 68-33-44.5 655.678 #Data in FeetUS .UNITS Meters M 26-25-27 98-45-55.4 201.335 #Data in Meters M 27-26-28 79-33-24.3 194.667 .UNITS FeetUS #Resets to FeetUS M 32-27-55 87-43-52.1 702.345 etc... The following are a few rules for constructing inline options: 1. An inline option begins with a period “.” and is directly followed by the option name in either upper or lower case. (Examples: .UNITS or .units) 2. An option name may be abbreviated to as little as one character, however sufficient characters must be supplied to differentiate it from other options beginning with the same letters. (Examples: .UNITS or .U, .DATA or .DA, .DELTA or .DE) 3. Most inlines contain parameters which turn an option ON or OFF, toggle a setting one way or another, or change a value. The same rules apply to parameter names as with option names. They may also be upper or lower case, and be abbreviated to as little as one character as long as they are unique. (Examples: ON or OF) Even though you can abbreviate option and parameters names, it is recommended, that you spell out enough of the identifier names so that you and others reading your data files can easily recognize the meanings of the options. Data for a project may consist of one or more data files. Inline options entered in one data file do not affect subsequent files. As each file is read during an adjustment, all options that affect data are reset to the project defaults for the next file. For example, if you use the “.REF” inline to change the refraction index in one file, it will be automatically reset to the Project Options default value for the next file. 78
Chapter 5 Preparing Input Data Inline Options that Relate to Settings in Options Dialogs The following inline options allow you to override certain Project Options default settings that affect the interpretation of your entered data. INLINE OPTION: .UNITS [Linear] [Angular] [StdErr] By default, input data must be in the units specified in the Project Options. This inline option, however, allows you designate the units in data lines that follow. You can specify linear units, angular units, or both. This option, for example, allows you to easily mix meters and feet in the same data file. Knowing the units, the program will convert data to the default units set in the Project Options with no work on your part. The “Linear” keyword may be any item from the dropdown list of the “Linear Units” field in the Project Options/Adjustment dialog. And the “Angular” keyword may be either “DMS” or “GONS.” .UNITS FeetUS #Changes linear units for following data .UNITS DMS #Changes angular units for following data .UNITS Meters GONS #Changes both linear and angular units .UNITS #Resets all units to project defaults In addition, the “.UNITS” inline can be used to redefine the units of explicitly-entered standard error values when angular data is being entered in GONS. In this <strong>STAR*NET</strong> version, standard errors for angular data entered in GONS are stated as Milligons (GONS/1000) by default rather than Centesimal Seconds (GONS/10,000) as in earlier versions. This change to the program was made by popular demand from the international surveying community. If you have existing data files that contain explicitly entered standard errors stated as Centesimal Seconds, you can do one of two things: either edit your files changing all these entered standard error values to Milligons, or simply use the “.UNITS” inline with the “CSECONDS” keyword to indicate the units of following data lines, and let the program make the necessary conversions to Milligons. The “MGONS” keyword is also provided to change back the to the Milligons default in the same file if necessary. .UNITS CSeconds #Units for angular std errors following .UNITS Mgons #Units for angular std errors following .UNITS Met Gons CSec #Changing several on a single line .UNITS #Resets all units to project defaults Note that the “CSECONDS” units keyword is also useful for those using GONS who still prefer to enter explicit standard errors in their data as Centesimal Seconds. 79
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 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 134 and 135:
Chapter 8 Analysis of Adjustment Ou
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
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?