Skip to content

Add field to designate stations that support vehicle charging - #340

Merged
mplsmitch merged 2 commits into
masterfrom
station-services
Sep 2, 2021
Merged

mplsmitch merged 2 commits into
masterfrom
station-services

Conversation

@mplsmitch

Copy link
Copy Markdown
Contributor

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, to station_information.json

Is this a breaking change?

  • Yes
  • No
  • Unsure

Which files are affected by this change?

gbfs.md:

  • station_information.json

Adds field to designate stations that offer vehicle charging
@mplsmitch

Copy link
Copy Markdown
Contributor Author

CC:
@gerazenobi @l4b4r4b4b4 @thlaunois

@kanagy

kanagy commented Aug 2, 2021

Copy link
Copy Markdown

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.

@mplsmitch

Copy link
Copy Markdown
Contributor Author

@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 charging_station to the return_type array in #329. What I expect to see is that only certain locations will offer charging and operators will offer incentives to get users to return vehicles where they want them.

@gerazenobi

Copy link
Copy Markdown

@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.

@heidiguenin heidiguenin added proposal:nonbreaking v2.3 Candidate change for v2.3 (minor release) labels Aug 16, 2021
@heidiguenin heidiguenin mentioned this pull request Aug 19, 2021
1 of 3 tasks
@mplsmitch

Copy link
Copy Markdown
Contributor Author

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.

@mplsmitch

Copy link
Copy Markdown
Contributor Author

CC: @gerazenobi @l4b4r4b4b4 are you still interested in supporting this?

@kanagy kanagy mentioned this pull request Aug 23, 2021
1 of 3 tasks
@nbdh

nbdh commented Aug 26, 2021

Copy link
Copy Markdown
Contributor

Nextbike supports this proposal and we would add this field to our feeds in the future.

@nbdh nbdh mentioned this pull request Aug 26, 2021
1 of 3 tasks
@gerazenobi

Copy link
Copy Markdown

CC: @gerazenobi @l4b4r4b4b4 are you still interested in supporting this?

yes @mplsmitch 👍

@heidiguenin

Copy link
Copy Markdown
Contributor

Hi @gerazenobi ! For your vote to count, we need to know which organization you're working with 😄

@gerazenobi

Copy link
Copy Markdown

Hi @gerazenobi ! For your vote to count, we need to know which organisation you're working with 😄

Oups, my bad @heidiguenin : the organisation is Qucit.

@viestat

viestat commented Aug 27, 2021

Copy link
Copy Markdown
Contributor

Dott supports this change, however at the current moment this is a field that would not apply to our free floating model.

@evansiroky

Copy link
Copy Markdown
Contributor

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.

@cait32

cait32 commented Sep 1, 2021

Copy link
Copy Markdown

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.

@ncancelliere

Copy link
Copy Markdown

Spin supports this change. We likely will not immediately implement this.

@ezmckinn

ezmckinn commented Sep 1, 2021

Copy link
Copy Markdown
Contributor

Superpedestrian supports this change. We don't plan to implement this, as our system does not use stations.

@josee-sabourin

Copy link
Copy Markdown
Contributor

This vote has now closed, and it passes!

Votes in favour:
Nextbike (producer)
Qucit (consumer)
Dott (producer)
IBI Group (consumer)
BCycle (producer)
Spin (producer)
Superpedestrian (producer)

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.

@mplsmitch
mplsmitch merged commit 9be2d69 into master Sep 2, 2021
@richfab
richfab deleted the station-services branch July 2, 2025 09:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

gbfs.md proposal:nonbreaking v2.3 Candidate change for v2.3 (minor release) Vote Passed

Projects

None yet

Development

Successfully merging this pull request may close these issues.