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.
Chapter 9 Tools<br />
By default, the precisions used (number of places beyond the decimal) for coordinates<br />
and elevations are controlled by the “Default Precisions” settings existing in the Project<br />
Options/Other Files dialog when the adjustment was last run. However, you can define a<br />
different precision if you wish. To specify two places beyond the decimal for a northing<br />
definition for example, “N0.2” would be entered rather than just an “N” definition. Or<br />
perhaps you want elevations rounded to the nearest foot or meter written to your<br />
converted file. Just enter is “Z0.0” rather than the normal “Z” definition. The example<br />
illustrates defining coordinates exported to two places and elevations to one place.<br />
p n0.2 e0.2 z0.1<br />
If you want your output items formatted in columns rather than separated by only a space<br />
or comma, do this by appending a “field width” to each definition character. For<br />
example, if you want your point names, northings, eastings and elevations lined up in<br />
column widths of 10, 15, 15 and 9 spaces respectively, and using default precisions, you<br />
would enter either of the following format definitions:<br />
p10n15e15z9 (using the actual column width value)<br />
p10 n14 e14 z8 (or a space plus the remaining width)<br />
You can use this field width value with the P (or R), N, E, H and Z definition codes.<br />
When you use a field width with the “P” point name code, the name string will be left<br />
justified in the field width. When you use a field width with the alternate “R” point name<br />
code, the name string will be right justified in the field. Northings, eastings and<br />
elevations, when defined with a field width value, are always right justified.<br />
When using field width values for northings, eastings and elevations as shown above, the<br />
decimal precision is controlled by the “Default Precisions” settings existing in the<br />
Project Options/Other Files dialog when the adjustment was last run. However, as<br />
previously described, you can also enter explicit precisions. Simply attach the desired<br />
precision to the field width. If we want a 3 place precision for northings and eastings,<br />
and 1 place for elevations, the example lines above would look like this:<br />
p10n15.3e15.3z9.1 (using actual column width value)<br />
p10 n14.3 e14.3 z8.1 (or a space plus remaining width value)<br />
It is recommended that you actually use a space separation between defined column<br />
widths as shown in the last line above. First, the definition is much easier to read. But<br />
more importantly, if for one reason or another a coordinate value is large enough to fill<br />
the entire field width, the space in the format definition is guaranteed to create a space in<br />
the output rather than allowing the output values to run together.<br />
141