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.

22. Data Structure<br />

SVN-NUMBER= 2 MESSAGE-NR= 1<br />

0.125200000000000000D+04<br />

0.172800000000000000D+06<br />

0.265618431506390683D+08<br />

0.231909182620999993D-01<br />

0.931938345555999970D+00<br />

0.121485586332999995D+01<br />

-0.172696358223000002D+01<br />

0.211032279951000001D+01<br />

0.532093592404999958D-08<br />

-0.801640534402999908D-08<br />

....<br />

07-JAN-04 06:20<br />

Figure 22.19: Broadcast messages (BRD File). 40 lines of information per message.<br />

Directory: Campaign-specific directory ORB.<br />

Extension: PRE<br />

Content: Precise ephemerides.<br />

Created by: STDPRE (”Menu>Orbits/EOP>Convert standard to precise orbits”), RXNPRE (”Menu>RINEX<br />

>Import RINEX to <strong>Bernese</strong> format>Navigation files to SP3”), CCPREORB (”Menu>Orbits/EOP<br />

>Cut/concatenate precise orbit files”), PREWEI (”Menu>Orbits/EOP>Set accuracy codes in precise<br />

orbits”), and KINPRE. Official exchange format within IGS.<br />

Used by: PREWEI, PRETAB (”Menu>Orbits/EOP>Create tabular orbits”), ORBGEN (”Menu<br />

>Orbits/EOP>Create standard orbits”), and ORBCMP (”Menu>Orbits/EOP>Compare orbits<br />

>Precise orbits”).<br />

Example: Figure 4.7 shows a precise orbit file created by CODE for December 12, 2003.<br />

Files from external sources may also have the extensions sp3, sp3d, EPH. Apart from SP3c<br />

older precise orbit file formats (SP1, SP2, and SP3) may be read and written by the <strong>Bernese</strong><br />

<strong>GPS</strong> <strong>Software</strong>. All the satellite positions in the precise files are given in an Earth-fixed<br />

reference frame.<br />

SP1 positions of the satellites (obsolete).<br />

SP2 positions and velocities of the satellites (obsolete).<br />

SP3 positions in km (and optionally velocities in dm/s) and clock information of the<br />

satellites in microseconds.<br />

SP3c positions in km (and optionally velocities) and clock information of the satellites in<br />

microseconds (the new format allows, e.g., for maneuver and prediction flags).<br />

The recommended format is SP3c. Detailed informations may be found in [Remondi, 1989]<br />

and at ftp://ftp.igs.org/igscb/data/format/sp3c.txt.<br />

The satellite-specific formal rms values are given in lines 8–9, specifying the rms in 2 x mm,<br />

x = 5−14 (accuracy codes). Satellites with accuracy codes zero or exceeding a user specified<br />

limit may be excluded in PRETAB (”Menu>Orbits/EOP>Create tabular orbits”, “PRETAB 2: General<br />

Options”). Accuracy codes can also be set or changed by program PREWEI (”Menu>Orbits/EOP<br />

>Set accuracy codes in precise orbits”) using a LST file written by ORBGEN. For more details on<br />

the satellite clock values (last column, 999999.999999 if not available) and their use see<br />

Section 5.5.<br />

Page 504 AIUB

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

Saved successfully!

Ooh no, something went wrong!