After reviewing the specification, MobilityData has realized the differentiation between vehicle_capacity and vehicle_type_capacity is not extremely clear. This is due, in part, to both the geofencing.json and vehicle_types.json extensions occurring concurrently. As a result, both of these fields were not able to be viewed in tandem before being merged into the specification.

vehicle_capacity is defined as:

An object where each key is a vehicle_type_id as described in vehicle_types.json and the value is a number representing the total number of vehicles of this type that can park within the area defined in the station_area field. If the field station_area is defined and a particular vehicle type id is not defined in this object, then an unlimited virtual capacity is assumed for that vehicle type.

vehicle_type_capacity is defined as:

An object where each key is a vehicle_type_id as described in vehicle_types.json and the value is a number representing the total docking points installed at this station, both available and unavailable for the specified vehicle type.

Given that v2.1 is still in RC, we feel these fields should be clarified before an official release. What would be the best way to do that?

• Renaming vehicle_capacity? (ex: station_area_capacity, vehicle_type_area_capacity, vehicle_type_virtual_capacity, etc.)
• Renaming vehicle_type_capacity? (ex: vehicle_type_dock_capacity, or others)
• Editing the descriptions to make them more clear?
• All of the the above?
• Other solutions?

Please let us know what you think and if you're implementing these fields!