RESEPI Logo

PPK, RTK, and SLAM Breakdown

« All Documentation

RESEPI User Manual
Table of contents
 

Workflows #

Data processing in PCMasterProGL is streamlined for efficiency and user convenience. This section outlines the most commonly used workflows: one for those not interested in post-processing inertial data before generating clouds (RTK), another for those interested in post-processing inertial data before generating clouds (PPK), and a new workflow for SLAM that can operate with or without GNSS.

  1. Default RTK and Default PPK Workflows

    • The files for the Default RTK and Default PPK workflows are automatically generated for user convenience by the system after every data-recording session. If using the one-click processing feature, these project workflows provide quick, streamlined analysis and output all data points captured within the preset field of view of the system.
    • If the user does not have an RTK modem or PPK license for corrections, a cloud can be created using the RTK workflow with raw GNSS aided INS and LiDAR data. However, the absence of corrections will significantly impact data quality of the trajectory.

  2. Custom Projects and Post-Processing

    • For custom projects and information on post-processing with other forms of Inertial Explorer (outside of the embedded SDK for PCMasterProGL), users can adjust and modify how PCMasterProGL outputs the final solution. Users will need to create a new project file or modify the existing project (.proj) file.

  3. SLAM Workflow

    • PCMasterProGL now supports a LiDAR+IMU SLAM workflow, which can operate with or without GNSS. This workflow incorporates just LiDAR and IMU data, providing an alternative processing method for scenarios where GNSS data may be unavailable or unreliable.

Incorporating these workflows allows users to choose the best processing method suited to their specific requirements, ensuring flexibility and accuracy in their data processing efforts.