{"id":4389,"date":"2017-12-02T16:45:13","date_gmt":"2017-12-02T16:45:13","guid":{"rendered":"https:\/\/www.use-snip.com\/kb\/?post_type=ht_kb&p=4389"},"modified":"2020-08-28T14:34:43","modified_gmt":"2020-08-28T14:34:43","slug":"pfat-parse-settings","status":"publish","type":"ht_kb","link":"https:\/\/www.use-snip.com\/kb\/knowledge-base\/pfat-parse-settings\/","title":{"rendered":"PFAT: Parse Settings and Uses"},"content":{"rendered":"

\"\"SNIP<\/strong><\/span> uses an intelligent auto-parse<\/em> logic to determine the format of the messages<\/a> in the data stream and reacts accordingly.\u00a0 When a data stream is first parsed a process examines the first 3K of data (or 30 seconds of data for slow streams) and attempt to determine the message content that is present.<\/p>\n

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

As a best practice, enable the Parse checkbox on all streams.<\/strong> Do this unless you specifically want the stream to be treated in the bent-pipe<\/a> mode (where all inbound content is sent to all corrected users with no PFAT operations<\/a> applied to it).<\/p>\n

Default Parse behavior for new in-bound<\/em> data streams is set on the major tab (Push-In<\/a>) and on the individual setup dialog for each of the other stream types<\/a>.\u00a0 Every active data stream has its own Parse menu item in the right-click stream menu<\/a> system.\u00a0 When SNIP<\/span><\/strong> stores the settings data for a stream, the current Parse setting is also kept.<\/p>\n

Side Note<\/strong><\/span><\/em>:\u00a0 Because of this improvement, the RTK2go.com<\/a><\/strong> site has also been switched to a default parse enabled mode.\u00a0 In the past, a few users with CMR and CMR+ type data streams requested that we leave default Parsing off.\u00a0 A prior reservation was required to enable parsing for RTCM3 users.\u00a0 Getting your own reservation<\/a> is still the best way to use RTK2go<\/strong> as your own Caster. In the current release, SNIP<\/strong><\/span> will correctly deal both RTCM 3 and other message types<\/a> without user intervention.\u00a0 This setup better serves those L1-only users of RTK2go<\/strong> who often need SNIP<\/strong><\/span>‘s help creating a suitable Caster Table Entry.<\/p>\n

Advantages…<\/h3>\n

By enabling Parse on a data stream, SNIP<\/strong><\/span> will detect if the stream contains RTCM3 messages (as well as other well know formats) and set suitable content in the Caster Table Entry<\/a> for that stream to complete it.\u00a0 If the stream provides a field or an entry, that data will be used.<\/p>\n

If the data is in the RTCM 3.x format, SNIP<\/strong><\/span> will analyze the data and extract details about it.\u00a0 This includes the RTCM 3.x message types<\/a> present, details about the Base Station<\/a>, and various counts and statics about the data itself. RTCM 3.x messages can decoded<\/a> and shown in a view, or used to feed basic graphical navigation filters.<\/p>\n

If the data is in the RTCM 2.x format, SNIP<\/strong><\/span> will also analyze the data and extract more limited details about the data stream and the RTCM 2.x message types<\/a> present.<\/p>\n

Other formats (such as uBlox binary) are also detected, and set in the Caster Table Entry. The universal decoder<\/a> provides some content details, but further processing such a navigation filtering is not provided.<\/p>\n

How It Works…<\/h3>\n

When a stream first starts, an analysis process occurs for the first 3KB of data or the first 30 seconds of its lifetime (whichever occurs first).<\/p>\n

During that time the data is not sent to end users, this ensures that gross corrupted data is not sent onward.\u00a0 Hence no PFAT™<\/strong> content filtering is occurring either. The data stream is not yet published for use by NTRIP Clients<\/a>.<\/p>\n

During this period of time, if the data stream comes from another NTRIP Caster<\/a>, a copy of the remote Caster Table entries are obtained and compared with the data present.\u00a0 Certain conflicts are reported and corrected when found, otherwise the remote data is used in the local Caster Table.<\/p>\n

When analysis completes, the message format is determined and used to create the local Caster Table Entry (if needed). A few other tasks then occur.<\/p>\n