Evaluating the Impact of Freeway Service Patrol on Incident Clearance Times: A Spatial Transferability Test
Bibliographic record
Abstract
Freeway service patrol (FSPs) programs have been considered as an effective tool for traffic incident management in minimizing the adverse effects of traffic incidents. In this study, random parameters hazard-based duration modeling method was used to evaluate the impact of the newly implemented Alabama Service and Assistance Patrol (ASAP) program, using incident clearance time as a performance measure. It was determined that there is a statistically significant difference in the factors that influence incidents clearance times between incidents that occurred inside and outside the ASAP regions. A total of five variables (on-road, nighttime, peak hours, rain, and fire response present) were observed to have random effects along with ten fixed effects variables on incidents occurring inside the ASAP regions. On the other hand, incidents that occurred outside the ASAP regions were found to have three random effects variables (on-road, nighttime, and fire response present) and seven fixed effects variables. The estimation results indicate a significant association of incident clearance times to incident related variables such as involvement of CMVs, fatality, vehicle towing, seat belt indicated as involved, and on-road incidents that occurred both inside and outside the ASAP regions. The results also reveal that incident clearance times are influenced strongly by temporal variables (e.g., nighttime), traffic factors (e.g., AADT), and operational variables (e.g., fire response present) for incidents both inside and outside the ASAP area models. Overall, it was observed that the incident clearance times recorded in the regions where the ASAP program is in effect are significantly different. The findings of this study are expected to be useful for the state traffic incident management (TIM) agencies in developing and executing strategies to minimize incident clearance times. Ultimately, the study provides a data-driven evidence-based assessment of the ASAP program in the state.
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.006 | 0.026 |
| 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.001 | 0.001 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.002 | 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".