27.03.2013 Views

STAR*NET V6 - Circe

STAR*NET V6 - Circe

STAR*NET V6 - Circe

SHOW MORE
SHOW LESS

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

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Appendix C Additional Technical Information<br />

C.3 Datum Schemes for 2D and 3D “Local” Jobs<br />

In the Adjustment Options for the project, when you set the coordinate system to “Local”<br />

(i.e. you are not running a grid job), you must choose a Datum Scheme as discussed on<br />

page 17 in Chapter 4, “Options.” You can choose one of two schemes:<br />

1. Apply an Average Scale Factor: Whatever “Average Scale Factor” you choose is<br />

applied to the horizontal components of all distances and this becomes the basis for<br />

calculating the horizontal coordinates. Elevations of points are not considered in this<br />

scheme. If your project varies greatly in elevation, and you want horizontal<br />

coordinates calculated to a certain elevation (datum), it is up to you to change the<br />

scale factor of your job as needed using the “.SCALE” inline option.<br />

You might use this scheme in various parts for small, fairly flat projects. Entering a<br />

factor of 1.0 causes your coordinates to be calculated right at the elevation of your<br />

observations. Users sometimes choose this scheme to simulate a grid adjustment by<br />

entering a grid factor that is known for the project area.<br />

Even though this datum scheme doesn’t consider elevations, it is still important to<br />

enter a realistic “Avg. Project Elevation” for 2D jobs so that any entered 3D slope<br />

distances will be properly reduced to horizontal using curved-earth geometry!<br />

2. Reduce to a Common Elevation: Using this scheme, elevations of stations in the<br />

project are considered. Using curved-earth geometry (given earth radius with the<br />

divergence of verticals) plus elevations of the instrument and target points,<br />

horizontal distance components are factored up or down to a common elevation. One<br />

often-used reduction to a common datum is the reduction to Sea Level. For this you<br />

would enter 0.0 as your “Reduce to Common Elevation” value. However, you can<br />

enter any elevation, one above, below or right at your project.<br />

You would normally use this scheme for projects containing stations that vary<br />

considerably in elevation. This allows you to choose a consistent elevation datum at<br />

which all horizontal coordinates will be created whether it be sea level, an average<br />

project elevation or some other desired elevation.<br />

Using the “Reduce to a Common Elevation” datum scheme, the factor applied to the<br />

horizontal component of a distance observation is computed by:<br />

Factor = (R + Common Elevation) / (R + (ElevA + ElevB) / 2)<br />

Where: R is the given earth radius value<br />

Common Elevation is the given (desired) elevation datum<br />

ElevA + ElevB are the elevations at the ends of the distance observation<br />

Whichever datum scheme you choose, always enter horizontal “controlling” coordinates<br />

at the datum you selected. For example, if you choose to reduce to a “Sea Level”<br />

elevation during an adjustment, and you enter some fixed controlling coordinates, these<br />

coordinates must be sea level coordinates, not coordinates at your project elevation!<br />

192

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!