Effects of LiDAR Point Density on Extraction of Traffic Signs: A Sensitivity Study
Bibliographic record
Abstract
Datasets collected using light detection and ranging (LiDAR) technology often consist of dense point clouds. However, the density of the point cloud could vary depending on several different factors including the capabilities of the data collection equipment, the conditions in which data are collected, and other features such as range and angle of incidence. Although variation in point density is expected to influence the quality of the information extracted from LiDAR, the extent to which changes in density could affect the extraction is unknown. Understanding such impacts is essential for agencies looking to adopt LiDAR technology and researchers looking to develop algorithms to extract information from LiDAR. This paper focuses specifically on understanding the impacts of point density on extracting traffic signs from LiDAR datasets. The densities of point clouds are first reduced using stratified random sampling; traffic signs are then extracted from those datasets at different levels of point density. The precision and accuracy of the detection process was assessed at the different levels of point cloud density and on four different highway segments. In general, it was found that for signs with large panels along the approach on which LiDAR data were collected, reducing the point cloud density by up to 70% of the original point cloud had minimal impacts on the sign detection rates. Results of this study provide practical guidance to transportation agencies interested in understanding the tradeoff in price, quality, and coverage, when acquiring LiDAR equipment for the inventory of traffic signs on their transportation networks.
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 distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.005 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.002 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.001 |
| 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 teacher head, 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".