This generic error message is typically caused geocoding failing to produce LAS files or generated erroneous LAS files.
Below are know causes and resolutions. Relevant error messages can be found in the project geocoding.log file. If you intend to send a ticket to support please include the geocoding.log and the POSPac report associated with that cycle dataset.
Cause #1: You are using an older version of LP360 that does not support a newer sensor
Resolution: Upgrade LP360
https://support.geocue.com/lp360-software-update-guide-2/
Cause #2: Geocoding settings such as Scan Angle or Clip Range is set to a value where one or more of your flight lines are producing empty LAS files
Resolution: Adjust your Scan Angle or Clip Range to a less extreme value
Cause #3: A very short flight line that contains partial or no trajectory information produced an empty LAS files.
Resolution: Review flight lines and ensure they are of substantial length and are covered by the time span of the trajectory solution.
Cause #4: The trajectory solution is invalid or incomplete
Resolution: Review your POSPac report and ensure the fixed percentage is at 100% and that the time span of your trajectory spans the majority of the middle section of your flight where the needed data will be.
https://support.geocue.com/true-view-pospac-report/
Cause #5: One or more laser files are corrupt and the geocoder is unable to read them
Resolution: Try to obtain and original copy of dataset, ideally you will want to get the original cycle data from the sensor USB drive. Put the USB drive into your computer and directly import from that location so that LP360 will perform a verified file transfer. This method is the best practice for field operations. If the original USB cycle is not available and the dataset has been transmitted through different media, such as cloud storage or external storage drive, obtain the closest to the original copy. If an uncorrupted copy of the laser files cannot be obtained the area will need to be reflown.
Cause #6: One of the drives you are reading from or writing to is unable to read or write the data or the throughput low. Certain types of media are ill-suited for processing large datasets. Slow media like network storage, SD cards, and cloud storage will poor bandwidth can cause problems with reading and writing data. Also cloud sync folder can sometimes lock files and make them temporarily inaccessible for writing data.
Resolution: It is strongly recommended to allows process data on a local solid state drive (SSD) Also ensure that the folder your data resides on is not setup for cloud synchronization or pause the synchronization until you are finished with file operations with your project.
Cause #7: The trajectory was processed in a manner that deviates from our typical workflow and the trajectory may not conform to the expected data format.
Resolution: If your are generating the trajectory manually in POSPac Desktop or within other POSPac license types the trajectory needs to conform to these specification: LP360 expects each cycles /POS/ folder contain the sbet.out and smrmsg.out named exactly as such and set to the ITRF2014 geographic coordinates.
