search

openmobilityfoundation / mobility-data-specification

A data standard to enable right-of-way regulation and two-way communication between mobility companies and local governments.
https://www.openmobilityfoundation.org/about-mds/
Other
676 stars 232 forks source link

Add a "Data Provider UUID" to MDS #805

Closed schnuerle closed 1 year ago

schnuerle commented 1 year ago

Is your feature request related to a problem? Please describe.

Per discussions around Modes in general and passenger services scenarios in particular, it is essential for some cities like SFMTA to get an ID around who is running the MDS feed, eg, who is the data provider. Traditionally this has been the operator of the service, but in micromobility recently and in other new modes there is also a hardware/software data solution provider filling the data needs for companies.

This new field will be part of MDS in most endpoints for agencies to consume where provider_id exists now. Here are the commit where this has been added as part of the #801 work:

It is suggested to add this as part of the Modes work, but I wanted to create this issue to make sure the concept and discussions are captured accurately.

Describe the solution you'd like

A clear and concise description of what you want to happen.

Is this a breaking change

Impacted Spec

For which spec is this feature being requested?

Describe alternatives you've considered

We could put this only in trips, or only in a certain mode, but I think this is important enough to put in the MDS base setup so it's available in all relevant endpoints for all modes.

Additional context

We created a similar field when building CDS 1.0, where it's important to know both the operator (who is using the curb) and the data provider (who is sending the data, which could be the operator or a company running a sensor).

pierre-bouffort commented 1 year ago

This looks good to me. A fairly simple change to implement really.

schnuerle commented 1 year ago

Added along with work in #801