Modern high-accuracy GNSS is no longer limited to one workflow. For many field users, RTK is still the first choice when a local base station, CORS network, NTRIP service, or radio correction link is available. But many projects happen outside reliable correction coverage, or in places where setting up local infrastructure is slow, expensive, or inconvenient.
This is where modern PPP, or Precise Point Positioning, becomes important. PPP gives users another path to high-accuracy positioning without requiring a nearby base station. With satellite-broadcast correction services such as Galileo HAS and BeiDou PPP-B2b, PPP is becoming more practical for real-time field work, not only for expert post-processing.
PPP should not be treated as a universal replacement for RTK. RTK remains the preferred tool for fast centimeter-level work when correction infrastructure is available and well configured. PPP is better understood as another tool in the high-accuracy GNSS toolbox, especially useful when users need wide-area or standalone positioning.
The High-Accuracy GNSS Landscape
Before comparing PPP, RTK, SBAS, and other correction services, it helps to separate the main positioning methods.
| Method | Typical role | Correction source | Typical accuracy class | Main limitation |
|---|---|---|---|---|
| Standalone GNSS / SPP | Basic positioning | Broadcast navigation data | ~1-10 m | Limited precision |
| SBAS | Wide-area augmentation and integrity | SBAS broadcast | ~0.5-2 m | Not designed as PPP-level high precision |
| PPP | Wide-area high-accuracy positioning | Satellite-delivered PPP corrections, such as HAS or PPP-B2b | ~0.1-1 m; cm possible in some workflows | Needs convergence and compatible receiver/workflow |
| RTK | Centimeter positioning near infrastructure | Local base, CORS, NTRIP, or radio | ~1-3 cm | Needs correction infrastructure and ambiguity fixing |
The important point is that not every satellite correction service is the same. SBAS, RTK, traditional PPP post-processing, Galileo HAS, and BeiDou PPP-B2b all improve GNSS in different ways.
What Is PPP in GNSS?
PPP means Precise Point Positioning. It is a GNSS positioning method that can produce high-accuracy results with a single user receiver, without requiring a nearby local base station.
Standard GNSS positioning uses broadcast satellite information and usually gives meter-level results. PPP improves the satellite information used by the receiver. Instead of relying only on standard broadcast navigation data, a PPP solution uses precise correction data for satellite orbit, clock, and signal-related errors. With enough observations, suitable receiver hardware, and continuous correction input, the receiver can estimate a much more precise position.
PPP is commonly associated with SSR, or State Space Representation, corrections. In simple terms, SSR describes error sources separately, such as satellite orbit error, clock error, and signal bias. The receiver then applies those correction parameters inside its own PPP engine.
PPP still depends on the real field environment. It needs good satellite visibility, high-quality observations, suitable antennas, supported frequencies and constellations, correction availability, and convergence time.
What PPP Corrections Actually Correct
PPP works because it improves the model used by the receiver. Instead of treating the GNSS satellites as perfectly known timing and positioning references, PPP uses precise correction information to reduce the main error sources.
PPP corrections may include:
- Satellite orbit corrections
- Satellite clock corrections
- Code or signal bias corrections
- Phase bias corrections, depending on the service and maturity
- Atmospheric information in some advanced or regional services
Orbit and clock corrections improve the satellite position and timing information used by the receiver. Bias corrections help align measurements from different signals, frequencies, and constellations. Multi-frequency measurements help reduce ionospheric error, while carrier-phase observations give the PPP engine the precision needed for high-accuracy positioning.
SSR vs OSR: Why PPP and RTK Work Differently
SSR and OSR are two different ways to think about GNSS corrections. The simple version is this: RTK usually corrects the rover relative to a nearby reference, while PPP improves the satellite model itself.
OSR means Observation Space Representation. It is correction information expressed close to actual receiver observations, usually from a base station or correction network.
SSR means State Space Representation. It describes GNSS system error states, such as satellite orbit, clock, and bias errors, so the receiver can apply those corrections inside its own PPP engine.
| Correction style | Commonly used by | What it describes | Practical meaning |
|---|---|---|---|
| OSR Observation Space Representation |
RTK / network RTK | Corrections tied to a base station or correction network | Very fast centimeter-level results, but coverage depends on local infrastructure and communication links. |
| SSR State Space Representation |
PPP, including HAS and PPP-B2b style workflows | Satellite orbit, clock, bias, and sometimes atmospheric correction information | Works over wider areas without a nearby base station, but usually needs convergence time and compatible receiver processing. |
For field users, this is the key difference: RTK depends more on local correction infrastructure, while PPP depends more on precise satellite corrections, receiver support, and convergence behavior. That is why PPP can be useful in remote or wide-area work, but it should not be described as an instant RTK replacement.
Short Satellite Orbit Cheat Sheet
Satellite system and orbit type are different concepts. GPS, Galileo, BeiDou, and QZSS are systems or constellations. GEO, MEO, IGSO, and LEO describe how satellites move around Earth.
Orbit type helps explain coverage and signal behavior. GEO satellites look almost fixed from the ground, while MEO satellites move across the sky and the visible satellite set changes over time.
| Orbit type | What it means | GNSS / SBAS / PPP examples | Non-GNSS satellite examples |
|---|---|---|---|
| LEO | Low Earth Orbit, fast-moving satellites close to Earth | No main GNSS, SBAS, Galileo HAS, or BeiDou PPP-B2b service in this article uses LEO as its primary satellite orbit | SpaceX Starlink and OneWeb communication satellites; Landsat and Sentinel Earth-observation satellites |
| MEO | Medium Earth Orbit, used by most global navigation satellites | GPS, Galileo, GLONASS, and BeiDou MEO satellites; Galileo HAS is broadcast from Galileo MEO satellites | SES O3b / O3b mPOWER communication satellites |
| IGSO | Inclined geosynchronous orbit, traces a figure-eight path | BeiDou IGSO satellites; QZSS quasi-zenith satellites; NavIC IGSO satellites | Less common outside navigation; Sirius XM’s legacy Tundra-orbit satellites are a related inclined geosynchronous-family example, but not standard circular IGSO |
| GEO | Geostationary orbit, appears fixed from Earth | SBAS GEO broadcast payloads; BeiDou GEO satellites; BeiDou PPP-B2b broadcast through BDS-3 GEO satellites | Intelsat and Inmarsat communication satellites; GOES weather satellites |
In practice, BeiDou PPP-B2b uses BDS-3 GEO satellites, so its broadcast direction is stable and its service is mainly regional. Galileo HAS uses Galileo MEO satellites, so it is designed for wider coverage, but the visible satellites change as they orbit. This does not mean HAS is unstable; it means the receiver is tracking a moving constellation.
PPP vs RTK: Which One Fits Your Field Workflow?
RTK and PPP can both support high-accuracy field positioning, but they fit different workflows. The best choice depends on whether the job needs fast local centimeter fixing, wider-area operation, or less dependence on local correction infrastructure.
| Feature | RTK | PPP-HAS / PPP-B2b |
|---|---|---|
| Correction model | Usually OSR-style corrections from base or network | Usually SSR-style precise satellite corrections |
| Typical accuracy | Centimeter-level when fixed and well configured | Decimeter-level target for satellite PPP services under suitable conditions |
| Infrastructure | Needs base station, CORS, NTRIP, or radio link | No local base station required |
| Coverage | Limited by network, base, or link availability | Wide-area or regional satellite correction service |
| Setup | More dependent on correction source and communication link | More standalone once receiver and service support are available |
| Best use | Survey-grade precision near reliable infrastructure | Wide-area or remote high-accuracy positioning where RTK access is limited |
For practical buying decisions, RTK is strongest when reliable local infrastructure is available and fast centimeter-level fixing is required. PPP is strongest when the workflow benefits from satellite-delivered corrections, wider coverage, simpler field logistics, or operation away from local base stations and correction networks.
Modern PPP vs Older PPP Workflows
PPP is a positioning method, not one single product. There are multiple ways to compute a PPP result, which is why users often confuse desktop PPP processing, online post-processing services, Galileo HAS, and BeiDou PPP-B2b.
Older and Post-Processing PPP
Older PPP workflows are often associated with RINEX files, post-processing, scientific or engineering software, delayed precise orbit and clock products, long observation sessions, and expert configuration.
These workflows are still valuable for research, geodesy, control points, quality checking, and high-quality post-processing.
Modern Real-Time Satellite PPP
Modern satellite PPP services broadcast correction messages in real time. With compatible receivers, users can receive corrections in the field and compute a live PPP solution.
This workflow does not require file-based post-processing, does not require a nearby base station, and can work directly from satellite-delivered correction signals when the receiver supports the service.
RTKLIB PPP
RTKLIB is an open-source GNSS toolkit with PPP processing capability. It is software, not a satellite correction service.
RTKLIB PPP commonly uses raw observations, RINEX files, precise orbit and clock products, and careful configuration. It is often used for testing, research, education, and post-processing. Advanced users can build real-time workflows, but the common beginner experience is usually not the same as using a receiver that directly supports Galileo HAS or BeiDou PPP-B2b.
RTKLIB PPP and PPP-HAS or PPP-B2b are related by the PPP concept, but they are not the same user workflow. RTKLIB is a processing tool. HAS and B2b are correction services that compatible receivers can use for real-time PPP.
Online PPP Services Such as CSRS-PPP
Online PPP services usually require users to collect GNSS data first, submit RINEX or similar files for server-side processing, and then review the processed position result afterward.
Services such as CSRS-PPP are useful for control, checking, education, and post-processing workflows. They help users understand PPP as a positioning method, but they are not the same as real-time PPP-HAS, real-time PPP-B2b, RTK corrections, or SBAS.
| Topic | RTKLIB / Desktop PPP | Online PPP Service | Real-time PPP-HAS / PPP-B2b |
|---|---|---|---|
| Workflow | Process data in software | Submit collected data for server-side processing | Receive satellite corrections in the field |
| Real-time use | Possible in advanced setups, often post-processing | Usually no | Yes, with compatible receiver support |
| Typical requirement | Raw observations, precise products, and expert configuration | Collected GNSS observation file and service-side processing | Compatible receiver, supported signals, and satellite-delivered corrections |
| User skill | High | Medium | Lower after receiver workflow is configured |
| Best use | Research, testing, post-processing | Control, checking, education, post-processing | Live field positioning |
Galileo HAS Explained
Galileo HAS means Galileo High Accuracy Service. It provides free high-accuracy PPP corrections and is one of the most important public examples of modern satellite-based PPP.
HAS corrections are distributed through Galileo E6-B. For field users, direct E6-B reception can reduce dependence on local NTRIP/CORS infrastructure when the receiver supports it.
HAS corrections include orbit, clock, and satellite bias information. Initial Service capabilities may be more limited than Full Service objectives, so users should check the service phase, receiver firmware, and implementation details.
Real results depend on receiver support, service area, sky view, convergence, multipath, antenna quality, signal tracking, and PPP engine implementation.
BeiDou PPP-B2b Explained
BeiDou PPP-B2b is a BeiDou-3 precise point positioning service. It is mainly intended for China and surrounding areas, and it is often discussed in Asia-Pacific use cases. It should not be described as a global service in the same way as the Galileo HAS concept.
Official service material describes PPP-B2b correction information as broadcast through the PPP-B2b signal by BDS-3 GEO satellites. The service supports real-time PPP using correction data such as orbit, clock, and code bias corrections.
For practical users, PPP-B2b should be described conservatively as a regional real-time PPP service that can support decimeter-level positioning under suitable conditions. Performance depends on location, receiver support, correction availability, convergence, sky view, multipath, and field environment.
PPP-B2b is not identical to Galileo HAS. The coverage, signal path, service design, and receiver requirements differ. Buyers should verify explicit B2b signal support, PPP-B2b decoding, firmware support, and the receiver’s PPP processing capability.
PPP vs SBAS
SBAS and PPP are both satellite-related, but they are not the same thing.
SBAS systems such as WAAS, EGNOS, MSAS, and GAGAN focus on integrity and wide-area augmentation, especially for safety-critical aviation-style use cases. SBAS can improve standard GNSS positioning, but it is generally not designed as a centimeter or decimeter PPP correction service.
PPP aims at higher precision through precise orbit, clock, and bias modeling. It uses correction data that allows the receiver to improve the satellite model and estimate a more precise position after convergence.
| Feature | SBAS | PPP |
|---|---|---|
| Main goal | Integrity and wide-area augmentation | High-accuracy positioning |
| Typical accuracy class | Meter/sub-meter class depending on region and receiver | Decimeter to centimeter class depending on service and workflow |
| Correction philosophy | Wide-area augmentation and integrity information | Precise orbit, clock, bias, and sometimes atmospheric correction modeling |
| Delivery | Often GEO broadcast payloads | GNSS or GEO satellite correction broadcasts depending on service |
| Receiver requirement | SBAS-capable GNSS receiver | PPP engine plus support for the required correction format |
In short, SBAS is mainly wide-area augmentation and integrity. PPP is a high-accuracy positioning method based on precise corrections.
Realistic Accuracy Expectations
Accuracy claims are easy to misunderstand. A responsible PPP discussion should describe both the potential and the limitations.
For practical field use, satellite PPP-HAS and PPP-B2b should usually be presented as decimeter-level solutions under suitable conditions after convergence. Some PPP workflows can reach higher accuracy with good data, precise products, and careful processing, but that is not the same as instant real-time RTK performance.
Several factors affect PPP performance:
- Sky view
- Multipath
- Antenna quality and placement
- Supported frequencies and constellations
- Correction service availability
- Convergence time
- Receiver PPP engine implementation
- User motion or static condition
- Regional service coverage
PPP is a powerful standalone high-accuracy option, but it is not a universal replacement for RTK in every centimeter-level surveying task.
Real-World Use Cases
Modern PPP is not only a backup for RTK. It is a practical high-accuracy option when users value wide-area coverage, simpler field logistics, and less dependence on local correction infrastructure.
PPP-capable GNSS receivers are especially useful for GIS and asset mapping, utility inspection, environmental surveys, public works, rural asset inventories, and field data collection where users need better-than-consumer GPS accuracy but do not always need instant centimeter-level RTK fixing.
PPP also fits projects that move across different regions, job sites, or correction environments. Instead of setting up a local base station or depending on nearby CORS/NTRIP availability at every site, users can work with satellite-delivered PPP corrections when the receiver, signal support, and service coverage are suitable.
Agriculture, rural mapping, emergency deployment, remote infrastructure work, and temporary construction planning can all benefit from PPP because the workflow is more independent of local networks. Robotics, autonomy, and machine guidance teams can also use PPP-capable receivers for high-accuracy positioning, testing, and navigation workflows.
RTK backup is still a useful benefit, but it should be seen as one advantage of a flexible receiver, not the only reason to choose PPP. For many field users, PPP is valuable because it provides another reliable positioning path for real-world work where local RTK infrastructure is limited, inconvenient, or unnecessary.
Hardware and Receiver Requirements
PPP support is not only a software label. The receiver must support the signals, correction messages, firmware workflows, and PPP engine required by the intended service.
For Galileo HAS, direct signal-in-space reception requires Galileo E6-B support. For BeiDou PPP-B2b, the receiver needs B2b support and compatible PPP-B2b decoding and processing. A basic GPS-only receiver cannot directly use modern PPP-HAS or PPP-B2b.
Multi-frequency GNSS helps reduce ionospheric error and improves PPP performance. Multi-constellation support improves availability and satellite geometry. A practical PPP-capable receiver needs the required signal tracking, correction-message decoding, firmware support, and a PPP processing engine.
Generic signal examples that may matter for modern high-accuracy receivers include:
- GPS L1/L2/L5
- Galileo E1/E5/E6
- BeiDou B1/B2/B3 and B2b
- QZSS L1/L2/L5/L6
- GLONASS and NavIC where relevant
Buyers should check the receiver specification carefully. “Supports PPP” does not always mean “supports Galileo HAS through E6-B” or “supports BeiDou PPP-B2b.” It also does not always mean the receiver can consume every RTCM SSR, SPARTN, or system-native correction service.
FAQ
Is PPP the same as RTK?
No. RTK usually depends on a local base station, CORS network, NTRIP service, or radio correction link. PPP uses precise satellite corrections such as orbit, clock, and bias information. It is a different high-accuracy GNSS method, not simply a weaker version of RTK.
Does PPP need a base station?
PPP does not need a nearby local base station. It does need precise correction data and a receiver or processing workflow that can use those corrections.
Does Galileo HAS need a local RTK base station?
No. Galileo HAS corrections are broadcast through Galileo E6-B from Galileo satellites. With compatible receiver support, users can receive HAS corrections without setting up a local RTK base station or depending on a nearby CORS/NTRIP correction link.
Is PPP-HAS free?
Galileo HAS is a free high-accuracy service. Users still need compatible receiver hardware, firmware, signal support, and PPP processing capability.
Is BeiDou PPP-B2b global?
No. BeiDou PPP-B2b is a regional BeiDou-3 PPP service mainly intended for China and surrounding areas, often discussed for Asia-Pacific use cases.
Is PPP in RTKLIB the same as PPP-HAS?
No. RTKLIB PPP is software processing capability that often uses observation files and precise products. Galileo HAS is a satellite-broadcast correction service that can support real-time PPP in compatible receivers. They share the PPP concept but are not the same workflow.
Is CSRS-PPP the same as real-time PPP-HAS?
No. CSRS-PPP and similar online PPP services are useful for post-processing, checking, and learning PPP concepts after data has been collected. Real-time PPP-HAS is a live field workflow using satellite-broadcast correction messages with compatible equipment.
Can PPP replace RTK for every survey job?
No single GNSS method is best for every job. RTK remains the preferred option for fast centimeter-level work when local correction infrastructure is available and reliable. PPP is valuable as its own practical option when wide-area coverage, simpler field logistics, or base-station-free positioning is more important.
Why does PPP need convergence time?
PPP estimates a precise position from carrier-phase observations, correction data, and receiver-side modeling. The receiver needs time and continuous observations to resolve or estimate key parameters well enough for high accuracy.
What receiver hardware is needed for PPP-HAS or PPP-B2b?
For Galileo HAS, check Galileo E6-B tracking and HAS decoding/processing support. For BeiDou PPP-B2b, check B2b signal support and PPP-B2b decoding/processing support. In both cases, the receiver needs a suitable PPP engine.
What is the difference between GEO, MEO, IGSO, and LEO satellites?
They are orbit types. MEO is used by most global navigation satellites. GEO appears fixed from Earth and is useful for broadcast. IGSO strengthens regional coverage. LEO satellites move quickly and are mostly used today for communications and remote sensing, with future potential in positioning and augmentation.
Which orbit type is used by Galileo HAS?
Galileo HAS corrections are broadcast through Galileo E6-B from Galileo navigation satellites, which are MEO satellites.
Which orbit type is used by BeiDou PPP-B2b?
Official material describes BeiDou PPP-B2b correction messages as broadcast through the PPP-B2b signal by BDS-3 GEO satellites.
Why do some correction services use communication satellites?
Satellite broadcast can deliver correction data over very large areas without local base-station infrastructure. Some services use GEO communication satellites, while others use navigation satellites or GEO navigation satellites depending on the system design.
What applications benefit most from RTK + PPP support?
Users who work across different regions and correction environments benefit most. RTK is useful where local infrastructure is available, while PPP provides a practical satellite-based option for wide-area, remote, or infrastructure-light workflows.
Buyer Guidance: When to Choose RTK, PPP, or Both
Choose RTK if you need fast centimeter-level field results, have reliable NTRIP/CORS, radio, or local base station access, work inside a known correction network area, and need established survey-grade RTK methods.
Choose PPP-HAS or PPP-B2b if you need high accuracy without local correction infrastructure, work over wider or more remote areas, want satellite-delivered correction options, can accept decimeter-level accuracy where suitable, and want less dependence on cellular or RTK network availability.
Choose RTK + PPP-capable equipment if you want RTK when infrastructure is available and PPP when local RTK access is unavailable. This is often the most flexible choice for users who work across different regions, correction environments, and field workflows.
When evaluating equipment, check whether the receiver supports the signals and correction services required by your workflow, such as RTK/NTRIP, Galileo E6-B HAS, BeiDou B2b, multi-frequency GNSS, and the PPP engine needed for real-time high-accuracy positioning.
Conclusion
Modern PPP does not make RTK obsolete. It expands what high-accuracy GNSS can do.
RTK remains the preferred tool for fast centimeter-level work where correction infrastructure is available. PPP-HAS and PPP-B2b add valuable standalone positioning options for users who need high accuracy without relying on a local base station or nearby RTK network.
The best choice depends on accuracy requirements, coverage, correction availability, supported signals, convergence time, receiver workflow, and field environment. For many professional users, the most practical future-ready approach is not RTK or PPP alone, but equipment and workflows that can use both.