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. Station Coordinates and Velocities<br />

Table 10.2: List of programs used for coordinate/velocity estimation.<br />

Program Input data type Location<br />

Station Coordinates<br />

CODSPP code, zero-difference ”Menu>Processing>Code-based clock synchronization”<br />

MAUPRP phase, epoch-difference ”Menu>Processing>Phase preprocessing”<br />

<strong>GPS</strong>EST code and/or phase, zero- or ”Menu>Processing>Parameter estimation”<br />

double-difference<br />

ADDNEQ2 combination on NEQ level ”Menu>Processing>Normal equation stacking”<br />

Station Velocities<br />

ADDNEQ2 combination on NEQ level ”Menu>Processing>Normal equation stacking”<br />

to generate good a priori coordinates – as recommended in Section 3.5 – these preliminary<br />

coordinate results are not needed anymore. Otherwise, they may be used as a priori<br />

information in subsequent analysis steps.<br />

Although <strong>GPS</strong>EST is still the main parameter estimation program in the <strong>Bernese</strong> <strong>GPS</strong><br />

<strong>Software</strong>. It is gradually superseded by ADDNEQ2 when it comes to coordinate estimation.<br />

If final coordinate results are to be estimated, <strong>GPS</strong>EST is mainly used to create a normal<br />

equation file. The geodetic datum is then defined in a separate step with ADDNEQ2. Multisession<br />

solutions and velocity estimation are only possible with ADDNEQ2, anyhow.<br />

The program panels dedicated to datum definition are very similar in programs <strong>GPS</strong>EST<br />

and ADDNEQ2. The only differences are the minimum constraint solution and the velocity<br />

related panel, which both are not available in <strong>GPS</strong>EST. Figure 10.1 shows the corresponding<br />

ADDNEQ2 panel.<br />

The options let you select one of the datum definition types described in Section 10.2.2 and if<br />

necessary the corresponding constraints or minimum constraint conditions. The comboboxes<br />

next to each datum definition type offer several possibilities for reference site selection<br />

(stations to which the datum definition should apply). The FIRST, LAST, or ALL stations<br />

may be selected without any additional user interaction. The other three possibilities need<br />

further specifications in a subsequent panel. Reference sites can be picked by hand from a<br />

list of stations (MANUAL), taken from a station selection or sigma file (FROM FILE), or from<br />

a coordinate file depending on the corresponding flags (WITH FLAG). If coordinates are to<br />

be constrained FROM FILE, not only the list of reference sites but also the a priori sigmas are<br />

taken from that file. Sections 22.8.13 and 22.8.12 provide more details on station selection<br />

and station sigma files. Please note that the afore mentioned datum definition options do<br />

not apply for kinematic stations. The datum may be analogously defined for velocities in<br />

program ADDNEQ2.<br />

The a priori coordinates of the reference sites should always refer to the current epoch of<br />

the processed session. If the reference coordinates refer to a different epoch they must be<br />

extrapolated accordingly with program COOVEL before being introduced in <strong>GPS</strong>EST. For<br />

program ADDNEQ2 this is not necessary, provided that an a priori velocity file is specified<br />

in the input panel. In that case ADDNEQ2 internally propagates the coordinates before the<br />

normal equation system is solved.<br />

Page 218 AIUB

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

Saved successfully!

Ooh no, something went wrong!