-
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 city in station_information #704
base: master
Are you sure you want to change the base?
Conversation
Thank you @hbruch for raising this issue and opening a PR 🙏 It seems like a good idea to be able to indicate the A vote will be opened 7 days after the PR was created as per the governance. |
I hereby call a vote on this proposal. Voting will be open for 10 full calendar days until 11:59PM UTC on Thursday, November 28, 2024. |
+1 from Transit. |
+1 from Where To? / FutureTap. |
+1 from Raumobil. |
+1 from Entur |
+1 from VOI |
I missed the 2 day announcement last week, so here it is. 💁 Voting on this PR closes in 2 calendar days. |
This vote has now closed, and it passes! Votes in favor:
There were no votes against. This change will be part of the next MINOR release, planned in May 2025, as per the version release cycle in the governance. Thank you for your involvement in the GBFS spec 🙏 |
What problem does your proposal solve?
Currently, gbfs supports declaring
street
/cross_street
/post_code
of a rental station instation_information
, but notcity
(see this slack discussion).What is the proposal?
Add OPTIONAL field
city
tostation_information
.Is this a breaking change?
Which files are affected by this change?
station_information
Other options considered
The concept of regions could be used to provide information on the city/political jurisdiction a station is located in, but that might conflict with usage for other zoning schemes, like neighborhoods or economic zones, as stated in the spec. In addition, I'm only aware of a few providers which use regions.