Currently a Curb Zone only accounts for availability_time but not if the zone is actually available for a vehicle to use. Curb Space does account for these but is an optional endpoint while the Curb Zone endpoint is required.
Is this a breaking change
No, not breaking
Impacted Spec
For which spec is this feature being requested?
Curbs
Solution
I would like to propose two new fields available and available_spaces to work hand in hand with the current availability_time field.
Name
Type
Required/Optional
Description
available
Boolean
Required
If true, the curb zone is open for normal use. If false, the curb zone is closed and vehicles should look for alternative zones. (Could use WZDx reference as one example)
available_spaces
Integer
Optional
The number of curb spaces that are open for use within the zone.
Description
Currently a Curb Zone only accounts for
availability_timebut not if the zone is actually available for a vehicle to use. Curb Space does account for these but is an optional endpoint while the Curb Zone endpoint is required.Is this a breaking change
Impacted Spec
For which spec is this feature being requested?
CurbsSolution
I would like to propose two new fields
availableandavailable_spacesto work hand in hand with the currentavailability_timefield.availableBooleantrue, the curb zone is open for normal use. Iffalse, the curb zone is closed and vehicles should look for alternative zones. (Could use WZDx reference as one example)available_spaces