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: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@
21
21
22
22
# About
23
23
24
-
The Mobility Data Specification (**MDS**), a project of the [Open Mobility Foundation](http://www.openmobilityfoundation.org) (**OMF**), is a set of Application Programming Interfaces (APIs) that helps cities better manage transportation in the public right of way, standardizing communication and data-sharing between cities and mobility providers, allowing cities to share and validate policy digitally, and enabling vehicle management and better outcomes for residents. Inspired in part by projects like [GTFS](https://developers.google.com/transit/gtfs/reference/) and [GBFS](https://github.com/MobilityData/gbfs), MDS is focused on managing mobility services such as dockless scooters, bicycles, mopeds, car share, delivery robots, and passenger services.
24
+
The Mobility Data Specification (**MDS**), a project of the [Open Mobility Foundation](http://www.openmobilityfoundation.org) (**OMF**), is a set of Application Programming Interfaces (APIs) that helps cities better manage transportation in the public right of way, standardizing communication and data-sharing between cities and mobility providers, allowing cities to share and validate policy digitally, and enabling vehicle management and better outcomes for residents. Inspired in part by projects like [GTFS](https://developers.google.com/transit/gtfs/reference/) and [GBFS](https://github.com/MobilityData/gbfs), MDS is focused on managing mobility services such as dockless scooters, bicycles, mopeds, car share, delivery robots, fixed route services and shuttles, fleets, and passenger services.
25
25
26
26
**MDS** is a key piece of digital infrastructure that supports the effective implementation of mobility policies in cities around the world. For a high level overview and visuals, see the [About MDS](https://www.openmobilityfoundation.org/about-mds/) page on the OMF website.
Copy file name to clipboardExpand all lines: data-types.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -113,7 +113,9 @@ Events represent changes in vehicle status.
113
113
|`battery_percent`| Integer | Required if Applicable | Percent battery charge of vehicle, expressed between 0 and 100 |
114
114
|`fuel_percent`| Integer | Required if Applicable | Percent fuel in vehicle, expressed between 0 and 100 |
115
115
|`trip_ids`| UUID[]| Required if Applicable | Trip UUIDs (foreign key to /trips endpoint), required if `event_types` contains `trip_start`, `trip_end`, `trip_cancel`, `trip_enter_jurisdiction`, or `trip_leave_jurisdiction`|
116
+
|`stop_id`| UUID | Required if Applicable | Stop that the vehicle is currently located at. See [Stops][stops]|
116
117
|`associated_ticket`| String | Optional | Identifier for an associated ticket inside an Agency-maintained 311 or CRM system |
118
+
|`gtfs_stop_id`| UUID | Optional | A unique stop ID to be recorded when a vehicle makes a stop event at a location. Matches [GTFS](https://gtfs.org/documentation/schedule/reference/)`stop_id`|
117
119
118
120
### Event Times
119
121
@@ -140,6 +142,7 @@ A standard point of vehicle telemetry. References to latitude and longitude impl
140
142
|`battery_percent`| Integer | Required if Applicable | Percent battery charge of vehicle, expressed between 0 and 100 |
141
143
|`fuel_percent`| Integer | Required if Applicable | Percent fuel in vehicle, expressed between 0 and 100 |
142
144
|`tipped_over`| Boolean | Required if Known | If detectable and known, is the device tipped over or not? Default is 'false'. |
145
+
|`gtfs_stop_id`| UUID | Optional | A unique stop ID to be recorded when a vehicle makes a stop event at a location. Matches [GTFS](https://gtfs.org/documentation/schedule/reference/)`stop_id`|
143
146
144
147
### GPS Data
145
148
@@ -237,6 +240,8 @@ A Trip is defined by the following structure:
237
240
|`standard_cost`| Integer | Optional | The cost, in the currency defined in `currency`, to perform that trip in the standard operation of the System (see [Costs & Currencies][costs-and-currencies]) |
238
241
|`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]) |
239
242
|`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]) |
243
+
|`gtfs_trip_id`| UUID | Required if Applicable | A unique trip ID for the associated scheduled GTFS route-trip. Matches [GTFS](https://gtfs.org/documentation/schedule/reference/)`trip_id` in the trips.txt and other files.|
244
+
|`gtfs_api_url`| String | Required if Applicable | Full URL to the location where the associated [GTFS](https://gtfs.org/documentation/schedule/reference/) dataset zip files are located. |
0 commit comments