Transims does not have a trips file; indeed, the same information can be derived from Transims activity files (see Sec. ). Transims activity files contain much more information than we need here, and they have been a continuous source of error and misunderstanding. And as a final argument, we believe that the activities file should be an XML subset of the plans file, as we will discuss in Sec. 24.3. For all those reasons, at this point we deviate once more from Transims file formats and introduce our own file format for trips.
The format is as follows: 0.99trips
This can be read in a similar way as a links or nodes file; and we will use the already existing plan class for storing the information. In consequence, reading the trips looks as follows:
/home/nagel/src/book/router/book/Plan::readNextTrip
Note that the methods to set the plans variables were already defined in Sec. 9.5.