Open Karol-Kolenda opened 1 month ago
Thanks for raising this issue. We will investigate the attribute(s) that exist and report back.
On behalf of DfT:
Many thanks for raising this issue, Karol. The section of the data specification (the data model and hence the JSON schema) addressing conditions relating to permits is developmental and has not been subject to wide testing. The issue you have raised illustrates that some attributes may be placed in the wrong class (not allowing such conditions to be describe for permits that do not have an associated payment). We will certainly look to review this, and welcome inputs on which data configuration could meet the range of permit conditions that are practically found within existing TROs. We will look to adjust this in a future release.
In the meantime, using v3.2.4 of the data specification we suggest you use the existing attributes in the "PermitSubjectToFee" class. Note "amountDue" is optional.
Added to backlog.
I seem to be missing something, and would appreciate some guidance on how to encode the "no return" parameter of a parking regulation. Specifically, I have: Parking, Mon-Sat, 8am-7pm, 20 minutes, No return within 40 minutes. How can I represent this (duration and no return interval)?
I am aware of the
PermitSubjectToFee
propertiesmaximumAccessDuration
andminimumTimeToNextEntry
, but since they strictly relate to the paid permit (Subject To Fee), they don’t quite fit my needs here.