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.
Appendix D Error and Warning Messages<br />
One or more points were found having ZERO elevation while running in<br />
non-local coordinate system. This may cause erroneous scaling! Check<br />
your entered elevations, or your project elevation if running 2D.<br />
When running adjustments in “grid” systems, all stations should have real elevations or<br />
at least a real project elevation when running in 2D. Check your elevations, or if running<br />
in 2D, check to make sure your “project elevation” is not set to zero - unless of course<br />
your project really is right at sea level.<br />
Only One Fixed Station and No Orientation Constraint<br />
If you have only one fixed station in the network, you should have at least one fixed<br />
azimuth or bearing to provide orientation. Sometimes a partially fixed bearing or azimuth<br />
(or a partially fixed station) will provide the orientation required to allow the network to<br />
successfully solve. Therefore this is only a warning, not necessarily an error.<br />
Only One Fixed XY Station and No Distances<br />
If you have only one fixed station in the network, you need at least one fixed distance to<br />
provide scale. Sometimes a partially fixed distance (or a partially fixed station) will<br />
provide the scale required to allow the network to successfully solve. Therefore this is<br />
only a warning, not necessarily an error<br />
Two Stations Have the Same 2D Estimated Coordinates<br />
An observation is found having its two ends defined by two stations that have the same<br />
approximate coordinates. <strong>STAR*NET</strong> changes the coordinates on one slightly (as long<br />
as it is not fixed) and continues processing.<br />
Vertical Observations Ignored in 2D Adj Using 3D Mode<br />
Any single observation “V” line entered as 3D data is ignored in a 2D adjustment. Also<br />
any elevation difference data value entered as 3D data on a “T”, “M”, “DM” or “DV”<br />
line is ignored in a 2D adjustment. The message is only published once upon the first<br />
encounter of a data line having the ignored data. This is not an error, only a reminder that<br />
some data entered by you is not being used for any purpose in the adjustment.<br />
200