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
**Note:** See the [Adding an MDS Agency ID](https://github.com/openmobilityfoundation/mobility-data-specification/wiki/Adding-an-MDS-Agency-ID) page for more help.
11
+
12
+
Opening this issue will allow you as a city or governmental agency get an official agency ID for use across MDS globally, and include in your Requirements URL.
13
+
14
+
**Fields needed from you for the [agencies.csv file](https://github.com/openmobilityfoundation/mobility-data-specification/blob/main/agencies.csv).**
15
+
16
+
_All fields are required._
17
+
18
+
1.**agency_country_iso_code** - Two letter ISO country code where your agency is located.
19
+
- ...
20
+
1.**agency_state** - Geographic abbreviation or name of the state where your agency is located.
21
+
- ...
22
+
1.**agency_city** - Geographic name of the city where your agency is located.
23
+
- ...
24
+
1.**agency_name** - Full name of your governmental city/agency.
25
+
- ...
26
+
1.**agency_id** - A random UUID version 4. There are lots of way to generate a unique UUID, like using this website.
27
+
- ...
28
+
1.**department_url** - URL to the home page of your agency's department.
29
+
- ...
30
+
1.**requirement_url** - Full https:// URL where your current Policy Requirements endpoint is located.
31
+
- ...
32
+
33
+
Additionally, please provide your name and role within your agency to help with verification.
**Note:** See the [Adding an MDS Provider ID](https://github.com/openmobilityfoundation/mobility-data-specification/wiki/Adding-an-MDS-Provider-ID) page for more help.
11
+
12
+
Opening this issue will allow you as a mobility service provider get an official provider ID for use across MDS globally.
13
+
14
+
**Fields needed from you for the [providers.csv file](https://github.com/openmobilityfoundation/mobility-data-specification/blob/main/providers.csv).**
15
+
16
+
_All fields are required._
17
+
18
+
1.**provider_name** - Short name of your company.
19
+
- ...
20
+
1.**provider_id** - A random UUID version 4. There are lots of way to generate a unique UUID, like using this [website](https://www.uuidgenerator.net/version4).
21
+
- ...
22
+
1.**url** - URL to the home page of your company.
23
+
- ...
24
+
1.**mds_api_url** - Full https:// URL where your root MDS feeds are located.
25
+
- ...
26
+
1.**gbfs_api_url** - Full https:// URL where your public GBFS feeds are located.
27
+
- ...
28
+
29
+
Additionally, please provide your name and role within your agency to help with verification.
The 1.2.0 minor release adds digital program Requirements, new options for policies, better GPS telemetry data, and moves Provider Vehicles out of beta.
8
+
9
+
### CHANGES
10
+
11
+
See the closed PRs tagged with [Milestone 1.2.0](https://github.com/openmobilityfoundation/mobility-data-specification/pulls?q=is%3Apr+is%3Aclosed+milestone%3A1.2.0) and [Issues](https://github.com/openmobilityfoundation/mobility-data-specification/issues?q=is%3Aissue+milestone%3A1.2.0+is%3Aclosed) for a full list of changes.
12
+
13
+
**_General MDS_**
14
+
15
+
-[Richer telemetry data](https://github.com/openmobilityfoundation/mobility-data-specification/issues/589), including [616](https://github.com/openmobilityfoundation/mobility-data-specification/issues/616), [73](https://github.com/openmobilityfoundation/mobility-data-specification/pull/73), [51](https://github.com/openmobilityfoundation/mobility-data-specification/pull/51)
-[Program Requirements](https://github.com/openmobilityfoundation/mobility-data-specification/issues/646) - For agencies to describe program requirements digitally to allow providers and the public to see what MDS and GBFS versions, APIs, endpoints, and fields are required, and communicate available MDS agency information to providers.
21
+
-[Ability to express data sharing requirements in Policy](https://github.com/openmobilityfoundation/mobility-data-specification/issues/608)
22
+
-[Method to Exclude some Provider Fields from Response](https://github.com/openmobilityfoundation/mobility-data-specification/issues/507)
23
+
-[Retrieve operational zones from operators](https://github.com/openmobilityfoundation/mobility-data-specification/issues/639)
24
+
-[Make Trip 'route' field optional for privacy](https://github.com/openmobilityfoundation/mobility-data-specification/issues/504)
25
+
26
+
-[Multiple options added to Policy](https://github.com/openmobilityfoundation/mobility-data-specification/pull/658)
27
+
-[Add rate options to other rules types](https://github.com/openmobilityfoundation/mobility-data-specification/issues/633)
28
+
-[Support parking fees by duration](https://github.com/openmobilityfoundation/mobility-data-specification/issues/631)
29
+
-[Min and max clarity on Rules](https://github.com/openmobilityfoundation/mobility-data-specification/issues/689)
30
+
-[Add a "rate applies when" field to Rules](https://github.com/openmobilityfoundation/mobility-data-specification/issues/666)
31
+
32
+
**_Provider_**
33
+
34
+
-[Vehicles out of beta](https://github.com/openmobilityfoundation/mobility-data-specification/issues/637)
35
+
-[Clarify use cases between MDS Vehicles and GBFS](https://github.com/openmobilityfoundation/mobility-data-specification/issues/641)
36
+
37
+
_Minor Updates_
38
+
39
+
-[Clarify single object response on policy/geography](https://github.com/openmobilityfoundation/mobility-data-specification/issues/599)
40
+
-[Schema updates](https://github.com/openmobilityfoundation/mobility-data-specification/issues/693), including [645](https://github.com/openmobilityfoundation/mobility-data-specification/issues/645), [687](https://github.com/openmobilityfoundation/mobility-data-specification/issues/687), [683](https://github.com/openmobilityfoundation/mobility-data-specification/issues/683)
41
+
- Add VeoRide, Boaz Bikes, and update Superpedestrian provider IDs
|`vehicle_state`| Enum | Required | see [Vehicle States][vehicle-states]|
186
186
|`event_types`| Enum[]| Required | see [Vehicle Events][vehicle-events]|
187
-
|`timestamp`|[timestamp][ts]| Required | Date of last event update |
187
+
|`timestamp`|[timestamp][ts]| Required | Date of last event update |
188
188
|`telemetry`|[Telemetry](#telemetry-data)| Required | Single point of telemetry. |
189
-
|`event_geographies`| UUID[]| Optional |**[Beta feature](/general-information.md#beta-features):***Yes (as of 1.1.0)*. Array of Geography UUIDs consisting of every Geography that contains the location of the event. See [Geography Driven Events][geography-driven-events]. Required if `telemetry` is not present. |
189
+
|`event_geographies`| UUID[]| Optional |**[Beta feature](/general-information.md#beta-features):***Yes (as of 1.1.0)*. Array of Geography UUIDs consisting of every Geography that contains the location of the event. See [Geography Driven Events][geography-driven-events]. Required if `telemetry` is not present. |
190
190
|`trip_id`| UUID | Optional | UUID provided by Operator to uniquely identify the trip. Required if `event_types` contains `trip_start`, `trip_end`, `trip_cancel`, `trip_enter_jurisdiction`, or `trip_leave_jurisdiction`|
0 commit comments