Geocoding Report

The Geocoding Report documents the inputs, settings, and results of a Geocoding job. It includes point-cloud previews, processing metadata, output file information, and point-cloud statistics. When Run Advanced Analytics is selected, it also includes available Surface Precision and Flight Line Overlap results.

Use the report to confirm that the intended data and settings were used, review the generated outputs, and identify areas requiring closer inspection in LP360. The report is a processing record and review aid; it does not replace trajectory review, point-cloud inspection, or independent accuracy assessment.

Opening the Report

1. Open Job Manager.
2. Select the Geocoding job after processing has finished.
3. Select View Report to open the generated PDF.

Completing the Geocoding job also opens the report when the report file is available.

Report Files

The report files are written to the job working folder.

The PDF title is Geocoding Report, although its filename uses Geocoding_Summary. Keep the report with the corresponding processing records when archiving or sharing a job.

Report Sections

Content depends on the job settings and available data. For example, a point cloud without RGB color does not have a Color Preview page, and Advanced Analytics results require the analytics processing option.

Color Preview

Displays an overview of the output point cloud using its RGB color. This page appears only when a color preview is available.

Review the image for general coverage and obvious colorization issues. Use the point cloud in LP360 for detailed inspection; the report image is an overview rather than a full-resolution deliverable.

[IMAGE PLACEHOLDER: Color Preview from a colorized Geocoding output.]

Elevation Preview

Displays an elevation-colored overview of the output point cloud. If no Color Preview is available, the report begins with Elevation Preview.

Review the overall extent and elevation pattern for unexpected gaps, isolated areas, or abrupt changes that warrant inspection in LP360. An apparent issue in the preview should be checked against the actual point cloud before drawing conclusions.

[IMAGE PLACEHOLDER: Elevation Preview showing the output coverage.]

Project Metadata

Identifies the processing run using the project name, Cycle name, processing date/time, job start and end times, and the user's notification email address.

Confirm that the project and Cycle match the dataset you intend to review, particularly when comparing reports from repeated processing runs.

Input Data

Records information about the trajectory, payload, calibration, and camera. Available fields include:

• Trajectory filename and its last-modified timestamp.
• Payload serial number and model.
• Calibration date from the sensor calibration file (SCF).
• Camera model.
• Raw LiDAR input filenames and sizes, when available.

Use this section to confirm the expected trajectory, sensor, and calibration were associated with the job. A calibration date is a record of the calibration information used; it does not, by itself, confirm that the calibration is the latest available.

Flight Lines

Displays the point cloud colored by point source ID, with flight-line geometry drawn in dark blue. Arrows indicate the direction of flight.

Review the spatial relationship between the flight lines and the generated point cloud. This preview is different from Flight Line Overlap: it shows point source IDs and flight paths, rather than the number of distinct point source IDs in each cell.

[IMAGE PLACEHOLDER: Flight Lines preview with point source colors, dark-blue flight paths, and direction arrows.]

Processing Settings

Records the processing options associated with the job. Depending on the sensor and workflow, these include:

• LiDAR processing status, field of view or clip angle, range clipping, and TrueTrack.
• Boresight roll, pitch, and heading from the sensor calibration file.
• Remove Gross Outliers status and the recorded number of affected points.
• Colorization, photo processing, EXIF updates, retained-photo method, and the job's photo count.
• CoPre height filtering, when applicable to the Sensor Extension workflow.

Remove Gross Outliers (Flyer/Sinkers) shows whether the option was enabled and, when available, the number of points removed or flagged. If the report states count not recorded, the count was unavailable; do not interpret this as zero affected points.

Some settings are sensor-dependent. For example, TrueTrack is shown as N/A (Sensor Extension) for Sensor Extension processing. A boresight entry of (not found in SCF) indicates that the report could not obtain those values from the calibration file.

[IMAGE PLACEHOLDER: Processing Settings table showing clipping, boresight, and Remove Gross Outliers results.]

Results Summary

Summarizes the processing window, total points in the output LAS files, and output LAS file count. The Output files table lists each output LAS filename, point count, and file size.

Check that the output files and point counts are consistent with the intended processing extent. Clipping and outlier removal can affect the number of output points. A point count alone does not establish whether the output has adequate coverage or meets project accuracy requirements.

Point Cloud Statistics

For jobs with LiDAR geocoding enabled, this section summarizes the generated point cloud using a fixed Geocoding statistics preset. Statistics are calculated across the job's output point cloud rather than presented as separate statistics tables for each LAS file.

The automated preset does not include LAS header-attribute statistics. Its statistics are incorporated into the Geocoding Report rather than delivered as a separate automated statistics PDF.

Overall density and nominal point spacing summarize the dataset; they do not show every local variation or gap. Inspect spatial coverage in LP360 when evaluating project requirements.

[IMAGE PLACEHOLDER: Point Cloud Statistics tables with density, nominal point spacing, and example attribute ranges.]

Advanced Analytics

When Run Advanced Analytics is selected, the report includes available analytics settings and product statuses. Settings include point density, cell size, and the sensor-based global, inter-swath, and intra-swath thresholds.

Geocoding analytics generates two products:

• Surface Precision - A color-coded Global SDASN surface-precision product.
• Flight Line Overlap - A count of distinct point source IDs in each raster cell.

Successfully generated previews appear on separate pages with their color scales. The Surface Precision preview uses the global threshold; the listing of inter-swath and intra-swath thresholds does not mean that separate inter-swath or intra-swath rasters were generated.

Add Analytics to Map controls whether generated analytics rasters are loaded into the project map when the job is completed. It does not control whether analytics results appear in the report.

See Advanced Analytics for product interpretation, threshold selection, color scales, raster naming, output locations, and how analytics differs between Geocoding and Strip Align.

[IMAGE PLACEHOLDER: Optional example of the Geocoding analytics report pages and their legends.]

Software and Hardware Version 

Records the LP360 version, Sensor Extension version, Windows version, processor, installed RAM, and video card, where available. Include this information when discussing processing differences or submitting a support request.

Understanding Missing or Unavailable Results 

Missing previews, statistics, or analytics products are different from a failure to save the report itself. A failure to write the Geocoding Report PDF or its companion text file is treated as a job error.

Recommended Review Sequence 

1. Confirm the project, Cycle, trajectory, sensor, and calibration information.
2. Verify that the processing settings match the intended job.
3. Review the color, elevation, and flight-line previews for coverage and areas requiring closer inspection.
4. Check the output filenames, point counts, and point-cloud statistics.
5. Review analytics statuses and previews when analytics was requested.
6. Inspect questionable areas in LP360 and complete the project's required quality-control and accuracy checks.

Related Information

• Advanced Analytics
• Job Manager
• Troubleshooting Geocoding Issues