{"id":2885,"date":"2016-12-29T16:00:58","date_gmt":"2016-12-29T16:00:58","guid":{"rendered":"\/kb\/?post_type=ht_kb&#038;p=2885"},"modified":"2018-03-01T14:10:13","modified_gmt":"2018-03-01T14:10:13","slug":"nearest-mountpt-use","status":"publish","type":"ht_kb","link":"https:\/\/www.use-snip.com\/kb\/knowledge-base\/nearest-mountpt-use\/","title":{"rendered":"Nearest MountPt Use"},"content":{"rendered":"<p>The use of &#8220;<strong>NEAR<\/strong>&#8221; mountPt feature (default name: NEAR2 and NEAR3 for RTCM2 and RTCM3 data streams) can be used to allow your NTRIP Clients to easily connect to the closest operational base station without having to examine the contents of each entry found in the Caster table.<\/p>\n<p style=\"text-align: left;\"><a href=\"\/kb\/wp-content\/uploads\/2017\/01\/NEAR_ExampleNetwork.png\"><img loading=\"lazy\" decoding=\"async\" class=\"wp-image-3033 alignright\" src=\"\/kb\/wp-content\/uploads\/2017\/01\/NEAR_ExampleNetwork.png\" alt=\"NEAR_ExampleNetwork\" width=\"383\" height=\"286\" srcset=\"https:\/\/www.use-snip.com\/kb\/wp-content\/uploads\/2017\/01\/NEAR_ExampleNetwork.png 676w, https:\/\/www.use-snip.com\/kb\/wp-content\/uploads\/2017\/01\/NEAR_ExampleNetwork-300x224.png 300w, https:\/\/www.use-snip.com\/kb\/wp-content\/uploads\/2017\/01\/NEAR_ExampleNetwork-50x37.png 50w, https:\/\/www.use-snip.com\/kb\/wp-content\/uploads\/2017\/01\/NEAR_ExampleNetwork-600x448.png 600w, https:\/\/www.use-snip.com\/kb\/wp-content\/uploads\/2017\/01\/NEAR_ExampleNetwork-320x239.png 320w\" sizes=\"auto, (max-width: 383px) 100vw, 383px\" \/><\/a><\/p>\n<p style=\"text-align: left;\">The NEAR feature allows the the <span style=\"color: #0000ff;\"><strong>SNIP<\/strong><\/span> operator to set up a sub-set of the Base Stations in their network and federate these into a common group.\u00a0 NTRIP Clients which connect to a NEAR stream are then automatically connected to the closest Base Station for their reported location.\u00a0 Other NTRIP Clients can also connect to these stations directly, or to any other station in the <span style=\"color: #0000ff;\"><strong>SNIP<\/strong><\/span> network as well.\u00a0\u00a0 This allows operating a network containing widely dispersed Base Stations while still providing a &#8220;local&#8221; single point NEAR connection ability.<\/p>\n<h3 style=\"text-align: left;\">Background<\/h3>\n<p style=\"text-align: left;\">Supporting a &#8220;nearest&#8221; mountPt is an often requested feature by <span style=\"color: #0000ff;\"><strong>SNIP<\/strong> <\/span>users.\u00a0 The basic concept is to support a \u201cNEAR\u201d mountPt functionality wherein any <a href=\"\/kb\/knowledge-base\/question-what-is-an-ntrip-client\/\">NTRIP Client<\/a> can connect to <span style=\"color: #0000ff;\"><strong>SNIP<\/strong><\/span>, and then periodically send its current <a href=\"\/kb\/knowledge-base\/nmea-gga-strings-in-ntrip-clients\/\">NMEA-183 $GGA<\/a> sentence to <span style=\"color: #0000ff;\"><strong>SNIP<\/strong><\/span>.\u00a0 The client then receives the nearest, closest (i.e. \u201cbest\u201d) data stream for its location. This result is connecting each <a href=\"\/kb\/knowledge-base\/question-what-is-an-ntrip-client\/\">NTRIP Client<\/a> to the best data from among the caster streams that copy of <span style=\"color: #0000ff;\"><strong>SNIP<\/strong> <\/span>offers, as opposed to creating a unique stream for that specific user such as a more classical Virtual Reference Station connection (<a href=\"\/kb\/knowledge-base\/virtual-reference-station-vrs-connection-examples\/\">VRS<\/a>) would do.<\/p>\n<p style=\"text-align: left;\">It is generally presumed that such functionality will also periodically re-evaluate what stream is sent. This means a moving user can be assured that it will always get the best data (best connection) as it changes location. It is further presumed that if the best data is not in fact available at that moment (due to data drop-outs, etc.) that the Caster will determine the \u201cnext best\u201d and seamlessly send that along. <span style=\"color: #0000ff;\"><strong>SNIP<\/strong> <\/span>does this as well and will use a hysteresis distance value set by the <span style=\"color: #0000ff;\"><strong>SNIP<\/strong> <\/span>operator to determine how often changing casters will occur.<\/p>\n<p style=\"text-align: left;\"><span style=\"color: #0000ff;\"><strong>SNIP&#8217;s<\/strong><\/span> unique features also allow creating a defined &#8220;region&#8221; where qualifying nearby base stations form a part of the NEAR base station pool.\u00a0 This can be used to operate local NEAR mountPt while still having other base station streams located anywhere in the world on the same SNIP NTRIP Caster installation.\u00a0 The setup details can be found<a href=\"\/kb\/knowledge-base\/nearest-mountpt-regional-settings\/\"> here<\/a>.<\/p>\n<p style=\"text-align: left;\">As a general rule these \u201cNEAR\u201d mountPts are provided for RTCM3 and RTCM2 streams and do not differentiate between GPS, GLO and other content types in each message format.\u00a0 <span style=\"color: #0000ff;\"><strong>SNIP<\/strong><\/span> provides the operator easy checkbox style controls to select what message content are to be allowed in each &#8220;pool&#8221; to control this.\u00a0 There are also a few technical issues with switching a live stream of corrections dealing with the need to make sure the new current ECEF is used by the clients, <span style=\"color: #0000ff;\"><strong>SNIP<\/strong><\/span> manages these issues for each client.\u00a0 Performing an Automatic fall-over to the next best base station when a stream fails is also an expected feature in such systems. <span style=\"color: #0000ff;\"><strong>SNIP<\/strong> <\/span>handles all of these issues.<\/p>\n<p style=\"text-align: left;\">For <span style=\"color: #0000ff;\"><strong>SNIP<\/strong> <\/span>deployments this is a paid feature only [it is not supported in the free <em><strong>Lite<\/strong> <\/em>model].\u00a0 But the evaluation mode offers a useful way for new users to fully evaluate this feature.<\/p>\n<h3 style=\"text-align: left;\">Set Up<\/h3>\n<p style=\"text-align: left;\">Here is a <a href=\"\/kb\/knowledge-base\/nearest-mountpt-dialog\/\">link <\/a>to primary set-up dialog used to control NEAR settings.<\/p>\n<h3 style=\"text-align: left;\">Best Practices<\/h3>\n<p style=\"text-align: left;\"><a href=\"\/kb\/knowledge-base\/nearest-mountpt-use-case-examples\/\">This <\/a>article serves to provide a few remarks on the practical details of using NEAR mountPts with your NTRIP Clients.<\/p>\n<hr \/>\n<p style=\"text-align: left;\"><strong>Status:<\/strong><\/p>\n<p style=\"text-align: left;\">Released for general use as of <span style=\"color: #0000ff;\"><strong>SNIP<\/strong><\/span> revision1.4.0, released on February 14th 2017<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The use of &#8220;NEAR&#8221; mountPt feature (default name: NEAR2 and NEAR3 for RTCM2 and RTCM3 data streams) can be used to allow your NTRIP Clients to easily connect to the closest operational base station without having to examine the contents of each entry found in the Caster table. The NEAR [&hellip;]<\/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":[282],"ht-kb-tag":[301,292,287],"class_list":["post-2885","ht_kb","type-ht_kb","status-publish","format-standard","hentry","ht_kb_category-nearest-caster","ht_kb_tag-base-line","ht_kb_tag-near","ht_kb_tag-nearest"],"_links":{"self":[{"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb\/2885","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=2885"}],"version-history":[{"count":19,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb\/2885\/revisions"}],"predecessor-version":[{"id":3463,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb\/2885\/revisions\/3463"}],"wp:attachment":[{"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/media?parent=2885"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb-category?post=2885"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb-tag?post=2885"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}