Minimum age requirement

[mplsmitch]

**What problem does your proposal solve?

I'm doing this PR on behalf of @marius-at-atb in in Trondheim, Norway. Additional discussion can be found in #771 . They have a need for a field to contain a minimum age requirement in order to use a vehicle. There are potentially a number of user requirements that could be included in the vehicle_types file, such as a drivers license, helmets etc but until we have real-world use cases my preference is to limit this to a single field that contains minimum age. In the future if there are additional needs beyond age we could develop a list of enums.

If anyone has additional needs in this area I'd like to hear from you so we can include them before this goes to a vote.

What is the proposal?

This PR adds a single field min_age to vehicle_types.json. The field is OPTIONAL and defined as a non-negative integer that describes the minimum age required to use the vehicle.

This is a non-breaking change that would be included in the next minor version release scheduled for November.

Is this a breaking change?

• Yes
• No
• Unsure

Which files are affected by this change?

vehicle_types.json

[fredericsimard]

LGTM!

[mplsmitch]

I hereby call a vote on this proposal. Voting will be open for 10 full calendar days until 11:59PM UTC on November 12.

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.

[testower]

Entur votes in favor and will implement it.

[futuretap]

FutureTap / Where To? votes in favor, too. We won’t implement it anytime soon, though.

[mplsmitch]

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.

[marius-at-atb]

AtB votes in favor as well, and will implement it 👍

[hbruch]

NVBW votes in favor and will implement it.

[cmonagle]

+1 from Transit. No plans to implement at the moment.

[mplsmitch]

This vote has now closed, and it passes!

Votes in favor:

Entur (producer)
Where To? / FutureTap (consumer)
AtB (consumer)
NVBW (consumer)
Transit (consumer)

There were no votes against.

This change will be part of the next MINOR Release, which is currently planned spring of 2026, as per the version release cycle in the governance.

Thank you all for your involvement in the GBFS spec 🙏

[fredericsimard]

@richfab should this be closed?

[richfab]

You're right, it should remain open until it's merged as part of the next MINOR release. Thanks!

[fredericsimard]

LGTM!