Can Trip Planner Log Files Analysis Help in Transit Service Planning?
Bibliographic record
Abstract
Transit trip planners are now found on most transit authority websites. This feature gives transit users a full itinerary from a point of origin to a destination. The web server on which the trip planner is installed usually stores usage logs on a daily basis. Log files contain data on origins, destinations, calculated paths, and other website entries. The main purpose of this article is to determine whether the analysis of trip planner log files can help to improve transit service by providing better knowledge on transit users. A website-oriented analysis and a transit-oriented analysis based on four years of observations on the Montreal Transit Commission website are presented. Results show that, even though not all transit users have access to the Internet or use the planner regularly, log files can be useful for identifying new locations to be accessed by a transit system, for better understanding user behaviors, and for guiding updates of the geographic information system (GIS) and the trip planner itself.
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.004 | 0.037 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.009 | 0.010 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.004 | 0.007 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.002 | 0.001 |
| Insufficient payload (model declined to judge) | 0.014 | 0.006 |
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".