TBCManual Dec 15

Manual
Trimble Business Centre v3.5 Planning, Processing

and Adjusting GNSS Networks
December 2015
Copyright
http://creativecommons.org/licenses/by/3.0/au/
State of Queensland (Department of Transport and Main Roads) 2015
Feedback: Please send your feedback regarding this document to: tmr.techdocs@tmr.qld.gov.au
Trimble Business Centre v3.5 Manual, Transport and Main Roads, December 2015
Contents
1
Introduction and background information ..................................................................................1
1.1
Preparation for success Get the fieldwork right! .......................................................................... 1
1.2
Verification photos .......................................................................................................................... 1
1.3
TMR GNSS ribbon and quick access toolbar ................................................................................. 1
1.4
Definitions ....................................................................................................................................... 2
GNSS planning ...............................................................................................................................4
2.1
GNSS planning online .................................................................................................................... 4
Create and setup a new project....................................................................................................6
3.1
Create a new project ....................................................................................................................... 6
3.2
Project settings ............................................................................................................................... 7
3.3
Save a new project ....................................................................................................................... 10
Import data .................................................................................................................................. 11
4.1
Download data .............................................................................................................................. 11
4.2
Import GNSS Data files ................................................................................................................ 11
4.3
Ephemeris data ............................................................................................................................. 13

4.3.1
Download final ephemeris data ................................................................................... 13
4.3.2
Import ephemeris data ................................................................................................ 15
4.4
Import known coordinates ............................................................................................................. 16

4.4.1
Import known Latitude, Longitude and Ellipsoidal height (LLE) .................................. 16
4.4.2
Assign to survey mark and set quality ......................................................................... 17
Baseline processing ................................................................................................................... 19
5.1
Seed coordinate ............................................................................................................................ 19

5.1.1
Selecting the seed coordinate ..................................................................................... 19
5.1.2
Seeding primary control point enter coordinates ...................................................... 21
5.1.3
Seeding primary control points imported coordinates .............................................. 21
5.2
Baseline assessment using the time based view ......................................................................... 21
5.3
Process Baselines ........................................................................................................................ 23

5.3.1
Analysis of the Processing Results ............................................................................. 24
5.4
Baseline processing report ........................................................................................................... 26

5.4.1
Report on an individual baseline ................................................................................. 26
5.4.2
Report on all baselines ................................................................................................ 27
5.5
Errors and problem solving ........................................................................................................... 28

5.5.1
User Errors .................................................................................................................. 28
5.5.2
Satellite data ................................................................................................................ 30
5.6
GNSS loop closure report ............................................................................................................. 35
Minimally constrained adjustment ............................................................................................ 37
6.1
Enter all known coordinate values ................................................................................................ 37
6.2
Perform the adjustment ................................................................................................................ 39

6.2.1
View network adjustment report .................................................................................. 41
6.2.2
Disable an outlier baseline vector ............................................................................... 42
6.2.3
Apply a weighting strategy .......................................................................................... 42
6.2.4
Review the Network Adjustment Report ..................................................................... 43
6.2.5
Calculate survey uncertainty (SU) ............................................................................... 44
Constrained adjustment ............................................................................................................. 45
7.1
Run the Constrained Adjustment .................................................................................................. 45

7.1.1
Constrain Horizontally ................................................................................................. 45
7.1.2
Constrain vertically ...................................................................................................... 48
7.1.3
Apply a scaler to the network ...................................................................................... 50
7.2
Constrained adjustment network adjustment report ..................................................................... 50
7.3
Calculate Project Positional Uncertainty (PPU) ............................................................................ 51
Output final adjusted coordinates ............................................................................................ 53
8.1
Ascii output ................................................................................................................................... 53
8.2
Point list report .............................................................................................................................. 54
Output of network for DNRM ..................................................................................................... 55
9.1
Creating Rinex output ................................................................................................................... 55

9.1.1
Submit to DNRM.......................................................................................................... 57
10
Project archival ........................................................................................................................... 58
Appendix A Configuring TBC ............................................................................................................. 59

Appendix B Setting up the TMR Ribbon............................................................................................. 60
Appendix C GNSS planning in TBC ................................................................................................... 61
Appendix D - Settings for Automatic Orbit Download ........................................................................... 63
Appendix E Create a new Import Format ........................................................................................... 64
Appendix F Baseline Processing Example High RMS .................................................................... 66
Appendix G Import Known Control Data ............................................................................................ 70
Appendix H Processing and Adjustment Workflow ............................................................................ 71
ii
Planning, Processing and Adjusting GNSS Networks
Introduction and background information
This manual has been created to assist Global Navigation Satellite System (GNSS) users to utilise
Trimble Business Centre (TBC) adjustment software to plan, import data, process and adjust a GNSS
Fast Static network.
Users of this manual are urged to be familiar with the Intergovernmental Committee on Surveying and
Mapping's (ICSM) publication Standards and Practices for Control Surveys (SP1) v2.1. SP1 is
available in pdf format from the ICSM website, http://www.icsm.gov.au.
SP1 documents Standards of Accuracy and best practice guidelines for Surveys and Reduction. This
includes GNSS Survey guidelines, connection to datum, network adjustment and quantifying survey
quality in terms of uncertainty.
1.1
Preparation for success Get the fieldwork right!
The most crucial contributing elements to the success of any GNSS project is the recording of good
quality satellite data for a sufficient length of time with connections to high quality datum control survey
marks. Selecting good sites with no obstructions and recording longer sessions than is theoretically
required will almost guarantee good quality results. No amount of manipulation of the data in TBC can
make up for poor field craft.
Get the fieldwork right and the network adjustment will be quick, easy and to a high quality!
1.2
Verification photos
Photos are an easy way of providing quality assurance and confidence in the setup. For longer
occupations (over three hours) photos also help get around the need for independent occupations.
Photos should be taken showing, and in this order:
verification of the physical mark showing its identifier
the receiver ID
the height measurement at both the start and finish of the session, and
any obstructions that may affect the processing.
a photo looking through the optical plummet showing the cross-hairs on the mark is
sometimes possible and a photo of the level bubble provide additional confidence.
1.3
TMR GNSS ribbon and quick access toolbar
This version of TBC enables a ribbon of commonly used commands/functions to be customised. A

TMR GNSS ribbon has been created featuring commands that represent the normal flow of a GNSS
network project. In conjunction with the Quick Access Toolbar, the ribbon features the majority of
commands/functions that are used. This manual will refer to the ribbon not the default tab position of
the command/function.
Due to differing monitor sizes the ribbon may look a little different but will have the same
commands/functions. The ribbon presented below has been broken into two to fit on this page.
The Quick Access Toolbar (below) has a number of useful features like Archive a Project, Licence
Manager and Change Coordinate System.
Steps to setup the ribbon are detailed in Appendix B.
1.4
Definitions
A priori variance
factor
Used to scale each observation variance just prior to network

adjustment
A Posteriori variance
factor (variance of unit
weight)
A statistical measure of how well the adjustment results match the

expected errors as described by the a priori standard errors for the
observations
AHD
The Australian Height Datum (1971) is the NGRS normal-orthometric

height datum for mainland Australia
AusGeoid
The national quasi-geoid model for converting between GDA94

ellipsoidal heights and AHD heights. The current version is AusGeoid09
CORS
Continuously Operating Reference Station. A survey control mark

hosting a permanent GNSS station
Datum Control Survey
The network of survey control marks which have been adjusted in the
National Geospatial Reference System. These control marks have the
most rigorous estimation and testing of position and uncertainty
Degrees of Freedom
(DOF)
The number of independent measurements beyond the minimum

required to uniquely define the unknown quantities. The strength of and
confidence in the solution increases as the degrees of freedom
increase. Adding redundancy in the network helps maximise the DOF
DNRM
Queensland Department of Natural Resources and Mines
GA
Geoscience Australia
GDA94
Geodetic Datum of Australia (1994)
ICSM
Intergovernmental Committee on Surveying and Mapping
ITRF
International Terrestrial Reference Frame
MGA94
Map Grid of Australia (1994)
NGRS
National Geospatial Reference System is Australias authoritative,

reliable, high accuracy spatial referencing system. It includes GDA94
and AHD71 datums
NLN
National Level Network
PSM
Permanent Survey Mark
Project Reference
Frame (PRF)
The skeleton that all other TMR project survey information is referenced
to. The PRF defines the position of the survey project
QEHA
Queensland Ellipsoidal Height adjustment the highest quality network

adjustment of Queenslands Survey Datum Control marks
Reference Factor
(Standard error of unit
weight)
An indicator for testing the quality of testing the quality of measurements

and isolating suspect measurements. The reference factor is about 1.00
when the amount of the adjustment to the observations equals the
estimated errors of those observations. Reference factor is the square
root of the A Posteriori variance factor
SCDB
Survey Control Database administered by DNRM
SP1
ICSM Standard for the Australian Survey Control Network Special

Publication 1
Uncertainty Positional (PU)
The uncertainty of the horizontal and/or vertical coordinates of a survey

control mark with respect to the defined datum and represents the
combined uncertainty of the existing datum realisation and the new
control survey. That is, PU includes SU as well as the uncertainty of the
existing survey control marks to which a new control survey is
connected. A fully constrained least squares adjustment is the preferred
and most rigorous way to estimate and test PU. PU is expressed in SI
units at the 95% confidence level
Uncertainty - Survey
(SU)
The uncertainty of the horizontal and/or vertical coordinates of a survey

control mark relative to the survey in which it was observed and is free
from the influence of any imprecision or inaccuracy in the underlying
datum realisation. Therefore, SU reflects only the uncertainty resulting
from survey measurements, measurement precisions, network
geometry and the choice of constraint. A minimally constrained least
squares adjustment is the preferred and most rigorous way to estimate
and test SU. SU is expressed in SI units at the 95% confidence level
TBC
Trimble Business Centre v3.5 software
GNSS planning
There a number of ways available to determine how many satellites will be available on the project site
for the planned observation times. An easy way is presented below. Another option using the Planning
function in TBC is more useful when away from the office is shown in Appendix C. It does depend on
having an almanac available on the computer to be able to be used without an internet connection.
2.1
GNSS planning online
GNSS planning can easily be completed online using the link below.
http://www.trimble.com/GNSSPlanningOnline/#/Settings
Enter a latitude and longitude or use the Pick button (see below). Enter a height, elevation mask
cutoff, enter the relevant date and times. If a particular site has obstructions use the Obstructions tab
to customise (see below).
Alternatively to typing in Lat/Longs, use the Pick option to bring a map window up. Select a point on
the map and the Your Position tag will mark it. Select Apply.
If obstructions are required to be mapped, use the Obstructions tab to define the curtain. Initially the
blue line in the diagram below will be a circle representing the elevation mask entered in the initial
Settings screen. Left clicking on the blue line will create orange nodes. These can be pulled into place
to create the required obstructions and will change colour to blue. These points, once created, can be
adjusted by editing the azimuth and elevation in the right hand window below using the pencil icon.
Press Enter on the keyboard to activate the change. When happy with the obstruction curtain, select
Apply.
There are a number of options to display relevant information. Some of the more useful options are:
Number of Satellites use this button to show a graph of the number of satellites available.
DOPs will show a graph of the DOP values which can be helpful to avoid observing when
DOP values are high.
Sky Plot shows the track of the satellites across the sky. Can be helpful once onsite to
ensure obstructions are removed from a particular quadrant that has high satellite traffic.
3
3.1
Create and setup a new project

Create a new project
Open TBC and select the Project function from the ribbon.
TMR templates have been set up for each of the three MGA94 zones that cover Queensland. Select
which MGA94 Zone the project is in with the left mouse. Select OK.
3.2
Project settings
Select Project Settings from the ribbon
Most of the project settings have been pre-set as required.

Under General Information enter the reference number (Field book/file number) and project name.
Put the Reference number as a prefix to the Project Name as the reference number field wont appear
on reports generated.
Fill out the relevant Company Information.
Fill in the relevant Office User and Field Operator details.
Under Baseline Processing > General > Ephemeris type will be pre-set to Automatic. If the Precise
ephemeris is to be used, use the drop down to change to Precise.
If you choose to process without Glonass, under Baseline Processing > Satellites highlight the
Glonass tab and select None. They can turned back on by using All.
The Satellite Elevation Mask can be adjusted from the pre-set recommended 15 degrees but this is
not recommended. 15 degrees helps reduce the amount of noisy data, minimise multipath and lesson
ionospheric effects.
If required to be changed simply replace 15 with the new value in the Elevation mask field.
The Network Adjustment Covariance Display should be changed PPM and Spherical settings as
below.
The Default Standard Errors for GNSS should be entered with the appropriate values as specified by
the manufacturer. Trimble R8s, R10s, Leica GS14 and GS15 should be set as below.
Navigate to Default Standard Errors > GNSS and ensure values are set as below.
Choose Confidence Level Display from the Default Standard Errors list and ensure the Precision
Confidence Level is set to 95%.
When editing of the Project Settings has been completed select OK

3.3
Save a new project
Select Save from the ribbon, browse to the desired folder, enter a file name and Save.
10
Import data
A number of different types and formats of data can be importing into a project.
4.1
Download data
Follow manufacturers procedures to download data for the receiver or hand controller used.
Some ways to download files are:
copy from hand controller to USB stick
bluetooth from receiver to hand controller to USB stick
with TBC open and project created, connect hand controller or receiver to computer and use
the Devices pane to navigate to, select and import files.
1. connect hand controller or

receiver to computer
2. navigate to and highlight
required files (T01, T02)
3. select Import
4.2
Import GNSS Data files
If the receiver files have been downloaded through ActiveSync or via USB direct to the project folder
the following steps can be used to import them into TBC.
TBC will recognise many different file types automatically.
Select Import from the Ribbon

Browse to the correct folder to import from. Select the required file(s) and select Import.
Repeat as necessary to import all GNSS data from different folders. The example below features
CORS zip, Trimble T01, Trimble T02 and Rinex files.
11
12
Ensure all Point IDs, antenna type, method of height measurement and the height measured have
been entered correctly. Record filenames onto the booking sheets for QA and metadata purposes.
Once happy, select OK
4.3
Ephemeris data
You may want to import more accurate ephemeris data to improve the baseline processing. The
Broadcast ephemeris is transmitted by the satellites every 30 seconds but is a projection of expected
location and its clock behaviour and therefore not precise. For projects covering less than 50 km or
baseline lengths less than 50 km, if proper field practices are followed including generous session
logging lengths, the broadcast ephemeris should be sufficient for most projects.
The Final ephemeris is the most precise available but has a latency of 12-18 days. It is especially
useful on larger projects covering over 50 km, projects with baselines exceeding 50 km, and where
atmospheric events like solar flares have occurred. The Final ephemeris has to be downloaded from a
NASA website.
Each Final Ephemeris file hold 24 hours of ephemeris data that covers one GPS day (10am to
9:59:59am AEST).
4.3.1
Download final ephemeris data
TBC has a very useful and easy option to download Final ephemeris data.
Select
from the ribbon. Highlight IGS Final Orbits in the Internet Download
window. Either right mouse and select Automatic Download or select
at the bottom of
the window.
13
The Download Parameters panel will show the TBC calculated parameters. From the project it takes
the start time and date of the first recorded data and the end time and date of the final session. This
time range is expanded in both directions to allow for the difference between local time and the GPS
day.
For most projects this will work perfectly as long as all data has been imported into the project. The
example project has GNSS sessions on three different days across a 16 day period. As shown below,
the TBC calculated parameters would download 408 hrs (17 days) of data to cover the three different
observation days.
To avoid this excessive download, use the Session drop down menu to show a number of options. For
the example project session that cover each of the observation periods are available. By selecting one
of the individual sessions only the files required are downloaded. This process will have to be
repeated for all sessions (three sessions in the example).
14
When Ok is selected the files will be downloaded. Select Import. The files will be imported into the
TBC project.
To check, ensure the files are in the Imported Files list in the Project Explorer pane.
The final ephemeris data is now available for TBC to use.
4.3.2
Import ephemeris data
If the final ephemeris has been downloaded via a different method it can be imported as follows.
Select Import from the ribbon.
Browse to the correct folder to import from. Select the required file(s) and select Import.
Files will be imported and appear in the Project Explorer pane under Imported Files.
15
4.4
Import known coordinates
Known control mark coordinates are able to be imported in a number of different formats. This step is
optional and may be skipped. The survey mark name must be exactly the same (including case) for
TBC to assign to the mark correctly. All marks imported using this method will have a Control Quality
set on the coordinate. If coordinates of varying quality are imported the Quality may have to be
changed to Unknown before processing baselines as that process will use all Control Quality
coordinates. Vide Section 5 Process Baselines for more information.
A similar process can be used to import easting, Northing and AHD heights using the P,E,N,elev,Code
import format (vide Appendix G). The best time to import this data is after the baselines have been
processed.
4.4.1
Import known Latitude, Longitude and Ellipsoidal height (LLE)
Network Control mark position and elevation information can be imported from a file (.csv). This is
especially useful if the same control marks are used frequently (e.g. CORS). Caution must be
exercised to ensure the current published coordinates of the mark havent changed. A new Import
Definition may need to be defined to import Latitude and Longitude in Degrees Minute Second format.
Vide Appendix E Create a new Import Format.
With an Import Format created, known control mark LLE in degree minute second format can be
imported.
Select Import from the ribbon.
In the window below browse to the correct folder to import from. Select the required file(s). The file
type will initially be identified incorrectly as P,E,N,elev,Code (Control). Ignore this and select Import.
16
Highlight the correct Definition Name P,L,L,h,Code (DMS Global) and check that the details in the
Import Preview section of the window are now assigned to the correct field. Select Import.
The file name will appear in the Imported Files folder of the Project Explorer. The points will appear
under the Point name if the point name has been associated correctly (see below).
4.4.2
Assign to survey mark and set quality
If the survey mark has been named correctly in the imported file the coordinates will be automatically
assigned to the point as highlighted below.
17
The properties should be checked and quality set by right mouse on the highlighted file and selecting
Properties. Check the coordinate information has been correctly imported and assigned. The Quality
will have been set as Control.
If these coordinates have been imported before Process Baselines has been run, only the mark with
the highest quality coordinates should have Control Quality assigned. To change the quality of other
marks, left mouse on the Latitude
symbol and select Unknown Quality.
Symbol will change to the unknown symbol
. Repeat the process on the Height quality symbol.
18
Baseline processing
Processing baselines determines the highest quality coordinates for each mark in the project. Vectors
are created from the processed baselines and are subsequently used in the adjustment.
Prior to processing baselines, a coordinate seed point must be set and the sessions scrutinised to
determine sufficient overlap of the individual sessions on each mark of the baseline.
Appendix H contains a processing and adjustment workflow which may be of help.
5.1
Seed coordinate
One survey mark of known coordinates (seed) needs to be set to control the baseline processing. For
TMR networks this mark will be a Datum Control Survey mark with a horizontal uncertainty of less
than 20 mm.
TMR surveys should always have the seed point set to GDA94 Latitude and Longitude coordinates
and a GRS80 ellipsoidal height obtained from a Regulation 13 certificate or Qld Globe derived Form 6.
5.1.1
Selecting the seed coordinate
The Datum Control Survey mark with the best Uncertainty values for horizontal and vertical
(ellipsoidal) quality should be seeded. A Least Squares Adjustment works best when the adjustments
required are minimal. Inaccurate seed coordinates adversely affect the accuracy of the baseline
results and therefore the adjustment.
If the network includes CORS marks they should generally be selected as the Seed point/s. In addition
to having very good Uncertainty values, CORS are likely to be more stable and less likely to be
disturbed than a traditional PSM. The coordinated position of CORS marks are regularly checked
against Australias fundamental network giving extra confidence in the mark.
If the network does not include CORS, the QEHA PSM with the best uncertainties is the next best
option. Consideration should also be given to the quality of the mark (stability, condition and
obstructions present) and its influence in the network (distance to the project, number of baselines to
the mark). E.g. seeding a PSM with 8 mm uncertainty that is in unstable country, remote to the project,
surrounded by trees and with only two baselines to it, may not be the best choice. Professional
judgement is required.
5.1.1.1
Source Google earth SNA CORS status
Regulation 13 Certificates and up to date positions can be obtained of all SmartNetAus CORS marks
using the SmartNetAus (SNA) Status kml in Google Earth.
Left mouse on a CORS symbol. If it has a Reg13 Certificate, use the download link to obtain the
certificate. These certificates should be kept in the TMR project folders as metadata pertaining to the
position of the mark at time of survey just like a PSM Form 6 should be.
The current accepted position of a CORS will be displayed when left mouse clicking on a mark. For a
non Reg13 mark these windows should be screen captured as a record of the Latitude, Longitude and
Ellipsoidal Height used in the adjustment of the TMR network.
19
5.1.1.2
Source Qld Globe PSM form 6
If no CORS marks have been used within the network, the control PSM with the best Uncertainty
values should be used. The Qld Globe is the single point of truth for PSM Form 6s. Form 6s derived
by other means should not be used as the details may not feature all the latest position and quality
information about a PSM.
A Qld Globe Form 6 will display the Horizontal and Vertical Uncertainty of GDA94 Latitude, Longitude
and Ellipsoidal Height of PSMs included in the QEHA adjustment. Choose the PSM with the best
Uncertainty values as the seed point.
20
5.1.2
Seeding primary control point enter coordinates
In the Project Explorer panel use the drop down beside Points to show the list of occupied marks.
Right mouse on the chosen seed point and select Add Coordinate.
Set the Coordinate Type to Global. Enter the known Latitude, Longitude and Ellipsoidal Height.
Select the coordinate quality by selecting
5.1.3
and choose Control Quality.
. OK
Seeding primary control points imported coordinates
If Survey Control Datum coordinates have been imported from a control file, ensure only the selected
seed points have Quality set to Control. All survey marks in the imported file will have been assigned
Control Quality. TBC will use all control quality points as seeds.
Vide Section 4.4 for steps to import, set and change the quality level on a survey mark.
5.2
Baseline assessment using the time based view
All baselines should be assessed to ensure they have sufficient session overlap duration to be
processed. The overlap requirements should have been determined before the fieldwork commenced.
It will vary from project to project depending on factors such as network size, baseline length,
occupation method and desired accuracy of the resultant coordinates. Any baselines that do not meet
requirements need to be disabled or deleted. Baselines that almost meet requirements and could
possibly be used if the network has problems should be disabled. Delete baselines that will never be
of any use.
21
Select Time-Based View from the ribbon
. All overlapping sessions that meet TBCs
basic duration requirement will be shown. In the example the network has been read on three
separate days.
The overlap duration can be obtained by right mouse on a baseline in the list and selecting
Properties. Start and End Time of the overlap are shown as well as the Duration and the Status of
the baseline.
22
To disable a baseline use the drop down Status list to choose Disable.
Professional judgement is required when choosing to disable, delete or accept baselines. In the
example project the duration was planned to be two hours. A number of baselines from PM6s session
were 1 hr 56 min. These were deemed close enough to meet requirements.
Baseline B148 above was found to have a duration of only nine minutes. Being of no value, it was
deleted.
To delete a Baseline, close the Properties window, right mouse on the baseline in the Session
column in the Time-Based View list and select Delete.
5.3
Process Baselines
Once a Survey Datum Control Mark has been seeded and baselines have been assessed for
sufficient duration the baselines can be processed. Be sure no baselines are selected or only that
baseline will be processed. In Plan View, all baselines should be green. A selected baseline will be
coloured purple.
Firstly ensure the Flags Pane is active, its icon should be highlighted yellow in the ribbon
with
the window itself visible below the Plan View.
23
Select Process Baselines from the ribbon
After all baselines have processed the results are displayed.
Once the results have been assessed, if no problems are identified, the baseline processing can be
saved by using the Save button. Check for Flags (vide Section 5.3.1.1), review the Baseline
Processing Report (vide Section 5.4), and generate GNSS Loop Closure Report (vide Section 5.6).
If the results reveal issues that require review, continue below through Sections 5.3.1, 5.4 and 5.5.
5.3.1
Analysis of the Processing Results
There are a number of indicators and reports available to help find and fix baseline problems in the
network.
The solution should be Fixed which denotes the processor was able to resolve the integer
ambiguity with confidence.
A Float solution occurs when the baseline processor is unable to confidently resolve the
integer ambiguity to be able to select one set of integers over another. The baseline needs to
be analysed to determine why this has happened.
The Horiz. and Vert. Precision should be sufficiently low to give confidence in the result.
Larger than expected precisions may indicate a problem and should be looked at even if TBC
doesnt highlight the baseline as having a problem.
The RMS column shows the quality of the solution as a Root Mean Square (RMS). It is based
solely on the measurement noise of the satellite ranging observations and is independent of
satellite geometry. The closer to zero the better.
TBC will use Flags to highlight baselines that havent met set criteria (vide Section 5.3.1.1).
Baseline Processing Report can be generated for an individual baseline or for every
baseline (vide Section 5.4).
24
The processing results can be ordered by any of the columns which makes it easy to spot any
potential problems.
The screenshot above has been ordered by RMS, largest first. Look for problems by also ordering the
Horiz and Vert Precision columns. The results show larger than desired RMS for a few marks however
the precisions are good.
5.3.1.1
Flags
TBC will use Flags to highlight any baselines that do not meet the entered settings:
A Yellow Flag indicates a warning about data or computations. Yellow flags denote that the
precision fell outside of the Flag acceptance criteria as set in the Quality section of baseline
processing settings.
A Red Flag indicates an error or failure in data or computations. Red Flags denote that the
precision fell outside of the Fail acceptance criteria.
Red flagged baselines need to be looked at to determine why they failed. Yellow flags should also be
analysed to see why the baseline was flagged and if it warrants further attention.
In the example above two baselines have been flagged as having issues. The red flagged baseline
(PM140618 PM173135) obviously has problems. TBC hasnt been able to resolve the integers and
therefore it has only a float solution. Horiz and Vert Precisions are very bad. The baseline processing
report for this baseline will be an abridged version of the normal and will not help much.
The yellow flagged baseline (PM140618 TBM1) has larger Horiz and Vert Precisions than would be
expected. Both of these baselines would need to be analysed further. The baselines processing report
is a good place to start.
25
5.3.1.2
Root Mean Square (RMS)
The RMS shows the quality of the solution as a root mean square. It is based solely on the
measurement noise of the satellite ranging observations and is independent of satellite geometry.
The baseline solution is an estimate using all of the data collected in the field (less any manipulation in
TBC like turning glonass satellites off). The processor compares each measurement epoch to the
baseline solution. Each epoch is then compared, and the differences averaged. The RMS is the
average of the epochs residuals. The closer to zero the better. Values less than 15 mm are generally
acceptable for most small to medium sized projects.
Larger RMSs need to be analysed to determine if there is a problem. Quite often larger RMS are the
result of processing using Glonass and broadcast ephemeris. The baseline processing report is a
good place to start looking for issues.
5.4
Baseline processing report
5.4.1
Report on an individual baseline
An individual baseline processing report contains a summary of the process and detailed information
about a processed baseline. It is often a valuable source of information to determine if a baseline
needs to be disabled, satellite disabled or data edited. It is also another chance to ensure no mistakes
have been made in the type of receiver, antenna height measurement and so on.
Select a high RMS observation in the grey section to the left of the tick box on the far left of the
Processing Results pane. The line will highlight and the Report option will now be available to use.
Select Report and the baseline processing report will open in a web browser.
Peruse the Session Details at the top of the report. Check that the ephemeris used, processing
duration and processing interval are correct. An incorrect processing interval would mean one of
the receivers was logging data at different epoch intervals than the other.
Aposteriori Covariance Matrix is a mathematical statement of quality of the processed vectors.
Look at the Residuals plot for each satellite to see if any large spikes or anomalies that would be
affecting the quality of the baseline are present.
If large spikes or anomalies exist, questions to ask whilst analysing the plots would be:
Are the spikes on every satellite for the baseline?
Is the spike/s at the same time on all satellites?
Are there similar spikes on other or all baselines?
Do the baselines with spikes feature a common survey mark?
Below is an example of data with large spikes. On examination of the other satellite plots these spikes
were present in most but not all satellites. The spikes where present in other baselines in a number of
satellites, both GPS and Glonass. The spikes werent consistent across all processed baselines but
were present on a quite a few and not always featuring the same survey mark.
26
If it was found to be the same satellite causing problems on all baselines at the same time, it would
suggest a satellite problem. This satellite could be deselected from the list of satellites available for
use by selecting Project Settings from the ribbon or Settings in the Process Baselines window. Select
Baseline Processing > Satellites highlight the correct tab (GPS for G satellites and Glonass for
R satellites) and untick the satellite in question.
If the problem was found on baselines featuring a common survey mark, it would suggest multipath or
a noise problem at the mark. This may be noise from a low satellite or where a tree has partially
blocked the signal. This can sometimes be fixed by editing the satellite data on the problem baselines.
In the example project there is no obvious source of the problems. The problem is present across
numerous but not all baselines without a common mark being involved. There are two options that
may fix the problem:
a) try processing baselines without the Glonass satellites (vide Section 5.5.2.5)
b) if sufficient time has elapsed since the fieldwork was completed, processing baselines using
the Final Ephemeris may also fix the problems (vide Section 5.5.2.6).
5.4.2
Report on all baselines
Once the Baseline Processing results have been Saved, a baseline processing report can be
generated for all the processed baselines. The report will be quite large but contains valuable
information that should be kept for the project record.
From the ribbon, select
Reports > Baseline Processing Report.
The report will be generated in TBC. The report can be printed (not recommended) or saved as an
Excel spreadsheet, Word doc or in pdf format (recommended). The report contains a Processing
Summary and the same information as the individual baseline processing report for every processed
baseline in the network.
27
5.5
Errors and problem solving
There are a number of ways to potentially solve errors and problems depending on what the error or
problem is.
Errors and Problems are attributable to three main sources and can be fixed in a number of ways:
User errors - Correct the user entered data
Satellite Data - Remove a satellite, remove all glonass satellites, disable a baseline, raise the
elevation mask, exclude some satellite data, or use precise ephemeris
5.5.1
Network Design read longer session, read additional baselines.

User Errors
Good field craft and checking of the entered data should eliminate user errors from affecting the TBC
processing. Errors, if made, like misnamed Point IDs, incorrect instrument heights, antenna type and
method of height measurement should have been corrected in the Raw Data Check-in stage when
importing data (vide Section 4.2). Antenna height, type and measured to method can be edited in the
Occupation window
. After changes are made, the baselines will require to be re-
processed.
Problems with entered data, like an incorrect instrument height, will not be identified when baselines
are processed. TBC will apply the Baseline Processing Quality acceptance criteria (defined in Project
Settings) only once the processed baselines are Saved.
Below are Processing Results using the correct instrument heights. The 1st window is ordered by
descending RMS, 2nd by descending Vert. Precision.
28
In the following two windows are Processing Results after an incorrect instrument height (by 200 mm)
has been entered on one of the sessions. The 1st window is ordered by descending RMS, 2nd by
descending Vert. Precision. There are no noticeable errors because of the incorrect height as the
baselines are being processed individually and the survey marks at the end of the baselines are not
compared.
29
Its only after the Processing Baselines has been saved that TBC will raise flags in the Flags Pane and
the Plan View.
The prevalence of PM1 in the flags list above strongly suggests PM1 has error in the vertical
component. The flags on the other marks in this case will be a result of the baselines from PM1.
To examine the entered heights for PM1, select the Occupation View
from the ribbon.
Check that the antenna height and method of height measurement are correct against the booking
sheets and photos. The blue text fields are editable and any errors can be corrected.
Process Baselines can then be re-run.
5.5.2
Satellite data
A number of problems can be the result of the process of recording the satellite data. These may be
satellite based like an unhealthy satellite or issues between the GPS and Glonass systems. Others
are due to site based issues like the presence of obstructions or a high multipath environment.
5.5.2.1
Disable a satellite
Disable a Satellite for all Baselines

If the analysis of the Residual Plots in the baselines processing reports showed problems with one
satellite across all baselines, that satellite can be turned off. The satellite number is at the centre
bottom of the Residual Plot.
Project Settings > Baseline Processing > Satellites and tick off the satellite in question.
OK and re-run Process Baselines. Analyse the results again.
Disable a Satellite for all Baselines from a Mark
The satellite may only be a problem at one survey mark which will then affect all baselines from that
survey mark but no others in the network. This may be because it was flicking in and out of view
because of a tree for example. In this case, disabling the satellite for the every baseline as shown
30
above would have a detrimental effect on the network. To disable the satellite only for the affected
baselines, will require it to be disabled for each of those baselines separately.
Highlight one of affected baselines in the Time Based View, right mouse, select Session Editor and
left mouse on the satellite number to disable it. The corresponding row of data will be greyed out. Left
mouse on the satellite number will also enable it. Repeat on all baselines that include the affected
recording session.
A second way is to right mouse in the white space of the required satellites row and select will Disable
Satellite. Right mouse on a disabled satellite will allow Enable Satellite to be selected. Repeat on all
baselines that include the affected recording session.
OK and re-run Process Baselines. Analyse the results again. If the disabling didnt help, enable the
satellite again as above.
5.5.2.2
Exclude poor data
Poor satellite data can be cut-out to potentially improve the resultant solution. Care needs to be taken
as to what data to cut and also ensure not too much data is cut making it harder for TBC to process
the baseline. A lot of time can be spent improving the data, only to end up with a worse solution.
In the Time-based view, right mouse on a baseline and select Session Editor (or select
in the ribbon).
For example, in the baseline processing report for baseline S167, from PM4 to PM6, there was some
larger residuals at the end of the session for satellite G26 (as below). The recorded data is also
segmented and may have been dropping in and out through an obstruction. This section could be
edited out if required to try and improve the baseline result.
31
The resultant session editor window will show the from (PM4) and to (PM6) survey mark and
baseline number B167. Satellites will be listed down the left edge, time across the top. For each
satellite the top blue line shows the recorded data at PM4, the bottom green line the data recorded at
PM6. Only the overlapping parts of the blue and green data lines will be processed.
After finding satellite G26 and squaring across to the end of the session some cycle slips can be seen
on the green line (PM6). A break in a line and subsequent black tick when data starts being recording
again indicate cycle slips. A cycle slip is a discontinuity of the receivers continuous phase lock on a
satellites signal. Cycle slips are common when a satellite is flicking in and out of sight through a tree
and also in urban environments where the satellite is being tracked, the tracking signal is lost, and
then re-acquired again.
By moving the mouse arrow across the session data the corresponding time can be seen in the middle
top of the window. The time of the cycle slips corresponds to the start of the spikey data in the
baseline processing report.
To cut these cycle slips out, pull a window around the area by left click and hold at the bottom left
corner of the area and pull across to the top right corner and releasing the button. A black hashed box
(Time Slot) will be created (as below left). Be careful to stay within the top and bottom grey lines when
pulling the box as a second satellite may also be boxed. If a mistake is made, right button in the
hashed box and select Remove Time Slots (as below right).
32
If many time slots require removal, use the Select All Time Slots option. All the Time Slots will now
have a black surround to show they are selected, right button on one of them and select Remove
Time Slots.
Once finished editing other satellites on this baseline or satellites on other baselines, select OK and
re-run processing Process Baselines. Analyse the results again.
If it is found the editing has made the solution worse, the time slot can be highlighted and removed as
previously shown above.
5.5.2.3
Disable a baseline
Baselines may be disabled if they are causing problems and cant be fixed in other ways like disabling
satellites. If the Residual Plots shows bad data across the majority or all satellites that cant be
rectified through disabling a satellite or two, the baseline may have to be disabled. Consideration
needs to be given to the baselines importance in the network. If it is critical, the baseline will have to
be measured again in the field.
In the Project Explorer pane, navigate to the relevant baseline under Points and the point name,
right click on the baseline and choose Disable Vectors.
5.5.2.4
Raise the elevation mask
An elevation mask of 15 degrees is recommended for processing as noise, multipath and ionospheric
effects are reduced. If the project has a noisy satellite/s that is low in the sky, the elevation mask may
be lifted to remove this noisy data from the processing. This approach can also help to further
minimise multipath. However clean data on other satellites will also be removed from the processing
which could have a detrimental effect on the results.
33
This option should only be used after careful consideration and is a when all else fails type option
before committing to re-observing the affected baselines.
Project Settings > Baseline Processing > Satellites > Elevation Mask
Change the elevation mask to a higher angle. Try increasing by a degree at a time and re-processing.
5.5.2.5
Process without Glonass
Processing with Glonass can quite often introduce problems to the baseline solutions as they
introduce a lot of noise that can be seen in the RMS and residuals. Using the final ephemeris will
usually fix these problems. If the project cant wait two weeks for the final ephemeris to become
available, processing without Glonass will produce very good results in most cases. Geoscience
Australias online adjustment service AUSPOS and DNRMs QEHA do not use Glonass in their
processing.
The decision to drop out Glonass needs to be taken on a project by project basis as some networks
may need the Glonass satellites to help overcome unfavourable site conditions. The RMS will
generally improve dramatically when the Glonass is removed. However, testing has shown that if the
noisy Glonass is used, the adjusted networks resultant coordinates can differ only slightly when
compared with when the Glonass is not used. Therefore even though the Glonass is noisy, it can still
be used especially when site conditions where not favourable.
Select Settings from the Baseline Processing panel. Navigate to Baseline Processing > Satellites
> Glonass > None > OK. TBC will return to a now blank Process Baselines panel. Select Process.
Analyse the results.
The example projects RMS results have benefitted from processing without Glonass. The Horiz. and
Vert Precisions have only very small changes. The list has been sorted in descending order of RMS.
The RMS has improved significantly over the results when Glonass was included.
34
5.5.2.6
Process with precise ephemeris
The Precise ephemeris is the most accurate ephemeris, but it does take 12 14 days to become
available. The Broadcast ephemeris is the most commonly used but is also the least accurate as it is a
projection of the satellites location and its clock behaviour. Accuracy of orbit is ~ 100 cm and clock
~ 5ns RMS. The precise ephemeris has an Orbit accuracy is ~ 2.5 cm with a clock accuracy of ~ 75ps
RMS.
Generally the noise problems associated with Glonass satellites will be fixed by using the precise
ephemeris.
If Glonass satellites have been turned off:
Select Settings from the Baseline Processing panel or the ribbon.
Navigate to Baseline Processing > Satellites > Glonass > All > OK.
Under Baseline Processing > General the Ephemeris type will be preset to Automatic.
Use the drop down to change it to Precise.
Process the baselines by selecting Process Baselines from the ribbon or Process from the Process
Baselines window if its still open. Analyse the results.
Save when happy with the results.
5.6
GNSS loop closure report
Loop closures are used to check the quality of, and identify any errors in a network of GNSS
observations. GNSS Loop Closure should be run after successful processing of the baselines.
The closure parameters must firstly be set.
From the ribbon, select Reports
> Report Options
> GNSS Loop
Closure Results.
Expand the Report Setting and Report Sections.
Networks featuring both short and long baselines are difficult to set parameters for that will work for all
baseline lengths. Be aware that loops with short baselines will often fail this test purely because of the
short length. A baseline shouldnt be disabled just because its features in loops that fail this test.
Disabling should only be undertaken when all factors have been assessed including how well it
processes.
In Report Setting fields, set the Pass/Fail criteria as PPM and the PPM to 5.0.
35
In Report Sections, if only the Failed loops sections are of interest, ensure Passed loop section is
set to Hide.
Apply and Ok.
From the ribbon select GNSS Loop Closure
and the report will be generated and
opened in a web browser. The report has a Summary that provides information on number of loops,
how many failed and the statistics on the best, worst and average loop.
A failed loop can be highlighted in the plan view by selecting its name (PV167-PV156-PV165) in the
Failed Loops section.
The Observations in Failed Loops is useful in that a particular baseline that occurs a number of
times in failed loops can easily be identified. These baselines can subsequently be investigated and
disabled if required (vide Section 5.5.2.3).
36
Minimally constrained adjustment
A minimally constrained adjustment is used to evaluate the internal observations and the standard
errors assigned to them. The quality and internal consistency of the survey network is assessed to
verify the GNSS measurement precisions. As the network is only tied to one point, it can move freely
during the adjustment and, provided good network geometry has been established, any measurement
blunders are more likely to be isolated and detected.
Use it to:
check the internal consistency of the network
detect blunders or ill-fitting observations
obtain accurate observation error estimates.
A minimally constrained adjustment holds only control point fixed which shifts observations to the
correct location within the datum.
6.1
Enter all known coordinate values
All the high quality known MGA94 coordinate and AHD height values that are intended to be used in
the adjustment should now be entered if not done previously. By entering all known high quality
values, TBC can report differences to these values in relation to the minimally constrained adjustment
values (vide Network Adjustment Report, Section 6.2.4). The differences can be assessed to
determine which control marks fit together and therefore help form a strategy for the constrained
adjustment.
Ellipsoidal Height AusGeoid project
On projects where AHD heights arent required to be derived from the GNSS network, AHD is
unavailable, or too distant to the project to be of any value; enter all known GDA94 latitude and
longitude values and ellipsoidal heights.
In the Project Explorer pane, right mouse on a mark that requires known values to be entered and
select Add Coordinate.
37
In the Coordinate type ensure Grid is selected. Enter the known values as required and change the
quality to Control Quality. It is perfectly ok to only enter an Easting and Northing on a point or only an
AHD height. Only control points with high quality Horizontal Uncertainty or Class and Order for AHD
height should be entered.
Select OK when finished. Repeat for all control marks with high quality known values.
Use the Coordinate type drop down menu to select Global.
Enter Latitude, Longitude and ellipsoidal height values of known high quality (low
PU) marks. Ensure Quality level is set as Control for entered values.
38
6.2
Perform the adjustment
Ensure no baselines or points are currently selected.
From the ribbon select Adjust Network
. The minimally constrained adjustment should
always be performed holding a GDA94 latitude and longitude and ellipsoidal height.
In the example project there are three marks with known horizontal coordinates (2D) and ellipsoidal
heights (h). Three marks have AHD heights (e) to the required quality (PM3, PM5 and PM8).
As a GDA94 and ellipsoidal height seed point was used when processing baselines, that point should
Fixed have 2D and h boxes ticked (as below).
Select Adjust
A message will display about unresolved project computation errors.
Click Yes to continue the network adjustment.
A summary of the adjustment results will displays on the Results tab. If the Reference Factor is close
to 1.00 and the Chi Square Test has passed, the network is tight within itself and the a priori variances
are realistic.
The Network Adjustment Report should be viewed by selecting Reports > 5. Network Adjustment
Report from the ribbon or the clipboard icon in the Adjust Network panel.
39
The example project has a very good Reference Factor, has passed the Chi Square test and the
Degrees of Freedom are large.
The Reference Factor is an indicator for testing the quality of measurements and isolating suspect
measurements. It is a measure of the magnitude of observational residuals in an adjusted network as
compared to estimated pre-adjustment errors.
The Chi Square Test is used to test the hypothesis that the a priori variances (estimated errors for
observations before a network adjustment is performed) for all observations in the network as a whole
are realistic based on the adjustment. If the a priori variances for all of the observations as a whole are
in agreement with the adjustment, the A posteriori Variance factor (variance of unit weight) will
approach 1.00. The Reference Factor (standard error of unit weight) is the square root of the A
posteriori Variance Factor.
The Reference Factor is about 1.00 when the amount of adjustment to the observations equals the
estimated errors:
if the Reference Factor is less than 1.00, then the errors have been overestimated and the
network exceeds the precision estimated for it
if it is greater than 1.00, it indicates one or more of the errors have been underestimated.
If the Reference Factor is too low or too high and the Chi Square has failed, some vectors may be
flagged as outliers in the adjustment. Any outliers should be assessed and disabled if necessary
before applying a weighting strategy. A weighting strategy should only be applied if the Reference
Factor is below 2.0. If its above 2.0 the network has significant problems which need to be resolved.
Where the Reference Factor is greater than 1.00, remove all outliers or statistically justify them and
apply a scaler weighting strategy to the estimated errors to bring them in line with the residuals of the
observations. Vide Section 6.2.1 for Outlier assessment.
Applying a weighted strategy will improve the initial a-priori error estimates for the observations (vide
Section 6.2.3).
40
6.2.1
View network adjustment report
From the Adjust Network panel, click on the Network Adjustment Report icon
Pay particular attention to the Adjusted GPS Observations and Covariance Terms sections.
Observations with a standardized residual that fails the Tau criteria are displayed in red and are
termed outliers. Outlier baselines should be assessed and can be disabled if required (vide
Section 6.2.2). In the example below, the outlier baselines were assessed and accepted as the
A-posteriori Error, Residual and Precision PPMs were deemed acceptable in the context of the
network.
If after assessment the outlier baseline is deemed to not meet requirements and is critical to the
project, it will need to be re-observed.
Peruse the Covariance Terms section of the report. For very good quality networks the Horiz Precision
(PPM) should be less than 5ppm. Shorter baselines will often be higher than 5ppm due to the short
baseline length. As a guide shorter lines (approx. less than 4km) should be less than 15ppm.
Empirically 7.5ppm equated to the old 1st Order and 15ppm to 2nd Order.
An example of a very good PPMs (Horz: 0.973 and 3D: 1.158).
Baseline example below has a short length of 448.385 m which has elevated the Precision PPMs.
This result is acceptable as once calculated out, 10.201ppm over 448.385m is approx. 5 mm. In
addition to a good A-posteriori error and Residuals in the Adjusted GNSS Observations section gives
confidence in the quality of the baseline.
If the adjustment has passed the Chi Square test and there are no outliers, save the report in an
appropriate format or print to pdf, and then close the report. In the Adjust Network window, select OK
to finish the adjustment. Jump to Section 6.2.5 Calculate SU.
If the adjustment has failed the Chi Square test and there are no outliers, close the report and skip to
Section 6.2.3 to apply a weighting strategy.
41
6.2.2
Disable an outlier baseline vector
If the network has sufficient redundancy the outlier may be able to be disabled. This should only be
done after carefully evaluating the baseline.
To disable, in the Project Explorer pane, navigate to the relevant baseline, right click on it and
choose Disable Vectors. A Clear Adjustment window will open, select Clear Adjustment.
Re-run the adjustment Adjust Network, ensure the fixed coordinates are selected correctly > Adjust.
Re-check the Network Adjustment Report for outliers.
If there are no outliers, close the report.
6.2.3
Apply a weighting strategy
If the Chi Square test still fails once outliers have been either disabled or investigated, a weighting
strategy can be applied to improve the initial a priori error estimates.
In the Adjust Network window, select the Weighting tab. In the Post processed Vectors section, the
network reference factor is shown in the left box (as below, 1.55). The goal is to get the reference
factor to 1.0. The Reference Factor is about 1.00 when the amount of adjustment to the observations
equals the estimated errors:
if the Reference Factor is less than 1.00, then the errors have been overestimated and the
network exceeds the precision estimated for it
if it is greater than 1.00, it indicates one or more of the errors have been underestimated.
To apply a scalar to the estimated errors, click on the Postprocessed vectors star button
. TBC
will compute a new scaler using the network reference factor from the last network adjustment.
The minimally constrained network can now be re-run by selecting Adjust. The network Reference
Factor is now 1.00 (or close to it) and the Chi Square test has Passed.
Select Ok to save and close the Adjust Network panel.
The project is now ready for a Constrained Adjustment (vide Section 7).
42
6.2.4
Review the Network Adjustment Report
To view the Network Adjustment Report, from the ribbon use the drop arrow under Reports
to select 5. Network Adjustment Report.
The Settings and Statistics are summarized at the top of the report and are a repeat of the information
in the Results tab of the Adjust Network panel. The Control Coordinate Comparisons are worth looking
at as differences are shown to all entered coordinates and height values. Generally the CORS
ellipsoidal heights should agree with each other but it is quite common to see differences for AHD
heights. This is due to inaccuracies in the relationship of the ellipsoid to AHD (N values) and of CORS
stations to local AHD.
As can be seen in the example project, CORS2 and PM1 are part of the QEHA adjustment and have
very good horizontal agreement with the held station CORS1. This result gives confidence the
horizontal component of the Constrained Adjustment will produce a good result. The ellipsoidal height
of CORS2 also agrees with CORS1 ellipsoidal height.
The known AHD heights of PM1, PM3, PM5 and PM8 show larger differences that suggests the
relationship of the CORS ellipsoidal height to local AHD via AusGeoid09 has some inaccuracy. The
small spread in AHD height difference between PM1, PM3, PM5 and PM8 suggests that when held in
the constrained adjustment, there should be no problems holding all of these marks for AHD height.
Assess the error ellipses to ensure the quality of the resultant network will meet the project
requirements. The project should now be assessed for Survey Uncertainty as per SP1.
Where global latitude and longitude have been entered for control marks, TBC will still display
easting and northing differences in the Control Coordinate Comparisons. Ellipsoidal heights will be
correctly displayed as difference in Height.
43
6.2.5
Calculate survey uncertainty (SU)
SP1 defines Survey Uncertainty (SU) as - the uncertainty of the horizontal and/or vertical coordinates
of a survey control mark relative to the survey in which it was observed and is free from the influence
of any imprecision or inaccuracy in the underlying datum realisation. Therefore, SU reflects only the
uncertainty resulting from survey measurements, measurement precisions, network geometry and the
choice of constraint. A minimally constrained least squares adjustment is the preferred and most
rigorous way to estimate and test SU. SU is expressed in SI units at the 95% confidence level.
SU is similar to the previous method of assessing for Class in that it is an expression of the quality of
the network within its self, free of any influence from datum.
The minimally constrained adjustment has to be performed at the two sigma (95%) confidence level,
however SU is calculated using one sigma error ellipse values. Therefore the 95% error ellipse axes
must be scaled to one sigma by dividing by 2.448 before calculating the uncertainty.
There should generally be very little variance in the error ellipses sizes across the adjusted marks.
Find the worst error ellipse value and assess it for SU.
Use the GNSS Uncertainty Calculation spreadsheet or 12d macro to perform these calculations.
44
Constrained adjustment
A constrained adjustment can now be performed on the network which will compute adjusted
coordinates for the measured marks relative to the existing known control marks. This is done by
constraining the remaining control points with their known coordinates.
This step can be completed using a few different approaches:
add one known constraint at a time (starting with horizontal), adjust and review. Repeat for all
constraints
add all known horizontal constraints, adjust and review. Add all known vertical constraints,
adjust and review.
The most common is the first one, an incremental approach. This approach makes it easy to check
that each newly added point is not contributing to errors in the adjustment.
The second approach may be used when the known control points are regularly used and have been
found to fit together very well. This fit doesnt guarantee success.
7.1
Run the Constrained Adjustment
The minimally constrained adjustment showed that the observations fit together and a fairly rigid
network is defined. It can be assumed that if any large errors are present in the fully constrained
adjustment they are a result of the control point coordinates. Any ill-fitting control points should not be
constrained.
Run the Constrain Horizontally part of the adjustment as below in 7.1.1.
7.1.1
Constrain Horizontally
If a scalar weighting was applied to the minimally constrained adjustment, that adjustment should be
cleared before undertaking the constrained adjustment.
From the ribbon, select Clear Adjustment Results.
Select Adjust Network
and then the Fixed Coordinates tab. Tick on the 2D box for the next
best (after the seed) horizontal control mark.
45
Select Adjust. Select Yes on the Question window. All going well, the adjustment will still pass the
Chi Square test. If it fails, check the reference factor and ensure its not too high. Ideally it should be
below approximately 1.5 and definitely below 2.0. If its not un-constrain the newest constrained mark,
tick on another one, adjust and re-assess.
Now is a good time to review the Network Adjustment Report. Select the
icon in the Adjust
Network mini ribbon. The primary focus is checking the Control Coordinate Comparisons section. This
compares the entered control coordinates to their current adjusted coordinates. These comparisons
give an early indication as to what marks fit together. This knowledge may change the strategy of the
order in which order additional marks will be fixed and the adjustment run. Marks that may potentially
not fit the network should be the last to be fixed and run.
In the example project below, PM1 appears to be a good horizontal fit to the currently constrained
CORS1 and CORS2. The ellipsoidal height of CORS2 fits well to the currently held CORS1 ellipsoidal
height.
However the comparisons show the four known AHD heights compare well with each other but do not
fit to the ellipsoidal heights of the two CORS. This indicates the relationship between CORS ellipsoidal
heights and local AHD via AusGeoid09 isnt well defined and shows an approximately 70 mm offset.
46

Where global latitude and longitude have been entered for control marks, TBC will still display
easting and northing differences in the Control Coordinate Comparisons. Ellipsoidal heights will be
correctly displayed as difference in Height.
The other important information is the Azimuth Rotation and Scale Factor in the Adjusted GNSS
Observations. Azimuth Rotation should be very close to zero and Scale Factor very close to one. If
theyre not, the network is getting distorted by the held coordinates. This could be because one mark
has had incorrect coordinates assigned to it, the two marks are from different adjustments or are of
different quality levels (Uncertainty). This is generally more prevalent when only two marks are held in
the horizontal as the Chi Square test would normally fail when three or more marks are held.
Once happy all is ok, re-select the Fixed Coordinates tab and tick on 2D box of the next known
horizontal value. Re-run the adjustment. Again, dont worry too much about the Chi Square test
passing. If the reference factor stays about the same, continue ticking on 2D boxes until all known
horizontal marks are constrained.
If the Reference factor moves significantly at any step, untick the last constrained mark and tick on the
next known mark. If the reference factor remains approx. the same, add subsequent marks until all but
problem marks are constrained (ticked). As a last step, try ticking on the problem mark and adjust. If it
still significantly increases the reference factor, untick the mark and run the adjustment.
After finishing constraining horizontal marks, check the Network Adjustment Report for any issues with
Azimuth Rotation and Scale factor before moving onto constraining the vertical.
In the example project, when PM1 is 2D constrained the adjustment fails the Chi Square test but not
badly (as below). From the previous adjustment, the adjusted coordinates of PM1 were 11 mm in
Easting and 6 mm in Northing different to the Form 6. In this case, applying a scaler to properly model
the network error is an acceptable strategy.
47
For projects where adjusted heights are not required from the GNSS network:
if the Chi Square test passes, select OK and skip to Section 7.2
if the Chi Square test fails, review the network adjustment report Section 7.1.1.1 and then
skip to Section 7.13.
7.1.1.1
Review the network adjustment report
Once happy with the horizontally constrained adjustment, check the Network Adjustment Report for
any issues. The most important area to look is the Azimuth Rotation and Scale Factor in the
Adjusted GNSS Observations section. The Azimuth rotation should be small and the Scale factor very
close to one. If theyre not, the network is getting distorted by the held coordinates. This could be
because one mark has had incorrect coordinates assigned to it, marks are from different adjustments
or marks are of differing quality levels (uncertainty). This is generally more prevalent when a large
scalar weighting has been applied.
7.1.2
Constrain vertically
Now the network is successfully constrained in the horizontal, repeat the process by incrementally
constraining the marks with known AHD values (or ellipsoidal heights if required).
The amount of work put into the vertical will depend on how critical heights from the GNSS network
are to the project. Projects that require good AHD heights from the GNSS network, require carefully
selected marks to be observed in the field. A bare minimum of four AHD marks should be connected
to. Along with other factors, session times should be determined based on what height quality is
required rather than the required horizontal quality as height quality is much harder to achieve.
Getting the network to pass when constraining AHD heights can be harder than the horizontal. This is
due to the larger errors associated with working with AHD and GNSS in general. Even carefully
chosen 3rd Order NLN marks from the same level run can sometimes cause problems.
Do not constrain published ellipsoidal heights with published AHD heights as the two generally dont
mix. The constrained adjustment should always be performed on one datum, either ellipsoidal or AHD.
Where Ellipsoidal heights are to be constrained, AHD elevations will subsequently be derived
from ellipsoidal heights using AUSGeoid09. Be aware that, often, these derived AHD elevations
will not match local AHD heights due to inaccuracies in AUSGeoid.
Firstly untick the h box of the seed mark.
Tick the e box of the best AHD mark.
48
PM3 is a 3rd Order NLN mark and the highest accuracy height mark in the network so it has been
chosen as the first AHD mark to hold.

Tick on the h box of the mark with the next best (after the seed) ellipsoidal height (look at Vertical
Uncertainty from the Reg 13 or Globe derived Form 6).
Select Adjust to run the adjustment.
Repeat the incremental approach as used with horizontal until all known ellipsoidal heights are
constrained or have been rejected.
Adjust the network. Repeat the incremental process used with the horizontal constraints. If the
adjustment passes the Chi Square test, add another mark. If it doesnt pass and makes the Reference
Factor significantly worse, untick the previous mark and try another one. If after constraining a mark,
the Chi Square test fails but the reference factor remains the same or only slightly changes, proceed
to constrain the next mark for elevation. As long as the reference factor is reasonable, applying a
scalar weighting (vide Section 7.1.3) is an appropriate strategy. If the reference factor is too large
(more than 2.0) the network will get stretched or distorted too much.
Depending on the need for good vertical heights, keep trying combinations until satisfied with the
vertical component and the Reference Factor is acceptable (less than 2.0).
49
If after applying the last constraint, the network passes the Chi Square test, select OK in the Adjust
Network panel and skip to Section 7.2.
If the adjustment fails the Chi Square test and the Reference Factor is reasonable (less than 2.0) go to
Section 7.1.3.
7.1.3
Apply a scaler to the network
If the adjustment has failed the Chi Square test and the reference Factor was acceptable (less than
2.0) a scaler will need to be applied. This will scale the network to fit the control.
Select the Weighting tab in the Adjust Network window. In the Post-processed vectors section, left
click on the
icon to set the scaler for the next adjustment to be the same as the reference factor
for the last adjustment.
Select Adjust, choose Yes to continue on the unresolved question and the Chi Square test will pass
and the Reference Factor will be 1.00 or very close to it.
7.2
Constrained adjustment network adjustment report
The Network Adjustment Report for the constrained adjustment should now be examined closely.
Open the report using the TMR GNSS ribbon using the drop down arrow under Reports
to
select 5. Network Adjustment Report.

Review the Settings and Statistics to ensure all is ok. Peruse the Control Coordinate Comparisons.
Look at the errors in the Adjusted Grid Coordinates. If the network has been observed and processed
correctly the errors should be small. The Elevation Error may be large for marks with entered
ellipsoidal heights due to inaccuracies of the ellipsoidal to AHD relationship. A visual representation of
50
the errors can be accessed by left clicking on a point name. The errors with visualisation will be shown
in the Adjust Network window. A number of marks can be shown at the same time by dragging a
window around the required marks and vectors.
Returning to the report, the Error Ellipse Components should be less than the quality level planned for.
The Transformation Parameters in the Adjusted GNSS Observations section should be checked for
acceptability.
Save the report in an acceptable format such as web archive .mht or print/save to pdf.
7.3
Calculate Project Positional Uncertainty (PPU)
Positional Uncertainty (PU) is the uncertainty of the horizontal and/or vertical coordinates of a survey
control mark with respect to the defined datum and represents the combined uncertainty of the
existing datum realisation and the new control survey. That is, PU includes SU as well as the
uncertainty of the existing survey control marks to which a new control survey is connected. A fully
constrained least squares adjustment is the preferred and most rigorous way to estimate and test PU.
PU is expressed in SI units at the 95% confidence level.
PU shall be estimated and tested by way of a constrained least squares adjustment.
In order to achieve the most rigorous estimates of position and uncertainty for survey control marks,
the system of survey measurements (excluding the constraints) should be including within the
jurisdiction adjustment (vide SP1 Guideline for the Adjustment and Evaluation of Survey Control v2.1).
In Queensland this requires the project baselines to be included in the QEHA statewide adjustment.
Therefore when the projects PSM Form 6s details are entered or updated, Positional Uncertainty
should be left blank.
TMR can assess for Positional Uncertainty of the project (PPU) to quantify the quality of the adjusted
positions to the datum control marks used.
51
Assess for PPU using the marks error ellipses. The constrained adjustment is performed at the
two sigma (95%) confidence level, however PU is calculated using one sigma error ellipse values.
Therefore the 95% error ellipse axes must be scaled to one sigma by dividing by 2.448 before
calculating the positional uncertainty.
There should generally be very little variance in the error ellipses sizes across the adjusted marks.
Use the GNSS Uncertainty Calculation spreadsheet or 12d macro to perform these calculations.
52
Output final adjusted coordinates
A number of different outputs are required depending on intended use of the adjusted coordinates and
the quality of the network. The project should also be archived.
8.1
Ascii output
Ascii output is useful for importing final coordinates to 12d or uploading to an instrument for use as
control stations.
From the ribbon choose Select Points
and then tick on Fixed in Adjustment
and Adjusted and then OK. All the points in the Project Explorer pane will highlight yellow and the
point names will turn purple (This step can also be completed by using Ctrl or Shift left click on the
required stations in the Project Explorer pane).
Select Export
from the ribbon.
Select P,E,N,elev,Code from the list under the Custom tab.

The Data field should already be filled out with the number of points selected in the previous step.
Enter a suitable file name and ensure the path is set correctly to the required folder.
Select Export. File will be exported. Use Explorer to navigate to the folder, open the file and ensure
the data is correct.
53
8.2
Point list report
The Point List report is a neat report of the final coordinates which may be of use to include in a
Fieldbook. A couple of useful pieces of information are missing from the default report which can be
added by editing the report content.
From the ribbon select Reports > Report Options
Find Point List in the list of reports. In the Settings section of the bottom pane, find Combined Scale
Factor and left click on Hide to expose the drop down menu and select Show. Expand the Header
section below Settings and find User Information. Click Hide and select Show.
To generate the report. Select from the ribbon Reports > 7. Point List.
The report will open in a new window. Save the report to pdf by using the drop down beside the 3.5
floppy icon and selecting pdf.
Close the report by clicking the
in the top right of the Point List window.
54
Output of network for DNRM
GNSS control surveys for TMR form part of the states survey and mapping infrastructure and are of
value to the community because they contribute to the state's economic, environmental and social
development as required under the Surveying and Mapping Infrastructure Act 2003 and associated
Regulations. TMR can meet these obligations and also improve the states high quality control network
by submitting GNSS networks to DNRM for inclusion in their state-wide adjustment. This data can also
help improve the relationship between ellipsoidal and AHD heights, thus improving future AusGeoid
versions.
9.1
Creating Rinex output
Observation sessions are required to be written to Rinex format. CORS or data imported from
non-Trimble receivers will already be in Rinex format and therefore wont require conversion. Existing
files must have correct heights and station identifiers. Rinex files shall be output in Rinex version 2.11.
From the ribbon, select Convert to RINEX from the Export tab
From the Convert to RINEX window, select Tools > Options. In the Agency field replace text with
TMR, replace the Observer name as applicable, and ensure the Default Format is set to
RINEX v2.11 (these settings should now stay as the default). Select Ok to continue.
The observations files can be imported now the options have been set.
55
Select File > Open and navigate to the raw observation T01 or T02 files. Select the required files and
select Open.
The files will be imported and scanned by the software. The information for each file can be perused if
required. Simply highlight an observation file in the left pane and its details will display in the right
pane. Ensure the information is correct. This should include RINEX file version, the Agency and
Observer name as entered in Options above. If the marker name and antenna height were entered in
the field these entries will be filled but the height displayed will be different as it has been converted to
a true vertical height to the Antenna Reference Point (ARP).
If these details have not been entered in the field, the Marker Name and Antenna offset, meters
should be carefully entered for each of the observation files. It is important to remember that the height
must be the corrected to true vertical height to the ARP.
In the example below, the slant height measured in the field was 1.354 to the centre of bumper of an
R8. The height has been adjusted to 1.296 true vertical to ARP.
56
To convert the files, select File > Convert Files.
The files will convert and the result for each file will appear in the bottom pane of the window.
Each file will be listed and all going well will report success.
Exit the Convert to RINEX window.
Usually three files will be generated for each raw observation file but is dependent on what data was
recorded.
15G is the Glonass Navigation Message file with the 15 representing the year
15N is the GPS Navigation Message file
15O is the Observation file.
9.1.1
Submit to DNRM
DNRM require the Rinex files, pdf of the booking sheets and the photos taken for verification of the
physical mark; the receiver ID; the height measurement at both the start and finish of the session; and
any obstructions that may affect the processing.
Submit to your local DNRM contact or Geospatial Technologies who will pass it on.
57
10 Project archival
The Archive function in TBC allows the project (.vce) file and its associated subfolders to be saved in a
compressed (.zip) file of the same name. This is useful for project archival purposes or emailing a
project.
To make a complete record of the GNSS network project copy any related files such as the PSM and
Reg 13 pdfs into the project folder (folder of the same name as the project that sits beside the
.vce file). Any file imported into the project like raw obs or ephemeris do not need to be copied in as
they already there courtesy of the import process.
Firstly, use the ribbon to Save and Close the project.
From the mini ribbon choose Archive Project
Navigate to the project folder and select the project (.vce) file and select Save.
The archival zip function will run and create the file (e.g 123456 Bruce Hwy 6 Mile Crk.zip) in the same
project folder as the .vce.
Include this archival file in the project deliverables.
58
Appendix A Configuring TBC

Configuring TBC as below helps TBC perform as expected.
Firstly, browse to L:\spatialConfig\Surveys\Trimble\TBC and copy TMR TBC Ribbon v3.50_v2.bin
to C:\SharedData\Apps\TMRCust\TBC.
Open Trimble Business Centre 64 bit v3.5.
Select File > Options > File Locations
Change the Project Management and Office Synchronizer folders to match those shown below.
You may need to create the folders if they dont already exist.
After filling out the Project Management folder, untick and then re-tick the Use Project Subfolders
option.
59
Appendix B Setting up the TMR Ribbon

This section will detail how to setup the TMR GNSS ribbon as used by this manual. The TMR GNSS
ribbon has been set up to provide easy access to the majority of the features required to import,
process, adjust and report a Fast Static GNSS Network. Features are presented in a logical order from
left to right to represent the flow of the processing from project creation to archival of the finished
project.
Select Import from the Customize Ribbon tab of the Options window.
Browse to C:\SharedData\Apps\TMRCust\TBC and select TMR TBC Ribbon v3.50_v2.bin.
Select Open and OK.
The ribbon should update to look as below (ribbon has been cut in two to fit in this document).
Left click on Project Explorer so the Project Explorer pane is displayed on the left of the Plan View.
If the Flags Pane isnt already highlighted yellow, left click on it to turn the Flags Pane on so errors
and warnings during processing can be seen.
60
Appendix C GNSS planning in TBC

The Online Planning service in Section 2 is easier to use and doesnt rely on an almanac having been
downloaded recently. This option is presented as sometimes planning needs to be completed when
away from internet connectivity.
From the ribbon select the Planning tool

window
. Select the Station Editor icon from the planning
. Fill in the details as applicable including latitude, longitude and height of the project, start
date and time, and the duration of the required planning session.
Select Apply > OK.

If a recent almanac file isnt available use the link below to download from the Trimble website.
http://www.trimble.com/Support/GPD_Data_Resources.aspx
Right click on GPS/GLONASS almanac in Trimble Planning format and select Save target as.
Save the alm file to an appropriate folder.
61
In Planning window, select Almanac > Import > Almanac.
Navigate to where the alm file was saved, highlight the file and Open. A new window detailing how
many satellites were imported will pop up. OK it.
Use the various Graphs such as Number of Satellites
, Skyplot
, Visibility
and DOPs
to plan the fieldwork.

Exit when finished.
62
Appendix D - Settings for Automatic Orbit Download

Settings must be correct for the Automatic Download to work. Typically the default settings are correct,
however if they arent, please check the settings below.
Select
from the TMR GNSS ribbon. From the resultant window (below) right
mouse of IGS Final Orbits and select Properties.
Providers tab should be set as below as a default and shouldnt require changing.
Contact tab isnt relevant.

In the Security tab ensure Public Access is selected.
In the FTP tab, the FTP Protocol should be set to Active Mode.
OK when finished.
63
Appendix E Create a new Import Format

If a new Import format is required the following steps can be adapted to various situations. This
procedure will create an Import format for a control mark with Latitude and Longitude coordinates
(Degrees Minute Second format) and an ellipsoidal height (m).
Use the menu arrow beside Import
in the ribbon to access the Import
Format Editor.
Highlight P,L,L,h,Code(Global) and select Copy.
A copy of the highlighted Definition Name will be created and appear in the list. Left mouse click in the
Definition Name field to edit the name {P,L,L,h,Code (DMS Global)}. Select Next.
64
Description and Search Type window allows editing of the Description and the Type. Edit the
description as necessary. As a comma delimited file is to be created, leave Delimited selected. Select
Next.
A Select General Properties window should appear but does not require any editing.
Select Next on it.
The new window Fields allows changes to the Fields.
Select the Latitude (Global) tab and use the Units drop down to select Degrees minutes seconds.
Ensure the Apply to all field is ticked on, as this will also change the Longitude tab. All other fields
should be correct.
Select Finish.
65
Appendix F Baseline Processing Example High RMS

Example of an extremely high RMS but tight Horiz and Vert Precisions on baseline STNB STN1.
Baseline Processing Report for the high RMS baseline above STNB STN1 (S130).
66
Residual plot for GPS satellite #12 for baseline S130 showing large spike in the data.
Session editor for B130 (S130) which doesnt show anything wrong, like cyclic slips, in the data.
67
Glonass satellites have been turned off and the baseline re-processed. RMS is now small.
Baseline processing report for S130 with Glonass satellites not used.
68
GPS satellite #12 residuals now has no spike and is tight around the average.
69
Appendix G Import Known Control Data

Below is an example of importing P,E,N,elev,code where not every mark has a known value of
sufficient quality to import. PM1 has only an Easting and Northing. PM3, PM5 and PM 8 have valid
AHD heights.
70
Appendix H Processing and Adjustment Workflow

Baseline Processing
1. Import Observation files and check raw data in
2. Import Ephemeris (if required), Import known coordinates (if required)
3. Assign seed coordinate
Determine why:
4. Assess baselines for overlap
5. Process baselines
6. Analyse results
fixed or float
view baseline report
error in user entered info
noisy data, cyclic slips
Flags:
No
Yes
exclude poor data
High RMS:
No
Yes
bad satellite
multipath
disable poor baseline
process without Glonass
process with final ephemeris.
7. View Baseline Processing Report
8. Loop closure report

Minimally Constrained Network Adjustment
9. Assign a seed point

Determine why:
10. Run the Adjustment
Review Adjustment report
Identify, assess and disable outliers if

necessary
11. Chi Square test passes Yes No
Modify weighting strategy (apply a

scalar).
12. Review Network Adjustment Report

-
including error ellipse information and check other known coordinates
save report.
13. Calculate Survey Uncertainty (SU)
71
Constrained Network Adjustment

14. Run the constrained adjustment
15. Reference factor is close to one and Chi Square test passes
Yes
No
Modify weighting strategy (apply a

scalar)
16. Review Network Adjustment Report

-
including error ellipse information
save report as pdf
17. Calculate Project Positional Uncertainty (PPU)
18. Output final adjusted coordinates in suitable format
19. Output for DNRM
20. Archive project
72

TBCManual Dec 15

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

TBCManual Dec 15

Hochgeladen von

Copyright:

Verfügbare Formate

Manual

Trimble Business Centre v3.5 Planning, Processing

Introduction and background information ..................................................................................1

Preparation for success Get the fieldwork right! .......................................................................... 1

Verification photos .......................................................................................................................... 1

TMR GNSS ribbon and quick access toolbar ................................................................................. 1

GNSS planning ...............................................................................................................................4

GNSS planning online .................................................................................................................... 4

Create and setup a new project....................................................................................................6

Create a new project ....................................................................................................................... 6

Project settings ............................................................................................................................... 7

Save a new project ....................................................................................................................... 10

Import data .................................................................................................................................. 11

Download data .............................................................................................................................. 11

Import GNSS Data files ................................................................................................................ 11

Ephemeris data ............................................................................................................................. 13

Import known coordinates ............................................................................................................. 16

Baseline processing ................................................................................................................... 19

Seed coordinate ............................................................................................................................ 19

Baseline assessment using the time based view ......................................................................... 21

Process Baselines ........................................................................................................................ 23

Baseline processing report ........................................................................................................... 26

Errors and problem solving ........................................................................................................... 28

GNSS loop closure report ............................................................................................................. 35

Minimally constrained adjustment ............................................................................................ 37

Enter all known coordinate values ................................................................................................ 37

Perform the adjustment ................................................................................................................ 39

Constrained adjustment ............................................................................................................. 45

Run the Constrained Adjustment .................................................................................................. 45

Constrained adjustment network adjustment report ..................................................................... 50

Calculate Project Positional Uncertainty (PPU) ............................................................................ 51

Output final adjusted coordinates ............................................................................................ 53

Ascii output ................................................................................................................................... 53

Point list report .............................................................................................................................. 54

Output of network for DNRM ..................................................................................................... 55

Creating Rinex output ................................................................................................................... 55

Project archival ........................................................................................................................... 58

Appendix A Configuring TBC ............................................................................................................. 59

Planning, Processing and Adjusting GNSS Networks

Introduction and background information

Preparation for success Get the fieldwork right!

verification of the physical mark showing its identifier

any obstructions that may affect the processing.

TMR GNSS ribbon and quick access toolbar

This version of TBC enables a ribbon of commonly used commands/functions to be customised. A

Planning, Processing and Adjusting GNSS Networks

Steps to setup the ribbon are detailed in Appendix B.

Used to scale each observation variance just prior to network

A statistical measure of how well the adjustment results match the

The Australian Height Datum (1971) is the NGRS normal-orthometric

The national quasi-geoid model for converting between GDA94

Continuously Operating Reference Station. A survey control mark

Datum Control Survey

The number of independent measurements beyond the minimum

Queensland Department of Natural Resources and Mines

Geodetic Datum of Australia (1994)

Intergovernmental Committee on Surveying and Mapping

International Terrestrial Reference Frame

Planning, Processing and Adjusting GNSS Networks

Map Grid of Australia (1994)

National Geospatial Reference System is Australias authoritative,

National Level Network

Permanent Survey Mark