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
-37Lines changed: 0 additions & 37 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -245,43 +245,6 @@ Examples of mode-specific `trip_attributes`:
245
245
246
246
[Top][toc]
247
247
248
-
### Reservation Data
249
-
250
-
A Reservation is defined as follows:
251
-
252
-
| Field | Type | Required/Optional | Comments |
253
-
| ----- | ---- | ----------------- | -------- |
254
-
|`reservation_method`| Enum | Required | Way the customer created their reservation, see [reservation-method](#reservation-method)|
255
-
|`reservation_time`| Timestamp | Required | Time the customer *requested* a reservation |
256
-
|`reservation_type`| Enum | Required | Type of reservation, see [reservation-type](#reservation-type)|
257
-
|`quoted_trip_start_time`| Timestamp | Required | Time the trip was estimated or scheduled to start, that was provided to the passenger |
258
-
|`requested_trip_start_location`|[GPS][gps]| Conditionally Required | Location where the customer requested the trip to start (required if this is within jurisdictional boundaries) |
259
-
260
-
[Top][toc]
261
-
262
-
#### Reservation Type
263
-
264
-
The reservation type enum expresses the urgency of a given reservation. This can be useful when attempting to quantify metrics around trips: for example, computing passenger wait-time. In the `on_demand` case, passenger wait-time may be quantified by the delta between the `reservation_time`, and the pick-up time; however, in the `scheduled` case, the wait time may be quantified based on the delta between the `scheduled_trip_start_time` found in the Trips payload, and the actual `trip_start_time`.
0 commit comments