STAR*NET V6 - Circe

APPENDIX D - ERROR AND WARNING MESSAGES
Error and warning messages published by STAR*NET are designed to help you diagnose
errors detected in your data or problems found while adjusting. Most of these messages
are written to the “PROJECT.ERR” file where “PROJECT” is the name of your job. To
view the errors, select Output>Errors, or press the Errors tool button.
Only a small portion of the possible error or warning messages are shown here. Most of
the messages such as “Input Data File Does Not Exist”, “Invalid File Name” or
“Previous Traverse Set Not Properly Ended” need no further explanation and are not
listed. Also, certain internal errors should never appear unless you have problems with
your computer system, possibly disk or memory problems. These also are not listed
below.
If you get an error message or warning that is not listed below and you do not understand
it, please call or email technical support at Starplus Software for assistance.
D.1 Errors
Below are a few commonly-seen error messages listed in alphabetical order. These are
errors which cause an adjustment to terminate and must be corrected before you can
successfully perform the adjustment.
Converting Coordinates Produced Invalid Latitude:
Converting Coordinates Produced Invalid Longitude:
When running “grid” jobs, the program converts back and forth between grid coordinates
and geographical positions (latitudes and longitudes) using published geodetic formulas.
If the conversion from coordinates to geographical positions generates calculated values
of latitude or longitude that are completely out of a reasonable range (i.e. latitudes
greater than 90 degrees), this error is posted and the processing is terminated.
One likely cause for this is that you have entered signs for longitudes inconsistent with
the “longitude sign convention” set in the Project Options/General Settings dialog. For
example, if you have the convention set for positive west longitudes, but enter a negative
longitude in your data, this may cause geodetic formulas to fail.
Another cause might be that, because of typing errors, you entered a grid coordinate
value in your data that is way off from coordinate values consistent with the selected grid
zone, or maybe they are entered in units different than units set for the project.
Therefore if this error occurs, make sure the correct grid coordinate system has been
selected, that signs of all input longitudes values have been entered using the sign
convention chosen for the project, and that all input coordinate values are correct for
your zone, and they are entered using correct units.
195