Skip to content

Commit a9b6466

Browse files
committed
remove redundancies, raise question
1 parent 7a1117f commit a9b6466

1 file changed

Lines changed: 2 additions & 6 deletions

File tree

data-types.md

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -218,9 +218,6 @@ A Trip is defined by the following structure:
218218
| `end_location` | [Point](point) | Required | Location of the end of the trip. See also [Stop-based Geographic Data][stop-based-geo]. |
219219
| `publication_time` | [Timestamp][ts] | Optional | Date/time that trip became available through the trips endpoint |
220220
| `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) |
224221
| `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] |
225222

226223
(?) Reconcile inconsistent use of `trip_`
@@ -236,13 +233,12 @@ Examples of mode-specific `trip_attributes`:
236233
| `dispatch_time` | [Timestamp][ts] | Conditionally Required | Time the vehicle was dispatched to the customer (required if trip was dispatched) |
237234
| `quoted_trip_start_time` | [Timestamp][ts] | Required | Time the trip was estimated or scheduled to start, that was provided to the passenger |
238235
| `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) |
242236
| `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) |
243237
| `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] |
244238
| `parking_verification_url` | String | Optional | A URL to a photo (or other evidence) of proper vehicle parking |
245239

240+
(?) Do I have the right partitioning between trip attributes and reservation attributes?
241+
246242
[Top][toc]
247243

248244
[agency]: /agency/README.md

0 commit comments

Comments
 (0)