StarNet v6 manual - Engineering Surveyor
StarNet v6 manual - Engineering Surveyor
StarNet v6 manual - Engineering Surveyor
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Chapter 5 Preparing Input Data<br />
5.3 An Overview of STAR*NET Data Files<br />
STAR*NET input data files are relatively free in format. Generally, lines begin with a<br />
one or two character code identifying the type of data, followed by the station names and<br />
actual observations. These data elements do not have fixed positions on a line, but they<br />
must appear in the proper order.<br />
You may insert comment lines anywhere in the file using the “#” symbol. Anything<br />
following the “#” on a line is interpreted as a comment, and is ignored. We highly<br />
recommend that you add notes and comments to your data files documenting survey data,<br />
field conditions, or any unusual situations that may prove valuable later. To many users,<br />
comments added to their data files become part of an historical document.<br />
Input data files are standard text (ASCII) files that can be created with a text editor,<br />
either inside the STAR*NET program or external to the program.<br />
Data files might also be generated as output from some another program, such as a third<br />
party COGO program or a data collector routine. Starplus Software, for example,<br />
supplies several utility programs that convert raw data collector field files to files<br />
formatted for STAR*NET use. And certain large companies and public organizations<br />
have written their own data converter utilities based on the way their surveyors collect<br />
field data and how they wish to use that data in the STAR*NET program.<br />
Data lines may be up to 500 characters long.<br />
Blank lines can be placed anywhere in the file. You can use spaces and tabs to align the<br />
data items if you wish. Comments, beginning with “#” characters, can be freely entered,<br />
both as separate lines, and attached to the ends of data lines.<br />
5.4 Naming Data Files<br />
File dialogs have been designed in STAR*NET to expect, by default, that input data files<br />
will have a DAT extension. This is a descriptive extension which is very easy to<br />
distinguish from all other file types.<br />
However, the use of DAT as an extension is not required. For example, in the<br />
“Professional” edition, a GPS extension is used when adding GPS vector data to the data<br />
file list. Although it is recommended that observations be created in data files using the<br />
DAT extension so that you can use default file types built into the dialogs, any extension<br />
may be used as long as it is not one of the several reserved output file extensions<br />
automatically used by the program when creating output files.<br />
The following reserved extensions and should not be used for data files: PRJ, LST, PTS,<br />
POS, GND, DMP, ERR, SBF and DXF.<br />
45