27.03.2013 Views

STAR*NET V6 - Circe

STAR*NET V6 - Circe

STAR*NET V6 - Circe

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Point Descriptors<br />

Chapter 5 Preparing Input Data<br />

A point descriptor, if entered, is always the last item on a data line. A descriptor may be<br />

assigned to any station. A descriptor is prefixed by a single or double quote character and<br />

can be up to 48 characters in length. Descriptors can be entered on Coordinate or<br />

Elevation data lines, Geodetic Positions data lines, or any kind of observation data line.<br />

For Traverse lines, the descriptor is assigned to the “AT” station name. For all other<br />

kinds of observation lines, the descriptor is assigned to the “TO” station name. Once a<br />

descriptor has been assigned to a network station, any subsequent descriptor entered for<br />

the same station will be ignored. Point descriptors are written to the output coordinate<br />

file as well as the listing file. Examples:<br />

C 4 5644.445 6645.526 ! ! 'Jones & Taylor<br />

M 2-1-6 38-24-76 963.672 'Descriptor for Sta6<br />

D 2-7 2044.334 'Descriptor for Sta7<br />

Providing Approximate Coordinates<br />

For a least squares adjustment to work, approximate coordinates (and elevations if you<br />

are running a 3D adjustment) must exist for all adjustable stations in a network.<br />

Fortunately, <strong>STAR*NET</strong> has the ability to look through your data and figure out the<br />

approximate coordinates and elevations based on the actual angle, distance and vertical<br />

observations present in the data file. They are automatically computed using a variety of<br />

methods including angle-angle intersection, and angle-distance computation.<br />

Often, however, you will have to enter approximate coordinates for a station or two to<br />

help <strong>STAR*NET</strong> get started calculating other approximate coordinates. For example, in<br />

the first sample project in the tutorial, we gave approximate coordinates for the first<br />

traverse backsight point. <strong>STAR*NET</strong> will tell you when it can’t compute coordinates by<br />

posting a message in the error file.<br />

When a network has a full compliment of entered angles and distances, simply providing<br />

fixed or approximate coordinates for some station directly adjacent to another station<br />

having known coordinates (or supplying a fixed or approximate bearing or azimuth<br />

adjacent to another station in the network having known coordinates) is normally all that<br />

is required to allow <strong>STAR*NET</strong> to complete the job of computing the remaining<br />

approximate coordinates.<br />

Some networks will require you to provide coordinates for many or all of the stations. In<br />

the case of a pure trilateration project (distances only) for example, you would have to<br />

supply approximate coordinates for all points since <strong>STAR*NET</strong> is not be able to<br />

determine coordinates from distances alone.<br />

48

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

Saved successfully!

Ooh no, something went wrong!