Waste service
Requirements
The Service model should have properties for:
name
For identification.
frequency
An indication of typically how often the collection is run.
description
For specific instructions about the service, such as when and where to put containers out, that bin lids must be closed, etc.
next collections
To know upcoming dates of when upcoming collections will happen, when filtered by property. Also if any adjustments to the scheduled dates are made.
last collections
To know when the last few collections have taken place, when filtered by property.
container types
What types of containers (and in relation, materials) are collected by this service.
Types
This WasteService type:
- Is a derivation of the Service concept in the Smart City Concept Model.
- Extends from the GovernmentService schema.org type.
Properties
Term | Mapping | Definition |
---|---|---|
name | schema:name | Name of the service. |
description | schema:description | A short description of the service. |
frequency | Text | How often it runs, e.g. weekly. |
next collections | Task | List of dates of next collections. |
last collections | Task | List of dates of previous collections. |
feature types | Feature type | The container types that are collected. |
provider | schema:provider | The council providing the service. |
service area | schema:serviceArea | The geographic area where the service is provided. |
service operator | schema:serviceOperator | The operator of the service, if different to the provider. |
Serialisation
Codelists
Freqency
- weekly
- alternate weekly