NicolasFrasie
commented
3 years ago Hi everybody,
At Communauto, we suggest an alternative : keep free_bike_status and vehicle_types as light as possible and describe precisely the wide range of vehicles and accessories into a new file whose name could be vehicle_description.
As a result, you would obtain :
-
vehicle_types.json - new optional data only:
rider capacity trunk size vehicle description vehicle image -
vehicle_description.json - optional data only: caracterization of the vehicle (brand, model, propulsion_energy_type, etc.) accessories present in the vehicule (such as child seats) ` { "vehicle_description": { "vehicle_desc_id": "Family1", "propulsion_energy_type": "hybrid", "eco_stickers": [ { "country": "FR", "eco_sticker": "critair_1" }, { "country": "DE", "eco_sticker": "euro_2" }, { "country": "BE", "eco_sticker": "euro_1" } ] "vehicle_desc": “The favorite car of our customers !”, "vehicle_accessories": [ "air_conditioning", "automatic ", "cruise_control", "doors_4" "child_seat_4" ], "g_CO2_km": 75, "share_type": "round_trip", "Vehicle_model": [ "Toyota", "Yaris", ],
} } `
-
station_information.json: BREAKING: share type allowed by station : free floating, one-way or round-trip Other optional types specific to car stations (type of station...)
-
free_bike_status.json: BREAKING: the file would be renamed to free_vehicle_status.json new optional data only: a datetime specifying how much time the vehicule is available (for round trip carsharing)
I look forward to hearing from the community about these 2 options.
Thanks @Miryad3108 and French NAP team for all the fantastic job to get there.
Nicolas Frasie
teebot
thbar
josee-sabourin
Introduction
Transport.data.gouv is the French national access point for mobility data.
We are opening this issue on our behalf and on behalf of a working group involving the “Association des Acteurs de l’Autopartage” (AAA), a French National Association for carsharing grouping 20+ operators, and Iodines.
Why are we opening this issue?
Following European Directive EU 2010/40/UE, French carsharing operators will be requested to open and publish their data.
We have noticed strong similarities between car sharing and bike sharing. We are considering the opportunity to evolve the GBFS standard in order to support both use cases and to leverage GBFS proven efficiency and popularity.
The goal of this issue is to discuss this idea with the community, before we go forward with a PR.
Proposal overview
We would like to propose an evolution of the GBFS which allows to model car-sharing data by extending the following files.
The detailed proposal to discuss is currently in this Google Document.
vehicle_types - new optional data only:
station_information.json:
free_bike_status.json:
Is your potential solution a breaking change?
Yes.
It seems that currently in the GBFS the share type is implicitly defined by the type of station : in case of a physical station, the share type is one-way. In case of a virtual station, it is free floating.
As the round trip share type is commonly used by car-sharing companies, the share type would become explicitly defined among one-way, free-floating and round-trip.
Note on potential variant of the proposal
Following the discussions related to the creation of a car-sharing compatible version of the GBFS specification, an alternative solution emerged. The information added is the same, but an additional optional file is added to the specification, allowing the creation of generic vehicles types, refined by a notion of vehicle sub-types. We’ll let Nicolas Frasie, of Communauto, explain this alternative in more detail.
What do you think?
We also created this issue in order to have feedback from the community about this file architecture choice. Thanks in advance for your comments.