> For the complete documentation index, see [llms.txt](https://docs.premium-positioning.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.premium-positioning.com/guides/mergin-maps.md).

# Mergin Maps

These steps connect a Mergin Maps (Input app) to the Premium Positioning correction network over NTRIP, using Mergin Maps / Input app (QGIS). They assume you already have your NTRIP credentials.

### Before you start

* Your NTRIP username and password, from your Premium Positioning welcome email or your account on the customer portal.
* Mergin Maps / Input app (QGIS).
* A working internet connection on the controller or phone.
* A clear view of the sky at the point you are measuring.

### Network settings

These are the same for every Premium Positioning customer. Only your username and password are unique to you.

* Server or host: rtkpremium.xyz
* Port: 2101
* Mountpoint: COMMON
* Protocol: NTRIP

### Steps

1. Important: Mergin Maps has no built-in NTRIP client: Mergin Maps (the Input app) does NOT receive RTK corrections itself - it only reads the finished, corrected position over Bluetooth from your GNSS receiver. So the caster details (host, port, mountpoint, username, password) go into your GNSS RECEIVER or its own companion app (e.g. Emlid Flow, Leica Zeno Connect, Trimble Mobile Manager, GNSS Master, SW Maps, or a generic NTRIP client app) - NOT into Mergin Maps. Set up corrections on the receiver first, then connect Mergin Maps to it.
2. Enter the NTRIP caster details in your receiver's app: Open your receiver's companion app and add a new NTRIP correction source / NTRIP client profile: Host rtkpremium.xyz, Port 2101, Mountpoint COMMON, Protocol NTRIP. For Username/Password enter YOUR OWN from your welcome email - unique to your account; do not reuse anyone else's.
3. Confirm the receiver is getting corrections: In the receiver's app, start the NTRIP client and confirm corrections are flowing (incoming bytes/age of corrections) and the status progresses single/autonomous → FLOAT → FIXED. You must reach FIXED on the receiver before Mergin Maps can report cm accuracy. Stay outdoors with clear sky and a working data connection.
4. Pair the receiver with your phone/tablet over Bluetooth: In your device's system Settings > Bluetooth, make the receiver discoverable and pair it (complete any PIN prompt). Done once per device.
5. Open Mergin Maps and go to Settings: Launch Mergin Maps (Input), open your project, tap More (bottom toolbar) and open Settings. Find the GPS section.
6. Open Manage GPS receivers: In the GPS section tap Manage GPS receivers (older versions: Select GPS receiver) - where Mergin lists internal and external position sources.
7. Connect to your paired receiver: Tap Connect new receiver(s), then choose your GNSS receiver from the paired Bluetooth devices. Mergin connects and reads the position stream (NMEA) from the receiver.
8. Set the antenna height: In the GPS settings, set the GPS antenna height - ground to the antenna reference point plus any antenna offset (pole height plus antenna phase-centre offset). You can also store it automatically via the @position\_gps\_antenna\_height variable in your form.
9. Confirm the source is your external receiver: Tap the GPS accuracy button (bottom-left of the map). In the GPS info panel, check that Source shows your external GPS device name, not the phone's internal GPS.
10. Check accuracy and fix quality: In the same panel review Horizontal/Vertical accuracy, Satellites, and the fix details. With corrections working on the receiver, horizontal accuracy should fall to \~1 - 2 cm. The GPS accuracy button colour reflects whether you're within your accuracy threshold.
11. Set your accuracy threshold (optional): In GPS settings set the GPS accuracy threshold so the GPS button turns a good colour only when you're within your required accuracy (e.g. a few centimetres) - a quick visual confirmation while surveying.
12. Confirm an RTK fix before recording: Verify the receiver reports FIXED and Mergin shows cm-level horizontal accuracy with your external receiver as the source. If you see only FLOAT or sub-metre, wait for the receiver to converge to FIXED (check sky view, data, and that the NTRIP client is still connected to rtkpremium.xyz:2101 / COMMON). Then capture points.

### If the fix will not hold

Mergin Maps / Input is QGIS-based and does NOT include a built-in NTRIP client. Corrections (rtkpremium.xyz / 2101 / COMMON / NTRIP) are configured on the GNSS receiver or its companion/NTRIP-client app - Mergin only consumes the corrected position over Bluetooth. Enter YOUR OWN NTRIP username/password into the receiver/app; never type them into Mergin Maps. UI labels (Manage GPS receivers, Connect new receiver, GPS accuracy button) vary slightly by version/platform. A FIXED solution on the receiver is required for cm accuracy.

For more, see RTK corrections troubleshooting and Fix inconsistent RTK accuracy on site.

### Need help

Support is available 24/7. Include your receiver model, the mountpoint, the solution status, and the correction age when you get in touch.