Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Modify /status_changes to represent docked event locations #438

Closed
thekaveman opened this issue Jan 31, 2020 · 2 comments · Fixed by #427
Closed

Modify /status_changes to represent docked event locations #438

thekaveman opened this issue Jan 31, 2020 · 2 comments · Fixed by #427
Labels
enhancement New feature or request Provider Specific to the Provider API
Milestone
1.0.0

Comments

@thekaveman
Copy link
Collaborator

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

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

Describe the solution you'd like

The current /status_changes endpoint (and by extension, the /events endpoint which inherits the data schema) was envisioned with dockless micromobility in mind - specifically, events have a geographic (lat/lng) location. In the world of docked bikeshare/micromobility, we would rather represent an event as occurring at a particular dock/stop.

Is this a breaking change

  • Yes, breaking

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

Impacted Spec

  • provider

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.
@thekaveman thekaveman added enhancement New feature or request Provider Specific to the Provider API labels Jan 31, 2020
@thekaveman thekaveman added this to the Future milestone Jan 31, 2020
cmdoptesc added a commit to remix/mobility-data-specification that referenced this issue Feb 4, 2020
@cmdoptesc
Introduce station_id and add fields to trips and status changes
e4838c9 
Addresses MDS Issues openmobilityfoundation#428 and openmobilityfoundation#438
cmdoptesc added a commit to remix/mobility-data-specification that referenced this issue Feb 4, 2020
@cmdoptesc
Introduce station_id and add fields to trips and status changes
755a6e5 
Addresses MDS Issues openmobilityfoundation#428 and openmobilityfoundation#438
@cmdoptesc cmdoptesc mentioned this issue Feb 5, 2020
Closed
@thekaveman thekaveman modified the milestones: Future, 1.0.0 Apr 9, 2020
@schnuerle schnuerle mentioned this issue Jun 11, 2020
Merged
@schnuerle
Copy link
Member

Confirming that #427 will resolve this issue @thekaveman.

@schnuerle schnuerle linked a pull request Jun 26, 2020 that will close this issue
Add MDS Stops RT Specification (Agency & Provider) #427
Merged
@schnuerle
Copy link
Member

We've got this resolved with #427.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request Provider Specific to the Provider API
Projects
None yet
Milestone
1.0.0
Development

Successfully merging a pull request may close this issue.

Add MDS Stops RT Specification (Agency & Provider) avatarneil/mobility-data-specification
2 participants
@schnuerle @thekaveman