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.

4. Import and Export of External File Formats<br />

The appropriate choice depends on the convention you adopted for your campaign.<br />

For the transfer of RINEX observation files from IGS we propose to verify with respect<br />

to the MARKER DOMES entry.<br />

• “Verify station name using RINEX filename”: Enable this option to verify the first four<br />

characters of the (new) station name with respect to the first four characters of the<br />

RINEX filename. This convention applies for RINEX observation files from the IGS.<br />

It may not be true for your own campaign.<br />

4.2.3.5 Naming of <strong>Bernese</strong> Observation Files<br />

<strong>Bernese</strong> binary observation files created by RXOBV3 follow a file naming convention similar<br />

to RINEX: Filenames ccccssss are composed of a 4-character station code cccc and the<br />

session identifier ssss.<br />

The station code is generated using the station name “Abbreviation table” specified in panel<br />

“RXOBV3 1.1: General Files”. This file contains the 4-character and 2-character station abbreviations<br />

for a list of station names. The file can be generated using ”Menu>Campaign>Edit station<br />

files>Abbreviation table”.<br />

Option “Action if station not in abbreviation list” (panel “RXOBV3 2: Input Options 1”, Figure 4.2)<br />

defines the behavior of RXOBV3 if the 4-character station abbreviation is not found in the<br />

abbreviation list:<br />

• ERROR: The program stops with an error.<br />

• UPDATE: Based on the station name the program automatically creates new and<br />

unique 4-character and 2-character abbreviations in capital letters.<br />

• UPDATE+: Same as previous option but in addition lower case letters are used. This<br />

option should not be used on Windows platforms due to missing case sensitivity for<br />

filenames.<br />

Do not enable UPDATE if RXOBV3 is running in parallel (e.g., in the BPE). Simultaneous<br />

modification of the abbreviation table may lead to unpredictable results.<br />

In option “Session ID used for <strong>Bernese</strong> observation files” you may define the session identifier<br />

which should be used for the observation filenames. This session ID is also written to the<br />

<strong>Bernese</strong> observation header files and must be defined in the session table. The session will<br />

be determined automatically if this field is left empty based on the start, end, middle, and<br />

median epochs: If at least three of these epochs fall into the same session or if the median<br />

epoch falls into the same session as the start or the end epoch, this session is used for naming<br />

the output file. Otherwise the program stops execution. It is recommended to specify the<br />

session explicitly in case of RINEX observation files covering more than one session (after<br />

being cut to the observation window specified in panel “RXOBV3 3: Observation Window”).<br />

4.2.4 Export from <strong>Bernese</strong><br />

Program BV3RXO (”Menu>RINEX>Export RINEX from <strong>Bernese</strong> format>Observation files”) converts <strong>Bernese</strong><br />

code and phase observation files to RINEX format. More than one file may be converted<br />

Page 62 AIUB

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

Saved successfully!

Ooh no, something went wrong!