Output Errors

• Output Error: Too Many Stations, Limit is 0

  Users may come across the following error message when running an adjustment: MicroSurvey STAR*NET-DEMO Error Log ERROR Too Many Stations Limit is 0 Processing Terminated Due to Errors.    This is bec...

• Output Error: Station * Outside of Geoid Model Boundary

  Sometimes STAR*NET will run and display the error message above (with the first observed station name in the place of the *.)  The content CAN be a little misleading. It COULD mean that all your input...

• Output Error: Geoid Grid Files Too Small to Contain Stations

  When adjusting a new project that uses a geoid you may see the error message:   Error -- Geoid Grid Files Too Small to Contain Stations   This error may mean that your coordinates are being computed c...

• Output Error: Station Incorrectly Connected to Network

  Below is an example of an error message that you might see when attempting to adjust or perform a data check on a network.  MicroSurvey STAR*NET-PRO Error Log ERROR Station Incorrectly Connected to Ne...

• Output Error: 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...

• Output Error: <Line: X> Missing or Invalid Coordinate Value

  When first trying to process your field data you may see a message like this: ERROR [Line: 4] Missing or Invalid Coordinate Value P R733 28-18-10.66188 81-26-28.82737 ! !  ****************************...

• "Buffer Overflow" when Adjusting your STAR*NET Network

  Occasionally users see the message Buffer Overflow in the Errors log when they attempt to run an adjustment. This can be caused by .dat files that have been saved using unicode encoding.  You can chan...