Storage path: Specifies the path to the root folder (local computer), where the data files are written to. To select or change the destination, set the focus into the value field and click the browse button. The Folder Browser dialog appears. By default, files are stored into the C:\ root.

Note - The name of the Controller host is not a part of the path. That means: If you move the module to a different Container than the Container of the parent module, it stores the files to the local computer where the parent Controller of this new Container resides.

Folder structure: Specifies the type of folder structure below the root. The default selection is Enhanced day.

Option	File location	Folder names depend on…
Plain	All files will be stored into one folder.	- Storage path setting.
Enhanced month	An enhanced data folder structure is applied to the data. This option writes all files generated within a month into the monthly folder.	- Storage path setting. - Year and month. For example: C:\Refdata.YY\Month.MMM\*.*
Enhanced day	An enhanced data folder structure is applied to the data. For each day a folder is created and files are written into the daily folder.	- Storage path setting. - Year, month, and day. For example: C:\Refdata.YY\Month.MMM\ Day.DD\*.*
CORS	An enhanced data folder structure is applied to the data. Below the root, for each file type a folder is created, which then contains folders for the year, day, and reference station.	- Storage path setting. - File type, year, day, and station. All characters in lower case. The station is characterized by a four character site ID. For example: C:\rinex\YYYY\DDD\SITE\*.*

Note - Both, the automatically created file names and the file contents refer to the measurement date and time, based on system time. With an enhanced folder structure, the files are located in folders whose structure also depends on GPS time.

Add station code to folder structure: Not available, if the folder structure is set to CORS.

In any other case, the data structure, regardless of which one was selected, may be further enhanced by the station code, if you set the Add station code to folder structure setting to Yes. Then the data files are written into a folder named according to the station code. If the Plain option is selected, the folder is created as a sub-folder to the folder named in the Storage path setting. With the Enhanced month option selected, the <Station code> folder is added below each <Month> folder. Similarly, the <Station code> folder can be found below each <Day> folder, if you have selected Enhanced day. With a CORS -based folder structure, a <Site> folder is automatically created and, therefore, the Add station code to folder structure option is internally set to Yes and is not available for editing. In other cases, the default selection is No.

Filtering: Filtering reduces the data amount written into the files. If Filtering is set to Yes, the Storage module discards all incoming data records, which do not comply with the selected data rate (the additional Data rate property becomes available). Default: Yes. If Filtering is set to No, the Storage module writes all incoming data records into the file.

Data rate: Only available, if Filtering is set to Yes. The data rate written into the data files. If the receiver sends data with a higher data rate, the data is reduced to match the Data rate setting. Selectable values are between 10 minutes and up to 20 Hz, depending on the parent receiver type. Default: 1 Hz.

New files are named following the CORS convention, where a file name consists of the 4 characters of the station code ("CODE"), the day of the year ("DOY") and a session identifier "S": "CODEDOYS.???". The session identifier is given in alphabetical characters. If the daily number of sessions exceeds 26 characters, the session identifier is increased at the expense of the day identifier.

Tip – To force strict CORS file naming, where the session identifier indicates the hour of the day, select a writing period of 3600 seconds and make sure that both, the Append, if file exists property (for files other than RINEX) and the Lower case only property are set to Yes.

As extension to the CORS convention, the file name is extended by an identifier of the minimum time span covered by the file, if the file covers less than an hour: "CODEDOYSMM.???", where MM can be one of 5, 10, 15, 20 or 30 minutes.

Note for RINEX file storage - If you have stopped and restarted RINEX data storage within the specified writing time, files already exist in the current folder that are named according to the current definition and that contain the data up to the time the storage was stopped. After restart of RINEX data storage, Trimble 4D Control Server automatically descides whether to append the data to the existing file or to create a new file. A new file is only created if properties of the file have changed. Its file name is then extended by the identifier "_A". For example: "CODEDOYSMM_A.???", if the file covers less than one hour. If storage integrity is enabled, only the last file of a set of files in a storage period would be replaced.

Note for non-RINEX file storage - If you have stopped and restarted data storage for file types other than RINEX files within the specified writing time, the data is appended to the old file and the file name is kept.

Start the next observation file after...: Specifies the start and end of data files depending on the duration of tracking. Select an upper time limit for the output file. If this threshold is exceeded, a new file is created. Default selection: 1 hour.

Lower case only: If set to Yes, the setting forces all characters of the resulting file to be written in lower case, even if the original station code contains upper case characters. To accept the use of upper case characters for the code and session identifiers, set the Lower case only value to No. Default: No.

To minimize used disk space you may compress the written output data files, and additionally delete the original files after compression. Several compress file formats are available. When you change the settings here, the Storage module uses the new settings for compression the next time output files are completed. Previously created files are not affected.

Activate compression: Activates the compression functionality. If set to Yes, more settings and one additional module-view are available. Default value: No.

Compression mode: If compression is activated, select the compression method and archive file format.

Selection	Resulting Files	More Information
WinZIP archives [.zip]	.zip	Data is compressed into archive files of the .zip type using the Zip method. Default selection.
Gnu – gnu files [.gz]	.gz	Each file is compressed into an archive file with the file extension .gz using the Unix-based Gnu method.
Gnu & Tar – gnu tar’ed files [.tgz]	.tgz	This selection adds the files of a session to a tar’ed file and then gnuzips that file into one archive using the extension .tgz. Preferable for RINEX files, when using the Unix-based Gnu method.

Delete original files after compression: If set to Yes, the source data files will be removed after the compression has been performed correctly, independent of the compression method. Default value: No.

Replace extension separator of original file with: With RINEX data, the archive file contains all RINEX files of the same file name and year extension (for example, navigation or almanac files). You do not have to define the names of the compressed files, since these are created automatically from the observation file name with the correct extension appended to it (for example: CODE001A.07o.zip contains CODE001A.07o, and, if available, CODE001A.07a, CODE001A.07n, and CODE001A.07g). By default, the new file name contains two dots as separators. To get rid of the first dot separating the original file name and its original extension, edit the Replace extension separator of original file with setting. You could use, for example, an underscore character instead. Default value: a dot.

The file rollover option lets you enter a command. The command will be executed after a file has been successfully written to disk. The command may be a batch file or an executable program.

File rollover: If set to Yes, the command specified in the File Rollover Command setting will be executed. To pause command execution for a while, set the value to No. The command specification will not be lost. Default value: No.

File rollover command: Only available, if the File Rollover setting is set to Yes. To specify the command to be executed, click the browse button. This opens the File Rollover dialog. Default: Empty as long as you have not yet entered a file name or command.

The RINEX category is only available, if you have set the Storage type setting to the RINEX file type.

RINEX format: Specifies the format version of the RINEX file into which the data received by the connected receiver are archived. Available selections are the versions 2.0, 2.1, 2.11, and 3.02. For detailed information on the RINEX convention refer, for example, to the following web sites:

• RINEX 2.0, US National Geodetic Survey: www.ngs.noaa.gov/CORS/Rinex2.html
• RINEX 3.0, Astronomical Institute of the University of Berne (AIUB): ftp.unibe.ch/aiub/rinex/rinex300.pdf

Store orbit files: Specifies whether broadcast orbits are stored into RINEX orbit files with extension .nav. Default value: Yes.

Store meteorological files: Specifies whether weather station data (temperature, humidity, pressure) is stored into RINEX files with extension .??m, if they are made available by a connected instrument. Default value: No.

QZSS storage mode: Only available for the RINEX 3.02 format. Specifies whether signals tracked from QZSS satellites are stored into RINEX files if they are made available by a connected instrument. If set to Disabled, QZSS signals are not stored. The Default selection stores pseudo ranges, carrier phase and signal strength observations as well as QZSS ephemeris. If set to Full, additionally Doppler observations are written into the RINEX files. Default value: Default.

BeiDou storage mode: Only available for the RINEX 3.02 format. Specifies whether signals tracked from BeiDou satellites are stored into RINEX files if they are made available by a connected instrument. If set to Disabled, BeiDou signals are not stored. The Default selection stores pseudo ranges, carrier phase and signal strength observations. If set to Full, additionally Doppler observations are written into the RINEX files. Default value: Default.

Store SBAS files: Only available for the RINEX 3.02 format. Specifies whether the raw signals tracked from SBAS satellites are stored into RINEX files with extension .??b, if they are made available by a connected instrument. Default value: No.

Use compact RINEX: If yet to Yes, the observation data are compressed into files according to the Hatanaka format with the standard RINEX file naming and the extension .??d. This process uses the RNX2CRX software, developed by Yuki Hatanaka. The compression starts whenever a RINEX file write-session has finished. The original .??o files are only used as intermediate files and are deleted after compact RINEX files have been created. Default value: No.

RINEX header: Specifies the contents of the header of the new RINEX files. To view and edit the entries set the focus into the value field and click the browse button. The RINEX Header dialog appears.

RINEX observations: Specifies observables to be stored in the RINEX files. To edit the selection, set the focus onto the value field and select the browse button. The Observables in RINEX File dialog appears.

Correct for clock jumps: Some receiver brands correct their internal clock in millisecond jumps. If Correct for clock jumps is set to No, the ms-jumps created by the receiver clock remain in the observables written to the RINEX observation files. If set to Yes, these receiver clock jumps are corrected before writing the observables. Default value: No.

By default, some parameters of the storage process are based on the station code stored in the global station list. For example:

• The folder structure, if CORS is selected.
• The file names of storage files (additionally to creation time and date).
• With RINEX files, the header contents includes the station code.

For overriding the default station code stored in the global station list by a custom string, use the settings of the Customization category.

Override station code: If set to Yes, the Custom station code property becomes available. Use it to enter a custom station code. Default value: No.

Custom station code: Only available, if the Override station code property is set to Yes. Specifies a 4-character string (consisting of alphanumerical characters, spaces, and/or underscores) that will be used instead of the station code stored with the station data. Default: Empty as long as you have not yet entered a valid 4-character string.

Note - For storage integrity to work, it must be enabled at the parent GNSS Receiver module as well as at the depending Storage module.

Use storage integrity: If set to Yes, the storage integrity feature is enabled. The Retrieval time and Epoch availability settings become available.

Retrieval time: Specifies the retrieval time in days (None, 1, 2, or 3 days and 1, 2, or 4 weeks, default: 1 day). The setting serves a twofold purpose:

• At startup it defines the period, for which the data files are checked.
• If the connection to the reference station is disturbed for a longer time: after reestablishment of the connection, storage integrity downloads only the data files covering the period set here. In this case, if None is selected, files covering gaps of up to 24 hours will be downloaded.

Tip - You can select a time range for each day and a number of days during the week for the receiver to store files to the internal memory. To do so, use the GNSS Receiver Properties > Data Logging category.

See the following table for how the retrieval time value determines the date (local file time) of the first and following data files to be respected (searched) by the storage integrity.

Retrieval time	Local file time of the first file
None	Current time
1 day	- 24 hours
2 days	- 48 hours
3 days	- 72 hours
1 week	...
2 weeks	...
4 weeks	...

Epoch availability : Specifies a minimum percentage of available epochs that a data file must contain. The default limit is 90 %. All information is stored in the database.

Based on the epoch availability information, the storage integrity decides, if it is necessary to replace a data file on the specified local folder. The test is performed at the end of a file storage session; that means, for hourly files at the end of each hour and for daily files at the end of the day. If less than the percentage of available epochs is found in the file, the file on the local Trimble 4D Control Server computer (and probably the respective compressed files) are deleted and replaced by the data of the receiver. File rollover will be performed, if the replacing file contains more epochs than the replaced one.