Station errors table
Basic concepts
The station errors table is an optional table inside the survey database that allows you to set up a Quality Assurance regime for new stations entering the survey database. You can create rules to determine the order or "quality" of a station (including giving INFORMATIONAL, WARNING or ERROR messages when new stations are created). The system also allows station orders to be propagated, as the particular station is used as a fixed station to calculate a new station, eg if the backsight and setup are both 2nd order then the foresight cannot be created as a new station with an accuracy greater than 2nd order.
The basic concept is that each station is assigned an order value (eg "1st", "2nd", "3rd" etc) which is stored in the station_order field for that station in the survey_stations table in the survey database. The purpose of the station errors table is to allow you to set up very flexible rules to determine how the order value will be assigned for a new station. The station errors table then "watches" all Surpac applications that create new stations, and assigns appropriate new station orders and displays INFORMATIONAL, WARNING or ERROR messages to the user as required. If no station errors table is present in the survey database then all applications proceed exactly as they used to and the station_order field in the survey_stations table is simply not used.
Benefits
The main benefit of using this system is that it gives the Senior Surveyor a lot of control in setting rules to govern the quality of stations entering the survey database. By associating a station order with each new station there is a quantifiable measure of the "quality" of each of the stations in the database. This is useful for audit purposes. The system is very flexible and covers each application function in Surpac that creates new stations.
Features of the system
- You can choose order names from a pre-defined picklist ("1st", "2nd", "3rd", "4th", "5th"), or you can make your own names for the orders.
- You can choose different actions to assign to the orders:
- CONTINUE Where the station is inserted into the database with no additional feedback to the user.
- INFORMATIONAL Where (in general) a text box with information on the new station order is displayed with an "OK" button to insert the station into the database.
- WARNING Where (in general) a text box with information on the new station order is displayed with an "OK" button to insert the station into the database and a "CANCEL" button to not insert the station into the database.
- ERROR Where (in general) a text box with information on the new station order is displayed with an "OK" button to not insert the station into the database.
- You have the option of setting up different "instruments" for which distinct sub-sets of rules apply. For example you can set up different rules for "LEICA1101" or "LEICA1103" instruments. Each Surpac function that creates new stations has a new form-field with a pick list which allows you to choose which instrument you are using for that function. You have total flexibility in defining the instrument names and the rule sub-sets for each instrument.
- You can set up station order rules based on:
- Standard deviations for measured horizontal and vertical angles and slope distances; or standard deviations of station coords for resected or survey network adjusted stations. The lower these standard deviations are the more likely you are to have an accurate result.
- Numbers of measured observations. The higher the number of observations, the more trustworthy the result.
- Distance from the setup station to the foresight station (for horizontal and vertical angle and measurements only). It might be the case that an angle measurement error is "large" but because the distance from the setup station to the foresight station is "small" the error does not have a large opportunity to propagate, therefore the new station can still be "accurate". This might be the case in an underground situation with short lines of sight. These values allow you model this situation.
- The use of the station errors table is optional. If no station errors table is present in the survey database then all applications proceed exactly as they used to and the station_order field in the survey_stations table is simply not used. However, if a station errors table is present then it will be used. Individual users of the database cannot switch the use of the table on and off as they please. This ensures the integrity of your survey_stations table.
NOTE: As stated earlier, this system supports the propagation of station order values as the station is used as a fixed (eg as a backsight or setup etc) station in the creation of new stations. As a consequence of this it is required that any existing stations in the database that you wish to use for this purpose, must have an order value in their station_order field that is defined in the station_errors table. This is a necessary condition, as the station errors table has to "know" the accuracy of all the fixed stations it is using before it can use them to determine the accuracy of a new station. You will find that if you try to use fixed stations in your database where the order value is unknown to the station errors table, then you will receive warning messages to this effect. This may mean you have to edit some of your historical stations in your database and manually assign them a station_order value before they can be used.
The station errors table is only used when you are creating new stations, if you are just doing a standard pickup and surveying points into a string file then this will work exactly as it did previously (and, for example, the backsight and setup stations you define won't have to have station_order values that are known in the station errors table).
If you have a survey database that doesn't have a station errors table and you want to create one, just go to Survey Survey database Administration - Create station errors table. If you have a survey database that has a station errors table and you want to delete the station errors table, go to Survey - Survey database - Administration - Delete table and select the station errors table.
Technical aspects
There are four generic situations where a station can be created or adjusted in Surpac. These situations each have slightly different values that give the best measurement of the quality of the new station produced. You can set up rules to determine the new station order for each of these four situations. The four cases are:
- Creating a station by a standard pickup
- Creating a station by resection
- Adjusting a station by a 3D survey network adjustment
- Adjusting a station by a 2D survey network adjustment
These four cases are discussed individually below:
Creating a station by a standard pickup
This case corresponds to the situation involving a backsight station, a setup station and a foresight station (which becomes the new station). Here one or more of each of the following measurements are made to determine the new station:
- horizontal angle measurements
- vertical angle measurements
- slope distance measurements
For this situation you can set up rules for the new station order based on:
- The standard deviation of the horizontal angle measurements. The rule
in this case is based on:
- The value of the standard deviation
- The number of horizontal angle measurements taken
- The horizontal distance between the setup and foresight stations. It might be the case that a horizontal angle standard deviation is "large" but because the horizontal distance from the setup station to the foresight station is "small" the error does not have a large opportunity to propagate, therefore the new station can still be "accurate". This might be the case in an underground situation with short lines of sight. Entering this value allows you model this situation.
- The standard deviation of the vertical angle measurements. The rule
in this case is based on:
- The value of the standard deviation
- The number of vertical angle measurements taken
- The slope distance between the setup and foresight stations. It might be the case that a vertical angle standard deviation is "large" but because the slope distance from the setup station to the foresight station is "small" the error does not have a large opportunity to propagate, therefore the new station can still be "accurate". This might be the case in an underground situation with short lines of sight. Entering this value allows you model this situation.
- The standard deviation of the slope distance measurements. The rule
in this case is based on:
- The value of the standard deviation
- The number of slope distance measurements taken
It may be the case that you only have one measurement for the horizontal angle and/or the vertical angle and/or the slope distance. If you only have one estimate for a value then you cannot determine a standard deviation for that value. The station errors table accounts for this by allowing you set rules so that instead of basing the order on all three standard deviations, you can just base the order on the standard deviations that can be determined. Alternatively it allows you to set default station order values in this case.
In general the station orders table calculates orders corresponding to the standard deviations (where they exist) of each of the horizontal angle, vertical angle and slope distance measurements and then compares these orders with the orders of the backsight and setup stations. The new station order is then assigned to be the lowest ranking of all these orders. For example, if the backsight and setup stations were "2nd" order and the station errors table determined the standard deviation of the horizontal angle measurements to be "1st" order, the standard deviation of the vertical angle measurements to be "1st" order, and the standard deviation of the slope distance measurements to be "2nd" order, then the new station order would be "2nd" ie the lowest ranking of all these five orders.
The following situations in Surpac where new stations are created correspond to the generic "creating a station by a standard pickup" case:
- Data recorder single face pointings to new stations
- Data recorder multiface pointings to new stations
- Surface traversing
- Underground traversing
- EDM survey
- Stadia survey
- Two wire stadia survey
- RDS survey
Creating a station by resection
For this situation you can set up rules for the new station order based on:
- The value of the x coord standard deviation of the new station
- The value of the y coord standard deviation of the new station
- The value of the z coord standard deviation of the new station
- The number of stations to which resection observations where made (Note: This is the same irrespective of whether you have done a single face or double face resection, eg if you have done a single face resection to three stations or a double face resection to three stations, "the number of stations to which resection observations where made" is still three.)
In general the station orders table calculates orders corresponding to the standard deviations of each of the x, y and z new station coords and then compares these orders with the orders of all the fixed stations in the resection. The new station order is then assigned to be the lowest ranking order of all these orders. For example, if the lowest ranking order of all the fixed stations in the resection was "2nd" and the station errors table determined the standard deviation x station coord to be "1st" order, the standard deviation of the y station coord to be "1st" order, and the standard deviation of the z station coord to be "2nd" order, then the new station order would be "2nd" ie the lowest ranking of all these orders.
Adjusting a station by a 3D survey network adjustment
For this situation you can set up rules for the new station order based on:
- The value of the x coord standard deviation of the new station
- The value of the y coord standard deviation of the new station
- The value of the z coord standard deviation of the new station
- The total number of direction, distance, horizontal angle and vertical angle observations that involved that station as a backsight, setup or foresight
In general the station orders table calculates orders corresponding to the standard deviations of each of the x, y and z adjusted station coords and then compares these orders with the orders of all the fixed stations in the adjustment. The new station order is then assigned to be the lowest ranking order of all these orders. For example, if the lowest ranking order of all the fixed stations in the adjustment was "2nd" and the station errors table determined the standard deviation x station coord to be "1st" order, the standard deviation of the y station coord to be "1st" order, and the standard deviation of the z station coord to be "2nd" order, then the new station order would be "2nd" ie the lowest ranking of all these orders.
Adjusting a station by a 2D survey network adjustment
For this situation you can set up rules for the new station order based on:
- The value of the x coord standard deviation of the new station
- The value of the y coord standard deviation of the new station
- The total number of direction, distance and horizontal angle observations that involved that station as a backsight, setup or foresight
In general the station orders table calculates orders corresponding to the standard deviations of each of the x and y adjusted station coords and then compares these orders with the orders of all the fixed stations in the adjustment. The new station order is then assigned to be the lowest ranking order of all these orders. For example, if the lowest ranking order of all the fixed stations in the adjustment was "2nd" and the station errors table determined the standard deviation x station coord to be "1st" order and the standard deviation of the y station coord to be "2nd" order, then the new station order would be "2nd" ie the lowest ranking of all these orders.
Edit station errors
This function allows you to edit the station errors table. The station errors table should only be edited by the Senior Surveyor, or the person in control of quality assurance for the survey database. For explanatory information on the station errors table see here.
To run this function: Choose Survey > Station errors > Edit, or...
The Orders and definitions section on the Edit station orders form allows you to set up the rules for the various station orders in the table:
Each row in this table has 10 fields:
order
Enter the station order value that is described by this row in the table. You can choose a value from the pre-determined list in the pick-list (that is, "1st", "2nd", "3rd", "4th", "5th"), or you can enter your own value. The way Surpac recognizes one order value as being higher ranking (ie more "accurate") than another order value is by the first order value appearing higher up in the table than the other order. Null values are not allowed in the order field.
parameter
Enter the parameter value that is described by this row in the table. There are 11 parameter values that are currently recognized by Surpac. These parameters are grouped according to the 4 generic ways of creating a new station in Surpac, ie:
- Creating a station by a standard pickup
The following 3 parameters are related to this method of creating a new station:
- HORIZONTAL ANGLE STANDARD DEVIATION
- VERTICAL ANGLE STANDARD DEVIATION
- SLOPE DISTANCE STANDARD DEVIATION
- Creating a station by resection
The following 3 parameters are related to this method of creating a new station:
- RESECTION X STANDARD DEVIATION
- RESECTION Y STANDARD DEVIATION
- RESECTION Z STANDARD DEVIATION
- Adjusting a station by a 3D survey network adjustment
The following 3 parameters are related to this method of creating a new station:
- 3D SURVEY NETWORK ADJUSTMENT X STANDARD DEVIATION
- 3D SURVEY NETWORK ADJUSTMENT Y STANDARD DEVIATION
- 3D SURVEY NETWORK ADJUSTMENT Z STANDARD DEVIATION
- Adjusting a station by a 2D survey network adjustment
The following 2 parameters are related to this method of creating a new station:
- 2D SURVEY NETWORK ADJUSTMENT X STANDARD DEVIATION
- 2D SURVEY NETWORK ADJUSTMENT Y STANDARD DEVIATION
As a result of these groupings, if you wish, for example, to set rules for a "1st" order station created by resection, you must define "1st" order rows for each of the parameters "RESECTION X STANDARD DEVIATION", "RESECTION Y STANDARD DEVIATION" and "RESECTION Y STANDARD DEVIATION". Null values are not allowed in the parameter field.
num meas fr
This field is related to the number of observations that were taken to obtain this particular parameter value. The definition of "number of observations" changes slightly depending on the value in the parameter field. If the parameter value is in the "standard pickup" group, then "number of observations" means the number of times the angle or slope distance observation was recorded. If the parameter value is in the "resection" group, then "number of observations" means the number of resection stations to which observations were taken. If the parameter value is in the "3D survey network adjustment" or "2D survey network adjustment" groups, then "number of observations" means the total number of observations that involved the particular new station as a backsight, setup or foresight station. You can define an interval for the number of measurements that will fall into this row. The num meas fr field is the lower limit of this interval. The minimum value of this field that you can enter depends on which of the grouping types the value in the parameter belongs to. If the parameter value is 3D SURVEY NETWORK ADJUSTMENT X STANDARD DEVIATION, 3D SURVEY NETWORK ADJUSTMENT Y STANDARD DEVIATION or 3D SURVEY NETWORK ADJUSTMENT Z STANDARD DEVIATION then the minimum value you can enter in the num meas fr field is 3, for all other parameter values the minimum value you can enter in the num meas fr field is 2.
num meas to
The num meas to field is the upper limit of the "number of observations" interval corresponding to the num meas fr field defined immediately above. Nulls are allowed in this field. A null in this field is defined to mean "from the value of the num meas fr field onwards".
value from
This field relates to the numerical value of the particular standard deviation value in the parameter field. You can define an interval for the standard deviation values that will fall into this row. The value from field is the lower limit of this interval. The units of the value in this field depends on the value in the parameter field. If the parameter value is in the "resection" group, the "3D survey network adjustment" group or the "2D survey network adjustment" group, or is SLOPE DISTANCE STANDARD DEVIATION then the units will be the distance units. If the parameter value is HORIZONTAL ANGLE STANDARD DEVIATION or VERTICAL ANGLE STANDARD DEVIATION then the units of this value will depend on the angle units you have chosen for Surpac. If you have selected DEGREES as your angle units, the value will be in seconds (eg 1.0, 5.0, 50.0, 120.0 etc); if you have selected GRADS as your angle units, the value will be in GRADS. Nulls are allowed in this field. A null in this field is defined to mean "from 0.0 up to the value in the value to field".
value to
The value to field is the upper limit of the "standard deviation values" interval corresponding to the value from field defined immediately above, and will have the same units as that field. Nulls are allowed in this field. A null in this field is defined to mean "from the value in the value from field onwards". Nulls in both the value from and value to fields means "all values".
dist from
This field should only be used if the value in the parameter field is HORIZONTAL ANGLE STANDARD DEVIATION or VERTICAL ANGLE STANDARD DEVIATION, otherwise it must be left null. This field relates to the horizontal distance between the setup and foresight stations if the parameter field is HORIZONTAL ANGLE STANDARD DEVIATION, or the slope distance between the setup and foresight stations if the parameter field is VERTICAL ANGLE STANDARD DEVIATION. For these two particular values of the parameter field you can define an interval of distances that will fall into this row. The dist from field is the lower limit of this interval. Nulls are allowed in this field. A null in this field is defined to mean "from 0.0 up to the value in the dist to field".
dist to
This field should only be used if the value in the parameter field is HORIZONTAL ANGLE STANDARD DEVIATION or VERTICAL ANGLE STANDARD DEVIATION, otherwise it must be left null. The dist to field is the upper limit of the "distances" interval corresponding to the dist from field defined immediately above. Nulls are allowed in this field. A null in this field is defined to mean "from the value in the dist from field onwards". Nulls in both the dist from and dist to fields means "all values".
action
Enter in this field the corresponding action for the order value in the order field for this row. The various allowable actions are described here. You must make sure that you use the order/action combination consistently in the table, for example you cannot define a "2nd" order value to have an action of WARNING in one row of the table and define it to have an action of ERROR in another row. Nulls are not allowed in the action field.
instruments
Enter in this field the names of the instruments that use this row, each name separated by a semi-colon. You can choose whatever names you want for your instruments, but you are advised to make the names as short as possible - possibly using abbreviations to shorten the name lengths (and don't have spaces within the names). The convention is that if you leave the instruments field null then ALL the instruments defined in the table apply to this row. If you decide that you don't want to define individual instruments (ie you want all the rules to apply in every situation), then just leave the instruments field of ALL the rows null. Any rows with parameter values from the "3D survey network adjustment" or "2D survey network adjustment" groups must have have a null value in their instruments field (this is because the instruments used for these functions are defined in terms of various error parameters inside the functions themselves).
The use of these rows of the station errors table is best illustrated by a simple example:
How the rows of the station errors table are used
For example say we are creating a new station F1 by a standard pickup. We are using station B1 as a backsight, and station S1 as a setup, B1 has an order of "1st", S1 has an order of "2nd". We have 2 measured horizontal angles with a standard deviation of 5 seconds, 2 measured vertical angles with a standard deviation of 7 seconds, and 2 measured slope distances with a standard deviation of 0.003. The mean horizontal distance between the setup and foresight stations is 6.0 and the mean slope distance between these stations is 6.2. The instrument used for the survey was "INST1".
The first thing that is done is that the table rows are scanned for the horizontal angle values from the top down until the first row is encountered that satisfies ALL of the following criteria:
- the value in the parameter field is HORIZONTAL ANGLE STANDARD DEVIATION
- the num meas fr to num meas to interval contains the value 2
- the value from to value to interval contains the value 5.0
- the dist from to dist to interval contains the value 6.0
- the instruments field contains the value INST1
When this row is found the corresponding values in the order and action fields are recorded.
Next the table rows are scanned for the vertical angle values from the top down until the first row is encountered that satisfies ALL of the following criteria:
- the value in the parameter field is VERTICAL ANGLE STANDARD DEVIATION
- the num meas fr to num meas to interval contains the value 2
- the value from to value to interval contains the value 7.0
- the dist from to dist to interval contains the value 6.2
- the instruments field contains the value INST1
Again, when this row is found the corresponding values in the order and action fields are recorded.
Next the table rows are scanned for the slope distance values from the top down until the first row is encountered that satisfies ALL of the following criteria:
- the value in the parameter field is SLOPE DISTANCE STANDARD DEVIATION
- the num meas fr to num meas to interval contains the value 2
- the value from to value to interval contains the value 0.003
- the instruments field contains the value INST1
Again, when this row is found the corresponding values in the order and action fields are recorded.
Next, the three order values obtained above are compared and the lowest ranking of these three orders is determined (ie the order that comes lowest down in the table). This lowest order is then compared with the orders of the backsight and setup stations, and the lowest of these three orders is assigned to the new station. The assigned action is the corresponding action value for the assigned order.
The order for each of the other three generic new station creation methods is calculated in a similar way (with the appropriate values of the parameter fields used).
NOTE: The process of finding a row in the table that matches the input standard deviation values starts from the top of the table and works its way down, always stopping at the FIRST row that satisfies the requirements. It is allowable, and is indeed recommended (from a simplicity point of view), to define rows that overlap with their defined field intervals as you go down the table. Any gaps you leave for field intervals between rows will be reported by the station errors validate function.
The Default order for new stations not defined in the above table section, on the Edit station orders form, contains the following fields:
action
Enter the default action for standard deviation parameter values that do not fall in the main table. When searching down the main table to find a matching row for a certain set of standard deviation values it may be the case that NONE of the rows are suitable. This may be due to gaps between row intervals, or you may have set this situation up deliberately. This field allows you to set a default action for any of the param fields for which this occurs.
order
This field allows you to set a default order corresponding to the default action defined above. This order must be a value that has not already been defined in the main table. In terms of accuracy ranking, this order is defined to be lower ranking than any order defined in the main table.
The Rules for single angles or single slope distance measurements section, on the Edit station orders form, contains the following fields:
As stated earlier, it is only possible to estimate a standard deviation for a value if there is more than one measurement for that value. There will always be valid standard deviations for resection and 3D and 2D survey network adjustment calculations, but for a standard pickup it will always be possible to just have one measurement for one of more of the horizontal and vertical angles and slope distance measurements. This part of the form allows the you to set rules for the eventuality where there is a standard deviation value for at least one of the trio of horizontal angle, vertical angle and slope distance, but not for all three.
Here you are allowed the following options:
- define an ERROR action for the missing standard deviation and not allow the new station to be inserted into the database
- proceed, just using the standard deviations that DO exist to define the new order
- proceed, using the standard deviations that DO exist to define the new order, but setting a default order that the order of the new station cannot be above
You are allowed to set different rules of this type for the different instances (where multiple observations can be entered) of stations created by the generic standard pickup method in Surpac, ie data recorder multiface observations, surface traverse, and underground traverse.
Data Recorder Multiface Observations: Action
Define the default action for the case when one or more standard deviations do not exist when creating a new station by multiface observations to a new station with a datarecorder.
Data Recorder Multiface Observations: Order
Define the default order for the case when one or more standard deviations do not exist when creating a new station by multiface observations to a new station with a datarecorder. Leave this field null to just use the standard deviations that DO exist to calculate the new station order. If you do enter a station order (one that must already be defined in the main table, or be equal to the overall default order), this value will be used so that the new station cannot have an order above the order entered here.
Surface Traverse: Action
Define the default action for the case when one or more standard deviations do not exist when creating a new station by multiface observations to a new station with a datarecorder.
Surface Traverse: Order
Define the default order for the case when one or more standard deviations do not exist when creating a new station by a surface traverse. Leave this field null to just use the standard deviations that DO exist to calculate the new station order. If you do enter a station order (one that must already be defined in the main table, or be equal to the overall default order for the main table), this value will be used so that the new station cannot have an order above the order entered here.
Underground Traverse: Action
Define the default action for the case when one or more standard deviations do not exist when creating a new station by multiface observations to a new station with a datarecorder.
Underground Traverse: Order
Define the default order for the case when one or more standard deviations do not exist when creating a new station by an underground traverse. Leave this field null to just use the standard deviations that DO exist to calculate the new station order. If you do enter a station order (one that must already be defined in the main table, or be equal to the overall default order), this value will be used so that the new station cannot have an order above the order entered here.
The Default order for single angles and single slope distance measurements section on the Edit station orders form contains the following fields:
It may be the case that there is only one measurement for EACH of the horizontal angle, vertical angle, and slope distance observations, therefore it is not possible to obtain a standard deviation value for any of the three parameters (this is the case, for example, for a new station created by a single face pointing to a new station with a data recorder). Here you can define rules for this situation. You can either assign a default order, or give an ERROR message and not allow this station into the database.
Action
Enter the action for the case where there is only one measurement for each of the of the horizontal angle, vertical angle, and slope distance observations.
Order
Enter the order for the case where there is only one measurement for each of the of the horizontal angle, vertical angle, and slope distance observations. This order must already be defined in the main table, or be equal to the overal default order.
The Report Output Options section, on the Edit station orders form, contains the following fields:
Report Filename
Enter the name of the table report file. While you are editing the station errors table you will find it useful to create a report of the whole table while you are editing it.
Validation Filename
Enter the name of the validation report file. The validation process of this function does many checks on the validity of the station errors table and creates a written report showing all the validation errors and warnings.
Report Format
Enter the required format for the reports.
Report...
Selecting this button creates a table report. You will find this an invaluable tool to help you create a valid station errors table as you can select this button at any time while you are editing the Orders and definitions form. See here for a more detailed description of the station errors table report.
Validate...
Selecting this button creates a validation report of the station errors table. You will find this an invaluable tool to help you create a valid station errors table as you can select this button at any time while you are editing the Orders and definitions form. See here for a more detailed description of the station errors validation report.
When you have finished editing the Orders and definitions form press Apply to commit your changes to the database, or Cancel to not commit the changes. Before the changes are committed to the database a validation check is done on your entered values. If the validation check finds any errors then the Orders and definitions form is redisplayed. If the check finds only warnings, or finds that everything is OK, then the changes are submitted to the database. If errors are found, and the Orders and definitions form is redisplayed, you are advised to use the Report... and Validate... buttons to create reports to help you find and correct the errors.
Validate station errors
This function checks for syntax errors, syntax warnings and gap warnings in the station errors table, and produces a report showing and explaining these issues. See here for a detailed description of the use of the station errors table, and here for a description of how to edit the station errors table.
To run this function: Choose Survey > Station errors > Validate, or...
A syntax error in the station errors table is a serious error that should be corrected before the table is used. A syntax warning is a minor issue that is highlighted by the report, it is up to you whether or not to resolve the issue, but it is recommended that you do. A gap warning highlights a gap in the defined row interval values, ie a region of parameter space that is not covered by any of the rows in the table. Parameter values that are not covered by any of the rows will be assigned the main default value for the table. It is recommended that you resolve all the gap warnings so that you cover all the possible values in the rows of the table.
NOTE: It is your responsibility to make sure that all the syntax errors in the station errors table have been resolved before you use the table. This must be done before you use the station errors table.
Fields on the Define file for validation report form.
File
Enter the name for the validation report file.
Format
Enter the file format for the validation report file.
Select Apply on the Define File for Validation Report form to create the report, or Cancel to cancel the function.
Result
The result of this function is a report showing details of the syntax errors, syntax warnings and gap warnings in the station errors table.
Report station errors
This function creates a report of the station errors table. See here for a detailed description of the use of the station errors table, and here for a description of how to edit the station errors table.
To run this function: Choose Survey > Station errors > Report, or...
Fields on the Define file for station errors report form.
File
Enter the name for the station errors report file.
Format
Enter the file format for the station errors report file.
Select Apply on the Define File for Station Errors Report form to create the report, or Cancel to cancel the function.
Result
The result of this function is a report of the station errors table.
Explanation of parameter values in the report:
Most of the rows in the report exactly correspond to how the table appears for editing in the main table of the edit station errors function. However the top five rows in the report contain information entered via the edit station errors function, but not on the main form table in that function. The sixth row contains the version number of the table (this may change in the future as more information is added to the station errors table in later releases of Surpac). The information in the top five rows of the report is explained below:
- The first row has the parameter value DEFAULT VALUE. See here for an explanation of the information in this row.
- The second row has the parameter value DATA RECORDER MULTIFACE ONE ANGLE OR SLOPE DISTANCE. See here for an explanation of the information in this row.
- The third row has the parameter value SINGLE SLOPE DISTANCE AND ANGLES. See here for an explanation of the information in this row.
- The fourth row has the parameter value SURFACE TRAVERSE ONE ANGLE OR SLOPE DISTANCE. See here for an explanation of the information in this row.
- The fifth row has the parameter value UNDERGROUND TRAVERSE ONE ANGLE OR SLOPE DISTANCE. See here for an explanation of the information in this row.
See below for an example of a station errors table report:
| Station Errors Table Report | |||||||||
| order | parameter | num meas from | num meas to | value from | value to | dist from | dist to | action | instruments |
| 4th | DEFAULT VALUE | ERROR | |||||||
| 2nd | DATA RECORDER MULTIFACE ONE ANGLE OR SLOPE DISTANCE | WARNING | |||||||
| 2nd | SINGLE SLOPE DISTANCE AND ANGLES | WARNING | |||||||
| 2nd | SURFACE TRAVERSE ONE ANGLE OR SLOPE DISTANCE | WARNING | |||||||
| 2nd | UNDERGROUND TRAVERSE ONE ANGLE OR SLOPE DISTANCE | WARNING | |||||||
| VERSION | 1 | TABLE VERSION | |||||||
| 1st | RESECTION X STANDARD DEVIATION | 2 | 0.00300 | INFORMATIONAL | LEICA1101 | ||||
| 1st | RESECTION Y STANDARD DEVIATION | 2 | 0.00300 | INFORMATIONAL | LEICA1101 | ||||
| 1st | RESECTION Z STANDARD DEVIATION | 2 | 0.00300 | INFORMATIONAL | LEICA1101 | ||||
| 1st | HORIZONTAL ANGLE STANDARD DEVIATION | 2 | 3.00000 | INFORMATIONAL | LEICA1101 | ||||
| 1st | VERTICAL ANGLE STANDARD DEVIATION | 2 | 3.00000 | INFORMATIONAL | LEICA1101 | ||||
| 1st | SLOPE DISTANCE STANDARD DEVIATION | 2 | 0.00300 | INFORMATIONAL | LEICA1101 | ||||
| 1st | 3D SURVEY NETWORK ADJUSTMENT X STANDARD DEVIATION | 3 | 0.00500 | INFORMATIONAL | |||||
| 1st | 3D SURVEY NETWORK ADJUSTMENT Y STANDARD DEVIATION | 3 | 0.00500 | INFORMATIONAL | |||||
| 1st | 3D SURVEY NETWORK ADJUSTMENT Z STANDARD DEVIATION | 3 | 0.00500 | INFORMATIONAL | |||||
| 1st | 2D SURVEY NETWORK ADJUSTMENT X STANDARD DEVIATION | 2 | 0.00500 | INFORMATIONAL | |||||
| 1st | 2D SURVEY NETWORK ADJUSTMENT Y STANDARD DEVIATION | 2 | 0.00500 | INFORMATIONAL | |||||
| 2nd | RESECTION X STANDARD DEVIATION | 2 | 0.00300 | 0.00500 | WARNING | LEICA1101;LEICA1103;LEICA1105 | |||
| 2nd | RESECTION Y STANDARD DEVIATION | 2 | 0.00300 | 0.00500 | WARNING | LEICA1101;LEICA1103;LEICA1105 | |||
| 2nd | RESECTION Z STANDARD DEVIATION | 2 | 0.00300 | 0.00500 | WARNING | LEICA1101;LEICA1103;LEICA1105 | |||
| 2nd | HORIZONTAL ANGLE STANDARD DEVIATION | 2 | 3.00000 | 5.00000 | WARNING | LEICA1101;LEICA1103;LEICA1105 | |||
| 2nd | VERTICAL ANGLE STANDARD DEVIATION | 2 | 3.00000 | 5.00000 | WARNING | LEICA1101;LEICA1103;LEICA1105 | |||
| 2nd | SLOPE DISTANCE STANDARD DEVIATION | 2 | 0.00300 | 0.00500 | WARNING | LEICA1101;LEICA1103;LEICA1105 | |||
| 2nd | RESECTION X STANDARD DEVIATION | 2 | 0.00300 | WARNING | LEICA1103;LEICA1105 | ||||
| 2nd | RESECTION Y STANDARD DEVIATION | 2 | 0.00300 | WARNING | LEICA1103;LEICA1105 | ||||
| 2nd | RESECTION Z STANDARD DEVIATION | 2 | 0.00300 | WARNING | LEICA1103;LEICA1105 | ||||
| 2nd | HORIZONTAL ANGLE STANDARD DEVIATION | 2 | 3.00000 | WARNING | LEICA1103;LEICA1105 | ||||
| 2nd | VERTICAL ANGLE STANDARD DEVIATION | 2 | 3.00000 | WARNING | LEICA1103;LEICA1105 | ||||
| 2nd | SLOPE DISTANCE STANDARD DEVIATION | 2 | 0.00300 | WARNING | LEICA1103;LEICA1105 | ||||
| 2nd | 3D SURVEY NETWORK ADJUSTMENT X STANDARD DEVIATION | 3 | 0.00500 | WARNING | |||||
| 2nd | 3D SURVEY NETWORK ADJUSTMENT Y STANDARD DEVIATION | 3 | 0.00500 | WARNING | |||||
| 2nd | 3D SURVEY NETWORK ADJUSTMENT Z STANDARD DEVIATION | 3 | 0.00500 | WARNING | |||||
| 2nd | 2D SURVEY NETWORK ADJUSTMENT X STANDARD DEVIATION | 2 | 0.00500 | WARNING | |||||
| 2nd | 2D SURVEY NETWORK ADJUSTMENT Y STANDARD | 2 | 0.00500 | WARNING | |||||
| 3rd | RESECTION X STANDARD DEVIATION | 2 | 0.00500 | ERROR | LEICA1101;LEICA1103;LEICA1105 | ||||
| 3rd | RESECTION Y STANDARD DEVIATION | 2 | 0.00500 | ERROR | LEICA1101;LEICA1103;LEICA1105 | ||||
| 3rd | RESECTION Z STANDARD DEVIATION | 2 | 0.00500 | ERROR | LEICA1101;LEICA1103;LEICA1105 | ||||
| 3rd | HORIZONTAL ANGLE STANDARD DEVIATION | 2 | 5.00000 | ERROR | LEICA1101;LEICA1103;LEICA1105 | ||||
| 3rd | VERTICAL ANGLE STANDARD DEVIATION | 2 | 5.00000 | ERROR | LEICA1101;LEICA1103;LEICA1105 | ||||
| 3rd | SLOPE DISTANCE STANDARD DEVIATION | 2 | 0.00500 | ERROR | LEICA1101;LEICA1103;LEICA1105 | ||||