TRITAPT observed data

TRITAPT stores scheduled and observed data for one day, one route and one direction in a file. If a route has branches, it must be defined as several routes (one for each branch). It is, however, allowed to have trips that visit only a sub-section of the route.
We have developed software that can import observed data that must usually be slightly adapted to the data that a transit company can provide. The file must contain data about one stop event per line. Each line consists of a fixed set of tab-separated fields, for instance:

Field	Description
1	Schedule date (date to which the event belongs, 8 digits in format YYYYMMDD)
2	Line number
3	Route number
4	Trip number (as used in the first column in the schedule file)
5	Stop name (exactly as defined in the schedule file), see below).
6	Total delay between departure from the previous stop and arrival at this one (in seconds)
7	Observed arrival time at this stop
8	Observed departure time at this stop
9	Observed number of alighting passengers at this stop (-1 if not available)
10	Observed number of boarding passengers at this stop (-1 if not available)

Events of different trips can occur in any order. Events on different routes can be mixed in one event file.
Comments can be used in this file by starting a line with a # (sharp) symbol.
Below is an example of a very simple event file in this format. This file matches the trips in the example schedule file.

# Events of different trips may be listed in any order, but in this case the order is chronological.
20041231	1	1	0010101	Stop 1	125	07:50:12	08:00:15	-1	-1
20041231	1	1	0010101	Stop 2	151	08:03:19	08:04:15	-1	-1
20041231	1	1	0010101	Stop 3	0	08:06:02	08:06:02	-1	-1
20041231	1	1	0010101	Stop 4	109	08:08:55	08:09:17	-1	-1
20041231	1	1	0010102	Stop 1	19	08:08:25	08:10:12	0	12
20041231	1	1	0010101	Stop 5	35	08:10:25	08:18:17	-1	-1
20041231	1	1	0010102	Stop 2	0	08:11:55	08:12:33	0	2
20041231	1	1	0010102	Stop 3	0	08:13:42	08:14:23	3	0
20041231	1	1	0010102	Stop 4	0	08:15:52	08:15:52	0	0
20041231	1	1	0010102	Stop 5	0	08:17:16	08:21:59	8	0

If the stop names on a route are not unique in the first 30 characters, stop numbers should be defined in the schedule file and used in the observed events file.
The observed event file above contains events that have somehow been matched against a particular trip and stop. If your company has not already implemented such a matching procedure, we can provide help.