# RTK Facet\_SW Maps NTRIP Client\_Mount Points

**URL:** <https://community.sparkfun.com/t/rtk-facet-sw-maps-ntrip-client-mount-points/63627>\
**Category:** GPS/GNSS\
**Created:** [February 26, 2025, 2:38pm UTC](https://community.sparkfun.com/t/rtk-facet-sw-maps-ntrip-client-mount-points/63627 "2025-02-26T14:38:56Z")\
**Posts on this page:** 1\
**Showing post:** 23

<div class="post-metadata">

**Author:** ![Bushman\_K](https://avatars.discourse-cdn.com/v4/letter/b/91b2a8/32.png) [@Bushman\_K](https://community.sparkfun.com/u/Bushman_K)\
**Post date:** [February 27, 2025, 7:04pm UTC](https://community.sparkfun.com/t/rtk-facet-sw-maps-ntrip-client-mount-points/63627/23 "2025-02-27T19:04:31Z")

</div>

Well, [wiscors.dot.wi.gov:2101](http://wiscors.dot.wi.gov:2101) returns this mount point table (filtered, removed everything with irrelevant CMR protocol):

 ![image](https://canada1.discourse-cdn.com/sparkfun/original/2X/d/d94fa7d64638cec0116f8c7a99bba726265ab91b.png)  
All these are “smart” mount points that provide corrections based on the rover’s location (when the rover reports its location to the NTRIP caster correctly).  
The “safest” mount point to try is `SingleBase_RTCM31` because it simply acts as an automatic “switch” to send corrections directly from the nearest base station instead of doing any additional “magic.”  
Otherwise, any failures to obtain a fixed solution are likely due to one of the factors:

- The rover doesn’t recognize RTCM messages specific to a certain protocol.
- The rover doesn’t send its location correctly so the caster can’t send proper data since it doesn’t know the rover’s location.

SW Maps absolutely allows typing in the mount point name by hand on Android, can’t say anything about iOS.

Another port, [wiscors.dot.wi.gov:2102](http://wiscors.dot.wi.gov:2102) returns a table of individual base stations.

---

_[View the full topic](https://community.sparkfun.com/t/rtk-facet-sw-maps-ntrip-client-mount-points/63627)._