itinerary
| Namespace: | (default namespace) |
| XML Schema: | ns0.xsd |
An Itinerary is one complete way of getting from the start location to the end location.
XML
Elements
| name (type) | min/max occurs |
description |
|---|---|---|
| duration (long) | 0/1 | Duration of the trip on this itinerary, in seconds. |
| startTime (dateTime) | 0/1 | Time that the trip departs. |
| endTime (dateTime) | 0/1 | Time that the trip arrives. |
| walkTime (long) | 1/1 | How much time is spent walking, in seconds. |
| transitTime (long) | 1/1 | How much time is spent on transit, in seconds. |
| waitingTime (long) | 1/1 | How much time is spent waiting for transit to arrive, in seconds. |
| walkDistance (double) | 0/1 | How far the user has to walk, in meters. |
| walkLimitExceeded (boolean) | 1/1 | Indicates that the walk limit distance has been exceeded for this itinerary when true. |
| elevationLost (double) | 0/1 | How much elevation is lost, in total, over the course of the trip, in meters. As an example, a trip that went from the top of Mount Everest straight down to sea level, then back up K2, then back down again would have an elevationLost of Everest + K2. |
| elevationGained (double) | 0/1 | How much elevation is gained, in total, over the course of the trip, in meters. See elevationLost. |
| transfers (int) | 0/1 | The number of transfers this trip has. |
| fare (fare) | 0/1 | The cost of this trip |
| legs/leg (leg) | 0/unbounded | A list of Legs. Each Leg is either a walking (cycling, car) portion of the trip, or a transit trip on a particular vehicle. So a trip where the use walks to the Q train, transfers to the 6, then walks to their destination, has four legs. |
| tooSloped (boolean) | 1/1 | This itinerary has a greater slope than the user requested (but there are no possible itineraries with a good slope). |