-
Notifications
You must be signed in to change notification settings - Fork 290
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.
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
Semantic Changes: Bike becomes Vehicle #354
Conversation
Changes language in File Requirements from SHOULD to MUST
Changes use of bike to vehicle in field names and end points. free_bike_status becomes vehicle_status
Removes system_id from vehicle_status endpoint
Change definition of system_id from SHOULD to MUST for each geography
I hereby call a vote on this proposal. Voting will be open for 10 full calendar days until 11:59PM UTC on December 9, 2021. Please vote for or against the proposal, and include the organization for which you are voting in your comment. Please note if you can commit to implementing the proposal. |
+1 from Google Maps. Not implementing right now, but will have to support in future as we start to ingest v3. |
+1 from Ito World. |
+1 from CROW |
+1 from Transit |
Entur supports this proposal |
+1 from nextbike wondering when GBFS is renamed to GVFS 😢 |
Voting on this PR closes in 2 calendar days. Please vote for or against the proposal, and include the organization for which you are voting in your comment. Please note if you can commit to implementing the proposal. |
+1 from Spin. |
+1 from TIER |
This vote has now closed, and it passes! Votes in favor: We will tag and merge this into v3.0-RC2 in the coming weeks. |
What problem does your proposal solve? Please begin with the relevant issue number. If there is no existing issue, please also describe alternative solutions you have considered.
As the specification has evolved to cover multiple vehicles types beyond bicycles, the term "bike" has continued to be used to describe vehicles which may or may not be bikes. This has been a cause of confusion for both publishers and consumers alike.
What is the proposal?
This proposal is a long planned change to remove this ambiguity by replacing the term "bike" with "vehicle' throughout the specification. This requires renaming of an endpoint and several fields including:
free_bikes_status.json
endpoint becomesvehicle_status.json
free_bike_status.bikes[ ]
array becomesvehicle_status.vehicles [ ]
free_bike_status.bikes[ ].bike_id becomes
vehicle_id`station_status.stations[ ].num_bikes_available
becomesnum_vehicles_available
station_status.stations[ ].num_bikes_disabled
becomesnum_vehicles_disabled
Is this a breaking change?
Which files are affected by this change?
gbfs.md
README.md