Impacts of point cloud density reductions on extracting road geometric features from mobile LiDAR data
Bibliographic record
Abstract
The variation in point cloud density is driven by many different factors. This variation is expected to affect the quality of the information extracted from the point clouds, however, the extent to which these variations impact the ability to accurately extract and assess geometric features of highways from point cloud data are unknown. This paper investigates the impacts of point density reduction on the extraction and assessment of four critical geometric features. The density of light detection and ranging (LiDAR) data was first reduced and the different features were extracted at varying levels of point density and on a selection of different highway segments in Alberta, Canada. The information obtained at lower point density was then compared to what was obtained at 100% point density. It was found that clearance assessments and sight distance assessments had low sensitivity to reductions in point density (i.e., reducing the point density to as low as 10% of the original data (30 ppm2 on the pavement surface) yielded results comparable to what was obtained at 100% density (300 ppm2) In contrast, for cross section slope estimation and curve attribute estimation higher sensitivity to point density was observed. These findings are critical for transportation agencies considering the adoption of LiDAR technology to manage elements of their infrastructure and for researchers developing data processing tools and algorithms for the semantic segmentation of transportation features from remotely sensed point clouds.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.002 | 0.011 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.000 | 0.001 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".