[{"data":1,"prerenderedAt":1343},["ShallowReactive",2],{"knowledge-page-en-\u002Ftroubleshooting\u002Fwrong-coordinates-rtk-fix":3},{"article":4,"posts":449,"relatedPosts":450},{"id":5,"title":6,"author":7,"body":8,"category":434,"cover":435,"description":436,"extension":437,"meta":438,"navigation":439,"path":440,"publishedAt":441,"relatedArticles":442,"seo":445,"stem":446,"updatedAt":447,"__hash__":448},"knowledge_en\u002Fen\u002Ftroubleshooting\u002Fwrong-coordinates-rtk-fix.md","My coordinates are wrong — but I have RTK Fix","Yuri",{"type":9,"value":10,"toc":423},"minimark",[11,30,35,38,59,63,98,102,138,145,149,169,173,208,212,235,239,242,409,416],[12,13,17],"card",{"additionalstyles":14,"color":15,"title":16},"mt-[60px]","primary","The key distinction: precision vs accuracy",[18,19,20,21,25,26,29],"p",{},"RTK Fix gives you high ",[22,23,24],"strong",{},"precision"," — your positions are repeatable and internally consistent to centimetres. ",[22,27,28],{},"Accuracy"," — how well those positions match real-world coordinates — depends on the datum, coordinate system and geoid model applied on top. Fix without the right transformation applied can be precise but inaccurate.",[31,32,34],"h2",{"id":33},"diagnose-by-offset-size","Diagnose by offset size",[18,36,37],{},"The size and direction of the coordinate error is the fastest clue to the cause. Select the pattern that matches your situation:",[39,40,42,47,51,55],"cards",{"additionalstyles":41},"mt-[40px]",[43,44],"cards-item",{"text":45,"title":46},"Consistent shift in one direction. Horizontal only — height looks fine.","0.5 – 2 m",[43,48],{"text":49,"title":50},"Height only — plan position is fine. Ellipsoidal vs orthometric height confusion.","0.3 – 1 m",[43,52],{"text":53,"title":54},"Large offset, possibly inconsistent. Completely wrong coordinate system selected.","10 m – 100 m+",[43,56],{"text":57,"title":58},"Height only and consistent across all points. Wrong antenna height entered.","2 cm – 50 cm",[31,60,62],{"id":61},"cause-1-datum-mismatch","Cause 1 — Datum mismatch",[64,65,70,73,76],"cause-card",{"additionalstyles":14,"frequency":66,"icon":67,"level":68,"title":69},"Typical offset: 0.5 – 2 m horizontal","icons\u002FWorld.svg","5","WGS84 \u002F ETRS89 corrections applied without local datum transformation",[18,71,72],{},"All NTRIP correction services — including GEODNET-based services — deliver corrections in WGS84 or ETRS89. These are global reference frames used by satellites. Most countries work in a local national datum — RD New in the Netherlands, OSGB36 in the UK, GDA2020 in Australia — which does not perfectly align with WGS84.",[18,74,75],{},"The difference between WGS84 and a national datum is small but significant for precision work: typically 0.5 – 1.5 m in the Netherlands, and similar magnitudes in other countries. If your field software is not applying the correct datum transformation, every point you collect will be shifted by this amount.",[77,78,79,83,89,95],"ol",{},[80,81,82],"li",{},"Check your job's coordinate system settings. Verify that both the horizontal datum and transformation method are set correctly for your country.",[80,84,85,88],{},[22,86,87],{},"For the Netherlands:"," the job must use RD New (EPSG:28992) with the RDNAPTRANS™ 2018 transformation. Without it, positions will be off by roughly 0.6 – 0.9 m.",[80,90,91,94],{},[22,92,93],{},"For the UK:"," use OSGB36 (British National Grid, EPSG:27700) with the OSTN15 transformation and OSGM15 geoid. Without OSTN15, horizontal positions are off by up to 1.5 m and heights by several metres.",[80,96,97],{},"Verify by occupying a known national control point. If the offset is consistent in direction and magnitude across all points, it is a datum transformation problem.",[31,99,101],{"id":100},"cause-2-missing-or-wrong-geoid-model","Cause 2 — Missing or wrong geoid model",[64,103,107,110,113,116],{"additionalstyles":14,"frequency":104,"icon":105,"level":68,"title":106},"Typical offset: 0.3 – 50+ m in height only","icons\u002FRuler.svg","Ellipsoidal height reported instead of orthometric (above sea level) height",[18,108,109],{},"GNSS receivers measure height relative to the WGS84 ellipsoid — a mathematical model of Earth's shape. This ellipsoidal height is not the same as the height above sea level (orthometric height) that appears on maps and is used in engineering.",[18,111,112],{},"In the Netherlands, the difference between ellipsoidal height and NAP (Normaal Amsterdams Peil, the Dutch vertical datum) varies between approximately 38 m and 44 m across the country. If your receiver outputs ellipsoidal height and your project uses NAP heights, every elevation you collect will be wrong by this amount.",[18,114,115],{},"The correction between ellipsoidal and orthometric height is called the geoid undulation. Applying the correct geoid model converts one to the other.",[77,117,118,125,130,135],{},[80,119,120,121,124],{},"Check whether your field software applies a geoid model. In Emlid Flow, go to ",[22,122,123],{},"Job settings → Coordinate system"," and verify that a geoid file is selected.",[80,126,127,129],{},[22,128,87],{}," use the NLGEO2018 geoid, included in RDNAPTRANS™ 2018. This converts ellipsoidal heights to NAP. Without it, heights are out by 38 – 44 m.",[80,131,132,134],{},[22,133,93],{}," use OSGM15. For Germany use GCG2016, Belgium BG03 and France RAF18. See the country table below for a full reference.",[80,136,137],{},"If the geoid file is not available in your software, download it from the national geodetic authority and import it into the coordinate library.",[12,139,142],{"additionalstyles":14,"color":140,"title":141},"orange","A 40-metre height error is not RTK failure",[18,143,144],{},"A common support question is: “My heights are completely wrong — off by 40 metres.” This is almost never a receiver problem. It is the difference between WGS84 ellipsoidal height and NAP, or another national vertical datum. The RTK Fix is working perfectly — the geoid model has simply not been applied.",[31,146,148],{"id":147},"cause-3-wrong-coordinate-system-in-your-job","Cause 3 — Wrong coordinate system in your job",[64,150,155,158],{"additionalstyles":14,"frequency":151,"icon":152,"level":153,"title":154},"Typical offset: 10 m to hundreds of metres","icons\u002FMap.svg","4","Job configured with the wrong projection or EPSG code",[18,156,157],{},"If your positions are off by tens or hundreds of metres, or if the offset varies across your site rather than being a consistent shift, the most likely cause is a completely wrong coordinate system. This happens when the job is created with the default coordinate system — often WGS84 geographic or a UTM zone — instead of the project's required system.",[77,159,160,163,166],{},[80,161,162],{},"Check the EPSG code of your job's coordinate system and compare it with what your project requires. Netherlands: EPSG:28992 (RD New). Germany: EPSG:25832 (ETRS89 \u002F UTM zone 32N) or state-specific systems. Belgium: EPSG:31370 (Belgian Lambert 72).",[80,164,165],{},"If the wrong system was used for existing data, re-process the raw observations in the correct coordinate system rather than applying a post-collection offset. Projection errors are not uniform across large areas.",[80,167,168],{},"Create a template job with the correct coordinate system and transformation before fieldwork begins. Share it with the whole team so everyone uses the same settings.",[31,170,172],{"id":171},"cause-4-antenna-height-error","Cause 4 — Antenna height error",[64,174,179,182],{"additionalstyles":14,"frequency":175,"icon":176,"level":177,"title":178},"Typical offset: 2 cm – 50 cm in height, consistent across all points","icons\u002FSatellite.svg","3","Incorrect antenna height or measurement reference entered",[18,180,181],{},"The antenna height you enter in your field software is subtracted from the measured position to compute the ground point. An error here shifts every height measurement by exactly the same amount. This is a systematic error, which makes it identifiable.",[77,183,184,190,196,202],{},[80,185,186,189],{},[22,187,188],{},"Verify what the height is measured to."," Different manufacturers measure to different reference points. Emlid heights are measured to the bottom of the receiver. Trimble heights are typically measured to the antenna reference point (ARP). Entering the wrong reference adds or subtracts the antenna offset on top of your field measurement.",[80,191,192,195],{},[22,193,194],{},"Check the vertical offset in the antenna profile."," Most field software stores a vertical offset for each receiver model. Verify this value matches the published receiver specifications.",[80,197,198,201],{},[22,199,200],{},"For tilted pole work:"," ensure the pole bubble is calibrated. A 2° tilt on a 2-metre pole introduces a 7 cm horizontal error.",[80,203,204,207],{},[22,205,206],{},"Test on a known benchmark."," If the height error equals your measured antenna height exactly, you have entered it in the wrong direction.",[31,209,211],{"id":210},"cause-5-antenna-phase-centre-offset","Cause 5 — Antenna phase centre offset",[64,213,218,221,224],{"additionalstyles":14,"frequency":214,"icon":215,"level":216,"title":217},"Typical offset: 2 – 10 cm, height only","icons\u002FCog.svg","2","Receiver antenna profile missing or incorrect in field software",[18,219,220],{},"GNSS receivers do not measure position at the physical base of the antenna. They measure at the antenna phase centre — a point inside the antenna that varies by satellite elevation angle. Field software corrects for this using antenna calibration data.",[18,222,223],{},"If your receiver model is not in the software's antenna database, or the wrong model is selected, the phase centre correction is not applied and height measurements are off by a few centimetres. This is less common than datum and geoid errors but matters for the highest-accuracy applications.",[77,225,226,229,232],{},[80,227,228],{},"In your field software, check that the antenna model matches your physical receiver exactly — including variant, such as RS2 versus RS2+.",[80,230,231],{},"For Emlid receivers used with third-party software, download the IGS antenna calibration file in ANTEX format and import it into the antenna database.",[80,233,234],{},"If the offset is consistent and small — 2 to 5 cm in height — it is worth investigating. If it is larger, revisit antenna height entry or the geoid model first.",[31,236,238],{"id":237},"correct-settings-by-country","Correct settings by country",[18,240,241],{},"Use this table to verify the coordinate system, datum transformation and geoid model for your working country. All of these must be configured correctly in your field software at the same time.",[243,244,245,264],"table",{},[246,247,248],"thead",{},[249,250,251,255,258,261],"tr",{},[252,253,254],"th",{},"Country",[252,256,257],{},"Horizontal CRS",[252,259,260],{},"Datum transformation",[252,262,263],{},"Vertical \u002F geoid",[265,266,267,284,300,316,332,348,362,377,393],"tbody",{},[249,268,269,275,278,281],{},[270,271,272],"td",{},[22,273,274],{},"Netherlands",[270,276,277],{},"RD New — EPSG:28992",[270,279,280],{},"RDNAPTRANS™ 2018",[270,282,283],{},"NAP via NLGEO2018",[249,285,286,291,294,297],{},[270,287,288],{},[22,289,290],{},"United Kingdom",[270,292,293],{},"British National Grid — EPSG:27700",[270,295,296],{},"OSTN15",[270,298,299],{},"ODN via OSGM15",[249,301,302,307,310,313],{},[270,303,304],{},[22,305,306],{},"Germany",[270,308,309],{},"ETRS89 \u002F UTM zone 32N — EPSG:25832",[270,311,312],{},"ETRS89 → DHDN BeTA2007",[270,314,315],{},"DHHN2016 via GCG2016",[249,317,318,323,326,329],{},[270,319,320],{},[22,321,322],{},"Belgium",[270,324,325],{},"Belgian Lambert 72 — EPSG:31370",[270,327,328],{},"BD72 transformation",[270,330,331],{},"TAW via BG03",[249,333,334,339,342,345],{},[270,335,336],{},[22,337,338],{},"France",[270,340,341],{},"RGF93 v2 \u002F Lambert-93 — EPSG:2154",[270,343,344],{},"Direct ETRS89 alignment",[270,346,347],{},"NGF-IGN69 via RAF18",[249,349,350,355,357,359],{},[270,351,352],{},[22,353,354],{},"Denmark",[270,356,309],{},[270,358,344],{},[270,360,361],{},"DVR90 via DK-GM2022",[249,363,364,369,372,374],{},[270,365,366],{},[22,367,368],{},"Sweden",[270,370,371],{},"SWEREF99 TM — EPSG:3006",[270,373,344],{},[270,375,376],{},"RH2000 via SWEN17",[249,378,379,384,387,390],{},[270,380,381],{},[22,382,383],{},"Australia",[270,385,386],{},"GDA2020 \u002F MGA — zone-specific",[270,388,389],{},"GDA94 → GDA2020 transformation grid",[270,391,392],{},"AHD via AUSGeoid2020",[249,394,395,400,403,406],{},[270,396,397],{},[22,398,399],{},"United States",[270,401,402],{},"State Plane or UTM (NAD83)",[270,404,405],{},"NAD83 (2011) — use epoch-matched",[270,407,408],{},"NAVD88 via GEOID18",[12,410,413],{"additionalstyles":14,"color":411,"title":412},"green","Always verify on a known control point",[18,414,415],{},"Before collecting data on any project, occupy a published national control point with known coordinates in the project datum. Compare your measured coordinates against the published values. A discrepancy of more than 3 cm horizontally or 5 cm vertically indicates a datum, geoid or antenna-height problem that must be resolved before fieldwork begins.",[12,417,420],{"additionalstyles":418,"color":15,"title":419},"mt-[30px]","Not sure which settings your software is using?",[18,421,422],{},"Describe your device, field software and the coordinate error you are seeing to the AI. Include the offset size, direction and whether it affects horizontal position, height or both for a specific diagnosis.",{"title":424,"searchDepth":425,"depth":425,"links":426},"",2,[427,428,429,430,431,432,433],{"id":33,"depth":425,"text":34},{"id":61,"depth":425,"text":62},{"id":100,"depth":425,"text":101},{"id":147,"depth":425,"text":148},{"id":171,"depth":425,"text":172},{"id":210,"depth":425,"text":211},{"id":237,"depth":425,"text":238},"troubleshooting","Troubleshooting\u002FWebP\u002Fmy-coordinates-are-wrong-but-i-have-rtk-fix.webp","RTK Fix means centimetre-level precision relative to the reference frame. It does not guarantee your coordinates match what you expect on a map or in a national coordinate system. When Fix is solid but coordinates are off, the cause is almost always a datum or coordinate system mismatch — not the RTK itself.","md",{},true,"\u002Fen\u002Ftroubleshooting\u002Fwrong-coordinates-rtk-fix","2026-07-25",[443,444],"\u002Fen\u002Ftroubleshooting\u002Fntrip-connection-failed","\u002Fen\u002Flearn\u002Fwhat-is-gga",{"title":6,"description":436},"en\u002Ftroubleshooting\u002Fwrong-coordinates-rtk-fix",null,"bt1ZB70v_ZMJpavlRxYatogsGLmX87nqkgkPGXJZTcY",[],[451,917],{"id":452,"title":453,"author":7,"body":454,"category":434,"cover":909,"description":910,"extension":437,"meta":911,"navigation":439,"path":443,"publishedAt":441,"relatedArticles":912,"seo":914,"stem":915,"updatedAt":447,"__hash__":916},"knowledge_en\u002Fen\u002Ftroubleshooting\u002Fntrip-connection-failed.md","Cannot connect to NTRIP caster — what now?",{"type":9,"value":455,"toc":900},[456,460,463,507,511,533,537,578,591,595,657,661,665,699,703,706,785,789,894],[31,457,459],{"id":458},"quick-diagnostic-checklist","Quick diagnostic checklist",[18,461,462],{},"Before diving into causes, run through these five checks. They resolve the majority of NTRIP connection failures.",[12,464,466],{"additionalstyles":14,"color":411,"title":465},"Quick NTRIP diagnostic",[77,467,468,474,489,495,501],{},[80,469,470,473],{},[22,471,472],{},"Internet working?"," Open a browser and load any website. If it fails, fix your connection first.",[80,475,476,479,480,484,485,488],{},[22,477,478],{},"Correct host and port?"," Port must be ",[481,482,483],"code",{},"2101",". Host must match exactly — no typos and no ",[481,486,487],{},"http:\u002F\u002F"," prefix.",[80,490,491,494],{},[22,492,493],{},"Credentials correct?"," Username and password are case-sensitive. Copy-paste rather than typing.",[80,496,497,500],{},[22,498,499],{},"Mountpoint exists?"," Load the sourcetable from the server to confirm the mountpoint name.",[80,502,503,506],{},[22,504,505],{},"GGA enabled?"," Required for VRS mountpoints. It must be enabled in your NTRIP client.",[31,508,510],{"id":509},"cause-1-no-internet-connection","Cause 1 — No internet connection",[64,512,516,519],{"additionalstyles":14,"frequency":513,"icon":514,"level":68,"title":515},"Most common cause on first setup","icons\u002FData.svg","Device has no data connection",[18,517,518],{},"NTRIP corrections travel over a standard internet connection. If your device cannot reach the internet, it cannot reach the NTRIP server — regardless of how correctly everything else is configured.",[77,520,521,524,527,530],{},[80,522,523],{},"Open a browser on the same device and navigate to any website. If it does not load, resolve the connectivity issue before proceeding.",[80,525,526],{},"If you use a receiver with a built-in SIM card (Emlid RS3, RS4 or some Trimble units), verify the SIM has an active data plan and signal bars are showing.",[80,528,529],{},"If you use a phone hotspot, check that the device connecting to the hotspot actually has internet access through it — not just a Wi-Fi connection to the hotspot.",[80,531,532],{},"In areas with weak cellular signal, switch between 4G and 3G modes. A stable 3G connection is better than an unstable 4G one for NTRIP streaming.",[31,534,536],{"id":535},"cause-2-port-2101-is-blocked","Cause 2 — Port 2101 is blocked",[64,538,542,548],{"additionalstyles":14,"frequency":539,"icon":540,"level":153,"title":541},"Common on corporate networks and some mobile carriers","icons\u002FLock.svg","Firewall or carrier blocking TCP port 2101",[18,543,544,545,547],{},"NTRIP uses TCP port ",[481,546,483],{},". Some corporate Wi-Fi networks and mobile carriers block outbound connections on non-standard ports. If you have general internet access but cannot reach the NTRIP server, port blocking is likely.",[77,549,550,556,562,568],{},[80,551,552,555],{},[22,553,554],{},"Switch networks."," If you are on corporate Wi-Fi, switch to mobile data. If you are on mobile data, try a different carrier's SIM or a Wi-Fi network at home.",[80,557,558,561],{},[22,559,560],{},"Use a personal hotspot."," Create a hotspot from your phone's mobile data connection and connect your field device to it. This bypasses most corporate network restrictions.",[80,563,564,567],{},[22,565,566],{},"Ask IT to open the port."," On a corporate network, request that TCP port 2101 outbound is opened for your device. This is a standard NTRIP requirement.",[80,569,570,573,574,577],{},[22,571,572],{},"Test the port directly."," On a computer, open a terminal and run ",[481,575,576],{},"telnet ntrip.rtksub.com 2101",". If the connection opens, the port is accessible. If it times out, the port is blocked.",[12,579,581],{"additionalstyles":14,"color":15,"title":580},"Quick port test on Android",[18,582,583,584,587,588,590],{},"Install the free app ",[22,585,586],{},"Port Authority"," on Android. Enter the NTRIP host and port ",[481,589,483],{},", then tap Scan. A green result means the port is reachable. A red result means it is blocked on your current network.",[31,592,594],{"id":593},"cause-3-wrong-credentials-or-mountpoint","Cause 3 — Wrong credentials or mountpoint",[64,596,600,611],{"additionalstyles":14,"frequency":597,"icon":598,"level":153,"title":599},"Connection reaches the server but is rejected","icons\u002FKey.svg","Authentication failure or unknown mountpoint",[18,601,602,603,606,607,610],{},"If the server is reachable but your client receives an error like ",[481,604,605],{},"401 Unauthorized"," or ",[481,608,609],{},"404 Not Found",", the problem is the credentials or mountpoint name.",[77,612,613,619,632,638],{},[80,614,615,618],{},[22,616,617],{},"Check for typos."," Username and password are case-sensitive. Copy and paste from your service confirmation email rather than typing manually.",[80,620,621,624,625,606,628,631],{},[22,622,623],{},"Load the sourcetable."," Most NTRIP clients have a ",[22,626,627],{},"Get Mountpoints",[22,629,630],{},"Source Table"," button. Use it to fetch the current list of available mountpoints from the server — do not type the mountpoint name manually.",[80,633,634,637],{},[22,635,636],{},"Check your subscription status."," If your trial or subscription has expired, the server will reject your credentials even though they look correct.",[80,639,640,643,644,606,646,649,650,653,654,656],{},[22,641,642],{},"Verify the host address."," Do not include ",[481,645,487],{},[481,647,648],{},"https:\u002F\u002F"," before the hostname. Enter the hostname only — for example ",[481,651,652],{},"ntrip.rtksub.com"," — and set the port separately to ",[481,655,483],{},".",[658,659],"terminal-box",{"additionalstyles":418,"items":660},"Host|ntrip.rtksub.com||Port|2101||Mountpoint — standard|RTCM3_NL||Mountpoint — DJI drones|RTCM3_NL_MSM5||Mountpoint — VRS (>30 km)|RTCM3_NL_VRS||Mountpoint — high-end|RTCM3_NL_MSM7",[31,662,664],{"id":663},"cause-4-gga-not-being-sent","Cause 4 — GGA not being sent",[64,666,670,673],{"additionalstyles":14,"frequency":667,"icon":668,"level":177,"title":669},"Affects VRS mountpoints — connection appears successful but no data flows","icons\u002FMarker.svg","No GGA position being transmitted to server",[18,671,672],{},"VRS (Virtual Reference Station) mountpoints require your rover to send its approximate position to the NTRIP server. The server uses this to generate a virtual correction point near you. If GGA is not sent, the server streams nothing — you are connected but receive 0 bytes per second.",[77,674,675,689,692],{},[80,676,677,678,681,682,606,685,688],{},"In your NTRIP client settings, look for ",[22,679,680],{},"Send GGA to caster",", ",[22,683,684],{},"Transmit NMEA GGA",[22,686,687],{},"Send position to server",". Enable it.",[80,690,691],{},"Make sure your receiver has at least a Single solution before connecting. GGA requires a valid position — even a rough one. If GGA contains all zeros, the server cannot generate corrections.",[80,693,694,695,698],{},"If you are not using VRS but still see 0 bytes, try switching to a non-VRS mountpoint such as ",[481,696,697],{},"RTCM3_NL",". Standard mountpoints do not require GGA.",[31,700,702],{"id":701},"device-specific-fixes","Device-specific fixes",[18,704,705],{},"Select your device for tailored instructions:",[707,708,711,737,755,769,775],"device-tabs",{"additionalstyles":14,"default-tab":709,"items":710},"Emlid","Emlid|DJI|SW Maps|Trimble \u002F Leica|Lefebure",[712,713,714,731,734],"device-tab",{"name":709},[18,715,716,719,720,723,724,727,728,730],{},[22,717,718],{},"Emlid Flow (Reach RS2+, RS3, RS4, RX2):"," Go to ",[22,721,722],{},"Correction input → NTRIP",". Tap ",[22,725,726],{},"Add profile"," and fill in the credentials. Enable ",[22,729,680],{}," if you use a VRS mountpoint. Make sure the receiver has satellite lock (Single or better) before connecting.",[18,732,733],{},"If the connection fails with correct credentials, toggle airplane mode on and off to refresh the data connection, then reconnect.",[18,735,736],{},"For Emlid on Windows with FieldGenius: configure NTRIP inside Emlid Flow via the receiver's IP, not inside FieldGenius.",[712,738,740],{"name":739},"DJI",[18,741,742,743,746,747,750,751,754],{},"In DJI Pilot 2, go to ",[22,744,745],{},"RTK Settings → Custom Network RTK"," and check the host, port and credentials. Use ",[481,748,749],{},"RTCM3_NL_MSM5"," for DJI drones, or ",[481,752,753],{},"RTCM3_NL_VRS"," for long baselines. Make sure the controller has internet access before connecting.",[712,756,758],{"name":757},"SW Maps",[18,759,760,761,764,765,768],{},"Open ",[22,762,763],{},"NTRIP Client"," only after connecting the external receiver. The option does not appear without an active Bluetooth GNSS or USB Serial GNSS connection. Enable ",[22,766,767],{},"Send NMEA GGA to NTRIP Caster"," for VRS.",[712,770,772],{"name":771},"Trimble \u002F Leica",[18,773,774],{},"Confirm the controller has an active internet data link, then reload the sourcetable rather than entering a mountpoint manually. In Trimble Access, check the received-byte counter under the receiver's Data Link status.",[712,776,778],{"name":777},"Lefebure",[18,779,780,781,784],{},"In Lefebure NTRIP Client, add a new profile and use the ",[22,782,783],{},"Get Source Table"," button. Allow the app to use mobile data, and enable GGA when the selected mountpoint is VRS.",[31,786,788],{"id":787},"common-error-messages","Common error messages",[243,790,791,804],{},[246,792,793],{},[249,794,795,798,801],{},[252,796,797],{},"Error message",[252,799,800],{},"Meaning",[252,802,803],{},"Fix",[265,805,806,818,830,843,856,867,881],{},[249,807,808,812,815],{},[270,809,810],{},[481,811,605],{},[270,813,814],{},"Wrong username or password",[270,816,817],{},"Check credentials. Copy-paste from your account dashboard.",[249,819,820,824,827],{},[270,821,822],{},[481,823,609],{},[270,825,826],{},"Mountpoint does not exist",[270,828,829],{},"Load the sourcetable and select a mountpoint from the list.",[249,831,832,837,840],{},[270,833,834],{},[481,835,836],{},"Connection refused",[270,838,839],{},"Port 2101 blocked or server unreachable",[270,841,842],{},"Switch to mobile data. Test the port with telnet or Port Authority.",[249,844,845,850,853],{},[270,846,847],{},[481,848,849],{},"Connection timeout",[270,851,852],{},"No route to server — network or firewall issue",[270,854,855],{},"Check the internet connection. Try a different network.",[249,857,858,861,864],{},[270,859,860],{},"Connected, 0 bytes\u002Fsec",[270,862,863],{},"GGA not sent for VRS, or wrong mountpoint",[270,865,866],{},"Enable GGA. Switch to a non-VRS mountpoint as a test.",[249,868,869,875,878],{},[270,870,871,874],{},[481,872,873],{},"ICY 200 OK"," then drops",[270,876,877],{},"Successful connection but stream interrupted",[270,879,880],{},"Unstable internet. Use a hotspot and enable auto-reconnect.",[249,882,883,888,891],{},[270,884,885],{},[481,886,887],{},"Sourcetable empty",[270,889,890],{},"Server reachable but no mountpoints returned",[270,892,893],{},"Your subscription may be inactive. Contact your correction service.",[12,895,897],{"additionalstyles":14,"color":411,"title":896},"Still stuck?",[18,898,899],{},"If none of the above resolves the issue, the problem may be specific to your receiver model or network environment. Describe your exact error message, device and current network setup to the AI for a targeted answer.",{"title":424,"searchDepth":425,"depth":425,"links":901},[902,903,904,905,906,907,908],{"id":458,"depth":425,"text":459},{"id":509,"depth":425,"text":510},{"id":535,"depth":425,"text":536},{"id":593,"depth":425,"text":594},{"id":663,"depth":425,"text":664},{"id":701,"depth":425,"text":702},{"id":787,"depth":425,"text":788},"Troubleshooting\u002FWebP\u002Fcannot-connect-to-ntrip-caster-what-now.webp","NTRIP connection failures have a small number of root causes. Work through this guide from the top — most problems are solved within the first three checks.",{},[913,444],"\u002Fen\u002Ftroubleshooting\u002Fstuck-on-float",{"title":453,"description":910},"en\u002Ftroubleshooting\u002Fntrip-connection-failed","6dPLfUP248llqwHU3VZpKE8iJ50c-nLalv8qxJwJOAw",{"id":918,"title":919,"author":7,"body":920,"category":1333,"cover":1334,"description":1335,"extension":437,"meta":1336,"navigation":439,"path":444,"publishedAt":441,"relatedArticles":1337,"seo":1340,"stem":1341,"updatedAt":447,"__hash__":1342},"knowledge_en\u002Fen\u002Flearn\u002Fwhat-is-gga.md","What is GGA and why do I need to enable it?",{"type":9,"value":921,"toc":1322},[922,926,933,941,944,948,951,954,1036,1041,1044,1155,1161,1165,1199,1203,1221,1225,1228,1300,1304],[31,923,925],{"id":924},"what-gga-is","What GGA is",[18,927,928,929,932],{},"GGA stands for ",[22,930,931],{},"Global Positioning System Fix Data",". It is one of several standardised NMEA 0183 sentences — short text strings that GPS and GNSS receivers use to report position and status information. You have probably seen NMEA sentences if you have ever looked at raw receiver output: they begin with a dollar sign and are comma-separated.",[18,934,935,936,940],{},"In the context of NTRIP, GGA has a specific role: it is the sentence your device sends ",[937,938,939],"em",{},"to the server"," — in the opposite direction from the correction data — to tell the server where you are. This is unusual because most NTRIP communication is one-way (server to rover), but VRS requires this two-way exchange.",[18,942,943],{},"GGA does not need to be accurate to centimetre level for NTRIP to work correctly. A Single or Float solution position — accurate to a few metres — is more than sufficient. The server only needs to know which part of the network you are in, not your exact position.",[31,945,947],{"id":946},"what-a-gga-sentence-contains","What a GGA sentence contains",[18,949,950],{},"A typical GGA sentence looks like this. Each comma-separated field carries a specific piece of information:",[658,952],{"additionalstyles":418,"items":953},"Example GGA sentence|$GPGGA,123519,5230.000,N,00452.000,E,4,09,0.9,25.4,M,46.9,M,,*47",[243,955,956,965],{},[246,957,958],{},[249,959,960,963],{},[252,961,962],{},"Field",[252,964,800],{},[265,966,967,977,987,997,1006,1016,1026],{},[249,968,969,974],{},[270,970,971],{},[481,972,973],{},"123519",[270,975,976],{},"UTC time — 12:35:19",[249,978,979,984],{},[270,980,981],{},[481,982,983],{},"5230.000,N",[270,985,986],{},"Latitude — 52° 30.000' North (Netherlands)",[249,988,989,994],{},[270,990,991],{},[481,992,993],{},"00452.000,E",[270,995,996],{},"Longitude — 4° 52.000' East",[249,998,999,1003],{},[270,1000,1001],{},[481,1002,153],{},[270,1004,1005],{},"Fix quality — 4 = RTK Fixed (see table below)",[249,1007,1008,1013],{},[270,1009,1010],{},[481,1011,1012],{},"09",[270,1014,1015],{},"Number of satellites in use",[249,1017,1018,1023],{},[270,1019,1020],{},[481,1021,1022],{},"0.9",[270,1024,1025],{},"HDOP — horizontal dilution of precision",[249,1027,1028,1033],{},[270,1029,1030],{},[481,1031,1032],{},"25.4,M",[270,1034,1035],{},"Altitude above mean sea level in metres",[1037,1038,1040],"h3",{"id":1039},"fix-quality-values","Fix quality values",[18,1042,1043],{},"The fix quality field in GGA tells the NTRIP server — and any other system reading the output — what kind of position solution your receiver currently has:",[243,1045,1046,1061],{},[246,1047,1048],{},[249,1049,1050,1053,1055,1058],{},[252,1051,1052],{},"Value",[252,1054,800],{},[252,1056,1057],{},"Typical accuracy",[252,1059,1060],{},"Suitable for VRS?",[265,1062,1063,1079,1095,1110,1125,1139],{},[249,1064,1065,1070,1073,1076],{},[270,1066,1067],{},[481,1068,1069],{},"0",[270,1071,1072],{},"No fix",[270,1074,1075],{},"—",[270,1077,1078],{},"No — position is invalid",[249,1080,1081,1086,1089,1092],{},[270,1082,1083],{},[481,1084,1085],{},"1",[270,1087,1088],{},"GPS fix (Single)",[270,1090,1091],{},"2–5 m",[270,1093,1094],{},"Yes — good enough to locate in network",[249,1096,1097,1101,1104,1107],{},[270,1098,1099],{},[481,1100,216],{},[270,1102,1103],{},"DGPS fix",[270,1105,1106],{},"0.5–2 m",[270,1108,1109],{},"Yes",[249,1111,1112,1116,1119,1122],{},[270,1113,1114],{},[481,1115,153],{},[270,1117,1118],{},"RTK Fixed",[270,1120,1121],{},"1–3 cm",[270,1123,1124],{},"Yes — best quality GGA",[249,1126,1127,1131,1134,1137],{},[270,1128,1129],{},[481,1130,68],{},[270,1132,1133],{},"RTK Float",[270,1135,1136],{},"0.1–1 m",[270,1138,1109],{},[249,1140,1141,1146,1149,1152],{},[270,1142,1143],{},[481,1144,1145],{},"6",[270,1147,1148],{},"Dead reckoning",[270,1150,1151],{},"Variable",[270,1153,1154],{},"Depends on accuracy",[12,1156,1158],{"additionalstyles":14,"color":15,"title":1157},"You do not need Fix before sending GGA",[18,1159,1160],{},"A common misunderstanding is that GGA only works when you already have RTK Fix. In fact, a Single solution (quality 1) is perfectly sufficient. Send GGA as soon as your receiver has any valid position — this allows VRS to start generating corrections, which then helps you get Fix.",[31,1162,1164],{"id":1163},"how-gga-enables-vrs","How GGA enables VRS",[1166,1167,1168,1175,1181,1187,1193],"stepper",{"additionalstyles":14},[1169,1170,1172],"stepper-item",{"marker":1085,"title":1171},"Your receiver gets a rough position",[18,1173,1174],{},"Within 30–60 seconds of powering on outdoors, your receiver acquires satellite signals and computes a Single solution — typically accurate to 2–5 metres. This is enough.",[1169,1176,1178],{"marker":216,"title":1177},"Your NTRIP client sends GGA to the server",[18,1179,1180],{},"Your client connects to the VRS mountpoint and immediately sends the GGA sentence containing your rough position. Most clients send GGA once on connection and then again every 10–60 seconds to account for movement.",[1169,1182,1184],{"marker":177,"title":1183},"The server identifies your location in the network",[18,1185,1186],{},"The VRS server reads the latitude and longitude from your GGA sentence and determines which surrounding physical reference stations apply to your area. This computation takes less than a second.",[1169,1188,1190],{"marker":153,"title":1189},"A virtual station is generated near you",[18,1191,1192],{},"The server synthesises an RTCM3 correction stream as if a base station existed 1–2 km from your position. It starts streaming this data back to your client immediately.",[1169,1194,1196],{"marker":68,"title":1195},"Your receiver achieves RTK Fixed",[18,1197,1198],{},"With local-quality corrections flowing, your receiver resolves carrier phase ambiguities and reaches Fixed — typically within 10–60 seconds in good sky conditions.",[31,1200,1202],{"id":1201},"when-gga-is-required-vs-optional","When GGA is required vs optional",[39,1204,1205,1209,1213,1217],{"additionalstyles":14},[43,1206],{"text":1207,"title":1208},"Any mountpoint labelled VRS, MAC or a similar network correction type. The server cannot generate a virtual station without your position.","GGA required — VRS mountpoints",[43,1210],{"text":1211,"title":1212},"Some NTRIP services select the closest physical station automatically based on your GGA position, rather than requiring you to choose a mountpoint manually.","GGA required — nearest-station auto-selection",[43,1214],{"text":1215,"title":1216},"When connecting to a fixed mountpoint like RTCM3_NL, the server streams corrections regardless of whether GGA is sent. You can enable GGA for logging purposes but it is not used.","GGA optional — standard single-station mountpoints",[43,1218],{"text":1219,"title":1220},"When using your own base-rover configuration without NTRIP, GGA is not involved in the correction exchange at all.","GGA optional — own base station setups",[31,1222,1224],{"id":1223},"how-to-enable-gga-on-your-device","How to enable GGA on your device",[18,1226,1227],{},"The setting name varies between NTRIP clients, but the function is the same on all of them.",[707,1229,1231,1243,1256,1265,1275,1284,1294],{"additionalstyles":14,"items":1230},"Emlid Flow|SW Maps|FieldGenius|Trimble Access|DJI Pilot 2|Lefebure NTRIP|Leica Captivate",[712,1232,1234],{"name":1233},"Emlid Flow",[18,1235,1236,1237,1239,1240,1242],{},"In ",[22,1238,722],{},", select your VRS mountpoint and enable ",[22,1241,680],{},". Connect after the receiver has a valid Single solution.",[712,1244,1245],{"name":757},[18,1246,1247,1248,1251,1252,1255],{},"Go to ",[22,1249,1250],{},"Settings → NTRIP Client",", select the VRS mountpoint and enable ",[22,1253,1254],{},"Transmit GGA"," before connecting.",[712,1257,1259],{"name":1258},"FieldGenius",[18,1260,1247,1261,1264],{},[22,1262,1263],{},"Set Up Corrections → RTK via Internet",". Select the VRS source and enable GGA transmission in the data-link settings.",[712,1266,1268],{"name":1267},"Trimble Access",[18,1269,1270,1271,1274],{},"Enter the VRS mountpoint in ",[22,1272,1273],{},"Survey Style → Rover radio",". Trimble Access sends GGA automatically while NTRIP is active.",[712,1276,1278],{"name":1277},"DJI Pilot 2",[18,1279,1280,1281,1283],{},"Enter the VRS mountpoint under ",[22,1282,745],{},". DJI sends GGA automatically after it has GPS lock, so configure it outdoors.",[712,1285,1287],{"name":1286},"Lefebure NTRIP",[18,1288,1289,1290,1293],{},"Enter the caster host, port and VRS mountpoint. Enable ",[22,1291,1292],{},"Send GGA"," and select the receiver or internal GPS as the GGA source.",[712,1295,1297],{"name":1296},"Leica Captivate",[18,1298,1299],{},"In the internet connection or rover settings, select the VRS mountpoint and enable NMEA GGA output to the NTRIP caster.",[31,1301,1303],{"id":1302},"gga-troubleshooting","GGA troubleshooting",[39,1305,1306,1310,1314,1318],{"additionalstyles":14},[43,1307],{"text":1308,"title":1309},"The connection is established but no corrections are flowing. This almost always means GGA is not being sent — or is being sent with quality 0 (no fix). Enable GGA, ensure the receiver has at least a Single solution, then reconnect.","Connected to VRS but 0 bytes per second",[43,1311],{"text":1312,"title":1313},"If corrections are flowing but Fix takes many minutes, the GGA position may have had low quality at connection time. Disconnect, wait for a better Single solution outdoors, then reconnect.","GGA sent but Fix is very slow",[43,1315],{"text":1316,"title":1317},"Most NTRIP clients send GGA periodically — every 5–60 seconds. The server receives updated positions and adjusts the virtual station to follow you. You do not need to reconnect when moving around the network coverage area.","Moving between areas — does GGA update?",[43,1319],{"text":1320,"title":1321},"GGA contains only your approximate position, altitude, satellite count and fix quality. It contains no personal identifiers; the NTRIP server uses it only to route corrections.","Privacy note",{"title":424,"searchDepth":425,"depth":425,"links":1323},[1324,1325,1329,1330,1331,1332],{"id":924,"depth":425,"text":925},{"id":946,"depth":425,"text":947,"children":1326},[1327],{"id":1039,"depth":1328,"text":1040},3,{"id":1163,"depth":425,"text":1164},{"id":1201,"depth":425,"text":1202},{"id":1223,"depth":425,"text":1224},{"id":1302,"depth":425,"text":1303},"learn","learn\u002Fwhat-is-gga.webp","GGA is a short position message your device sends to the NTRIP server. For standard mountpoints it is optional. For VRS mountpoints it is mandatory — without it the server cannot generate corrections and streams nothing back. This is the single most common reason VRS appears to connect but delivers no Fix.",{},[1338,1339],"\u002Fen\u002Flearn\u002Fwhat-is-vrs","\u002Fen\u002Flearn\u002Fwhat-is-ntrip",{"title":919,"description":1335},"en\u002Flearn\u002Fwhat-is-gga","HFG0RJGp9bO8FHQR5HkzNRVEiSqOCSmiRVEfH3EUQ58",1787304609945]