Open bergenklem opened 1 year ago
Great use cases!
A note to followup on this from a GBFS perspective. It looks like they did not end up implementing this field. Maybe for the same reasons we didn't (it may be hard to define types clearly):
https://github.com/MobilityData/gbfs/blob/master/gbfs.md#vehicle_typesjson
There is a form_factor
field, which has 'car' but not much else from the list.
They do have a free-form name
field which can be anything. They examples on the page include "Example Cargo Bike", "Four-door Sedan", "Example Basic Bike", "Example E-scooter V2".
Also like MDS there are make and model (but no year) fields.
Hi!
Referring to previous discussion in issue #640 regarding adopting possibility to distinguish between car types. We would very much like to see this as a feature of MDS (extra field in vehicle_attributes?):
We can see several use cases for such a field:
1 Insight into how different types of cars are being used in carsharing services (in combination with duration, mileage and so forth).
2 Tenders and allocation of reserved spots - give possibility to award companies with wanted mix of car types in their fleet (in our case; we prefer companies with wide range of car types in their fleet when we assign reserved parking lots in neighbourhood areas - not just vans). This has also been used as an family friendliness-indicator in some cities in EU.
3 Control - some of our reserved parking lots have requirements on type of cars they can place there (e.g. in streets to narrow to allow parking for big/wide cars)
Haven't really made up my mind if there's a need for MDS to detail and name the category types (Input from car sharing providers should in that case be considered), or if it should be left out for local goverments/organizations to decide (by leaving it as an open field). Open for discussion!