Troubleshooting: Unable to Locate the *.PosT File Below the Folder

Applies to sensors with a CHCNav POS.

📌 Problem

During Trajectory Processing through the Job Manager , the job fails with the following error:

Unable to locate the *.PosT file below the folder

When this occurs, trajectory processing stops and subsequent steps such as picture processing, LAS generation, or QA/QC cannot continue.

This error indicates that the required PosT trajectory output file was not generated or not found in the expected location. In most cases, the root cause is an upstream trajectory processing failure, missing or corrupted raw inputs, or an incomplete job folder. Reviewing logs and verifying data integrity will typically identify the cause and allow processing to proceed.

🧠 What Is the PosT File?

The PosT file is a required trajectory output generated during the sensor trajectory processing stage. It contains post-processed position and orientation data and must be successfully created before downstream processing can proceed.

If the PosT file is missing, LP360 cannot continue with picture processing or point cloud generation.

🔍 Root Causes

1. Trajectory Processing Did Not Complete Successfully

If the trajectory solver encounters an error or exits early, the PosT file is never written. In these cases, logs typically show trajectory processing starting but failing before PosT creation.

2. Missing, Invalid, or Corrupt Raw Position Data

Trajectory processing depends on valid raw position inputs (for example, GNSS/IMU position files). If these files are incomplete or corrupted, trajectory processing may fail and never produce a PosT file.

3. Unexpected Folder Structure or Manual File Changes

LP360 expects the PosT file to exist in a specific subfolder (commonly POS or POST) within the job directory. If files were moved, renamed, partially copied, or manually reorganized, LP360 may not be able to locate the PosT file.

4. Incomplete or Interrupted Data Transfer

If Cycle or POS data was copied from the sensor storage and the transfer was interrupted, the job folder may be incomplete. In these cases, trajectory processing may run but fail to generate required outputs such as the PosT file.

✅ Probable Resolutions

1. Check the expected POS / POST folder

   Navigate to the job directory and confirm whether a *.PosT file exists. If the folder exists but is empty, the file was never generated.

2. Verify raw position data integrity

   Confirm that all required raw position files are present and readable. If corruption is suspected, re-copy the data from the original sensor or storage media.

3. Review the trajectory processing log

   Look for a message confirming that a PosT file was created and copied. If no such message appears, trajectory processing did not complete successfully. Trajectory processing always produces one or more log files that explain why the PosT file was not created, even when the UI error message is generic. 

   Where to Find the Logs

   In the job directory, navigate to the following by selecting the job in the Job Manager and pressing File Explorer:

   <Project Folder>\Area_<AreaName>\Cycle_<CycleName>\POS\

   Look for subfolders from each processing attempt:

   TrajProc_<timestamp>

   Inside these folders, collect:

   • LOG.txt
   • StdOut.txt
   • StdErr.txt
   • The generated PDF report (if present)

Support frequently requests these exact files when troubleshooting PosT errors.

Trajectory Processing Errors: Causes and Resolutions

📬 Need Help?

If you're still stuck, please Contact Support and submit the logs found in \Project\Area\Cycle\POS\TrajProc_YYMMDD_hhmmss and transfer the archived Cycle to support via LP360 Cloud or upload using Upload to Support and select the option to include project logs for further analysis.