| Row | Content of columns 2 .. N | Required / Optional |
|---|---|---|
| Stop names | Name of each stop (only the first 30 characters are used by TRITAPT) | Required |
| Stop name abbreviations | One two-letter stop name abbreviation | Optional |
| Stop distances | Relative or cumulative distances of / between the stops in m, or any other unit of distance | Required |
| Geo locations | Geographical location of each stop | Optional |
| Stop codes | Positive integer number identifying each stop (must be unique within a route) | Optional |
| Time point indicators | "T" for yes, leave blank if no | Optional |
The trip specific information follows the route description. Each
scheduled trip occupies one row in the table. The first column must
contain a trip identifying, positive integer number. If a company
does not use such numbers, use the trip number, or use the fixed
value 0. Columns 2..N must be filled with the scheduled departure
time for each stop. If a trip visits only a sub-section of the
route, leave the cells for the non-visited stops blank.
The time in the last non-blank cell is interpreted as scheduled
arrival time; all others are considered departure times. But, if
at some stop the scheduled departure time differs from the scheduled
arrival time, an extra column must be inserted in the entire table
for that stop and both arrival and departure times must be specified
for that stops for all scheduled trips. The stop name, abbreviation,
number, geo-info, etc., should be the same for both columns. If
distances are cumulative, the distance for the departure time column
should be 0, otherwise it should be the same as the distance for the
arrival time column.
Times can be written in hh:mm:ss format, hh:mm format, or as the
number of seconds since the start of the day. However, times that
describe (part of) trips that occur past midnight, but belong to
the time-table of the preceding day must be written with un-wrapped
time values like 24:03:00, or 24:03, or 86580.
It is possible to use comments in the file. A comment starts with
a # (sharp) symbol and causes the remainder of the line to be
ignored.
A super-simple example of a schedule file with lots of comments is
shown below. This file describes a route with 5 stops and two
scheduled trips.
# This is a ultra simple file describing a schedule # Comments start with a hash (like this line) # # List of stop names (all on one line, preceded by one tab, separated by tab) Stop 1 Stop 2 Stop 3 Stop 4 Stop 5 # # List of cumulative stop distances in m (all on one line, preceded by one # tab, separated by one tab) 0 350 790 1010 1400 # # List of scheduled trips, one line per scheduled trip: # first field: trip ID (integer, preferably unique) # subsequent fields: scheduled departure times at the stops # These times can be specified in seconds since midnight or in # HH:MM:SS format. Times after midnight of trips that belong to # the preceding calendar day must be specified using values # from 86400 or 24:MM:SS # All fields are separated by one tab character # If a trip visits only part of a route, leave fields before # and after that route section blank (resulting in multiple, # consecutive tab characters). # trip 1: 0010101 8:00:00 8:02:00 8:04:00 8:05:00 8:07:00 # trip 2 (same time distribution; ten minutes later): 0010102 8:10:00 8:12:00 8:14:00 8:15:00 8:17:00The TRITAPT observed data page shows an example of an equally simple observed data file that matches the two trips shown here.