{"id":9339,"date":"2026-02-20T01:37:05","date_gmt":"2026-02-20T01:37:05","guid":{"rendered":"https:\/\/www.use-snip.com\/kb\/?post_type=ht_kb&p=9339"},"modified":"2026-04-07T22:00:45","modified_gmt":"2026-04-07T22:00:45","slug":"ntrip-client-recording","status":"publish","type":"ht_kb","link":"https:\/\/www.use-snip.com\/kb\/knowledge-base\/ntrip-client-recording\/","title":{"rendered":"NTRIP Client Recording"},"content":{"rendered":"

Note: This is a pending feature now in beta testing
\nwhich will be released as part of Rev 3.20<\/strong> in April.
\nContact us if you wish to participate in this testing.<\/p>\n

In this article we discuss controls SNIP<\/strong><\/span> provides to record data sent back from a connected NTRIP Client<\/a> to the SNIP<\/strong><\/span> NTRIP Caster<\/a>. This feature was first released in SNIP<\/strong><\/span> Rev 3.20<\/strong> and is available on all models of SNIP<\/strong><\/span> (including the free Lite<\/strong> <\/span><\/em>model).<\/p>\n

The primary use case for this feature is a deployment that needs to capture data from rover devices (NTRIP Clients) for later post-processing.\u00a0 Common examples include telemetry and field data from precision agriculture devices, streams of NMEA $GGA<\/a> position estimates for precise path plotting, any other NMEA message content, or any other text or binary formatted data which is desired to be captured.\u00a0 Using this feature your SNIP<\/strong><\/span> Caster becomes a basic data logging warehouse for any field data you care to send back to it,<\/p>\n

The recording (as well the specific defaults used) can be set for each individual User Account<\/a> and not every User Account need to make use of the feature.\u00a0\u00a0 The general recording controls are organized in their own tab below the various user restrictions<\/a> tabs, which is part of the general User Account setup dialog. This tab in the dialog is shown below.<\/p>\n

\"\"<\/a><\/p>\n

Dialog Controls<\/strong><\/h2>\n

The dialog controls themselves are fairly simple and described next.<\/p>\n

A basic on\/off check box (labeled Enable Raw Data Recording<\/em>) controls the use of this feature for the User Account that is currently being edited.<\/p>\n

The next several checkboxes control the comments and meta data which may be added to each data file. Hint<\/em><\/strong>:<\/span>\u00a0 If your use case requirements are to have no such data (for example, if you need to create a binary file that will be understood and processed by another program) then simply Un<\/strong>check all of these checkboxes.<\/p>\n

The File Header\u00a0 \u00a0<\/em><\/h3>\n

Each new file starts with a header similar to the example shown below when the \u201cAdd ### header\u2026\u201d check box has been checked.<\/p>\n

The lines starting with \u201c###\u201d can be considered simple comments.\u00a0 But the lines starting with \u201c#\u201d contain various meta data information about the User Account connection that you may wish to parse and extract and then process in some way.<\/p>\n

The File Tail<\/em><\/h3>\n

Each file ends with a comment line like the ones in the example text below. This is enabled when the \u201cAdd ### tail lines to file\u201d checkbox has been checked.<\/p>\n

Adding <CR><LF><\/em><\/h3>\n

Some files may need this appended to the file lines for readability or for syntax processing.\u00a0 These two chars are added to each write call when the \u201cAdd <CR><LF>\u2026\u201d checkbox has been checked.\u00a0 Note that in low bandwidth marginal TCP\/IP connections that are very poor, this option can also cause additional unwanted <CR><LF> content as well.<\/p>\n

Add a Custom Comment<\/em><\/h3>\n

The checkbox \u201cAdd Custom ### line\u2026\u201d provides a method to append the provided text comment in the line that follows to the header in each file.\u00a0 This can be used to add unique content to the produced files for that specific user. An example is shown in the section Example File<\/em> below using the text \u201cMy custom line is added here<\/span>\u201d.<\/p>\n

File Naming<\/strong><\/h2>\n

The file name is automatically created by appending the User Account name and the start date\/time of the file to the text \u201craw_<\/span>\u201d.\u00a0 This file name is updated every time a new file is created for the user, based on the log duration you have set in the combo.\u00a0 The file type (txt, dat, csv,<\/span> etc.) follows the selected file extension in that combo.\u00a0 The date and time value used can use either the local host machine time zone or can use UTC time (by convention many GNSS files use UTC as a common time zone).\u00a0 The date is preceded with \u201cD<\/span><\/strong>\u201d while \u201cT<\/span><\/strong>\u201d precedes the time (when present). A representative example is shown at the bottom of the dialog as the settings are changed.<\/p>\n

The created files are saved into the folder …\/data\/SNIPlogs\/<\/span>\u00a0 alongside the weekly console log files. Typically this path is set to be:\u00a0 C:\\Program Files (x86)\\SNIP\\bin\\data\\SNIPlogs<\/span><\/p>\n

All files follow the same naming pattern of:<\/p>\n

raw_<UserAccountName_D<date>_T<time>.<fileType><\/span><\/p>\n

Aside<\/em>: It has been decided to remove the start time control in the final release as it does not add any useful value. That will be done before production release.<\/p>\n

Aside:<\/em> All file start times are aligned with the clock.\u00a0 In other words, with a file duration of 15 minutes the resulting raw log files always start at either the top of the hour, or at the 15, 30 or 45 minute mark.\u00a0 Files with a duration of 2 hours always start at the top of even numbered hours, etc.<\/p>\n

Example File<\/strong><\/h2>\n

The below is just a very short raw data file containing only NMEA $GGA sentences<\/a> as an example.<\/p>\n

### Raw NTRIP Client Data from user account: aaaUserA\r\n### All the data which the client sends back to the Caster\r\n### is written to this file for port-processing which you may need to do.\r\n### Lines starting with '###' are comments.\r\n### Lines starting with '#' contain useful meta information about the user.\r\n###\r\n# Connection Start Time: Thursday, February 19, 2026 \u00a0at\u00a0 11:49:36 AM Pacific Standard Time (local time)\r\n# File Start (long): Thursday, February 19, 2026\u00a0 at\u00a0 11:49:36.308 AM Pacific Standard Time\r\n# File Start (short): 2026-02-19\u00a0 11:49:36\r\n# File Duration: 02:00:00 (H:M:S)\r\n# User Account: aaaUserA\r\n# User Id: UA056530\r\n# Customer Account: Admin Account (user's owner)\r\n# Customer Id: CA000000\r\n# Connected to Base: SCSC (at file start)\r\n# Comment: My custom line is added here.\r\n# Data Starts\r\n$GPGGA,194936.02,3407.6637498,N,11749.5273171,W,1,00,1.0,288.671,M,-33.512,M,0.0,*75\r\n$GPGGA,194941.02,3407.6638826,N,11749.5273100,W,1,00,1.0,286.218,M,-33.512,M,0.0,*70\r\n$GPGGA,194946.11,3407.6630311,N,11749.5273050,W,1,00,1.0,282.568,M,-33.512,M,0.0,*72\r\n$GPGGA,194951.06,3407.6630310,N,11749.5273050,W,1,00,1.0,282.567,M,-33.512,M,0.0,*7C\r\n$GPGGA,194955.99,3407.6630310,N,11749.5273051,W,1,00,1.0,282.567,M,-33.512,M,0.0,*7F\r\n$GPGGA,195001.43,3407.6630310,N,11749.5273051,W,1,00,1.0,282.567,M,-33.512,M,0.0,*71\r\n$GPGGA,195006.35,3407.6630310,N,11749.5273051,W,1,00,1.0,282.567,M,-33.512,M,0.0,*77\r\n$GPGGA,195011.27,3407.6630310,N,11749.5273051,W,1,00,1.0,282.567,M,-33.512,M,0.0,*72\r\n$GPGGA,195016.22,3407.6630310,N,11749.5273051,W,1,00,1.0,282.567,M,-33.512,M,0.0,*70\r\n$GPGGA,195021.16,3407.6630310,N,11749.5273051,W,1,00,1.0,282.567,M,-33.512,M,0.0,*73\r\n$GPGGA,195026.09,3407.6630310,N,11749.5273051,W,1,00,1.0,282.567,M,-33.512,M,0.0,*7A\r\n### User Raw Data, end of file. User:aaaUserA, UaNum:UA056530\r\n$GPGGA,195124.04,3407.6630311,N,11749.5273050,W,1,00,1.0,282.568,M,-33.512,M,0.0,*7B\r\n$GPGGA,195128.97,3407.6630311,N,11749.5273050,W,1,00,1.0,282.568,M,-33.512,M,0.0,*7D\r\n$GPGGA,195133.90,3407.6630310,N,11749.5273051,W,1,00,1.0,282.567,M,-33.512,M,0.0,*7F\r\n$GPGGA,195138.86,3407.6630310,N,11749.5273051,W,1,00,1.0,282.567,M,-33.512,M,0.0,*73\r\n### User Raw Data, end of file. User:aaaUserA, UaNum:UA056530<\/pre>\n
Note the meta information about the user, the base, and the connection found in the lines that start with \u201c#\u201d in the above.<\/p>\n
In the example file above the client disconnected at about the time 19:50:26 (the last time stamp in UTC in the NMEA data).\u00a0 It then reconnected and briefly began sending further data at about 19:51:24. The lines staring with \u201c### User Raw Data, end of file\u201d followed by more data denote such re-connection events.\u00a0 A new file is only started when the connection time has reached two hours (the file duration that was set for this example file).<\/p>\n
Concluding Remarks<\/strong><\/h2>\n