08.06.2013 Views

Bernese GPS Software Version 5.0 - Bernese GNSS Software

Bernese GPS Software Version 5.0 - Bernese GNSS Software

Bernese GPS Software Version 5.0 - Bernese GNSS Software

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

10.3 Coordinate and Velocity Estimation in Practice<br />

Column (7): Lengths of the principal axes of the 3-dimensional error ellipsoid (in meters).<br />

Column (8): Orientation of the error ellipsoid: zenith distance of the longest axis, azimuth<br />

(counted positive in East) and elevation angle of the second axis (in degrees)<br />

Column (9): Lengths of the principal axis of the 2-dimensional error ellipse in the horizontal<br />

plane (in meters).<br />

Column (10): Orientation of the error ellipse: azimuth of the principal axis counted positive<br />

in East (in meters).<br />

Please note that the internal representation of coordinates and velocities is always cartesian.<br />

Where needed, they are transformed to a geographical system based on the local geodetic<br />

datum defined in the respective a priori coordinate or velocity input file.<br />

The estimated coordinates and velocities can be stored in corresponding result files. They<br />

are flagged according to the applied constraints (see Section 22.8.5). Stations not appearing<br />

in the current session are directly inherited from the a priori input files (but without<br />

flags). Consequently, the resulting files contain all stations from the a priori files, no matter<br />

if actually processed or not. In addition, ADDNEQ2 can write coordinate and velocity results<br />

in SINEX format. Both programs, <strong>GPS</strong>EST and ADDNEQ2, can store the covariance<br />

information of coordinate parameters.<br />

10.3.2 Static Network Solution<br />

A static network solution is the most common case of coordinate estimation. It is usually<br />

based on double-differenced phase observations with orbit and Earth-orientation information<br />

introduced from an external source, such as the IGS or CODE. In a static solution one set<br />

of coordinates is estimated for the entire session for each station. This is, of course, only<br />

valid if station velocities can be neglected for the processed time interval which is usually<br />

fulfilled for ground mounted tracking stations.<br />

The geodetic datum of the network must be defined based on some reference sites with<br />

well known coordinates, especially for non-global networks. To ensure consistency with the<br />

orbits and Earth orientation parameters, it is recommended to include some nearby stations<br />

from the global IGS network as reference sites. The precise IGS coordinates and velocities<br />

for these stations may then be used for datum definition purposes. A no-net-translation<br />

condition or tight constraints on the single reference stations are well-suited for a final<br />

coordinate solution.<br />

Of course it is advisable to check the performance of the fiducial sites and – if necessary<br />

– to remove problematic stations from the list of reference sites. One possible approach is<br />

demonstrated in theRNX2SNX processing example (sequence PID 511–514, see Section 20.4.2)<br />

utilizing program HELMR1.<br />

10.3.3 Multi-Session Solution<br />

Normal equation systems from subsequent sessions can be combined in a multi-session<br />

solution with ADDNEQ2. All coordinate parameters belonging to the same station (identified<br />

by the station name) are combined to one single set of coordinates. The resulting coordinates<br />

<strong>Bernese</strong> <strong>GPS</strong> <strong>Software</strong> <strong>Version</strong> <strong>5.0</strong> Page 221

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!