MétaCan
Menu
Back to cohort
Record W1488176543 · doi:10.5038/2375-0901.5.3.2

Transit Itinerary Calculation on the Web: Based on a Transit User Information System

2002· article· en· W1488176543 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.
fundA Canadian funder is recorded on the work.

Bibliographic record

VenueJournal of Public Transportation · 2002
Typearticle
Languageen
FieldSocial Sciences
TopicTransportation Planning and Optimization
Canadian institutionsPolytechnique Montréal
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsHeuristicsTransit (satellite)Computer scienceThe InternetPedestrianGeographic information systemTransport engineeringWorld Wide WebPublic transportEngineeringGeography

Abstract

fetched live from OpenAlex

Transit path calculation is not yet widely available on transit authority websites. This is because the calculation of complete transit itineraries requires the integration of underlying components such as Geographic Information Systems (GIS) and operational database and, unlike a simple road application, involves a complex transportation network. In this article, a hybrid algorithm based on heuristics and optimization is presented for the calculation of urban transit itineraries including information on pedestrian access and egress paths, route sequences, schedules, and stops. The use of the Transit User Information System (TUIS) to support the calculations is emphasized. The TUIS uses the Totally Disaggregate Approach (TDA) and Transportation Object-Oriented Modeling (TOOM) in transportation to gather data on territory (for origin and destination specifications and for the pedestrian network) and transit operation (route geometry, schedules). Websites that have been implemented are referenced to demonstrate the applicability of the hybrid algorithm. These websites make use of some special techniques for disseminating user information over the Internet.

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.

Full frame distilled prediction

Teacher imitation

Not 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.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.492
Threshold uncertainty score0.461

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.028
GPT teacher head0.236
Teacher spread0.208 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it