STAR*NET V6 - Circe
STAR*NET V6 - Circe
STAR*NET V6 - Circe
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Example 1:<br />
E 301 982.53<br />
Chapter 5 Preparing Input Data<br />
Station “301” is assigned an elevation of 982.53. No standard error values or fixity<br />
symbol is entered, so the elevation will be assumed completely free to be adjusted.<br />
Example 2:<br />
E 302 845.25 ! ‘Benchmark 105<br />
Station “302” is assigned an elevation of 845.25. This elevation will be held fixed.<br />
Example 3:<br />
E Doug 1256.5 0.015 ‘GPS E007<br />
An elevation for “Doug” is entered with a given standard error. The elevation will be<br />
considered an observation. It will be counted in the statistics and will show up in the<br />
“Adjusted Observations and Residuals” section of the output adjustment listing file.<br />
Using “CH”, “PH” and “EH” Codes: Specifying Ellipsoid Heights<br />
This entry is for 3D grid data:<br />
CH Station North East Ellipsoid Height [Std Errors]<br />
This data type causes the entered elevation value to be taken as an ellipsoid height rather<br />
than an orthometric elevation. The data format is identical to the “C”, “P” and “E”<br />
formats, except the appended “H” causes the alternate interpretation of the elevation<br />
value. This data type is particularly useful in the <strong>STAR*NET</strong>-PRO edition where<br />
ellipsoids heights are commonly used in networks containing GPS vectors.<br />
Example:<br />
PH 335 33-22-44.123 120-24-41.122 835.32 ! ! ! ‘GPS BM335<br />
Point “335” has given latitude and longitude values, plus an ellipsoid height of 835.32.<br />
See Chapter 10, “Adjustments in Grid Coordinate Systems” for more details on grid<br />
systems, and the use of ellipsoids heights and orthometric elevations.<br />
53