Pedestrian and Bicyclist Traffic Control Device Evaluation Methods
Bibliographic record
Abstract
This report offers traffic engineering practitioners information on how to evaluate roadway traffic control devices used by pedestrians and bicyclists. Though presented in the context of devices meant for pedestrian and bicyclist facilities, the guidance provided can be applied in a more general sense to evaluations of traffic control devices in all settings. The evaluation methods report is designed for practitioners (State transportation departments and county or city engineers and planners) but could also be helpful to traffic safety students and researchers. Personnel without specialized statistical analysis skills should be able to use the report. It presents a detailed plan for practitioners to follow from the initial problem identification stages to documenting the evaluation effort. The first step of any evaluation is to clearly formulate the research question by identifying the motorist, pedestrian, or bicyclist behavior that poses a safety or operational problem. Candidate traffic control devices and other countermeasures can then be identified as potential solutions to that problem. The evaluation methods described in this report include user surveys or interviews, visibility studies, driving performance studies, observational traffic studies, and crash analyses. The selection of the appropriate evaluation method will consider cost, time, research aims, and available research equipment and staff.
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.011 | 0.020 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.003 | 0.001 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.000 |
| Insufficient payload (model declined to judge) | 0.010 | 0.002 |
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".