83
Storing G-Files
Collected During
Sessions
Converting,
Compressing,
Deleting G-Files
Collected During
Sessions
G-files are saved either in the receiver’s internal memory or
on a USB device, i.e. on the mass storage device connected
to the receiver via its USB port. In both cases, G-files are all
saved to the root directory of the selected storage device.
At this stage, special mention should be made of the
Ring File
Memory
. With this option activated, the receiver will be able
to collect data for an unlimited period of time without
external intervention. In practice, this option will allow the
receiver to automatically delete the oldest file when the
amount of available free memory (in the selected storage
device) drops below 60
0
MBytes.
G-files can be converted to a variety of RINEX formats (from
version 2.10 to version 3.03). This will happen only if the
navigation data included in the G-file are in ATOM format (the
conversion will otherwise fail).
You should be aware of the limitation in asking for RINEX
conversion. The receiver won’t convert to RINEX all G files
resulting from sessions whose duration is less than 5
minutes.
The receiver can automatically complete the RINEX file
header while converting G-files to RINEX files. The fixed
additional information you would like the receiver to insert
into that header can be entered using
Receiver
>
Memory >
RINEX Metadata
on the Web Server.
RINEX files resulting from the conversion of G-files may be
compressed to Hatanaka or/and Tar.Z.
If not converted to RINEX, G-files will always be Hatanaka
compressed and possibly Tar.Z compressed if desired.
The file conversion/compression may be followed by the
deletion of the original G-file, if desired.
