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
684 stars 231 forks source link

Modify /trips to represent docked start/end locations #428

Closed thekaveman closed 4 years ago

thekaveman commented 4 years ago

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

This Issue follows from the Provider WG discussion on 2020/01/16 and the existing Issue #374 and related PR #427 related to bringing docked bikeshare support to MDS Provider.

Describe the solution you'd like

The current /trips endpoint was envisioned with dockless micromobility in mind - specifically, trips have a geographic (lat/lng) start and end location. In the world of docked bikeshare/micromobility, we would rather represent the trip as starting/ending at a particular dock/stop.

Is this a breaking change

Likely breaking as we would be changing the /trips definition.

Impacted Spec

Describe alternatives you've considered

We want MDS to represent docked bikeshare true to the spirit of MDS - granular data useful in regulatory and planning contexts. While possible, simply encoding GBFS data into MDS endpoints/data types wouldn't represent a true evolution of the MDS spec.

jfh01 commented 4 years ago

Since start / end are represented via the Route, could we use define a GeoJSON "foreign member" to include a stop_id and/or name in the Feature for the start/end point of the Route.

schnuerle commented 4 years ago

I believe #442 will resolve this issue, adding the stop_id as an optional parameter.

schnuerle commented 4 years ago

This is sussed with #442. Thanks @avatarneil and @thekaveman.