M2P GER 2015 Field Survey GPS St.

Guillaume

We registered GPS measurements on 29 and 30 September 2015 on four benchmarks in St.

Guillaume. The aim of the GPS analysis is to calculate the distances between these four points
(baselines) in 2015, and to compare them with distances in 2014, 2013, 2012 and 2011. The data
available each year can be found in the following table that presents in particular the antenna
heights for each station in each measurement session:

2011 05/10
PT01 1.022 m / slant;
0.990 m / vert.
PTI3 0.076 m / vert.
PT04 1.535 m / slant;
1.504 m / vert.
PT05 1.158 m / slant;
1.126 m / vert.
PT07 1.331 m / slant;
1.300 m / vert.
2012 24/10
PT01 1.160 m / slant;
1.128 m / vert
PTI3 0.004 m / vert.
PT04 1.084 m / slant;
1.052 m / vert.
PT05 1.122 m / slant;
1.090 m / vert.
PT07 1.650 m / slant;
1.619 m / vert.
2013 01/10 morning 01/10 02/10 morning
afternoon
PT01 0.997 m /slant; 1.302 m /slant; 1.160 m /slant;
0.965 m / vert. 1.271 m / vert. 1.128 m / vert.
PTI3 0.075 m 0.075 m 0.075 m
/vertical /vertical /vertical
PT04 1.211 m /slant 1.182 m /slant 1.177 m /slant
1.180 m / vert. 1.151 m / vert. 1.146 m / vert.
PT05 1.024 m /slant 1.184 m /slant 1.040 m /slant
0.992 m / vert. 1.153 m / vert. 1.008 m / vert.
PT07 1.303 m /slant 1.487 m /slant 1.143 m /slant
1.272 m / vert. 1.456 m / vert. 1.111 m / vert.
2014 30/09 01/10
PT01 1.085 m /slant ? 1.405 m /slant;
1.052 m / vert. 1.374 m / vert.
PTI3 0.076 m 0.113 m ????
/vertical /vertical
 PT04 1.072 m /slant 1.144 m /slant
1.040 m / vert. 1.112 m / vert.
PT07 1.165 m /slant 1.196 m /slant
1.133 m / vert. 1.164 m / vert.
Base RTK 1.020 m slant
tacheo 0.988 m vert.
Base RTK 1.327 m slant 1.399 m slant
parking 1.296 m vert. 1.368 m vert.
AVR1 0.000 m 0.000 m
Trimble NetRS
with antenna
ASH700936E
2015 29/09 30/09
PT01 1.008 m /slant 0.995 m /slant;
0.976 m / vert. 0.962 m / vert.
PTI3 0.076 m /vert. 0.079 m /vert.
PT04 0.873 m /slant 1.185 m /slant
0.840 m / vert. 1.153 m / vert.
PT07 1.693 m /slant 1.670 m /slant
1.663 m / vert. 1.640 m / vert.
Base RTK 1.296 m slant 1.418 m
parking, 1.254 m vert. slant ???
antenna 1.376 m vert.
TRM55970.0
AVR1 0.000 m 0.000 m
Trimble NetRS
with antenna
ASH700936E

A) GPS data analysis with GNSS Solutions

1) copy GNSS Solutions software (file 3.80.8.zip) and GPS data from USB key.
- Landslide measurements (points PT01, PTI3, PT04 and PT07) are in data_2015/static,
data_2014/static, data_2013, data_2012 and data_2011 directories.
- RTK positions of gravimetry / seismic lines are in data_2015/RTK directory

Install GNSS Solution

- decompress 3.80.8.zip
- execute setup.exe
- choose “install GNSS Solution”

Very good documentation: The manual is opened with “open user’s guide” button on the
top right. Use it !
Methodological test: To obtain an objective view of the measurement precision in 2014, the data
are split artificially into two sub-sessions, one in the morning, one in the afternoon. Analyzing
these sub-sessions separately allows comparing 4 independent estimates of the same distances
between the individual points of our network. However, analyzing 2.5 hours of data should be a
little less precise than analyzing 5 hours of data. Therefore, two analyses could be performed, 1)
one analysis with the two sub-sessions of 2.5 hours; 2) one analysis with a single session over 5
hours. The results of this comparison should apply to the 2011 and 2012 measurements, where
only a single daily session of 4-6 h is available. In 2013, the 3 sessions have been acquired
independently (new antenna setup in each session) and are analysed as such, as well as the two
daily sessions in 2015.

2) start GNSS Solutions from “All programs” link or from icon on desktop :
Create separate projects for the three years of land slide measurements, and for one and two
session analyses (details below).
For each project:
Create processing directory (e.g. M2P_2014/two_sessions, M2P_2014/four_sessions,
M2P_2013)
Don’t load data immediately, first:

3) Define new antenna PG-A1 with:

Antenna Radius R = 0.1000 m
Slant Height Measurement Point Vertical Offset h = 0.0275 m
L1 Phase Center Vertical Offset = 0.03554 m
L2 Phase Center Vertical Offset = 0.05256 m
(Tools -> GNSS antennas -> “new” entry in the bottom of the list of predefined antennas),
don’t use predefined TPSPG-A1 antenna, no radius and height offset given !!!
OR: use vertical antenna heights – then the radius and height are not necessary !!!

4) Now load data for one measurement epoch (=one survey = 1, 2 or 3 sessions simultaneously)
from disk:
-fetch RINEX=Receiver Independent Exchange Format files from static directory:
Import raw data from files ...
We have no Ashtech format raw data (B or G-files), but data in receiver independent format
(RINEX).
Chose “File type” = “RINEX raw data”, not “Raw data files”.
Before importing the data files, correct the table with station names, antenna heights, height
type, antenna and receiver type. In case of error or doubt, this can be modified later.
- Antenna height and type valid for each data file are summarized at the end of this document.
- If you need to change site parameters after importation, left click twice the file number in
“files” tab !
- If you want to verify the definitions of the antennas, click “tools” -> GNSS antennas to get
the list, click on the antenna to get the parameters.

5) “Importing GPS data”

- If not yet done, indicate site name, antenna type, antenna height and height type
 - If measurements registered as “dynamic”, unselect.
- Use antenna type PG-A1 for fixed points PT01, PT04, PT05, PT07 and PTI3,
TRM55970.0 for base RTK. This antenna has also no radius and height offset in the
antenna table, so use vertical heights.

If you need to change site parameters after importation, left click twice the file number in “files”
tab !

If you want to verify the definitions of the antennas, click “tools” -> GNSS antennas to get the
list, click on the antenna to get the parameters.

6) “Control Sites” : none unless we have precise coordinates of a reference station. AVR1 could
be used as reference station, its coordinates in ITRF2008 are: N 44° 45’ 49.23511” E 5° 39’
11.64544” rad 6368.4296147562 km, or 44.95606993°N, 5.65323379°E, 923.6796 m.

7) process individually:
“OK to import, process and adjust”
- land slide network (PTI3, PT01, PT04, PT05, PT07): two experiences in 2014: one over
the whole day (directory one_session, rinex files session 0), and one where the data are
split in two successive sessions (directory two_sessions), one in the morning (rinex files
session 1 or a), one in the afternoon (rinex files session 2 or b).

8) Check processing:
What are the results (Proc_QA, Solution, Proc_D?_Conf, observation span, number of
satellites, …) ?
Which baselines can be improved ? Residuals ? Data quality ? Signal-to-noise ratio of
individual satellites ?
- Workbook window – Files – double right click on file number: S/N, elevation, carrier
phase – check raw data quality – if bad satellite, process
- Workbook window - Vectors – double click right on vector number – check residuals – if
bad satellites, process
- Process – Process options – table: deselected satellites (remove satellite totally from
baseline evaluation) and mask (graphically remove intervals of single or several satellites
from baseline evaluation)

9) Check precision of repeat measurements in 2015, 2014 and 2013 analyses of land slide
network):
- sort Vectors by left click – sort, by reference and rover station
- compare re-measured lengths and baseline components
- check Repeat Vectors: attention, baseline length is the best determined quantity, but in
Repeat Vectors, the error on the length is the square sum of the 3 component errors.

10) Discuss precision with respect to antenna setup, baseline component, observation span, …
Compare “one session” landslide network solution to “two sessions” in 2014. Compare the three
2013 sessions and two 2015 sessions. OK to detect motion of landslide since last years’
measurements ?

11) Run “Adjustment” (if not done yet) if you have repeat measurements to obtain single set of
solutions (baseline components, coordinates)

12) Extract numerical results using Export – Land Survey Report…(e.g. station coordinates,
baseline components, …): unselect what you do not want to export ! Find the Word file in process
directory, named project name.rtf.

13) Compare 2015 with previous analyses of 2011 to 2014 data, and then with previous results
given hereafter: check if the deformation measured between 2011 and 2015 could be seen in
former years. 2006 is only weakly constraint (Ashtech Promark 2 antennas, tripods centered with
level and plumb).

14) Write report (<12 pages):

- data analysis with GNSS Solutions
- interpretation and application of the positioning results
- include a graph to illustrate the results in terms of displacement (or displacement rate)
and its uncertainty.
- possible applications of GPS in your professional career
Results of baselines PT01-PTI3, PT01-PT04, PT01-PT07, PTI3-PT04, PTI3-PT07, PT04-
PT07

September 2006 (Adjustment Analysis):

DX DY DZ L
EM2006 + M2PGER 2006:
PTI3 - PT04 19/09/2006 12:35:44 -166,562 -0,025 -20,784 0,013 136,906 -0,010 216,606 0,030
PTI3 - PT01 18/09/2006 12:28:00 219,998 -0,006 397,929 -0,010 -175,032 -0,020 487,220 0,023
PT01 - PT04 19/09/2006 09:46:12 -386,560 -0,054 -418,713 -0,001 311,938 -0,053 649,657 0,076
PT01 - PT07 19/09/2006 10:18:48 -224,126 0,024 -677,048 0,013 227,555 -0,037 748,604 0,046
PT04 - PT07 18/09/2006 14:04:30 162,434 -0,750 -258,335 -0,954 -84,383 0,060 316,611 1,215
PTI3 - PT07 19/09/2006 09:30:28 -4,127 0,275 -279,119 0,050 52,523 -0,066 284,048 0,287

September 2007 (Adjustment analysis):

EM2007
PT04 - PT01 09/13/07 08:31:40 386.485 -0.025 418.714 -0.005 -311.988 -0.033 649.637 0.042
PTI3 - PT01 09/14/07 08:13:40 219.962 0.003 397.915 0.003 -175.083 -0.011 487.210 0.011
PTI3 - PT04 09/13/07 12:39:29 -166.523 0.039 -20.800 0.003 136.905 0.055 216.577 0.068

M2P GER November 2007:

PTI3 - PT07 27/11/2007 09:23:03 -4,130 0,005 -279,150 0,006 52,537 -0,010 284,081 0,013
PT07 - PT04 27/11/2007 09:55:19 -162,426 -0,001 258,380 0,002 84,395 0,003 316,647 0,004
PT07 - PT01 27/11/2007 09:37:09 224,134 0,006 677,066 0,005 -227,543 -0,005 748,619 0,009

October 2008 (Adjustment analysis):

EM2008
PT01 – PT07 10/10/2008 13:00:24 -224,121 -0,003 -677,095 -0,016 227,543 -0,033 748,642 0,036
PT04 – PT01 10/10/2008 12:23:49 386,561 -0,017 418,699 -0,001 -311,922 -0,012 649,641 0,021
PT04 – PT07 10/10/2008 08:12:00 162,440 -0,015 -258,396 0,003 -84,379 0,004 316,663 0,016
PTI3 – PT01 10/10/2008 09:12:27 220,014 -0,003 397,923 -0,002 -175,008 0,016 487,214 0,017
PTI3 – PT04 10/10/2008 12:23:49 -166,546 -0,006 -20,776 -0,003 136,914 -0,011 216,598 0,013
PTI3 – PT07 10/10/2008 13:00:24 -4,106 0,002 -279,172 -0,016 52,534 -0,011 284,102 0,019

October 2009 (Adjustment analysis):

EM2009
PT07 - PT04 02/10/2009 12:38 -162,484 -0,01 258,384 0,006 84,352 -0,008 316,668 0,014
PT07 - PTI3 02/10/2009 08:10 4,092 -0,009 279,169 -0,001 -52,529 -0,008 284,098 0,012
PTI3 - PT01 02/10/2009 08:47 220,029 -0,006 397,922 -0,003 -175,018 -0,007 487,223 0,01
PTI3 - PT04 02/10/2009 12:38 -166,576 -0,004 -20,785 -0,002 136,881 -0,002 216,601 0,005
PT01 - PT04 02/10/2009 12:38 -386,606 0,014 -418,707 -0,001 311,9 0,011 649,662 0,018

September 2010 (Adjustment analysis)

DX DY DZ L
PT07-PT01 29 septembre 2010 11:52:55.00 224.150 0.011 677.083 -0.002 -227.546 0.011 748.640 0.016
PT04-PT07 29 septembre 2010 11:21:34.00 162.472 0.006 -258.398 -0.005 -84.350 0.006 316.673 0.009
PTI3-PT07 29 septembre 2010 11:21:34.00 -4.132 0.004 -279.163 -0.002 52.496 0.008 284.086 0.009
PTI3-PT01 29 septembre 2010 11:52:55.00 220.017 0.003 397.920 0.004 -175.050 -0.008 487.227 0.010
PTI3-PT04 29 septembre 2010 12:59:02.00 -166.605 -0.007 -20.765 -0.015 136.846 -0.008 216.599 0.018
PT04-PT01 29 septembre 2010 11:52:55.00 386.622 -0.005 418.685 -0.005 -311.896 -0.004 649.656 0.008
Coordinate transformation X/Y/Z -> N/E/U
The baseline components are indicated as DX/DY/DZ in GNSS Solutions. The X/Y/Z coordinate
system is a geocentric reference system with the Z axis oriented along the rotation axis of the
Earth, the X axis penetrating the Earth’s surface at 0° N / 0° E (in the equatorial plane at 0°
longitude), and the Y axis perpendicular to X in the equatorial plane (penetrating at 0° N/ 90° E).
At the location of our network (about 44.953° N, 5.595° E, 801 m), we can transform
displacements or velocities in X/Y/Z direction into displacements or velocities in N/E/U direction
by applying a rotation matrix that is approximately the same for all stations in our small network.

-0.0975 0.9952 0.0000 Vx

Ve/Vn/Vu = -0.7032 -0.0689 0.7077 * Vy
0.7043 0.0690 0.7065 Vz

A full matlab routine to transform X/Y/Z coordinates into N/E/U at any point of the Earth is
given in the file M2PGER_DXDYDZ_to_dEdNdU.m.
B) GPS processing with RTKlib
1) Copy file rtklib_2.4.2_bin.zip and rtklib_2.4.2_p11.zip from USB key and unzip. The first one
contains the software documentation and some interesting data files, the second one contains the
best executables.
2) Start rtkpost.exe in rtklib_2.4.2_p11/bin directory.
3) RTKlib window 1:
- Indicate RINEX observation file (*.15o) of one Rover and one Base station (PT01 being the
base station)
- Indicate RINEX navigation file (*.15o) for both stations in the RINEX NAV field
- tick “solution” and indicate directory to write the solution file (*.pos) to.
4) Set the processing options according to RTKlib windows 2-6. In window 2 (settings 1) you
chose your positioning mode (static), observable (here L1+L2), type of filter (combined is
forward + backward for more stability), elevation mask, different models to correct
environmental/geophysical influences on the measurement (e.g; tropospheric delay), type of
satellite orbits, you can exclude one or more satellites, and you chose the satellite systems that
you want to use (the Topcon and Trimble receivers in the field register GPS and GLONASS). In
window 3 (settings 2), the most important choice is the ambiguity resolution “Fix and hold”. In
window 5 (Positions), you indicate antenna type and height, and the a priori position of your base
station (PT01 in our case, could also be AVR1, see coordinates above). In RTKlib window 6
(Files) you can upload the antenna phase center variation table that is in the RTKlib data
directory.
RTKlib window 7 shows the available satellites of one station with the data quality in color code.
You obtain this window by clicking on the circular icon at the right end of the RINEX OBS:
Rover or RINEX OBS: Base station line of RTKlib window 1. Here you can identify eventual
bad satellites to be removed from the analysis.
RTK window 1.

RTKlib window 2. RTKlib window 3.

RTKlib window 4. RTKlib window 5.

RTKlib window 6. RTKlib window 7.

5) To process the baseline, click on “Execute” in Window 1. When finished, you can visualize the
output file (*.pos) clicking on “View”. The “Plot” option shows the coordinate on a map, which
is not very interesting when chosing “single” as option for “Solution for Static Mode” in Window
4 (Output). The option “All” outputs all successive positions during the measurement span (every
second) that you can visualize as trajectory or time series in the “Plot” option of Window 4. The
strategy to first analyze with option “All” could allow you to identify segments of data with bad
ambiguity resolution to remove from the analysis in “Single” mode.
C) Online GPS Data Processing
Several services are indicated on http://www3.sympatico.ca/craymer/geodesy/gps.html#online.
Here we propose to use the service of NOAA (US National Oceanic and Atmospheric
Administration) that hosts the US National Geodetic Survey (NGS) that proposes an Online
Positioning User Service (OPUS):
http://www.ngs.noaa.gov/OPUS/about.jsp
and the online positioning service of Trimble:
http://www.trimblertx.com
The advantages of this service are: no software to install on your computer, little information
asked for the processing: RINEX file, antenna type and vertical antenna height.

In the case of OPUS, results are calculated from differential positioning with respect to three
reference stations close to the station, at 30 sec interval, and using only GPS data (no
GLONASS). Inconvenient: You get only absolute positions of each site. So you have to calculate
distances by yourself.
- Open web site
- Chose « Upload »
- Chose RINEX data file (*.14o) from your computer
- For Topcon PG-A1 antenna, chose model TPSPG_A1_6+GP
- For Trimble Zephyr II antenna, chose TRM55970.00
- For Trimble R8 antenna, chose TRM_R8_GNSS
- Enter antenna height
- Enter your email address
- Upload to rapid-static or static processing (with respect to file length <> 2 hours): after a
few minutes, the results are sent by email

Exploitation of OPUS results with respect to ITRF2008:

The positioning result is presented as station coordinates in different formats:
Longitude/Latitude/ellipsoidal height in degrees and meters, and in Cartesian coordinates in
meters (X/Y/Z).
ITRF2008 is a terrestrial reference frame based on position time series of hundreds of GPS,
DORIS, VLBI and SLR stations. For all stations included in ITRF, positions at a given epoch and
velocities are calculated. The velocities are in a “No Net Rotation” framework that minimizes the
velocities of all tectonic plates on the Earth’s surface.

Stations in Europe have a velocity of about 25-30 mm/yr towards the NE. To identify the
displacements of the land slide, we need, for each survey, to construct the baselines (the
distances) between the local stations, in particular with respect to station PT01 that is
geologically stable. This can be done easily by subtracting Cartesian station coordinates in
X/Y/Z, or differencing UTM horizontal coordinates (Northing/Easting). Then we can monitor the
repeatability of the baseline measurements between successive sessions and the time evolution of
the baselines from one year to the next. For transforming displacements in X/Y/Z into N/E/U, use
the rotation matrix mentioned above.

Discussion of the OPUS results:

- What is the positioning error of your OPUS analysis ? The error on baseline lengths and
components ?
- Compare 2011, 2012, 2013, 2014 and 2015 baseline lengths and components. Quantify
displacements, establish graph.
- Compare with GNSS Solution results.
In the case of TrimbleRTX, positions are calculated in Precise Point Positioning mode (PPP) in
the reference frame ITRF2008, with the data being decimated to 10 s. GPS and GLONASS data
are used. The output are absolute coordinates in ITRF2008 at two reference epochs, on the day of
the measurement, and at the reference epoch of ITRF2008, in 2005.0. TrimbleRTX corrects for
the Eurasia motion given in ITRF2008 to relate the present position to the position at the
reference epoch. To estimate an eventual motion of each point (other than the plate motion of
Eurasia), you can compare the positions calculated in successive years (2011-2015) at the same
reference epoch 2005.0. If the point is stable on the Eurasian plate, the position at reference
epoch 2005.0 should be the same over time. Otherwise, you can calculate the baseline
components in each year and compare them over time, as for OPUS.
Example of RINEX observation file (*yyo):

2.11 OBSERVATION DATA M (MIXED) RINEX VERSION / TYPE

teqc 2009Oct1 andrea 20111019 09:01:21UTCPGM / RUN BY / DATE
Linux 2.4.20-8|Pentium IV|gcc|Linux|486/DX+ COMMENT
teqc 2009Oct1 andrea 20111019 08:16:00UTCCOMMENT
BIT 2 OF LLI FLAGS DATA COLLECTED UNDER A/S CONDITION COMMENT
SNR is mapped to RINEX snr flag value [0-9] COMMENT
L1 & L2: min(max(int(snr_dBHz/6), 0), 9) COMMENT
pseudorange smoothing corrections not applied COMMENT
rx board ID: 8RS2BV98U80 COMMENT
PT01 MARKER NAME
PT01 MARKER NUMBER
-Unknown- -Unknown- OBSERVER / AGENCY
224791 TPS GB-1000 3.4 Dec,12,2009 p2 REC # / TYPE / VERS
-Unknown- TPSPG_A1 ANT # / TYPE
4500282.9887 440872.3410 4484234.0458 APPROX POSITION XYZ
0.9920 0.0000 0.0000 ANTENNA: DELTA H/E/N
1 1 WAVELENGTH FACT L1/2
7 L1 L2 C1 P1 P2 S1 S2 # / TYPES OF OBSERV
teqc windowed: start @ 2011 Oct 5 09:00:00.000 COMMENT
teqc windowed: end @ 2011 Oct 5 12:30:00.000 COMMENT
2011 10 5 9 0 0.0000000 GPS TIME OF FIRST OBS
15 LEAP SECONDS
END OF HEADER
11 10 5 9 0 0.0000000 0 16R22R12G25G12G29G14R21R11G30G02G09R13
R23G27G31G04
102160711.472 8 79458325.493 8 19138136.005 19138136.812 19138138.836
51.000 49.000
102530543.487 8 79745970.895 8 19193927.500 19193926.918 19193931.284
53.000 49.000
106793274.814 8 83215545.07647 20322086.684 20322086.283 20322092.086
53.000 46.0004
111024617.967 8 86512692.05946 21127283.872 21127283.485 21127287.378
48.000 40.0004
111232461.796 6 86674653.00145 21166834.160 21166833.418 21166839.689
40.000 30.0004
116216042.871 7 90557966.74644 22115182.109 22115181.435 22115186.313
42.000 29.0004
116995718.022 8 90996665.725 7 21863444.057 21863443.561 21863445.933
49.000 44.000
118083346.961 7 91842598.576 5 22097685.421 22097686.284 22097690.350
43.000 35.000
115193669.753 7 89761305.84345 21920627.035 21920626.964 21920630.734
45.000 30.0004
119382350.929 8 93025215.53346 22717708.379 22717707.723 22717711.014
49.000 40.0004
123125017.533 6 95941597.70141 23429917.635 23429917.282 23429931.834
37.000 7.0004
113499114.809 7 88277080.851 7 21254726.801 21254728.367 21254733.440
45.000 46.000
113822374.912 7 88528515.812 7 21277885.454 21277885.652 21277890.727
42.000 43.000
129145264.411 4 24575522.191
29.000
122899341.878 7 95765708.24445 23386963.492 23386962.855 23386967.176
44.000 33.0004
127580986.076 6 99413750.45342 24277854.090 24277853.956 24277860.698
40.000 17.0004
11 10 5 9 0 1.0000000 0 16R22R12G25G12G29G14R21R11G30G02G09R13
R23G27G31G04
102161197.932 8 79458703.853 8 19138227.229 19138227.937 19138229.923
52.000 49.000
102530802.650 9 79746172.466 8 19193976.022 19193975.465 19193979.816
54.000 48.000
…
…
…