What's Inside a Mount Point's Own Listing
Every mount point is described by a standard set of fields, published in the caster's sourcetable so a client can see what it's choosing between before connecting. The official NTRIP specification defines these fields for each one:
Field | What It Tells You |
|---|---|
Mountpoint | The stream's identifier, entered exactly as shown when configuring a receiver or controller |
Format | The correction data type, almost always RTCM for RTK work |
Carrier | Whether carrier-phase data is included, and on which frequency bands |
Navigation-System | Which satellite constellations the stream covers (GPS, GLONASS, Galileo, BeiDou, and others) |
Network | The name of the network the stream belongs to |
Country | An ISO country code for the stream's coverage area |
Latitude / Longitude | The stream's reference position, a single base's actual location, or a general area for a network stream |
Solution | Whether the stream is single-base (0) or network-generated (1), the field that actually distinguishes a physical base feed from a VRS or area-correction feed |
Authentication / Fee | Whether the stream needs login credentials and whether it's a paid service |
Most of these fields never need reading directly, a receiver's software handles the connection using just the mount point name and login details, but the Solution field is the one worth understanding: it's the technical answer to whether a given mount point is one fixed base station or a computed network correction.
Single-Base vs Network Mount Points, and How Naming Reflects It
A single-base mount point streams RTCM data from one physical reference station at a fixed, known position, its accuracy degrading with distance the same way any physical base does. A network or VRS mount point instead streams a correction computed from a grid of reference stations for whatever position the rover reports, the accuracy staying more consistent across a wider coverage area.
Providers commonly reflect this difference in the mount point name itself, a naming pattern built around the nearest physical station selects a single-base feed automatically, while a name referencing "VRS" or a general network label points to the computed, area-wide option. Our How Does NTRIP Work? and What Is an NTRIP Caster? guides cover the protocol and the caster's own role in publishing this list; this page focuses on the mount point itself, the specific line item a rover actually picks.
Choosing the Right Mount Point for a Job
A VRS or network-generated mount point is the more reliable default for most jobs, since it doesn't rely on how close the nearest physical station happens to be to the working site. A single-base mount point is worth choosing deliberately when a specific station is known to be closer or more reliable than the network average, or when a provider's network option isn't available in a particular area.
Getting the mount point wrong, selecting a single base many kilometres from the actual site instead of the correct VRS option, or picking the wrong regional network entirely, is one of the most common reasons a connection succeeds but the rover never reaches FIX, or takes far longer than it should to converge. The connection itself working (a status showing "connected" or data flowing) isn't confirmation the right correction is being applied.
What This Means in Practice
A provider's own documentation or support team can confirm the exact mount point name for a specific site, and it's worth checking rather than guessing from a long, unfamiliar list. Once entered correctly into a receiver's or DJI Pilot 2's NTRIP settings, the mount point doesn't need revisiting unless the working location changes significantly or the provider restructures its network, it's a one-time setup detail rather than something to check on every job.
RTK Network Subscription - 1Y Unlimited
More than 7,500 base stations · Accuracy of 1.5cm with EU Certification
Free Gifts Included
Free Gifts Included
Common Questions
No. A caster is the server hosting the connection; a mount point is one specific correction stream on that caster. A single caster can host many mount points at once.
Your NTRIP provider supplies the correct name for your area, usually found in their coverage map or account portal. Naming often reflects whether it's a single-base or network/VRS feed, but confirming directly with the provider avoids guesswork.
It's a Virtual Reference Station or similar computed correction, built from multiple physical stations rather than broadcast from one fixed point, keeping accuracy more consistent across a coverage area.
Yes, the connection itself can succeed while the correction is still wrong for your location, showing up as a rover stuck on FLOAT or taking unusually long to reach FIX rather than an outright failure.
Occasionally, if a provider restructures its network or renames streams. If a previously working mount point stops connecting, checking for a naming change with the provider is a reasonable first step.
