[{"data":1,"prerenderedAt":714},["ShallowReactive",2],{"knowledge-page-en-\u002Flearn\u002Ffloat-vs-fix":3},{"article":4,"posts":390,"relatedPosts":391},{"id":5,"title":6,"author":7,"body":8,"category":376,"cover":377,"description":378,"extension":379,"meta":380,"navigation":381,"path":382,"publishedAt":383,"relatedArticles":384,"seo":386,"stem":387,"updatedAt":388,"__hash__":389},"knowledge_en\u002Fen\u002Flearn\u002Ffloat-vs-fix.md","What is the difference between Float and Fix?","Wilko",{"type":9,"value":10,"toc":366},"minimark",[11,16,72,76,80,83,86,122,125,128,132,135,174,178,309,313,316,343,347,350,353,359],[12,13,15],"h2",{"id":14},"float-vs-fix-at-a-glance","Float vs Fix at a glance",[17,18,20,48],"cards",{"additionalstyles":19},"mt-[60px]",[21,22,26],"card",{"additionalstyles":23,"color":24,"title":25},"h-full","orange","Float — Accuracy: 10 cm–1 m horizontal",[27,28,29,33,36,39,42,45],"ul",{},[30,31,32],"li",{},"Corrections received but not fully resolved",[30,34,35],{},"Ambiguities treated as real numbers, not integers",[30,37,38],{},"Position jumps of 10–50 cm are normal",[30,40,41],{},"Never adequate for precision survey",[30,43,44],{},"Often a stepping stone toward Fix",[30,46,47],{},"Can look like Fix on some displays",[21,49,52],{"additionalstyles":23,"color":50,"title":51},"green","Fix — Accuracy: 1–3 cm horizontal, 2–5 cm vertical",[27,53,54,57,60,63,66,69],{},[30,55,56],{},"Carrier phase ambiguities fully resolved to integers",[30,58,59],{},"Position is stable and repeatable",[30,61,62],{},"Centimetre accuracy maintained at speed",[30,64,65],{},"Required for precision survey and stakeout",[30,67,68],{},"Takes 10–60 seconds in good conditions",[30,70,71],{},"Shown in green on most field software",[12,73,75],{"id":74},"what-makes-fix-different-ambiguity-resolution","What makes Fix different — ambiguity resolution",[77,78,79],"p",{},"To understand Float and Fix you need to understand one concept: carrier phase ambiguity. It is the reason RTK can achieve centimetre accuracy at all — and the reason Float cannot.",[77,81,82],{},"GNSS receivers measure position in two ways. The simpler method is pseudorange — measuring the travel time of a satellite signal to estimate distance. Pseudorange gives accuracy of 1–3 metres. The more precise method is carrier phase — measuring the phase of the satellite's radio wave at the receiver antenna. The carrier wave has a wavelength of about 19 cm (for GPS L1). By tracking how many whole wavelengths fit between the satellite and the receiver, and precisely measuring the fractional part, the receiver can measure distance to millimetre precision.",[77,84,85],{},"The problem: the receiver knows the fractional part of the carrier phase precisely, but it does not know how many whole wavelengths there are between it and the satellite. This unknown integer number is called the carrier phase ambiguity — or simply the integer ambiguity.",[87,88,92,109],"compare-table",{"additionalstyles":19,"items":89,"label":90,"winner":91},"Float|Fix","Float and Fix ambiguity comparison","Fix",[93,94,96,103],"compare-row",{"title":95},"Carrier phase ambiguity",[97,98,100],"compare-cell",{"status":99},"negative",[77,101,102],{},"The integer cycle count is still unknown and treated as a real-valued estimate.",[97,104,106],{"status":105},"positive",[77,107,108],{},"The integer cycle count has been confirmed as a specific whole number.",[93,110,112,117],{"title":111},"Position accuracy",[97,113,114],{"status":99},[77,115,116],{},"10 cm–1 m. The fractional phase is measured, but the unresolved cycle count limits accuracy.",[97,118,119],{"status":105},[77,120,121],{},"Centimetre precision. The resolved cycle count unlocks the precise fractional measurement.",[77,123,124],{},"Resolving the integer ambiguity is what RTK does. Using corrections from the reference station — which has its own precisely known position — the rover can cross-check its carrier phase measurements against the reference and mathematically determine the correct integer values. When the receiver is confident it has the right integers for all tracked satellites, it declares RTK Fixed.",[77,126,127],{},"Float means the receiver is still working on this. It has an estimate of the integers — good enough to give sub-metre accuracy — but not yet confident enough to fix them to specific integers. Float accuracy depends on how good the estimate is: anywhere from 10 cm to 1 m, with occasional larger jumps.",[12,129,131],{"id":130},"the-full-solution-progression","The full solution progression",[77,133,134],{},"When you connect to an NTRIP service and power up in the field, your receiver moves through several solution types before reaching Fix.",[136,137,138,146,153,160,167],"stepper",{"additionalstyles":19},[139,140,143],"stepper-item",{"marker":141,"title":142},"—","No fix — Accuracy: none",[77,144,145],{},"The receiver has no satellite lock and no valid position. It is still acquiring signals. This usually takes 15–60 seconds after power-on outdoors.",[139,147,150],{"marker":148,"title":149},"S","Single — Accuracy: 2–5 m",[77,151,152],{},"The receiver has satellite lock and a valid position, but no corrections are applied yet. It uses pseudorange only. This is the type of position reported by standard GPS apps on your phone.",[139,154,157],{"marker":155,"title":156},"D","DGPS \u002F SBAS — Accuracy: 0.3–1 m",[77,158,159],{},"Differential corrections are applied, but only to pseudorange measurements. It is better than Single, but not accurate enough for precision work. This can appear briefly when NTRIP corrections first arrive.",[139,161,164],{"marker":162,"title":163},"FL","Float — Accuracy: 10 cm–1 m",[77,165,166],{},"Carrier phase corrections are applied, but integer ambiguities are not yet resolved. The position is significantly better than Single but not precise enough for survey work. Float is often a transitional state lasting 10–60 seconds before Fix.",[139,168,171],{"marker":169,"title":170},"FX","Fixed — Accuracy: 1–3 cm horizontal, 2–5 cm vertical",[77,172,173],{},"Integer ambiguities are resolved and full RTK accuracy is achieved. This is the solution type required for precision survey, stakeout, machine guidance and drone mapping with ground control points.",[12,175,177],{"id":176},"which-solution-is-good-enough-for-what","Which solution is good enough for what",[87,179,182,198,216,231,247,262,278,293],{"additionalstyles":19,"items":180,"label":181,"winner":91},"Single|Float|Fix","Suitable RTK solution per application",[93,183,185,190,194],{"title":184},"Rough navigation — Finding a plot or general location",[97,186,187],{"status":105},[77,188,189],{},"Good enough",[97,191,192],{"status":105},[77,193,189],{},[97,195,196],{"status":105},[77,197,189],{},[93,199,201,206,211],{"title":200},"Drone mapping — Direct georeferencing without GCPs",[97,202,203],{"status":99},[77,204,205],{},"No",[97,207,208],{"status":99},[77,209,210],{},"Marginal",[97,212,213],{"status":105},[77,214,215],{},"Required",[93,217,219,223,227],{"title":218},"GCP collection for drone mapping",[97,220,221],{"status":99},[77,222,205],{},[97,224,225],{"status":99},[77,226,205],{},[97,228,229],{"status":105},[77,230,215],{},[93,232,234,238,242],{"title":233},"Precision agriculture — Auto-steer with 2–5 cm row guidance",[97,235,236],{"status":99},[77,237,205],{},[97,239,240],{"status":99},[77,241,210],{},[97,243,244],{"status":105},[77,245,246],{},"Preferred",[93,248,250,254,258],{"title":249},"Survey — Topographic surface mapping",[97,251,252],{"status":99},[77,253,205],{},[97,255,256],{"status":99},[77,257,205],{},[97,259,260],{"status":105},[77,261,215],{},[93,263,265,269,273],{"title":264},"Survey — Cadastral or legal property boundaries",[97,266,267],{"status":99},[77,268,205],{},[97,270,271],{"status":99},[77,272,205],{},[97,274,275],{"status":105},[77,276,277],{},"Required + verification",[93,279,281,285,289],{"title":280},"Stakeout to 1 cm",[97,282,283],{"status":99},[77,284,205],{},[97,286,287],{"status":99},[77,288,205],{},[97,290,291],{"status":105},[77,292,215],{},[93,294,296,300,305],{"title":295},"Machine control — Earthworks",[97,297,298],{"status":99},[77,299,205],{},[97,301,302],{"status":105},[77,303,304],{},"Sometimes",[97,306,307],{"status":105},[77,308,215],{},[12,310,312],{"id":311},"how-to-get-from-float-to-fix-faster","How to get from Float to Fix faster",[77,314,315],{},"Float is a transitional state. In good conditions it lasts 10–30 seconds. In challenging conditions it can persist indefinitely. These measures help most:",[17,317,318,323,327,331,335,339],{"additionalstyles":19},[319,320],"cards-item",{"text":321,"title":322},"Ambiguity resolution requires a strong, stable signal from many satellites simultaneously. Even partial canopy cover significantly slows initialisation.","Go outside with a clear sky view",[319,324],{"text":325,"title":326},"The RTK engine converges faster when the antenna is stationary. Once Fixed, you can move normally. Collecting data while still in Float can delay Fix.","Stand still during initialisation",[319,328],{"text":329,"title":330},"Shorter effective baselines make ambiguity resolution faster and more reliable. Beyond 20 km from a physical station, switch to VRS and enable GGA.","Use a VRS mountpoint",[319,332],{"text":333,"title":334},"More satellites provide more measurement redundancy. Adding GLONASS, Galileo and BeiDou can halve Float-to-Fix time compared with GPS-only.","Enable all satellite constellations",[319,336],{"text":337,"title":338},"Verify that bytes per second is non-zero. A dropped and reconnected correction stream resets initialisation and can leave the receiver stuck on Float.","Check the NTRIP connection",[319,340],{"text":341,"title":342},"Above 4, satellite geometry is poor and ambiguity resolution may not converge. Wait for the geometry window to improve, typically within 15–30 minutes.","Check PDOP",[12,344,346],{"id":345},"false-fix-the-hidden-danger","False Fix — the hidden danger",[77,348,349],{},"The most dangerous scenario in RTK is a false Fix — the receiver declares Fixed but has resolved the ambiguities to the wrong integers. The position looks centimetre-precise and stable, but it is wrong by one or more carrier wavelengths (19 cm per L1 cycle).",[77,351,352],{},"False Fix produces errors of exactly one or more multiples of the carrier wavelength — 19 cm, 38 cm, 57 cm and so on. It is more common at long baselines, in high multipath environments and during solar storms when ionospheric noise is high.",[21,354,356],{"additionalstyles":19,"color":24,"title":355},"How to detect a false Fix",[77,357,358],{},"Always verify on a known control point at the start of any precision survey. Set up over a point with published coordinates and compare your measured position with the known values. A discrepancy of exactly around 19 cm, 38 cm or 57 cm in any direction strongly indicates a false Fix. Disconnect, move to open sky, reconnect and re-initialise before continuing.",[21,360,363],{"additionalstyles":19,"color":361,"title":362},"primary","Fix quality indicator — ratio",[77,364,365],{},"Many receivers and field software applications report a Fix quality ratio alongside the solution type. A ratio above 3.0 indicates high confidence. A ratio between 1.5 and 3.0 means the Fix is tentative, so verify it on known points. A ratio below 1.5 may indicate that the receiver should not have declared Fix at all.",{"title":367,"searchDepth":368,"depth":368,"links":369},"",2,[370,371,372,373,374,375],{"id":14,"depth":368,"text":15},{"id":74,"depth":368,"text":75},{"id":130,"depth":368,"text":131},{"id":176,"depth":368,"text":177},{"id":311,"depth":368,"text":312},{"id":345,"depth":368,"text":346},"learn","learn\u002Ffloat-vs-fix.webp","Float and Fix are the two RTK solution types. They look similar on a status screen — both show a position with corrections applied — but the accuracy difference between them is enormous. Fix is centimetres. Float is decimetres to metres. Never collect survey data at Float.","md",{},true,"\u002Fen\u002Flearn\u002Ffloat-vs-fix","2026-07-24",[385],"\u002Fen\u002Flearn\u002Fwhat-is-ntrip",{"title":6,"description":378},"en\u002Flearn\u002Ffloat-vs-fix",null,"rVrcpStYIvAqW_8pcTB5DaAOMLXiCzzea9VNPOocA4Y",[],[392],{"id":393,"title":394,"author":7,"body":395,"category":376,"cover":708,"description":709,"extension":379,"meta":710,"navigation":381,"path":385,"publishedAt":383,"relatedArticles":388,"seo":711,"stem":712,"updatedAt":388,"__hash__":713},"knowledge_en\u002Fen\u002Flearn\u002Fwhat-is-ntrip.md","What is NTRIP and how does it work?",{"type":9,"value":396,"toc":695},[397,401,404,407,427,431,434,458,463,466,470,478,481,485,488,492,530,536,540,543,639,643,661,667,671,674,689],[12,398,400],{"id":399},"what-ntrip-stands-for","What NTRIP stands for",[77,402,403],{},"NTRIP stands for Networked Transport of RTCM via Internet Protocol. Unpacking the name tells you exactly what it does: it takes RTCM correction data — the standard format for RTK corrections — and delivers it over the internet using standard HTTP-based communication.",[77,405,406],{},"NTRIP was developed by the German Federal Agency for Cartography and Geodesy (BKG) in the early 2000s and became the global standard for internet-based RTK correction delivery. Today it is used by every major correction network, every modern RTK receiver and virtually every field survey software package.",[408,409,410,415,419,423],"text-grid",{"additionalstyles":19},[411,412],"text-grid-item",{"text":413,"title":414},"Standard TCP port","2101",[411,416],{"text":417,"title":418},"Protocol base","HTTP",[411,420],{"text":421,"title":422},"Data format carried","RTCM3",[411,424],{"text":425,"title":426},"Correction latency","\u003C1 s",[12,428,430],{"id":429},"the-three-components","The three components",[77,432,433],{},"NTRIP has three distinct roles — caster, server and client — that together form the correction delivery chain. Understanding these helps you configure your equipment correctly and diagnose connection problems.",[435,436,437,442,446,451,454],"flow-diagram",{"additionalstyles":19},[438,439],"flow-card",{"text":440,"title":441},"NTRIP Server","Reference station",[443,444],"flow-connector",{"text":445},"RTCM3 over internet",[438,447],{"text":448,"title":449,":highlighted":450},"Central hub","NTRIP Caster","true",[443,452],{"text":453},"RTCM3 stream on demand",[438,455],{"text":456,"title":457},"NTRIP Client","Your device",[459,460,462],"h3",{"id":461},"ntrip-server-the-reference-station-side","NTRIP Server — the reference station side",[77,464,465],{},"The NTRIP Server is the software running at each physical reference station. It reads the raw GNSS observations from the receiver and pushes them continuously to the caster over the internet. A reference station broadcasts its data to the caster 24 hours a day, typically at 1-second intervals. You never interact with the server directly — it operates invisibly in the background.",[459,467,469],{"id":468},"ntrip-caster-the-central-hub","NTRIP Caster — the central hub",[77,471,472,473,477],{},"The NTRIP Caster is the server infrastructure that receives data from all reference stations and distributes it to clients on request. It maintains a sourcetable — a list of all available correction streams (mountpoints) — and authenticates connecting clients. When you enter an NTRIP host address like ",[474,475,476],"code",{},"ntrip.rtksub.com",", you are connecting to a caster.",[77,479,480],{},"A caster can serve thousands of clients simultaneously from the same set of reference stations. This is why network correction services are economically viable — one physical infrastructure serves many subscribers.",[459,482,484],{"id":483},"ntrip-client-your-device","NTRIP Client — your device",[77,486,487],{},"The NTRIP Client is the software on your side — built into Emlid Flow, SW Maps, Trimble Access, FieldGenius and every other modern field application. It connects to the caster, authenticates, selects a mountpoint and receives the correction stream. The client passes the incoming RTCM3 data to the receiver, which uses it to compute an RTK Fix.",[12,489,491],{"id":490},"how-ntrip-works-step-by-step","How NTRIP works step by step",[136,493,494,500,506,512,518,524],{"additionalstyles":19},[139,495,497],{"title":496},"Reference stations observe satellites",[77,498,499],{},"Permanent GNSS receivers at fixed, precisely surveyed locations track all visible satellites continuously. They measure the difference between what the signals should look like at their known position and what they actually receive — this difference is the correction data.",[139,501,503],{"title":502},"Stations stream RTCM3 to the caster",[77,504,505],{},"Each reference station sends its correction data to the NTRIP caster in real time. The data is formatted as RTCM3 messages — the universal standard for RTK corrections. This stream flows continuously, every second of every day.",[139,507,509],{"title":508},"Your client connects and authenticates",[77,510,511],{},"Your field software (the NTRIP client) opens a TCP connection to the caster on port 2101. It sends an HTTP GET request including your username and password. The caster verifies your credentials and confirms the connection.",[139,513,515],{"title":514},"You select a mountpoint",[77,516,517],{},"The caster sends back a sourcetable listing all available correction streams. You select a mountpoint — the name of the specific correction stream you want. Your client sends the mountpoint name back to the caster, which begins streaming that correction data to you.",[139,519,521],{"title":520},"Corrections flow to your receiver",[77,522,523],{},"The caster streams RTCM3 correction messages continuously to your client. Your field software or NTRIP app passes these to your GNSS receiver — typically via Bluetooth, USB or directly over the network if the receiver has its own IP connection.",[139,525,527],{"title":526},"Your receiver computes RTK Fixed",[77,528,529],{},"The receiver combines the incoming corrections with its own satellite observations. It resolves carrier phase ambiguities — the mathematical step that unlocks centimetre accuracy — and outputs an RTK Fixed position. In good conditions this takes 10–60 seconds from the moment corrections begin flowing.",[21,531,533],{"additionalstyles":19,"color":361,"title":532},"NTRIP is essentially streaming audio — but for position",[77,534,535],{},"A useful analogy: NTRIP works like an internet radio stream. The caster is the radio server. Your NTRIP client is the app on your phone. The mountpoint is the station you tune to. Corrections flow continuously as long as you are connected — and like a radio stream, a brief internet dropout interrupts it until the connection re-establishes.",[12,537,539],{"id":538},"ntrip-vs-radio-link","NTRIP vs radio link",[77,541,542],{},"Before NTRIP became widespread, RTK corrections were delivered by UHF radio — a base station on site broadcast corrections to rovers within line-of-sight range. Radio is still used today, but NTRIP has become the dominant method for most professional applications.",[87,544,548,561,574,587,600,613,626],{"additionalstyles":19,"items":545,"label":546,"winner":547},"UHF radio link|NTRIP","UHF radio link compared with NTRIP","NTRIP",[93,549,551,556],{"title":550},"Range",[97,552,553],{"status":99},[77,554,555],{},"2–10 km line of sight. Terrain and buildings block signal.",[97,557,558],{"status":105},[77,559,560],{},"Unlimited within network coverage. Works across an entire country.",[93,562,564,569],{"title":563},"Infrastructure required",[97,565,566],{"status":99},[77,567,568],{},"Base station, tripod, radio module, battery. 15–30 min setup per job.",[97,570,571],{"status":105},[77,572,573],{},"One rover. Mobile data connection. No base station.",[93,575,577,582],{"title":576},"Works without internet",[97,578,579],{"status":105},[77,580,581],{},"Yes — fully independent of internet or mobile coverage.",[97,583,584],{"status":99},[77,585,586],{},"No — requires mobile data at the rover location.",[93,588,590,595],{"title":589},"Latency",[97,591,592],{"status":105},[77,593,594],{},"\u003C100 ms — very low latency, ideal for machine guidance.",[97,596,597],{"status":105},[77,598,599],{},"\u003C1 s over 4G — acceptable for all surveying applications.",[93,601,603,608],{"title":602},"Number of rovers served",[97,604,605],{"status":99},[77,606,607],{},"Unlimited — radio broadcast reaches all rovers in range.",[97,609,610],{"status":99},[77,611,612],{},"Each rover needs its own NTRIP connection and subscription.",[93,614,616,621],{"title":615},"Accuracy",[97,617,618],{"status":99},[77,619,620],{},"Best within 10 km of base. Degrades at distance.",[97,622,623],{"status":105},[77,624,625],{},"Consistent with VRS across the entire network coverage area.",[93,627,629,634],{"title":628},"Cost",[97,630,631],{"status":99},[77,632,633],{},"High upfront hardware cost. No ongoing fees.",[97,635,636],{"status":105},[77,637,638],{},"Low upfront (one receiver). Monthly subscription for corrections.",[12,640,642],{"id":641},"what-you-need-to-use-ntrip","What you need to use NTRIP",[17,644,645,649,653,657],{"additionalstyles":19},[319,646],{"text":647,"title":648},"Any modern multi-band RTK receiver. Emlid, Trimble, Leica, u-blox ZED-F9P and most others support NTRIP natively.","NTRIP-compatible receiver",[319,650],{"text":651,"title":652},"Built into Emlid Flow, SW Maps, Trimble Access, FieldGenius, Lefebure and most field apps. You are unlikely to need a separate client.","NTRIP client software",[319,654],{"text":655,"title":656},"Mobile data (4G or 3G) at the rover location. A few hundred kilobytes per hour — similar to a basic messaging app.","Internet connection",[319,658],{"text":659,"title":660},"Host address, port (2101), mountpoint name, username and password from your correction service provider.","NTRIP credentials",[21,662,664],{"additionalstyles":19,"color":50,"title":663},"NTRIP data usage is very low",[77,665,666],{},"A typical NTRIP correction stream uses 50–200 KB per hour depending on the mountpoint and number of satellite constellations. Over a full 8-hour working day this is under 2 MB — negligible on any mobile data plan. NTRIP will not meaningfully affect your data allowance.",[12,668,670],{"id":669},"ntrip-v1-vs-ntrip-v2","NTRIP v1 vs NTRIP v2",[77,672,673],{},"There are two versions of the NTRIP standard. Most users will never need to think about this distinction — your software handles it automatically — but it is useful to understand when troubleshooting.",[27,675,676,683],{},[30,677,678,682],{},[679,680,681],"strong",{},"NTRIP v1"," (2004) — the original standard. Uses basic HTTP 1.0. One-way communication: the caster sends corrections and receives nothing back from the client. Does not natively support GGA position transmission for VRS. Still widely supported by all servers and clients.",[30,684,685,688],{},[679,686,687],{},"NTRIP v2"," (2007) — adds bidirectional communication over HTTP 1.1. Supports GGA transmission from client to caster within the protocol — this is how VRS mountpoints work. Supports chunked transfer encoding for more reliable streaming. Trimble Access automatically negotiates v2 if the server supports it.",[21,690,692],{"additionalstyles":19,"color":24,"title":691},"Force v1 only if you have connection problems",[77,693,694],{},"Some older equipment or network configurations have problems with NTRIP v2 negotiation. If you cannot connect and everything else looks correct, try forcing your client to use NTRIP v1.0. In Trimble Access this is a checkbox in the survey style data link settings. In most other clients, look for an \"NTRIP version\" dropdown.",{"title":367,"searchDepth":368,"depth":368,"links":696},[697,698,704,705,706,707],{"id":399,"depth":368,"text":400},{"id":429,"depth":368,"text":430,"children":699},[700,702,703],{"id":461,"depth":701,"text":462},3,{"id":468,"depth":701,"text":469},{"id":483,"depth":701,"text":484},{"id":490,"depth":368,"text":491},{"id":538,"depth":368,"text":539},{"id":641,"depth":368,"text":642},{"id":669,"depth":368,"text":670},"learn\u002Fwhat-is-ntrip.webp","NTRIP is the internet protocol that delivers RTK correction data from reference stations to your rover over a mobile data connection. It replaced radio links as the dominant correction delivery method — and it is the reason a single receiver with a SIM card can achieve centimetre accuracy anywhere in a correction network's coverage area.",{},{"title":394,"description":709},"en\u002Flearn\u002Fwhat-is-ntrip","zwxVSM1r0uMgUoqabd-awIyiWlIAORHYhZCmNiesBK0",1787304609933]