-
Notifications
You must be signed in to change notification settings - Fork 293
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
Add field to designate stations that support vehicle charging #340
Conversation
Adds field to designate stations that offer vehicle charging
Hello, How does this proposal interact with #329 ? We're wondering how to model whether an electric bike can be returned to any station, or we should suggest returning it only to charging stations. |
@kanagy Good question. I'm not aware of any cases where only returning electric bikes to a charging station is a requirement. This may change in the future as charging capable stations become more common. If that's the case we could add another enum like |
@mplsmitch a small addition to your comment: there would be also the rebalancer's side that would decide its following actions based on that info for example. |
I hereby call a vote on this proposal. Voting will be open for 10 full calendar days until 11:59PM UTC on September 1st, 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. |
CC: @gerazenobi @l4b4r4b4b4 are you still interested in supporting this? |
Nextbike supports this proposal and we would add this field to our feeds in the future. |
yes @mplsmitch 👍 |
Hi @gerazenobi ! For your vote to count, we need to know which organization you're working with 😄 |
Oups, my bad @heidiguenin : the organisation is Qucit. |
Dott supports this change, however at the current moment this is a field that would not apply to our free floating model. |
At IBI Group we probably won't use this information since there don't seem to be dropoff restrictions or incentives associated with this particular addition, therefore we are neutral on this topic. As an aside, I wonder how this would interact with the potential changes in #350 that would expand the number of propulsion type definitions in the vehicle_types.json file. In doing so, this raises the question of whether this field is appropriate for just e-bikes and e-scooters or if it also applies to vehicles with any propulsion type. If it does apply to propulsion types other than electric vehicles, then "is_charging_station" is probably a confusing name. If it does apply only to those vehicle types, then the field's description should note this information. |
BCycle supports this change. We do not currently have stations that support vehicle charging so we will not add the field immediately, but we would add the field in the future. |
Spin supports this change. We likely will not immediately implement this. |
Superpedestrian supports this change. We don't plan to implement this, as our system does not use stations. |
This vote has now closed, and it passes! Votes in favour: There were no votes against. Regarding @evansiroky's comment: this field will likely only represent charging stations for electric vehicles, when we merge this into a v2.3-RC we will make sure to that is clear. |
Adds field to designate stations that offer vehicle charging
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.
The specification lacks a way to designate stations that offer electric vehicle charing. Discussion of this issue can be found in #280 and #326. Publishers are already doing this in a variety of ways using non-standard fields.
What is the proposal?
This proposal adds a single Boolean field:
is_charging_station
, tostation_information.json
Is this a breaking change?
Which files are affected by this change?
gbfs.md: