STAR*NET Errors Panel Reports: WARNING Network Has No Fixed XY Stations

Below is an example of a warning message that you might see when attempting to adjust or perform a data check on a network. 

MicroSurvey STAR*NET-PRO Error Log

WARNING Network Has No Fixed XY Stations  

WARNING Network Has No Fixed Z Stations  

ERROR Geometric Weakness Found During Solution  

Processing Terminated Due to Errors.

You might also see:

MicroSurvey STAR*NET-PRO Error Log

WARNING Only One Fixed Station and No Orientation Constraint 

ERROR Geometric Weakness Found During Solution  

Processing Terminated Due to Errors.

---

In general terms, this message, plus the comment that geometric weakness was found, is telling the user that there are not enough "Constraints" on the network.

Constraints:

In a conventional traverse STAR*NET requires that you input either two constrained points or one constrained point and one constrained direction.  Just like a regular traverse computation you need at least one known setup point and one known direction before you can compute the traverse.  STAR*NET can go one further step than a regular traverse computation because your second known point or direction does not have to be the backsight, it can be at any point in the network as long as the rest of the network ties in to it.  In a leveling network you require at least one constrained elevation.  In a vector network you require at least one constrained station.

How do I add Constraints to my Network?

Points and observations can be constrained by either using the "fixity" symbols "!" or by adding a numeric standard deviation to be applied to that observation.  Below are some examples:

C 1 100 100 10 !!! 'eg1

Point 1 has the N, and E coordinates and elevation "fixed"

P 2 45-32-12.543 123-31-53.592 100 !!* 'eg2

Point 2 has a latitude and longitude coordinates "fixed" and the elevation "floating"

C 3 100 100 10 .05 .05 .05 'eg3

Point 3 has the N, and E coordinates and elevation assigned as having a standard deviation of .05 distance units.  These coordinates will be treated as measurements and adjusted in the network.  If you do not have any fixed coordinates in your network you will still see the message that there are no fixed coordinates, but if there is no message about geometric weakness there is no problem with your input, you can just treat this message as a warning.  Perform all other checks for adjustment integrity as required.