huishoudelijkafvalplanningvoertuigen

Planningsgegevens van afvalinzamelingsvoertuigen voor huishoudelijk- en bedrijfsafval

dialect2020-12

typeobject

health13%

dependencies2

Schema gebruiken

JSON Schema

schema.json Download bundled

SourceMeta

SourceMeta name: huishoudelijkafvalplanningvoertuigen
Base dialect: https://json-schema.org/draft/2020-12/schema
SourceMeta dialect: https://json-schema.org/draft/2020-12/schema
Bytes: 6.927 bytes
Bytes bundled: 9.775 bytes
Health: 13%
Dependencies: 2

Dependencies

To: huishoudelijkafvalplanningvoertuigenlink
At: /properties/_links/properties/self/$ref

To: referentiekalenderdatumlink
At: /properties/_links/properties/werkzaamhedenDatumRef/$ref

Health issues

Name: top_level_title
Message: Set a concise non-empty title at the top level of the schema to explain what the definition is about
Pointers

Name: top_level_examples
Message: Set a non-empty examples array at the top level of the schema to illustrate the expected data
Pointers

Name: description_trailing_period
Message: Descriptions should not end with a period to give user interfaces flexibility in presenting the text
Pointers: /properties/_links/description

Name: title_trim
Message: Titles should not contain leading or trailing whitespace
Pointers: /properties/_links/title

Name: non_applicable_type_specific_keywords
Message: Avoid keywords that don't apply to the type or types that the current subschema expects
Pointers: /properties/aantalMedewerkers/format

Name: description_trailing_period
Message: Descriptions should not end with a period to give user interfaces flexibility in presenting the text
Pointers: /properties/aantalMedewerkers/description

Name: unknown_format_prefix
Message: For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification
Pointers: /properties/aantalMedewerkers/format

Name: non_applicable_type_specific_keywords
Message: Avoid keywords that don't apply to the type or types that the current subschema expects
Pointers: /properties/aantalMedewerkersInhuur/format

Name: description_trailing_period
Message: Descriptions should not end with a period to give user interfaces flexibility in presenting the text
Pointers: /properties/aantalMedewerkersInhuur/description

Name: unknown_format_prefix
Message: For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification
Pointers: /properties/aantalMedewerkersInhuur/format

Name: non_applicable_type_specific_keywords
Message: Avoid keywords that don't apply to the type or types that the current subschema expects
Pointers: /properties/aantalMedewerkersIntern/format

Name: description_trailing_period
Message: Descriptions should not end with a period to give user interfaces flexibility in presenting the text
Pointers: /properties/aantalMedewerkersIntern/description

Name: unknown_format_prefix
Message: For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification
Pointers: /properties/aantalMedewerkersIntern/format

Name: description_trailing_period
Message: Descriptions should not end with a period to give user interfaces flexibility in presenting the text
Pointers: /properties/activiteit/description

Name: description_trailing_period
Message: Descriptions should not end with a period to give user interfaces flexibility in presenting the text
Pointers: /properties/categorie/description

Name: description_trailing_period
Message: Descriptions should not end with a period to give user interfaces flexibility in presenting the text
Pointers: /properties/datumAanwezigBron/description

Name: description_trailing_period
Message: Descriptions should not end with a period to give user interfaces flexibility in presenting the text
Pointers: /properties/datumVerwerktStadsdelen/description

Name: description_trailing_period
Message: Descriptions should not end with a period to give user interfaces flexibility in presenting the text
Pointers: /properties/fase/description

Name: non_applicable_type_specific_keywords
Message: Avoid keywords that don't apply to the type or types that the current subschema expects
Pointers: /properties/id/format

Name: description_trailing_period
Message: Descriptions should not end with a period to give user interfaces flexibility in presenting the text
Pointers: /properties/id/description

Name: unknown_format_prefix
Message: For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification
Pointers: /properties/id/format

Name: description_trailing_period
Message: Descriptions should not end with a period to give user interfaces flexibility in presenting the text
Pointers: /properties/kenteken/description

Name: description_trailing_period
Message: Descriptions should not end with a period to give user interfaces flexibility in presenting the text
Pointers: /properties/kentekenKort/description

Name: description_trailing_period
Message: Descriptions should not end with a period to give user interfaces flexibility in presenting the text
Pointers: /properties/memo/description

Name: description_trailing_period
Message: Descriptions should not end with a period to give user interfaces flexibility in presenting the text
Pointers: /properties/pauzeEindtijd/description

Name: description_trailing_period
Message: Descriptions should not end with a period to give user interfaces flexibility in presenting the text
Pointers: /properties/pauzeStarttijd/description

Name: non_applicable_type_specific_keywords
Message: Avoid keywords that don't apply to the type or types that the current subschema expects
Pointers: /properties/pauzeUrenGepland/format

Name: description_trailing_period
Message: Descriptions should not end with a period to give user interfaces flexibility in presenting the text
Pointers: /properties/pauzeUrenGepland/description

Name: unknown_format_prefix
Message: For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification
Pointers: /properties/pauzeUrenGepland/format

Name: description_trailing_period
Message: Descriptions should not end with a period to give user interfaces flexibility in presenting the text
Pointers: /properties/soortWerkzaamheden/description

Name: description_trailing_period
Message: Descriptions should not end with a period to give user interfaces flexibility in presenting the text
Pointers: /properties/team/description

Name: non_applicable_type_specific_keywords
Message: Avoid keywords that don't apply to the type or types that the current subschema expects
Pointers: /properties/urenInzetMedewerkerInhuur/format

Name: description_trailing_period
Message: Descriptions should not end with a period to give user interfaces flexibility in presenting the text
Pointers: /properties/urenInzetMedewerkerInhuur/description

Name: unknown_format_prefix
Message: For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification
Pointers: /properties/urenInzetMedewerkerInhuur/format

Name: non_applicable_type_specific_keywords
Message: Avoid keywords that don't apply to the type or types that the current subschema expects
Pointers: /properties/urenInzetMedewerkerIntern/format

Name: description_trailing_period
Message: Descriptions should not end with a period to give user interfaces flexibility in presenting the text
Pointers: /properties/urenInzetMedewerkerIntern/description

Name: unknown_format_prefix
Message: For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification
Pointers: /properties/urenInzetMedewerkerIntern/format

Name: non_applicable_type_specific_keywords
Message: Avoid keywords that don't apply to the type or types that the current subschema expects
Pointers: /properties/urenInzetVoertuig/format

Name: description_trailing_period
Message: Descriptions should not end with a period to give user interfaces flexibility in presenting the text
Pointers: /properties/urenInzetVoertuig/description

Name: unknown_format_prefix
Message: For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification
Pointers: /properties/urenInzetVoertuig/format

Name: description_trailing_period
Message: Descriptions should not end with a period to give user interfaces flexibility in presenting the text
Pointers: /properties/voertuigInhuurIndicatie/description

Name: description_trailing_period
Message: Descriptions should not end with a period to give user interfaces flexibility in presenting the text
Pointers: /properties/werkzaamhedenCode/description

Name: description_trailing_period
Message: Descriptions should not end with a period to give user interfaces flexibility in presenting the text
Pointers: /properties/werkzaamhedenDatum/description

Name: non_applicable_type_specific_keywords
Message: Avoid keywords that don't apply to the type or types that the current subschema expects
Pointers: /properties/werkzaamhedenDatumRefId/format

Name: description_trailing_period
Message: Descriptions should not end with a period to give user interfaces flexibility in presenting the text
Pointers: /properties/werkzaamhedenDatumRefId/description

Name: unknown_format_prefix
Message: For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification
Pointers: /properties/werkzaamhedenDatumRefId/format

Name: description_trailing_period
Message: Descriptions should not end with a period to give user interfaces flexibility in presenting the text
Pointers: /properties/werkzaamhedenEindtijd/description

Name: description_trailing_period
Message: Descriptions should not end with a period to give user interfaces flexibility in presenting the text
Pointers: /properties/werkzaamhedenOmschrijving/description

Name: non_applicable_type_specific_keywords
Message: Avoid keywords that don't apply to the type or types that the current subschema expects
Pointers: /properties/werkzaamhedenUrenGepland/format

Name: description_trailing_period
Message: Descriptions should not end with a period to give user interfaces flexibility in presenting the text
Pointers: /properties/werkzaamhedenUrenGepland/description

Name: unknown_format_prefix
Message: For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification
Pointers: /properties/werkzaamhedenUrenGepland/format

JSON Schema

{
  "$id": "https://schemas.don.projects.digilab.network/schemas/api-register/gemeente-amsterdam/afvalcontainers-putten-en-weeggegevens--mrgfx6ng/huishoudelijkafvalplanningvoertuigen",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "description": "Planningsgegevens van afvalinzamelingsvoertuigen voor huishoudelijk- en bedrijfsafval",
  "properties": {
    "_links": {
      "description": "The contents of the `planningVoertuigen._links` field. It contains all relationships with objects.",
      "properties": {
        "schema": {
          "description": "The schema field is exposed with every record",
          "format": "uri",
          "readOnly": true,
          "type": "string"
        },
        "self": {
          "$ref": "./huishoudelijkafvalplanningvoertuigenlink"
        },
        "werkzaamhedenDatumRef": {
          "$ref": "../_shared/referentiekalenderdatumlink"
        }
      },
      "required": [
        "schema",
        "self",
        "werkzaamhedenDatumRef"
      ],
      "title": " links",
      "type": "object"
    },
    "aantalMedewerkers": {
      "description": "Aantal medewerkers dat op het voertuig is gepland.",
      "format": "double",
      "type": [
        "number",
        "null"
      ]
    },
    "aantalMedewerkersInhuur": {
      "description": "Aantal externe medewerkers dat op het voertuig is gepland.",
      "format": "double",
      "type": [
        "number",
        "null"
      ]
    },
    "aantalMedewerkersIntern": {
      "description": "Aantal interne medewerkers dat op het voertuig is gepland.",
      "format": "double",
      "type": [
        "number",
        "null"
      ]
    },
    "activiteit": {
      "description": "Fractie van de afvalverwerking (afgeleid van categorie, werkzaamheden en of memo).",
      "title": "Afval fractiesoort code",
      "type": [
        "string",
        "null"
      ]
    },
    "categorie": {
      "description": "Categorie afvalverwerking waar het voertuig op is gepland.",
      "title": "Afvalverwerking categorie code",
      "type": [
        "string",
        "null"
      ]
    },
    "datumAanwezigBron": {
      "description": "Indicatie over de actualiteit van de gegevens in deze set (laatste wijziging in de bron).",
      "format": "date-time",
      "type": [
        "string",
        "null"
      ]
    },
    "datumVerwerktStadsdelen": {
      "description": "Moment van laden data vanuit het (planningsdata)bronsysteem in het DWH stadsdelen (als intermediair voor datalevering).",
      "format": "date-time",
      "title": "Datum laden datawarehouse",
      "type": [
        "string",
        "null"
      ]
    },
    "fase": {
      "description": "Label van de fase waarin de planning zich bevindt.",
      "title": "Plannings fase omschrijving",
      "type": [
        "string",
        "null"
      ]
    },
    "id": {
      "description": "Uniek identificerend kenmerk van het record.",
      "format": "int64",
      "maximum": 9223372036854776000,
      "minimum": -9223372036854776000,
      "title": "Planningvoertuig ID",
      "type": "integer"
    },
    "kenteken": {
      "description": "Kenteken afvalinzamelingsvoertuig.",
      "type": [
        "string",
        "null"
      ]
    },
    "kentekenKort": {
      "description": "Kenteken afvalinzamelingsvoertuig zonder koppeltekens (-).",
      "type": [
        "string",
        "null"
      ]
    },
    "memo": {
      "description": "Extra toelichting zoals opgegeven in (planningsdata)bronsysteem.",
      "title": "Opmerking",
      "type": [
        "string",
        "null"
      ]
    },
    "pauzeEindtijd": {
      "description": "Eindtijd van de pauze op de WERKZAAMHEDEN_DATUM.",
      "type": [
        "string",
        "null"
      ]
    },
    "pauzeStarttijd": {
      "description": "Starttijd van de pauze op de WERKZAAMHEDEN_DATUM.",
      "type": [
        "string",
        "null"
      ]
    },
    "pauzeUrenGepland": {
      "description": "Berekening van het aantal bruto uren van de pauze (= eindtijd - starttijd).",
      "format": "double",
      "title": "Aantal pauze uren gepland",
      "type": [
        "number",
        "null"
      ]
    },
    "soortWerkzaamheden": {
      "description": "Specificatie van soort planning (Inzet of Onderhoud).",
      "title": "Werkzaamheden soort omschrijving",
      "type": [
        "string",
        "null"
      ]
    },
    "team": {
      "description": "Team waarvoor de voertuigplanning is gemaakt. In veel gevallen een stadsdeel, maar kan ook bijvoorbeeld Bedrijfsafval Centrum (BAC) zijn).",
      "title": "Team omschrijving",
      "type": [
        "string",
        "null"
      ]
    },
    "urenInzetMedewerkerInhuur": {
      "description": "Som van het totaal aantal netto uren van de externe medewerkers die op de planning zijn gezet (excl pauze).",
      "format": "double",
      "title": "Aantal uren inzet medewerker inhuur",
      "type": [
        "number",
        "null"
      ]
    },
    "urenInzetMedewerkerIntern": {
      "description": "Som van het totaal aantal netto uren van de interne medewerkers die op de planning zijn gezet (excl pauze).",
      "format": "double",
      "title": "Aantal uren inzet medewerker intern",
      "type": [
        "number",
        "null"
      ]
    },
    "urenInzetVoertuig": {
      "description": "Netto inzeturen van het voertuig (bruto - pauze).",
      "format": "double",
      "title": "Aantal uren inzet voertuig",
      "type": [
        "number",
        "null"
      ]
    },
    "voertuigInhuurIndicatie": {
      "description": "Is het voertuig ingehuurd (Ja / Nee).",
      "type": [
        "string",
        "null"
      ]
    },
    "werkzaamhedenCode": {
      "description": "Code voor de werkzaamheden waarop het voertuig is gepland.",
      "type": [
        "string",
        "null"
      ]
    },
    "werkzaamhedenDatum": {
      "description": "Datum waarop de werkzaamheden zijn gepland.",
      "format": "date-time",
      "title": "Geplande datum",
      "type": [
        "string",
        "null"
      ]
    },
    "werkzaamhedenDatumRefId": {
      "deprecated": true,
      "description": "Verwijzing naar datum dimensie.",
      "format": "int64",
      "maximum": 9223372036854776000,
      "minimum": -9223372036854776000,
      "readOnly": true,
      "title": "Datum referentie",
      "type": [
        "integer",
        "null"
      ]
    },
    "werkzaamhedenEindtijd": {
      "description": "Eindtijd van de werkzaamheden op de WERKZAAMHEDEN_DATUM.",
      "type": [
        "string",
        "null"
      ]
    },
    "werkzaamhedenOmschrijving": {
      "description": "Omschrijving voor de werkzaamheden waarop het voertuig is gepland.",
      "type": [
        "string",
        "null"
      ]
    },
    "werkzaamhedenStarttijd": {
      "description": "Starttijd van de werkzaamheden op de WERKZAAMHEDEN_DATUM",
      "type": [
        "string",
        "null"
      ]
    },
    "werkzaamhedenUrenGepland": {
      "description": "Berekening van het aantal bruto uren van de werkzaamheden (= eindtijd - starttijd).",
      "format": "double",
      "title": "Aantal werkzaamheden uren gepland",
      "type": [
        "number",
        "null"
      ]
    }
  },
  "required": [
    "_links",
    "id",
    "werkzaamhedenDatumRefId"
  ],
  "type": "object",
  "x-derived-from": [
    "https://api.data.amsterdam.nl/v1/huishoudelijkafval/openapi.json#/components/schemas/Huishoudelijkafvalplanning_voertuigen"
  ]
}

Metadata

Aangemaakt op: 21-7-2026
Laatst gecrawld op: 6-8-2026
ID: RvwBMnEvR

Schema-register: huishoudelijkafvalplanningvoertuigen

Details van JSON Schema: huishoudelijkafvalplanningvoertuigen

Details van JSON Schema: huishoudelijkafvalplanningvoertuigen

Beschrijving