The <tripDetails/> element captures extended information about a particular trip, potentially including the trip instance information, schedule, status, and active service alert information. It is returned as a sub-element in a number of api calls. For example:
<tripId>1_12540399</tripId> <serviceDate>1271401200000</serviceDate> <frequency>...</frequency> <status>...</status> <schedule> <timeZone>America/Los_Angeles</timeZone> <stopTimes> <tripStopTime> <arrivalTime>81706</arrivalTime> <departureTime>82620</departureTime> <stopId>1_18085</stopId> </tripStopTime> <tripStopTime>...</tripStopTime> </stopTimes> <previousTripId>1_12541128</previousTripId> <nextTripId>1_14469030</nextTripId> </schedule> <situationIds> <string>1_1289973261968</string> </situationIds>
We start with the tripId for the trip, which can be used to look up the referenced <trip/> element in the <references/> section.
Next we have optional trip instance information, including the <serviceDate/> and optional <frequency/> element.
The optional <status/> element captures real-time information about the trip, where applicable. For more details on the <status/> element, see the <tripStatus/>.
The <schedule/> section, which includes the following elements:
Details about the <tripStopTime/> element. Note that arrival and departure times are the scheduled times and do not reflect real-time arrival information, even if its available:
Finally, the <situationIds/> element contains ids for any active <situation/> elements that currently apply to the trip.