Minor additions to vehicle attributes // Car sharing

[bergenklem]

Had a look through the vehicle attribute list for car sharing, and would like to make proposals for minor additions to vehicle attributes - many relating to common days needs when booking a car in a nordic (winter) country:

• Wheel drive (string, required) - Type of wheel drive of the vehicle (4WD, AWD, front wheel drive, back wheel drive).

(_Could also be considered a boolean-value, with yes/no 4WD (which is usually what we/customers would be interested in).

• Children's seat (Boolean, optional) - the vehicle is equipped with a children's seat.
• Pets allowed (Boolean, optional) - it's allowed to bring pets into the vehicle
• Rooftop cargo box (Boolean, optional) - The vehicle is equipped with a rooftop cargo box
• Roof rails (Boolean, optional) - The vehicle is equipped with roof rails
• Ski hatch (Boolean, optional) - The vehicle has a ski hatch in the rear seat row
• Winter tyres (Boolean, optional) - The vehicle is equipped with winter tyres

Even though the use cases for these would mostly be customer-related (and hence more interesting for GBFS), we as a municipality could use such information to check the versatility of the car fleet of the providers (and all the providers already have this sort of information in their own system). So - if it's not a hassle... :)

[marie-x]

Thanks for the suggestions! The steering committee will see about adding to either 2.0.x or 2.1.

[schnuerle]

These would be great additions to vehicle_attributes as defined fields.

We may also want to add a note that agencies may be allowed to add their own custom ones for local circumstances, and bring those learnings back to the MDS working group for future inclusion.

[fractalf]

@schnuerle @marie-x
May I suggest the following improvements for 2.1.0

• Make a new property assessories (alternatively: equipment or simular) of type enum[]
• Move some existing boolean properties to this new property
• Most of these new additions also fit into this property

Example structure:

Corrections

1. The image has a small error. accessories should be an array, so type would be like this 'enum[]'
2. air_conditioning is also a boolean so it should also be moved to accessories

[schnuerle]

I like your restructuring @fractalf , but I think that may be a breaking change for a 3.0 release.

We are starting work on 2.1 now, so if this could be added as new optional fields as @bergenklem suggests, we may do that first.