STAR*NET V6 - Circe

More documents

Recommendations

Info

Chapter 9 Tools As discussed above, the portion of each line to the right of the second “:” is the formatting definition and is made up of a combination of special characters that tells <strong>STAR*NET</strong> how to format the new points. Only certain characters may be used in this formatting definition. Each character has a special purpose. A list of all formatting characters and the purpose of each is listed in the table below. This: Causes this action: P or R Point Name is written (left or right justified in a field when a field width is entered, i.e. P15). N Northing is written. E Easting will be written. H When project options coordinate order is set to “NE”, the first occurrence of an “H” writes a Northing, the second writes an Easting. The order is switched when the option is “EN”. Z Elevation is written. D Descriptor is written. Comma A comma is written. Space A space is written. Single Quote A single quote character (') is written. Double Quote A double quote character (") is written. Brackets [ ] Text between the [ and the ] is written. Slash ( / ) A new line (carriage return) is written. Reformatting Characters These formatting characters may be entered as upper or lower case, and of course in any order - the order you wish your data items to appear in the reformatted points file. If any characters other than those in the list above are entered (except for the text entered between the special square bracket characters), an error message “Invalid Definition Style” will be shown when the reformatter routine is used, and you will have to make a correction to the STAR6.FMT file before the routine will work. Every formatted line written to the output file is automatically ended with a new line (carriage return). However with the special “/” slash character available as shown in the list above, you can cause new lines to be inserted anywhere. Perhaps you would like one or more items on a separate line. Simply use the slash rather than a space or comma separator, and a carriage return will be inserted. 140
Chapter 9 Tools By default, the precisions used (number of places beyond the decimal) for coordinates and elevations are controlled by the “Default Precisions” settings existing in the Project Options/Other Files dialog when the adjustment was last run. However, you can define a different precision if you wish. To specify two places beyond the decimal for a northing definition for example, “N0.2” would be entered rather than just an “N” definition. Or perhaps you want elevations rounded to the nearest foot or meter written to your converted file. Just enter is “Z0.0” rather than the normal “Z” definition. The example illustrates defining coordinates exported to two places and elevations to one place. p n0.2 e0.2 z0.1 If you want your output items formatted in columns rather than separated by only a space or comma, do this by appending a “field width” to each definition character. For example, if you want your point names, northings, eastings and elevations lined up in column widths of 10, 15, 15 and 9 spaces respectively, and using default precisions, you would enter either of the following format definitions: p10n15e15z9 (using the actual column width value) p10 n14 e14 z8 (or a space plus the remaining width) You can use this field width value with the P (or R), N, E, H and Z definition codes. When you use a field width with the “P” point name code, the name string will be left justified in the field width. When you use a field width with the alternate “R” point name code, the name string will be right justified in the field. Northings, eastings and elevations, when defined with a field width value, are always right justified. When using field width values for northings, eastings and elevations as shown above, the decimal precision is controlled by the “Default Precisions” settings existing in the Project Options/Other Files dialog when the adjustment was last run. However, as previously described, you can also enter explicit precisions. Simply attach the desired precision to the field width. If we want a 3 place precision for northings and eastings, and 1 place for elevations, the example lines above would look like this: p10n15.3e15.3z9.1 (using actual column width value) p10 n14.3 e14.3 z8.1 (or a space plus remaining width value) It is recommended that you actually use a space separation between defined column widths as shown in the last line above. First, the definition is much easier to read. But more importantly, if for one reason or another a coordinate value is large enough to fill the entire field width, the space in the format definition is guaranteed to create a space in the output rather than allowing the output values to run together. 141
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 68 and 69:
Chapter 5 Preparing Input Data The
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 76 and 77:
Page 78 and 79:
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 92 and 93:
Page 94 and 95:
Page 96 and 97: Chapter 5 Preparing Input Data INLI
Page 98 and 99: Chapter 5 Preparing Input Data Lega
Page 100 and 101: Chapter 5 Preparing Input Data The
Page 102 and 103: Chapter 5 Preparing Input Data 5.9
Page 104 and 105: Chapter 5 Preparing Input Data 5.11
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 144 and 145: To run the utility, follow these st
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 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 186 and 187: Appendix A STAR*NET Tutorial Before
Page 188 and 189: Example 5: Resection Appendix A STA
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?