Mapit GIS NTRIP Setup: Android & iOS RTK

Connect Mapit GIS on Android and iOS to RTKdata NTRIP corrections for centimeter RTK. Built-in NTRIP client, receiver setup, Send GGA, and on-device geoid heights.

Mapit GIS is a GIS data collection and mapping app with a built-in NTRIP client for receiving real-time RTK corrections. NTRIP is integrated directly into the main app (Settings → NTRIP Corrections) — there is no separate companion app. Mapit connects to an external GNSS receiver, streams corrections from an NTRIP caster like RTKdata.com to that receiver, and lets you collect centimeter-level data in the field.

Download:

• Mapit GIS — Android (3.2.8+) (Google Play — free tier available, Pro/Pro Plus subscriptions for advanced features)

• Mapit GIS — iOS (1.7+) (App Store)

NTRIP is now built in. Earlier versions of this guide referenced a separate "Mapit GIS – NTRIP Client" companion app and an RTKLIB processing engine. That architecture no longer exists. Since the v3.0 rebuild, NTRIP corrections are part of the main Mapit GIS app. The receiver computes the RTK solution; Mapit forwards the RTCM corrections to it.

How it works

Mapit GIS connects to your NTRIP caster, receives RTCM corrections, and forwards them to your connected GNSS receiver. The receiver itself computes the RTK fix (Float → Fixed) — Mapit does not do on-device RTK processing. This is the standard "NTRIP client + smart receiver" model used by most field software.

Key capabilities

Feature	Details
Platform	Android and iOS (phone or tablet)
Cost	Free tier available. NTRIP RTK corrections require a Mapit Pro Plus subscription.
Receiver connection (Android)	Bluetooth Classic (SPP), Bluetooth LE (Nordic UART), USB serial, TCP/Wi-Fi
Receiver connection (iOS)	Bluetooth LE and TCP/IP work without restriction. Classic-Bluetooth receivers require Apple MFi whitelisting (currently Eos Arrow and Juniper Geode/Spire).
NTRIP support	Built-in NTRIP client — NTRIP v1 and v2
RTK processing	Performed by the receiver. Mapit forwards RTCM corrections and reads the receiver's NMEA position.
GIS features	Point/line/polygon collection, attribute forms
Export formats	GeoJSON, KML, Shapefile, CSV, DXF, GPX, GeoParquet, plus direct publishing to PostgreSQL/PostGIS and ArcGIS Online
Heights	Can apply a geoid model on-device (Pro Plus Orthometric Height feature, e.g. EGM2008 / OSGM15 / GEOID18) to output orthometric (MSL) heights directly

Requirements

• Android (3.2.8+) or iOS (1.7+) phone or tablet running a current version of Mapit GIS

• Mapit Pro Plus subscription (required for NTRIP RTK corrections)

• A multi-frequency (L1/L2) RTK-capable GNSS receiver that accepts RTCM3 corrections (e.g., Eos Arrow, Juniper Geode/Spire, ArduSimple, SparkFun RTK, u-blox F9P board)

• Internet connection (cellular data or Wi-Fi)

• Active RTKdata.com account with RTK credentials

Don't have an RTKdata.com account yet? Start 30-day Free Trial or View Pricing

Step-by-step setup

1

Install Mapit GIS and subscribe to Pro Plus

Install Mapit GIS (Android 3.2.8+ or iOS 1.7+) and subscribe to Mapit Pro Plus, which unlocks NTRIP RTK corrections.

2

Connect your GNSS receiver

Pair and connect your external GNSS receiver under Settings → External GNSS. Choose the connection type your receiver uses (Bluetooth / BLE / USB / TCP).

On iOS, classic-Bluetooth receivers require Apple MFi whitelisting (currently Eos Arrow and Juniper Geode/Spire). BLE and TCP/IP receivers connect without that restriction. On Android, pair Bluetooth receivers in the OS Bluetooth settings first.

3

Add an NTRIP configuration

Go to Settings → NTRIP Corrections → Add Configuration and enter your RTKdata caster details for your region:

North America

• Host: rtk.rtkdata.com

• IP Fallback: 13.56.117.10

• Port: 2101

• Username / Password: From RTK Credentials in the internal dashboard (not website login)

• Mountpoint (ALL CAPS): AUTO (recommended) — or AUTO_WGS84, AUTO_ITRF2020, AUTO_ITRF2014

Europe

• Host: eu.rtkdata.com

• IP Fallback: 3.73.41.96

• Port: 2101

• Username / Password: From RTK Credentials in the internal dashboard (not website login)

• Mountpoint (ALL CAPS): AUTO (recommended) — or AUTO_WGS84, AUTO_ITRF2020, AUTO_ITRF2014

Australia

• Host: aus.rtkdata.com

• IP Fallback: 54.206.56.130

• Port: 2101

• Username / Password: From RTK Credentials in the internal dashboard (not website login)

• Mountpoint (ALL CAPS): AUTO (recommended) — or AUTO_WGS84, AUTO_ITRF2020, AUTO_ITRF2014

4

Set the receiver target and keep Send GGA on

1. Set the receiver target (Bluetooth / BLE / TCP / USB) so corrections are forwarded to the right device.

2. Leave Send GGA on — this is required.

Send GGA must stay enabled. The RTKdata caster uses your GGA position to select the nearest reference station from its network and stream corrections from it. Without GGA, the caster authenticates you but never assigns a base station, and you stay stuck on Float. (RTKdata is a single-baseline network keyed to your position via GGA — it is not a VRS service.)

5

Connect and verify Fix

1. Tap Connect.

2. The NTRIP indicator on the map turns green once the receiver reaches Float/Fixed.

3. Wait for the receiver to report RTK Fixed. Convergence typically takes 15–60 seconds under open sky.

Vertical reference (heights)

RTKdata delivers ellipsoidal heights (height above the WGS 84 ellipsoid). Unlike most field apps, Mapit GIS can convert these on-device:

Mapit GIS Pro Plus includes an Orthometric Height feature that applies a geoid model (e.g. EGM2008, OSGM15, GEOID18) on-device to output orthometric (mean sea level) heights directly — you do not need post-processing just to convert from ellipsoidal to orthometric. See Understanding Heights.

Troubleshooting

Problem	Cause	Fix
Stuck on Float indefinitely	GGA not being sent to the caster	Confirm Send GGA is enabled in the NTRIP configuration
Connected but no corrections	Wrong host for your region, or blank port	Verify the regional host spelling and that the port is 2101
Mountpoint error	Wrong capitalization	Type AUTO in ALL CAPS
Receiver not found (Android)	Device not paired in OS settings	Pair the receiver in Android Bluetooth settings first, then select it under Settings → External GNSS
Classic-Bluetooth receiver won't connect (iOS)	Apple MFi restriction	Use a BLE or TCP/IP receiver, or one of the MFi-whitelisted models (Eos Arrow, Juniper Geode/Spire)
Receiver reaches Fixed but heights look wrong	Expecting orthometric but receiving ellipsoidal	Enable the Orthometric Height geoid model (Pro Plus) or convert in post-processing
NTRIP RTK options missing	Free tier, or app not updated	Subscribe to Mapit Pro Plus and update to the current app version

Tips for best results

• One app, NTRIP built in. There is no separate companion app and no RTKLIB/"Positioning Mode" configuration. Everything lives under Settings → NTRIP Corrections.

• The receiver computes the fix. Mapit forwards RTCM and reads NMEA — make sure your receiver is a true RTK receiver that accepts RTCM3 corrections.

• Send GGA is mandatory for the AUTO mountpoint. See NTRIP & GGA Essentials.

• Get orthometric heights on-device with the Pro Plus geoid feature instead of post-processing.

• Export is flexible — DXF, GPX, GeoParquet, GeoJSON, KML, Shapefile, and CSV, plus direct publishing to PostGIS and ArcGIS Online.

Reference links (Mapit GIS)

• NTRIP Client guide: mapitgis.com/docs/external-gnss/ntrip-client

• Connecting a receiver: mapitgis.com/docs/external-gnss/connecting-a-receiver

• RTK and fix types: mapitgis.com/docs/external-gnss/rtk-and-fix-types

• Geoid / orthometric heights: mapitgis.com/docs/settings/geoid-models

• Mapit Pro Plus: mapitgis.com/docs/subscriptions/mapit-pro-plus

Related Industry Solutions

• Utilities

• Environmental Monitoring