> For the complete documentation index, see [llms.txt](https://support.senterasensors.com/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.senterasensors.com/home/rtk-ppk-module/getting-started/education/rtk-vs-ppk.md).

# RTK vs PPK

RTK ( Real Time Kinematics) and PPK (Post Processing Kinematics) are two different methods to provide accuracy corrections to drone imagery. RTK corrections happen in real time. PPK corrections happen in post processing after the flight. Each method has pros and cons depending on your site and workflow.

## RTK

* Corrections applied during flight via a live link to a base station or CORS network.
* Enables instant centimeter-level accuracy for geotagging images.
* Ideal for time-sensitive projects like construction monitoring or emergency inspections.
* Requires a stable connection throughout the flight, signal loss can reduce accuracy.

## PPK

* Corrections applied after the flight using raw GNSS data from both drone and base station.
* More resilient to signal dropouts, making it suitable for remote or obstructed environments.
* Offers high accuracy, often better than RTK in challenging conditions.
* Requires additional post-processing time and software.

## Comparison

| Feature             | RTK                            | PPK                              |
| ------------------- | ------------------------------ | -------------------------------- |
| Correction Timing   | Real-time during flight        | After flight (post-processing)   |
| Connectivity Needed | Constant live link             | None during flight               |
| Workflow Speed      | Fast, immediate results        | Slower, requires post processing |
| Accuracy            | High, but connection-dependent | High, more consistent            |
| Best Use Cases      | Construction, inspections      | Remote Mapping, large areas      |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.senterasensors.com/home/rtk-ppk-module/getting-started/education/rtk-vs-ppk.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.