Basic

Function Overview

Basic mode is intended for first-time Pavement Distress Analysis users or users who want to obtain detection, PCI, and report results quickly by following the standard sequence. The interface is organized into Pavement Distress Analysis Workflow, Detection, and Verification. The workflow connects commonly used steps, while the independent functions supplement point cloud detection or allow manual correction of automatic results.

Basic Information

Outputs

  • Distress Results: Image-based or point cloud-based detection writes pavement distress to the "Distress" layer. The recommended workflow also uses Distress Verification for manual review.

  • Sample Unit Results: The pavement range is divided into sample units in the "Sample Unit" layer and can be corrected with Sample Units Editor.

  • PCI Results and Analysis Report: PCI is calculated from the verified "Distress" and "Sample Unit" layers, stored in the "PCI Section" layer, and used to export the analysis report.

Input Data

  • Point Cloud Data: Load point cloud data covering the target road into the current project

  • Image Data: Prepare photos and an image list file (*.imglist) matched to the point cloud for Image-based Distress Detection

  • Trajectory Data: Load trajectory data corresponding to the point cloud. It is used to generate sample units, associate PCI sections, and organize report results

Before running Pavement Distress Analysis Workflow, confirm that the point cloud, photos, image list, and trajectory correspond correctly in coordinates, time, and project relationships.

Functions

Automatic Workflow

The workflow uses image-based detection and runs the following functions in order:

1.Subsampling

2.Classify by Deep Learning

3.Image-based Distress Detection

4.Sample Units Generator

5.PCI

6.Export Report

Each step uses the preceding result: Subsampling and Classify by Deep Learning prepare the point cloud; Image-based Distress Detection creates the "Distress" layer; Sample Units Generator defines the PCI evaluation area; PCI is then calculated and the report is exported. Check the parameters for each step and click Run to process them together.

After the automatic workflow is complete, review and output the results in this order:

1.Use Distress Verification to review automatic results, confirm, delete, or edit distress, and add missed distress

2.Use Sample Units Editor to check and correct sample unit boundaries

3.Run PCI again to create a "PCI Section" layer consistent with the verified results

4.Export Report again to obtain a report suitable for formal analysis

The recommended workflow adds manual review to automatic processing and is intended for cases requiring higher result accuracy. If Point Cloud-based Distress Detection is used to supplement geometric deformation detection, complete it before Distress Verification.

The automatic workflow emphasizes speed and provides preliminary distress statistics, but it may contain missed detections, false detections, or incorrect distress type and severity assignments. The recommended workflow emphasizes accuracy; it is not a separate automatic process, but adds manual review and correction to the automatic results.

Process Dependencies

The outputs have sequential dependencies. After rerunning detection or editing sample units, recheck the downstream PCI and report results. See Function Index for all function entries.

Detection

  • Point Cloud-based Distress Detection: Detects rutting, depression, potholes, bumps, swell, corrugation, and shoving from point cloud geometry. It is not included in the image-based workflow and can be run independently when Lane Line data is available. Results are also written to the "Distress" layer.

Verification

  • Distress Verification: Reviews image-based and point cloud-based detection results by confidence. Confirm, delete, or edit existing distress, or manually draw distress missed by automatic detection. After both detection methods are complete, verify the results together.

  • Sample Units Editor: Checks and corrects automatically generated sample unit boundaries so non-pavement areas are not included and valid pavement is not omitted from PCI calculation.

results matching ""

    No results matching ""