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
+10-21Lines changed: 10 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,10 +11,6 @@
11
11
-[Stops](#stops)
12
12
-[Stop Status](#stop-status)
13
13
-[Trips](#trips)
14
-
-[Trip Attributes](#trip-attributes)
15
-
-[Reservation Data](#reservation-data)
16
-
-[Reservation Type](#reservation-type)
17
-
-[Reservation Method](#reservation-method)
18
14
19
15
## Vehicles
20
16
@@ -199,8 +195,12 @@ A Trip is defined by the following structure:
199
195
| Field | Type | Required/Optional | Comments |
200
196
| ----- | ---- | ----------------- | -------- |
201
197
|`provider_id`| UUID | Required | A UUID for the Provider, unique within MDS. See MDS [provider list](/providers.csv). |
198
+
|`provider_name`| String | Required | The public-facing name of the Provider |
202
199
|`data_provider_id`| UUID | Optional | If different than `provider_id`, a UUID for the data solution provider managing this data endpoint. See MDS [provider list](/providers.csv) which includes both service operators and data solution providers. |
203
200
|`device_id`| UUID | Required | A unique device ID in UUID format |
201
+
`vehicle_id` | String | Required | The Vehicle Identification Number visible on the vehicle itself |
202
+
|`vehicle_type`| Enum | Required | See [vehicle types][vehicle-types] table |
|`journey_id`| UUID | Optional | A unique [journey ID](/modes#journey-id) for associating collections of trips for its [mode]|
205
205
|`trip_type`| Enum | Optional |**[Mode](/modes#list-of-supported-modes) Specific**. The [trip type](/modes#trip-type) describing the purpose of a trip segment |
206
206
|`trip_id`| UUID | Required | A unique ID for each trip |
@@ -213,29 +213,18 @@ A Trip is defined by the following structure:
213
213
|`duration`| Integer | Required | Time, in Seconds |
214
214
|`distance`| Integer | Required | Trip Distance, in Meters |
215
215
|`publication_time`|[Timestamp][ts]| Optional | Date/time that trip became available through the trips endpoint |
216
-
| `reservation_attributes` | [Reservation](#reservation-data) | Required if available | Reservation details, if a reservation initiated this trip
217
-
|`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]|
218
-
219
-
[Top][toc]
220
-
221
-
### Trip Attributes
222
-
223
-
Examples of mode-specific `trip_attributes`:
224
-
225
-
| Field | Type | Required/Optional | Comments |
226
-
| ----- | -------- | ----------------- | ----- |
227
-
|`dispatch_time`|[Timestamp][ts]| Conditionally Required | Time the vehicle was dispatched to the customer (required if trip was dispatched) |
228
-
|`quoted_trip_start_time`|[Timestamp][ts]| Required | Time the trip was estimated or scheduled to start, that was provided to the passenger |
229
-
|`requested_trip_start_location`|[GPS](gps)| Conditionally Required | Location where the customer requested the trip to start (required if this is within jurisdictional boundaries) |
230
-
|`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) |
231
-
|`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]|
232
-
|`parking_verification_url`| String | Optional | A URL to a photo (or other evidence) of proper vehicle parking |
216
+
|`accessibility_options`| Enum[]| Optional |**[Mode](/modes#list-of-supported-modes) Specific**. [Accessibility options](/modes#accessibility-options) given as an array of enumerated values. 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']`. |
217
+
|`parking_verification_url`| URL | Optional | A URL to a photo (or other evidence) of proper vehicle parking |
218
+
|`standard_cost`| Integer | Optional | The cost, in the currency defined in `currency`, that it would cost to perform that trip in the standard operation of the System (see [Costs & Currencies][costs-and-currencies]) |
219
+
|`actual_cost`| Integer | Optional | The actual cost, in the currency defined in `currency`, paid by the customer of the *mobility as a service* provider (see [Costs & Currencies][costs-and-currencies]) |
220
+
|`currency`| String | Optional, USD cents is implied if null.| An [ISO 4217 Alphabetic Currency Code][iso4217] representing the currency of the payee (see [Costs & Currencies][costs-and-currencies]) |
Copy file name to clipboardExpand all lines: modes/passenger-services.md
+12-6Lines changed: 12 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ See the [modes overview](/modes) for how the mode specific information below app
8
8
9
9
## Taxi vs. TNC implementation differences
10
10
11
-
Taxis typically require explicit tracking of maintenance while TNCs typically do not. Public agency regulations, legal authority, differ based on local, state, and federal laws and jursidictions between taxis, TNCs, CTAs, PHV, etc.
11
+
Taxis typically require explicit tracking of maintenance while TNCs typically do not. Public agency regulations, legal authority, differ based on local, state, and federal laws and jurisdictions between taxis, TNCs, CTAs, PHV, etc.
12
12
13
13
## Table of Contents
14
14
@@ -94,14 +94,18 @@ The `trip_attributes` array **may** have the following key value pairs:
-`app_name` (text, optional): name of the app used to reserve the trip which could be provider's app or 3rd party app
96
96
-`passenger_count` (integer, required): unique count of passengers transported during trip duration
97
-
-`request_time` (timestamp, required): when the passenger requested the trip
97
+
-`requested_time` (timestamp, required): when the passenger requested the trip
98
+
-`requested_trip_start_location` ([GPS](gps), Conditionally Required): Location where the customer requested the trip to start (required if this is within jurisdictional boundaries)
99
+
-`quoted_trip_start_time` ([Timestamp][ts], Required): Time the trip was estimated or scheduled to start, that was provided to the passenger
100
+
-`dispatch_time` ([Timestamp][ts], Conditionally Required): Time the vehicle was dispatched to the customer (required if trip was dispatched)
98
101
-`trip_wait_time` (milliseconds, optional): part of the passenger trip where the vehicle was moving slow or stopped (e.g. <12mph), which is a different fare rate in some jurisdictions
99
102
-`trip_fare_time` (milliseconds, optional): part of the passenger trip where the vehicle was moving more quickly (e.g. >12mph), which is a different fare rate in some jurisdictions
100
103
-`pickup_address` (text, optional): street address where the trip originated from
101
104
-`dropoff_address` (text, optional): street address where the trip ended
102
-
-`permit_licence_number` (string, optional) - The permit licence number of the organization that dispatched the vehicle
105
+
-`permit_license_number` (string, optional) - The permit license number of the organization that dispatched the vehicle
103
106
-`driver_id` (string, optional): Universal identifier of a specific driver, static across operators, like a driver's license number. Could also be used as a lookup in an agency's internal driver system.
104
107
-`wheelchair_transported` (boolean, optional) - was a wheelchair transported as part of this trip?
108
+
-`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)
105
109
106
110
_See more available trip attributes for any mode in the [trips endpoint](/provider#trips)._
107
111
@@ -113,7 +117,7 @@ The `fare_attributes` array **may** have the following key value pairs:
-`fare_type` (enumerated, required): `meter_fare`, `upfront_pricing`, `flat_rate`. Indicator of which rate was charged.
116
-
-`meter_fare_amount` (currency, conditionally required): if `upfront_pricing` is used as a `fare_type` include what the metered fare would have been if `meter_fare` would have been used. Allows cost comparison in evalutation of programs and pilots.
120
+
-`meter_fare_amount` (currency, conditionally required): if `upfront_pricing` is used as a `fare_type` include what the metered fare would have been if `meter_fare` would have been used. Allows cost comparison in evaluation of programs and pilots.
117
121
-`tolls` (currency, optional) - Sum of any and all tolls charged for the trip, such as bridge tolls
118
122
-`base_rate` (currency, optional) - Minimum fare to be charged as soon as the trip starts.
119
123
-`exit_fee` (currency, optional) - Fee to exit location, like an airport
@@ -142,7 +146,7 @@ The `vehicle_attributes` array **may** have the following key value pairs:
142
146
-`color` (string, optional)
143
147
-`vin` (string, optional) - the Vehicle Identification Number of the vehicle
144
148
-`placard_number` (string, optional) - the registered placard number of the vehicle
145
-
-`license_plate` (string, optional) - the registered vehicle license/number/registartion plate identifer on the vehicle
149
+
-`license_plate` (string, optional) - the registered vehicle license/number/registration plate identifier on the vehicle
146
150
-`inspection_date` (date YYYY-MM-DD, optional) - the date of the last inspection of the vehicle
147
151
148
152
_See more available vehicle attributes for any mode in the [vehicles endpoint](/provider#vehicles)._
@@ -232,7 +236,7 @@ This is the list of `vehicle_state` and `event_type` pairings that constitute th
232
236
|`non_operational`|`non_contactable`| N/A |`comms_lost`| The vehicle has went out of comms while not operating commercially |
233
237
|`on_trip`|`elsewhere`| N/A |`leave_jurisdiction`| The vehicle has left jurisdictional boundaries while on a trip |
234
238
|`on_trip`|`stopped`|`stopped`|`trip_stop`| The vehicle has stopped while on a trip |
235
-
|`on_trip`|`unon_contactable`| N/A |`comms_lost`| The vehicle has gone out of comms while on a trip |
239
+
|`on_trip`|`non_contactable`| N/A |`comms_lost`| The vehicle has gone out of comms while on a trip |
236
240
|`removed`|`non_operational`| N/A |`maintenance_end`| The vehicle has left the depot |
237
241
|`removed`|`non_operational`| N/A |`recommissioned`| The vehicle has been re-added to the Provider's fleet after being previously `decommissioned`|
238
242
|`removed`|`non_contactable`| N/A |`comms_lost`| The vehicle has gone out of comms while removed |
@@ -297,8 +301,10 @@ if t.any(state == ‘reserved’):
0 commit comments