{"id":3192,"date":"2017-01-26T17:22:52","date_gmt":"2017-01-26T17:22:52","guid":{"rendered":"\/kb\/?post_type=ht_kb&p=3192"},"modified":"2017-12-02T15:42:04","modified_gmt":"2017-12-02T15:42:04","slug":"supported-caster-data-formats","status":"publish","type":"ht_kb","link":"https:\/\/www.use-snip.com\/kb\/knowledge-base\/supported-caster-data-formats\/","title":{"rendered":"Supported Caster Data Formats"},"content":{"rendered":"

SNIP<\/strong><\/span> supports receiving and sending any data format or style of data you care to use.<\/p>\n

The Basics\u00a0 [or: To parse or not to parse…<\/em>]<\/h3>\n

When it is used in the bent pipe<\/a> mode, SNIP<\/strong><\/span> will simply repeat the stream of data it is given to any NTRIP Client<\/a> connected to that mountPt.\u00a0\u00a0 No further processing (other than data logging, if enabled) takes place.<\/p>\n

It is more typical to use RTCM 3.x<\/strong> style messages<\/a> with SNIP <\/strong><\/span>and to parse them.\u00a0\u00a0 In this case, SNIP<\/strong><\/span> performs a full decode of the messages (when the Parse<\/strong> <\/em>switch is enabled for that stream).\u00a0 From this, SNIP<\/strong><\/span> can perform other useful functions.\u00a0 These include creating and correcting the Caster Table entry for that mountPt, displaying detailed message contents<\/a> (useful for researchers and debugging) , or performing a basic plots or navigation<\/a> filters with data itself to confirm it is working.\u00a0 Any ill-formed messages and other clutter (often stray NMEA contents<\/a>) is also removed during this process to ensure only valid data is sent to on to the NTRIP Clients.<\/p>\n

If one of the other common formats is used (such as RTCM 2.x<\/a> or one of the CMR styles), then no message level parsing occurs.\u00a0 To usefully employ such streams, the sender software (the NTRIP Server<\/a>) must correctly create a suitable and correct<\/em> Caster Table entry for SNIP<\/strong><\/span> to use.<\/p>\n

Note<\/strong><\/span>:\u00a0 A planned improvement to SNIP<\/strong><\/span> is to add a similar level of full message decoding to support both the older and the latest RTCM 2.x<\/a> format messages (currently these are RTCM SC-104 committee<\/a> working drafts).\u00a0 The RTCM 2.4 message standard is now being tested with improved support other constellations beside just GPS and GLONASS (message Types 41~43).\u00a0 Once this occurs, SNIP<\/strong><\/span> will be able to auto-correct similar errors in such streams as it does today for RTCM 3<\/a> streams.<\/p>\n

The Supported Formats<\/h3>\n

SNIP<\/strong><\/span> supports all the common format styles; see the list below.\u00a0 Because there are no precise rules in the NTRIP Protocol in this regard (any string can appear or be used), SNIP<\/strong><\/span> takes an relaxed attitude when matching such strings.\u00a0 Because of these issues, some format styles that are only trivially different but unique to a vendor are grouped together (such as the Trimble R17 and R27 formats).\u00a0\u00a0 This can also be an issue when Base Stations are being combined to create a NEAR stream.\u00a0 When the data sender (the NTRIP Server) provides a Caster Table entry, that entry is used as provided, unless it has obvious errors which are then corrected.<\/p>\n

The following format keywords are used by SNIP<\/strong><\/span> when constructing its own Caster Table Entries.\u00a0 These terms also appear in various drop-down selections in the Dialogs.\u00a0 When sorting entries for use with NEAR pools<\/a> or other operations, any entry with one of the stated format strings will be matched to a keyword and treated as belonging to the same basic group.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Keyword<\/td>\nVarious Format Strings Used with this keyword <\/u><\/strong><\/td>\n<\/tr>\n
RTCM 3.0^<\/em><\/span><\/strong><\/span><\/td>\nRTCM, RTCM3, RTCM 3.0 ~ RTCM3.x (and various pattern matches)<\/td>\n<\/tr>\n
RTCM 2.x^<\/em><\/span><\/strong><\/span><\/td>\nDGPS, RTCM2, RTCM 2.0 ~ RTCM2.x (and various pattern matches)<\/td>\n<\/tr>\n
CMR<\/strong><\/span><\/td>\nCMR, CMR+, CMRP, CMRr, sCMRx<\/td>\n<\/tr>\n
MBEN<\/strong><\/span><\/td>\nMBEN (Ashtech format)<\/td>\n<\/tr>\n
JPS<\/strong><\/span><\/td>\nJPS\u00a0 (Javad format)<\/td>\n<\/tr>\n
HEMI<\/strong><\/span><\/td>\nHEMI\u00a0 (Hemisphere Eclipse format)<\/td>\n<\/tr>\n
LB2<\/strong><\/span><\/td>\nLB2, Leica4G (various Leica formats)<\/td>\n<\/tr>\n
NVS<\/strong><\/span><\/td>\nNVS<\/td>\n<\/tr>\n
SBF<\/strong><\/span><\/td>\nSBF (Septentrio binary format)<\/td>\n<\/tr>\n
R17<\/strong><\/span><\/td>\nR17, R28<\/td>\n<\/tr>\n
uBlox^<\/em><\/span><\/strong><\/span><\/td>\nUBX, uBlox, (and various pattern matches)<\/td>\n<\/tr>\n
BINEX<\/strong><\/span><\/td>\nBINEX<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

(^<\/strong><\/span>) = Indicates a format where SNIP<\/strong> <\/span>performs some additional content parsing
\n<\/em><\/p>\n

The term “RAW” is also used when a streams contents are unknown or it is still being analyzed. The NTRIP Caster table specification also allows an empty GNSS type string (“;;”) to be used when the correct data is not available.\u00a0 It is generally safe to use this if you are are uncertain how best to set the value.
\n<\/em><\/p>\n

If you feel we should add logic for a new but missing GNSS type, please contact us.\u00a0<\/em><\/p>\n

On NTRIP Clients<\/h3>\n

Many NTRIP Clients (Rovers) are particular about the formats they will accept.\u00a0 For example, some devices want to see “RTCM 3.0” exactly and variants like “RTCM 3.1” or “RTCM3.x” are not acceptable to them.\u00a0 Nor is a blank entry.\u00a0 Many NTRIP Clients will simply complain that a format does not precisely match what it expects, but will thereafter connect to it without further issues.<\/p>\n

Often people will set up the format string slightly “off” as part of an ill-formed Caster Entry<\/a>.\u00a0 SNIP<\/strong><\/span> will not generally correct a “near miss” presuming that the operator knows what he\/she wants.\u00a0 For example, a string like “RTCM3” might appear when some rover devices can only cope with “RTCM 3”\u00a0 (note the additional space).\u00a0 This remains a weak area on the otherwise very successful NTRIP Protocol and the RTCM SC-104 committee is well aware of it.<\/p>\n

The best answer when faced with these issues is simply to try it and find out.\u00a0 The console log<\/a> in SNIP<\/strong><\/span> will allow you to see what is being sent in and correct things at the source as needed.<\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

SNIP supports receiving and sending any data format or style of data you care to use. The Basics\u00a0 [or: To parse or not to parse…] When it is used in the bent pipe mode, SNIP will simply repeat the stream of data it is given to any NTRIP Client connected […]<\/p>\n","protected":false},"author":13,"comment_status":"open","ping_status":"closed","template":"","format":"standard","meta":{"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"footnotes":""},"ht-kb-category":[285,341],"ht-kb-tag":[304,293,305,294,306,204],"class_list":["post-3192","ht_kb","type-ht_kb","status-publish","format-standard","hentry","ht_kb_category-base-station-setup","ht_kb_category-message-decoding","ht_kb_tag-caster-enty","ht_kb_tag-decoding","ht_kb_tag-format","ht_kb_tag-message-types","ht_kb_tag-rtcm2","ht_kb_tag-rtcm3"],"_links":{"self":[{"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb\/3192","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb"}],"about":[{"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/comments?post=3192"}],"version-history":[{"count":18,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb\/3192\/revisions"}],"predecessor-version":[{"id":3675,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb\/3192\/revisions\/3675"}],"wp:attachment":[{"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/media?parent=3192"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb-category?post=3192"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb-tag?post=3192"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}