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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

22. Data Structure<br />

22.6.2 Header and Observation Files<br />

Because of the identical format of all the header and observation files, these files are described<br />

together in one section.<br />

Type: Binary<br />

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

Extension: CZH/CZO, PZH/PZO, CSH/CSO, or PSH/PSO<br />

Content: Code/phase/range zero/single-difference observation and associated important<br />

information in the header files.<br />

Created by: Programs RXOBV3 (”Menu>RINEX>Import RINEX to <strong>Bernese</strong> format>Observation files”),<br />

<strong>GPS</strong>SIM (”Menu>Service>Generate simulated observation data”), and SNGDIF (”Menu<br />

>Processing>Baseline file creation”).<br />

Used by: All programs dealing with observation/header information (CODSPP,<br />

SNGDIF, MAUPRP, and <strong>GPS</strong>EST) and some other programs (e.g., service and<br />

conversion programs in ”Menu>Service><strong>Bernese</strong> observation files” and ”Menu>Conversion<br />

>Observation files”).<br />

Example: ASCII image of a header file (first part) and observation file (second part) in<br />

Figure 22.18 for single-difference phase observations.<br />

All observations are stored in a binary format. The program OBSFMT (”Menu>Conversion<br />

>Observation files>Binary to ASCII”) and the edit and browse utilites in ”Menu>Service><strong>Bernese</strong> observation<br />

files>Edit observation header file” and ”Menu>Service><strong>Bernese</strong> observation files>Browse observation data files” create<br />

an ASCII image of a binary file. In the binary format the header and the observations are<br />

stored in two different files. The program OBSFMT merges these two files into one ASCII<br />

image. Real values are rounded to millimeters and nanoseconds which should be below the<br />

measurement noise. Using program FMTOBS (”Menu>Conversion>Observation files>ASCII to binary”)<br />

ASCII observation files may be transformed back to binary.<br />

Remarks concerning this ASCII file (Figure 22.18, line numbers added for a better<br />

explanation of contents):<br />

Line Comment<br />

1 Campaign name (ch*16); title (ch*53).<br />

3 Measurement type: PHASE, CODE or RANGE; file creation date and time.<br />

4 The reference epoch is the full second part of the first observation epoch in the file;<br />

File modification date and time (updated by programs changing the file).<br />

6 Number of differences: 0 = zero-difference file, 1 = single-difference file; File format<br />

number (at present always set to 5, provided for further updates).<br />

7 Number of frequencies: 1 or 2; session number (used in program SNGDIF to be sure<br />

that the files are from the same session, in program IONEST to arrange files in sessions,<br />

and in program <strong>GPS</strong>EST to know which files have to be correlated).<br />

8 Total number of satellites in the file; The session file number is the last character of<br />

the session string.<br />

9 The number of epochs may be different from the number of observation epochs. The<br />

epoch of the last observation record in the file may be computed from the reference<br />

epoch, the number of epochs, and the observation interval.<br />

Observation interval in seconds (sampling rates below 1 sec are not supported, at<br />

present).<br />

Page 500 AIUB

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

Saved successfully!

Ooh no, something went wrong!