Saving Data into Log Files

SNIP allows you to save any mountPt stream as a raw log file on any input it gathers.  These files are useful for latter post processing in a variety of ways.  RINEX files are created in this way.

When using SNIP as a data logger use the “Data File Settings” menu and dialog and is covered in detail in this article.  The default setting is to create a new file every 24 hours.

You can enable/disable logging for any Base Station with the “Log raw data” right-click menu item which is found in any stream types shown in any tab.  Once setup, every stream with logging enabled will automatically be named, saved, and FTP processed automatically.

Hint:  Daily log files in raw RTCM can be fairly big (20~25 meg/days for a legacy L1/L2 file) and will require significant disk space over time.  This is why all models of SNIP provide both a ZIP file compression function and a remote FTP transfer function.  You may also select where these files are kept, a large secondary hard disk is a commonly used.

A common practice is to accumulate 24 hour files (completing at the end of each day at UTC midnight). Then to compress these files into a ZIP, deleting the original file. And then to copy the file by FTP to a remote site.  The SNIP features and settings discussed in the above article provide for doing this.

NoteSNIP saves all log files in as type *.dat which may not make sense if you are running a network with CMR data streams.  As all of this data is of a binary in nature, and unreadable by end users, the default file type should be changed from *dat to reflect the raw data nature when known.

When a Base Station is being logged, you will see a cross hatch pattern displayed in input columns for that station as a visual indication.


Was this article helpful?

Related Articles