The Effect of Type of Attributes on the Fill-Ability of Accident Reporting Forms (ARF)
Bibliographic record
Abstract
Accident Reporting Form (ARF) is the basic building block of an Accident Database. Incorrect and incomplete forms result into the formation of erroneous database which contains partial or no essential information required for the statistical analysis of accident data. Policies made on the basis of the results of such databases will have little or no effect on the improvement of safety of roadway facilities. In most countries filling of the ARF is the responsibility of Police/Investigating officers. Due to lack of interest, all the details are not recorded by them. Thus, it is very important to investigate the type of attributes and their respective items filled most. The objective of this study is to evaluate the attributes given most importance by the person in charge of filling the ARF and the items most neglected. The probable reasons for the complete/incomplete recording of the details of certain items were also examined. For this study a total of 642 forms were obtained from the Malaysian Institute of Road Safety Research (MIROS) for evaluation. Each form contained 91 attributes, as per number given in the accident reporting form known as POL 27. The items were divided with respect to driver, passenger, vehicle, pedestrian, location, road environment, road information and additional information. The fill-ability for each item was estimated in terms of percent filled. The items were evaluated in terms of least and most filled and the probable reason for the complete/incomplete filling of each item was then investigated. It was found that items related to location were most neglected. The second most incomplete items were associated with the vehicle and the driver. While the attributes related to the road and the environment were found to be the most filled. The probable reason for lack of fill-ability of location related items was their placement in inappropriate sections. The important finding of this study is the high number of items in the POL 27 which makes it difficult for the officer to fill the form completely and is the major cause of reduced fill-ability.
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.041 | 0.267 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.002 |
| Bibliometrics | 0.002 | 0.002 |
| Science and technology studies | 0.001 | 0.002 |
| Scholarly communication | 0.003 | 0.003 |
| Open science | 0.002 | 0.002 |
| Research integrity | 0.001 | 0.002 |
| Insufficient payload (model declined to judge) | 0.005 | 0.001 |
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".