You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: data-types.md
+2-6Lines changed: 2 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -218,9 +218,6 @@ A Trip is defined by the following structure:
218
218
|`end_location`|[Point](point)| Required | Location of the end of the trip. See also [Stop-based Geographic Data][stop-based-geo]. |
219
219
|`publication_time`|[Timestamp][ts]| Optional | Date/time that trip became available through the trips endpoint |
220
220
| `reservation_attributes` | [Reservation](#reservation-data) | Required if available | Reservation details, if a reservation initiated this trip
221
-
|`dispatch_time`|[Timestamp][ts]| Conditionally Required | Time the vehicle was dispatched to the customer (required if trip was dispatched) |
222
-
|`parking_verification_url`| String | Optional | A URL to a photo (or other evidence) of proper vehicle parking |
223
-
|`cancellation_reason`| Enum | Conditionally Required | The reason why a *driver* cancelled a reservation. (required if a driver cancelled a trip, and a `driver_cancellation` event_type was part of the trip) |
224
221
|`accessibility_options`| Enum[]| Optional | The **union** of any accessibility options requested, and used. E.g. if the passenger requests a vehicle with `wheelchair_accessible`, but doesn’t utilize the features during the trip, the trip payload will include `accessibility_options: ['wheelchair_accessible']`. See [accessibility-options][accessibility-options]|
225
222
226
223
(?) Reconcile inconsistent use of `trip_`
@@ -236,13 +233,12 @@ Examples of mode-specific `trip_attributes`:
236
233
|`dispatch_time`|[Timestamp][ts]| Conditionally Required | Time the vehicle was dispatched to the customer (required if trip was dispatched) |
237
234
|`quoted_trip_start_time`|[Timestamp][ts]| Required | Time the trip was estimated or scheduled to start, that was provided to the passenger |
238
235
|`requested_trip_start_location`|[Point](point)| Conditionally Required | Location where the customer requested the trip to start (required if this is within jurisdictional boundaries) |
239
-
|`reservation_method`| Enum | Required | Way the customer created their reservation, see [reservation-method](#reservation-method)|
240
-
|`reservation_time`|[Timestamp][ts]| Required | Time the customer *requested* a reservation |
241
-
|`reservation_type`| Enum | Required | Type of reservation, see [reservation-type](#reservation-type)|
242
236
|`cancellation_reason`| string | Conditionally Required | The reason why a *driver* cancelled a reservation. (required if a driver cancelled a trip, and a `driver_cancellation` event_type was part of the trip) |
243
237
|`accessibility_options`| Enum[]| Optional | The **union** of any accessibility options requested, and used. E.g. if the passenger requests a vehicle with `wheelchair_accessible`, but doesn’t utilize the features during the trip, the trip payload will include `accessibility_options: ['wheelchair_accessible']`. See [accessibility-options][accessibility-options]|
244
238
|`parking_verification_url`| String | Optional | A URL to a photo (or other evidence) of proper vehicle parking |
245
239
240
+
(?) Do I have the right partitioning between trip attributes and reservation attributes?
0 commit comments