You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
vehicle_type_id: The vehicle_type_id of each vehicle type at the station as described in vehicle_types.json. This field is REQUIRED if the vehicle_types.json is defined.
Possible interpretation: all vehicle types described in vehicle_types.json must be listed, including those with count=0.
This is an issue because producers with many different vehicle_types, wish they would not need to specify every single vehicle type not available at every station, but rather take a not listed vehicle_type_id as count=0 (which is already the current intention of the specs).
Please describe some potential solutions you have considered (even if they aren’t related to GBFS).
vehicle_type_id: The vehicle_type_id of each vehicle type at the station as described in vehicle_types.json. A vehicle type not available at the station can be omitted from the list or specified with a count=0.
What is the issue and why is it an issue?
In this Slack thread, @hbruch and @testower, pointed out that the description for
vehicle_type_id
in station_status.json is misleading.Possible interpretation: all vehicle types described in vehicle_types.json must be listed, including those with count=0.
This is an issue because producers with many different
vehicle_types
, wish they would not need to specify every single vehicle type not available at every station, but rather take a not listedvehicle_type_id
as count=0 (which is already the current intention of the specs).Please describe some potential solutions you have considered (even if they aren’t related to GBFS).
Update the
vehicle_type_id
description in station_status.json:Note that the JSON-Schema and gbfs-validator have been updated (PR MobilityData/gbfs-json-schema#94 and PR MobilityData/gbfs-validator#124) to reflect this change.
Is your potential solution a breaking change?
This change is editorial (it does not modify the behaviour of the specs). So a vote is not required.
The text was updated successfully, but these errors were encountered: