PPK Georeferencing FAQ

When a GNSS receiver is connected to Hovermap, a PPK toggle appears automatically in the mission workflow. Enable the toggle before starting the scan.

The PPK status indicator appears in blue on the Scan setup and Pointcloud pages when PPK is enabled. It is not shown if PPK was not selected before the scan. Tap the PPK status to display a prompt to check that RINEX logging is active in your receiver's app.

PPK post-processing requires an active RINEX log. If logging was not active during the scan, the data cannot be post-processed using PPK. Re-capture the mission with RINEX logging enabled.

Yes. A single continuous RINEX log can cover multiple scans for the same job. There is no need to stop and restart RINEX logging between scans. The receiver must remain logging throughout all scans.

Both options work. A local base station gives you full control over base data and works without network access, but requires a second receiver positioned over a known point. A GNSS correction network lets you download base observation data after the mission without any field setup. Confirm that your selected network site provides high-rate data (1 Hz or greater) before relying on it. Not all sites support high-rate data.

Georeferencing accuracy decreases by approximately 1 mm for every kilometre of baseline length. A baseline longer than 15 km is not recommended. If your nearest reference station exceeds this distance, use a local base station positioned closer to the scan site.

Fixed and float refer to the quality of ambiguity resolution during kinematic processing. A fixed solution means integer ambiguities were resolved with high confidence, producing the most accurate result. A float solution means ambiguities were estimated rather than resolved. Accuracy is lower, but the result may still be usable depending on your requirements. Aim for the highest fixed percentage possible. A low fixed percentage can indicate a long baseline, signal obstruction, or poor satellite visibility during the scan.

Use the main .pos file produced by Emlid Studio. Emlid Studio also produces an _events.pos file during processing. This file is not required for Aura.

Yes. RTK and PPK logging can run simultaneously. You can capture RTK corrections in real time while also recording RINEX data for PPK post-processing. If RTK quality is sufficient, use the RTK result. If not, use the PPK result.

PPK post-processing can recover accurate georeferencing for any period where RTK corrections dropped out. The PPK trajectory covers the full mission, including RTK dropout periods, as long as RINEX logging was active throughout the scan.