> 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/arcgis-survey123.md).

# ArcGIS Survey123

These steps connect an ArcGIS Survey123 to the Premium Positioning correction network over NTRIP, using ArcGIS Survey123 app (+ receiver/companion app for NTRIP). 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.
* ArcGIS Survey123 app (+ receiver/companion app for NTRIP).
* 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. Understand the setup (read first): ArcGIS Survey123 does NOT have its own NTRIP client - it can't dial a caster directly. Your GNSS receiver (or its companion app) connects to Premium Positioning's NTRIP service and computes the corrected RTK position; Survey123 reads that position. So: (1) set up NTRIP on the receiver / its app, (2) connect Survey123 to that receiver. Have your welcome email handy for your NTRIP username/password.
2. Have your details ready: You need the NTRIP settings (same for all): Host rtkpremium.xyz, Port 2101, Mountpoint COMMON, Protocol NTRIP; plus your personal NTRIP username/password from the welcome email. Enter your own credentials only.
3. Configure NTRIP in your receiver's companion app: Open the app that controls your receiver - e.g. Trimble Mobile Manager (Trimble), Emlid Flow (Emlid), Eos Tools Pro (Arrow), or the receiver's own NTRIP screen. Find the 'Correction source' / 'NTRIP' / 'RTK' / 'Real-time corrections' section (wording varies by brand/version) and add an NTRIP / NTRIP Client connection.
4. Enter the Premium Positioning caster settings: In that NTRIP form enter Server/Host = rtkpremium.xyz, Port = 2101, then your NTRIP Username and Password from the welcome email. Save/connect. This is the ONLY place your NTRIP login is typed - into the receiver/app, never into Survey123.
5. Select the COMMON mountpoint: After connecting, the app retrieves the source table. Select COMMON. If asked, let it send your position (GGA) to the caster. Some apps require you to connect first, then pick the mountpoint.
6. Confirm the receiver reaches RTK Fixed: Watch the receiver/app status: Autonomous/Single → DGPS/Float → RTK Fixed ('Fixed', 'RTK', or a cm-level accuracy figure). Don't proceed until the receiver itself reports Fixed - Survey123 only inherits the receiver's accuracy.
7. Make the corrected position available to Survey123: On iOS/Windows and most Android setups, Survey123 connects to the receiver directly over Bluetooth (or network/TCP). On some Android workflows where a separate app supplies RTK, enable that app as a mock-location provider and point Survey123 at the device's 'Integrated provider'. Check your receiver's Esri integration notes for which applies.
8. Open Location settings in Survey123: In Survey123 open the main menu > Settings > Location. (If your version differs, look for the 'Location' or 'GPS/Receiver' area under Settings.)
9. Add your receiver as a location provider: Choose 'Add provider' ('Add a location provider' / 'Add receiver'). Pick the connection type matching your setup: an external Bluetooth receiver (default), a Network connection (enter the receiver's IP and TCP port), or - for the mock-location route on Android - the device's Integrated provider. Select your receiver and connect.
10. Set antenna height and connection alerts: Open the provider's settings, name it, and set the Antenna height (antenna phase centre / receiver to the ground or survey point; Survey123 subtracts this from captured altitude). Optionally enable alerts if the link drops. Note: there's no NTRIP field in Survey123 - it stays in the receiver/companion app.
11. Check the location status in Survey123: Back on the Location screen, Survey123 shows live fix details from the receiver. Confirm it reports the corrected position - a Fixed/RTK fix type with cm-level accuracy, matching the receiver. If Survey123 shows only GPS/autonomous (metres), the corrected stream isn't reaching it - recheck the connection and the receiver's RTK status.
12. Prepare the survey for high accuracy (survey author): In the survey design, set quality controls on the geopoint question: an accuracy threshold (body::accuracyThreshold for averaging), optionally a constraint to block submission above a limit, or bind::esri:warning to warn the user. Capture GNSS metadata with pulldata('@geopoint', ...) for fields like accuracy and fix type. Match the survey's coordinate settings to the corrections' reference frame.
13. Capture a point and verify the cm-level fix: Add a geopoint. Confirm Survey123 shows a Fixed / RTK solution with cm-level accuracy (within your threshold) before recording. Let averaging settle if used, then save. If the fix drops to Float/autonomous, let the receiver re-establish RTK Fixed via COMMON before collecting.

### If the fix will not hold

Survey123 has no internal NTRIP client - corrections are set up on the receiver or its companion app (TMM, Emlid Flow, Eos Tools Pro, or the receiver's own NTRIP screen); Survey123 reads the corrected position over Bluetooth, network/TCP, or (on some Android setups) a mock/integrated provider. Caster (same for all): rtkpremium.xyz / 2101 / COMMON / NTRIP; your personal credentials go into the receiver/app, never Survey123. Labels vary by Survey123 version and receiver brand. A Fixed solution depends on the receiver reaching RTK first.

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.