Waste Container Model

Description

A model of waste container which captures the static properties of a class of containers.

Data Model

The data model is defined as shown below:

  • id : Unique identifier.

  • type: Entity Type. It must be equal to WasteContainerModel.

  • source : A sequence of characters giving the source of the entity data.

    • Attribute type: Text or URL
    • Optional
  • dataProvider : Specifies the URL to information about the provider of this information

    • Attribute type: URL
    • Optional
  • name. Name given to this container model. It is a "well-known", mnemotechnic or codename. This attribute is different than modelName which conveys the formal model name given by the manufacturer.

  • width. Width of the container.

  • height. Height of the container.

  • depth. Depth of the container.

  • weight. Weight of the container.

  • cargoVolume. Total volume the container can hold.

  • maximumLoad. Maximum load the container can hold safely.

    • Attribute type: Number.
    • Default Unit: Kilograms
    • Optional
  • recommendedLoad. Manufacturer recommended load for the container.

    • Attribute type: Number.
    • Default Unit: Kilograms
    • Optional
  • category. Container’s category.

  • insertHolesNumber. Number of insert holes the container has.

    • Attribute type: Number.
    • Optional
  • madeOf. Material the container is made of.

    • Attribute type: Text
    • Allowed values: one Of (plastic, wood , metal, other)
    • Optional
  • madeOfCode. Material Code as per standard tables. TBD.

    • Attribute type: Text
    • Optional
  • brandName. Name of the brand.

  • modelName. Name of the model as given by the manufacturer. This attribute is different than name which is just a codename usually given by municipalities.

  • manufacturerName. Name of the manufacturer.

  • description. Description about the waste container model.

  • colors. Available colors.

  • image. A URL containing a photo of the container model.

  • compliantWith. A list of standards to which the container is compliant with (ex. UNE-EN 840-2:2013)

    • AttributeType: List of Text.
    • Optional
  • features. A list of container features.

    • Attribute type: List of Text
    • Allowed Values:
      • wheels
      • lid
      • roundedLid
      • insertHoles
      • lockable
      • Any other value meaningful for the application.

Note: JSON Schemas only capture the NGSI simplified representation, this means that to test the JSON schema examples with a FIWARE NGSI version 2 API implementation, you need to use the keyValues mode (options=keyValues).

Examples

Normalized Example

Normalized NGSI response

{
    "id": "wastecontainermodel:c1",
    "type": "WasteContainerModel",
    "category": {
        "value": ["dumpster"]
    },
    "cargoVolume": {
        "value": 150
    },
    "modelName": {
        "value": "C1"
    },
    "name": {
        "value": "Dumpster_Brute_2009_Plastic_Green"
    },
    "compliantWith": {
        "value": ["UNE-EN 840-2:2013"]
    },
    "madeOf": {
        "value": "plastic"
    },
    "height": {
        "value": 0.8
    },
    "width": {
        "value": 0.5
    },
    "depth": {
        "value": 0.4
    },
    "brandName": {
        "value": "Brute"
    },
    "features": {
        "value": ["wheels", "lid"]
    }
}

key-value pairs Example

Sample uses simplified representation for data consumers ?options=keyValues

{
    "id": "wastecontainermodel:c1",
    "type": "WasteContainerModel",
    "name": "Dumpster_Plastic_Brute_2009",
    "width": 0.5,
    "height": 0.8,
    "depth": 0.4,
    "cargoVolume": 150,
    "brandName": "Brute",
    "modelName": "C1",
    "compliantWith": ["UNE-EN 840-2:2013"],
    "madeOf": "plastic",
    "features": ["wheels", "lid"],
    "category": ["dumpster"]
}

Test it with a real service

Open issues