Storage

To analyze or post-process the network GNSS data it is necessary to store the receiver’s data. The Storage modules collect the data received from the parent GNSS Receiver module, convert it into data files in different output formats, and save the files to specified folders on the local computer.

Note - Among other storage file formats, Trimble 4D Control Server uses the RNXCMP software for compressing RINEX files into and de-crompressing them from Compact RINEX files in the format according to Yuki Hatanaka. The RNXCMP software is made available by the Japanese Geographical Survey Institute (for the license text refer to \<Installation folder>\UI\Hatanaka_LICENSE.txt or to GSI RNXCMP License.txt).

A storage integrity functionality ensures full reliability of file collection for post-processing. If data is lost at a Trimble 4D Control Server server (for example, due to network downtime or instability of the communication links/devices), the Storage module can retrieve the data logged at the remote receiver.

Note - Repeatedly received ephemeris information is stored only once in a file, if the data has not changed.

Adding the Storage module

Storage modules are available from GNSS Receiver modules. Trimble 4D Control Server accepts an arbitrary number of Storage modules.

When the module is first being added, the Storage Properties dialog appears. It lets you define and select Storage module configurations. Each configuration holds the storage settings, such as the file type, file creation rules, the folder to store the data files in, data compression, and many more.

Note - Since Storage module configurations do not need unique settings, you can add the same configuration under multiple GNSS Receiver modules. RINEX Header settings can nevertheless be set up specifically for each module. Below a specific GNSS Receiver module, each configuration can be added only once.

Storage integrity

If storage integrity is enabled at both, the Storage module and its parent GNSS Receiver module, the modules interact closely to ensure full reliability of file collection for post-processing.

Status of the Storage module

In the Tree view, each Storage module is represented by its connection name and a status-identifying icon.

The module displays the Status and the History module-view pages.

Logging into the database and creating reports

All actions of the Storage modules are logged into the central database. The database contains the following tables referring to the Storage system:

Table name	Contents	More information
Storage	History of file storage. File and data information, file retrieval status.	All Storage modules in the system write into this table. One entry per station per requested file. Entries are sorted according to the station code. File retrieval status: 0: Original file. 1: File retrieved on second try using storage integrity. 2: Original file. Second try using storage integrity did not improve the number of epochs for this file.
StorageGaps	History of gaps. Start and end time of the detected gap in the data.	All Storage modules in the system write into this table. One entry per gap in a requested file. Gaps are periods of at least 1 missing epoch.

To create summary or detailed reports on storage events from the database entries, use the Trimble Report Generator application. Two report types are available for the Storage module, Storage Overview and Detailed Storage.