---
title: "Get Started with PPK Georeferencing"
slug: "get-started-with-ppk-georeferencing"
updated: 2026-08-24T05:26:44Z
published: 2026-08-24T05:26:44Z
canonical: "knowledge.emesent.com/get-started-with-ppk-georeferencing"
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.emesent.com/articles/llms.txt
> Use this file to discover all available pages before exploring further.

# Get Started with PPK Georeferencing

This article provides an overview of the PPK Georeferencing workflow. It links to detailed procedures for each step. Use this guide if new to PPK or for a summary of the end-to-end process before following the individual articles.

## Prerequisites

- Hovermap ST/ST-X with Backpack or Vehicle RTK kit, or GX1
- Rover GNSS receiver (Hovermap only): one of the receivers listed in [Supported GNSS receivers](/v1/docs/3rd-party-recievers). GX1 uses the integrated GNSS receiver.
- Base station data from one of the following sources:
  - **Local GNSS receiver:** Any GNSS receiver capable of logging RINEX data, positioned over a known point for the duration of the scan
  - **GNSS correction network:** A nearby permanent station that provides high-rate (1 Hz or greater) observation data downloadable after the mission
- Commander 2.3 or later installed on a supported mobile device
- Aura 2.2 or later with the RTK / PPK module active
- Emlid Studio installed on a computer (free download from [emlid.com](http://emlid.com))

## Workflow overview

PPK Georeferencing consists of 3 steps completed across two phases: field capture and office processing.

| Step | Phase | Tool | Action |
| --- | --- | --- | --- |
| 1 | Field | Commander and GNSS receiver app | Capture the scan and record RINEX data |
| 2 | Office | Emlid Studio | Process RINEX files to produce a .pos trajectory file |
| 3 | Office | Aura | Process the scan using the .pos trajectory file |

## Step 1: Capture a scan with PPK georeferencing

**Hovermap:** Start RINEX logging on the rover GNSS receiver before starting the mission in Commander. When the GNSS receiver is connected, a **PPK** toggle appears in the mission workflow. Enable it before starting the scan. Offload scan data and RINEX files when the mission is complete. See the receiver data guide for export and conversion instructions:

- [Export and convert Leica GS18 GNSS data to RINEX format](/v1/docs/export-and-convert-leica-gs18-gnss-data-to-rinex-format)
- [Export and convert Trimble GNSS data to RINEX format](/v1/docs/export-and-convert-trimble-gnss-data-to-rinex-format)
- [Export RINEX data from an Emlid receiver](/v1/docs/export-rinex-data-from-an-emlid-reciever)

**GX1:** Enable PPK during mission setup in Commander. The integrated GNSS receiver logs RINEX data automatically. Offload scan data when the mission is complete.

**(Optional) Local base station:** Position the base station over a known point and start RINEX logging before beginning the scan. Offload RINEX files when complete. Not required if using a CORS network.

See [Capture a Hovermap scan with PPK georeferencing](/v1/docs/capture-a-hovermap-scan-with-ppk-georeferencing) or [Capture a GX1 scan with PPK georeferencing](/v1/docs/capture-a-gx1-scan-with-ppk-georeferencing) for the full procedure.

## Step 2: Process RINEX files in Emlid Studio

Import rover and base RINEX files into Emlid Studio and configure kinematic processing settings. Processing produces a corrected .pos trajectory file.

See [Process RINEX files in Emlid Studio](/v1/docs/process-rinex-files-in-emlid-studio) for the full procedure.

## Step 3: Process scan data in Aura using PPK

Open Aura, select **SLAM / RTK / PPK**, and load scan data. Set the georeferencing mode to the appropriate PPK mode for the mount type, then add the .pos trajectory file generated in Emlid Studio. Select **Start** to begin processing.

See [Process scan data in Aura using PPK](/v1/docs/process-scan-data-in-aura-using-ppk) for the full procedure.

## Outcome

After completing these steps, Aura produces a fully georeferenced point cloud ready for use in project deliverables.