-
Use
use -
A use class or type of use
Required: True
Datatype: enum
Expected number: 1
-
Use other
use-other -
Specify use if use is "other"
Required: False
Datatype: string
Expected number: 1
-
Operational times
operational-times -
Structured data for operational hours by day
Required: False
Datatype: object
Expected number: 1 or more
-
Day type
day-type -
Day or type of day
Required: True
Datatype: enum
Expected number: 1
-
Closed
closed -
True or False - explicitly state when closed
Required: False
Datatype: boolean
Expected number: 1
-
Time ranges
time-ranges -
Opening and closing times for the day
Required: False
Datatype: object
Expected number: 1 or more
-
Open time
open-time -
Opening time
Required: True
Datatype: string
Expected number: 1
-
Close time
close-time -
Closing time
Required: True
Datatype: string
Expected number: 1
-
-
-
Hours not known
hours-not-known -
Applicant states they do not know the hours of operation
Required: False
Datatype: boolean
Expected number: 1
module: hrs-operation
Hours of operation
Proposed operating hours if the proposed development is intended for non-residential use.
Fields
-
Hours of operation
hours-of-operation -
List the hours of operation by non-residential use
Required: True
Datatype: object
Expected number: 1 or more
-
Additional information
additional-information -
Any additional information (such as hours of use of other machinery within the site-generators, pumps, etc)
Required: False
Datatype: string
Expected number: 1
Rules
- At least one hours-of-operation entry must be provided
- Either operational-times or hours-not-known must be provided within each hours-of-operation entry
- use-other is required when use is 'other'
- time-ranges is required when not closed
- open-time and close-time must be in HH:MM format
- close-time must be after open-time within same time range