wegenbestandzonezwaarverkeerbuiten

buiten

Dialect2020-12

Typeobject

Eigenschappen

Eigenschappen van het JSON Schema
Eigenschap	Type	Verplicht	Beschrijving en details
_links	`object`	Ja	The contents of the `buiten._links` field. It contains all relationships with objects.
_links.schema	`string`	Ja	The schema field is exposed with every record Format: uri
_links.self	`$ref`	Ja	- $ref: ./wegenbestandzonezwaarverkeerbuitenlink
beleidskaderAuto	`string, null`	Nee	beleidsfunctie van weg conform Beleidskader Verkeersnetten Gemeente Amsterdam, 24 januari 2018.
beleidskaderFiets	`string, null`	Nee	beleidsfunctie van weg conform Beleidskader Verkeersnetten Gemeente Amsterdam, 24 januari 2018.
beleidskaderOv	`string, null`	Nee	beleidsfunctie van weg conform Beleidskader Verkeersnetten Gemeente Amsterdam, 24 januari 2018.
geometry	`object`	Nee	GeoJSON geometry allOf: 2 schema's
geometry.allOf[1].coordinates	`array`	Nee	Based on the geometry type, a point or collection of points. Min items: 2 Items type: number
geometry.allOf[1].type	`string`	Ja	the geometry type Enum: Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon
geometry.allOf[2].coordinates	`array`	Nee	- Items type: array
geometry.allOf[2].type	`string`	Nee	- Enum: MultiLineString
gevaarlijkeStoffenRoute	`boolean, null`	Nee	indicator voor een route voor transport van routeplichtige gevaarlijke stoffen.
id	`integer`	Ja	unieke identificatie van het record. Format: int64 Minimum: -9223372036854776000 Maximum: 9223372036854776000
indicatieZoneAmsterdam	`boolean, null`	Nee	indicator of link valt binnen of grotendeels binnen de gemeente Amsterdam.
indicatieZoneMilieu	`boolean, null`	Nee	indicator Verkeersbesluit milieuzone Amsterdam (Staatscourant 2020, 32736).
indicatieZoneZwaarVerkeer	`string, null`	Nee	indicator Verkeersbesluit Zone Zwaar Verkeer Amsterdam (Staatscourant 2021, 24726).
laadLosRegime	`string, null`	Nee	het type laden-en-lossen regime.
laadLosVenstertijden	`string, null`	Nee	toegestane tijdsperioden voor laden-en-lossen.
laadLosVerbodStilTeStaanTijden	`string, null`	Nee	dagen en tijden voor verbod laden-en-lossen en stilstaan.
lengte	`number, null`	Nee	lengte van de link in meters. Format: double
linknummer	`integer, null`	Nee	unieke identificatie voor elke opgedeelde wegennetwerk object. Format: int64 Minimum: -9223372036854776000 Maximum: 9223372036854776000
percLijnInPolygoonWeg	`number, null`	Nee	welke % van 'lijn lengte' binnen BGT polygonen liggen met een van de volgende functies: ('rijbaan regionale weg','rijbaan autoweg','OV-baan','rijbaan autosnelweg','woonerf','rijbaan lokale weg'). Format: double
rijrichting	`integer, null`	Nee	toegestane auto rijrichtingen van de weg. Format: int64 Minimum: -9223372036854776000 Maximum: 9223372036854776000
source	`integer, null`	Nee	nummer van source node van edge. Format: int64 Minimum: -9223372036854776000 Maximum: 9223372036854776000
straatnaam	`string, null`	Nee	straatnaam die van toepassing is op wegennetwerk object.
target	`integer, null`	Nee	nummer van target node van edge. Format: int64 Minimum: -9223372036854776000 Maximum: 9223372036854776000
tijdskostenBeginEind	`number, null`	Nee	tijdskosten om van begin naar eind van link te gaan in seconden. Format: double
tijdskostenEindBegin	`number, null`	Nee	tijdskosten om van eind naar begin van link te gaan in seconden. Format: double
tunnelCategorie	`string, null`	Nee	een Europese categorisering voor tunnels met betrekking op het vervoer van gevaarlijke stoffen.
tunnelNaam	`string, null`	Nee	naam van de tunnel.
wegFunctie	`integer, null`	Nee	functional road class; geeft de functie van weg. Format: int64 Minimum: -9223372036854776000 Maximum: 9223372036854776000
wegbeheerder	`string, null`	Nee	wegbeheerder die hoort bij de weg.
wettelijkeSnelheid	`integer, null`	Nee	wettelijke Snelheid die toegestaan is op weg. Bij verschillende waarde voor de 2 rijrichtingen gaat het om maximum. Format: int64 Minimum: -9223372036854776000 Maximum: 9223372036854776000

JSON Schema

{
  "$id": "https://schemas.don.projects.digilab.network/schemas/api-register/gemeente-amsterdam/wegenbestand-gemeente-amsterdam-sxzpfuehr/wegenbestandzonezwaarverkeerbuiten",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "description": "buiten",
  "properties": {
    "_links": {
      "description": "The contents of the `buiten._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": "./wegenbestandzonezwaarverkeerbuitenlink"
        }
      },
      "required": [
        "schema",
        "self"
      ],
      "title": " links",
      "type": "object"
    },
    "beleidskaderAuto": {
      "description": "beleidsfunctie van weg conform Beleidskader Verkeersnetten Gemeente Amsterdam, 24 januari 2018.",
      "type": [
        "string",
        "null"
      ]
    },
    "beleidskaderFiets": {
      "description": "beleidsfunctie van weg conform Beleidskader Verkeersnetten Gemeente Amsterdam, 24 januari 2018.",
      "type": [
        "string",
        "null"
      ]
    },
    "beleidskaderOv": {
      "description": "beleidsfunctie van weg conform Beleidskader Verkeersnetten Gemeente Amsterdam, 24 januari 2018.",
      "type": [
        "string",
        "null"
      ]
    },
    "geometry": {
      "allOf": [
        {
          "description": "GeoJSON geometry",
          "discriminator": {
            "propertyName": "type"
          },
          "properties": {
            "coordinates": {
              "description": "Based on the geometry type, a point or collection of points.",
              "items": {
                "type": "number"
              },
              "minItems": 2,
              "type": "array"
            },
            "type": {
              "description": "the geometry type",
              "enum": [
                "Point",
                "LineString",
                "Polygon",
                "MultiPoint",
                "MultiLineString",
                "MultiPolygon"
              ],
              "type": "string"
            }
          },
          "required": [
            "type"
          ],
          "type": "object"
        },
        {
          "properties": {
            "coordinates": {
              "items": {
                "items": {
                  "description": "Point in 3D space",
                  "items": {
                    "type": "number"
                  },
                  "maxItems": 3,
                  "minItems": 2,
                  "type": "array"
                },
                "type": "array"
              },
              "type": "array"
            },
            "type": {
              "enum": [
                "MultiLineString"
              ],
              "type": "string"
            }
          }
        }
      ],
      "description": "GeoJSON geometry",
      "type": "object"
    },
    "gevaarlijkeStoffenRoute": {
      "description": "indicator voor een route voor transport van routeplichtige gevaarlijke stoffen.",
      "type": [
        "boolean",
        "null"
      ]
    },
    "id": {
      "description": "unieke identificatie van het record.",
      "format": "int64",
      "maximum": 9223372036854776000,
      "minimum": -9223372036854776000,
      "type": "integer"
    },
    "indicatieZoneAmsterdam": {
      "description": "indicator of link valt binnen of grotendeels binnen de gemeente Amsterdam.",
      "type": [
        "boolean",
        "null"
      ]
    },
    "indicatieZoneMilieu": {
      "description": "indicator Verkeersbesluit milieuzone Amsterdam (Staatscourant 2020, 32736).",
      "type": [
        "boolean",
        "null"
      ]
    },
    "indicatieZoneZwaarVerkeer": {
      "description": "indicator Verkeersbesluit Zone Zwaar Verkeer Amsterdam (Staatscourant 2021, 24726).",
      "type": [
        "string",
        "null"
      ]
    },
    "laadLosRegime": {
      "description": "het type laden-en-lossen regime.",
      "type": [
        "string",
        "null"
      ]
    },
    "laadLosVenstertijden": {
      "description": "toegestane tijdsperioden voor laden-en-lossen.",
      "type": [
        "string",
        "null"
      ]
    },
    "laadLosVerbodStilTeStaanTijden": {
      "description": "dagen en tijden voor verbod laden-en-lossen en stilstaan.",
      "type": [
        "string",
        "null"
      ]
    },
    "lengte": {
      "description": "lengte van de link in meters.",
      "format": "double",
      "type": [
        "number",
        "null"
      ]
    },
    "linknummer": {
      "description": "unieke identificatie voor elke opgedeelde wegennetwerk object.",
      "format": "int64",
      "maximum": 9223372036854776000,
      "minimum": -9223372036854776000,
      "type": [
        "integer",
        "null"
      ]
    },
    "percLijnInPolygoonWeg": {
      "description": "welke % van 'lijn lengte' binnen BGT polygonen liggen met een van de volgende functies: ('rijbaan regionale weg','rijbaan autoweg','OV-baan','rijbaan autosnelweg','woonerf','rijbaan lokale weg').",
      "format": "double",
      "type": [
        "number",
        "null"
      ]
    },
    "rijrichting": {
      "description": "toegestane auto rijrichtingen van de weg.",
      "format": "int64",
      "maximum": 9223372036854776000,
      "minimum": -9223372036854776000,
      "type": [
        "integer",
        "null"
      ]
    },
    "source": {
      "description": "nummer van source node van edge.",
      "format": "int64",
      "maximum": 9223372036854776000,
      "minimum": -9223372036854776000,
      "type": [
        "integer",
        "null"
      ]
    },
    "straatnaam": {
      "description": "straatnaam die van toepassing is op wegennetwerk object.",
      "type": [
        "string",
        "null"
      ]
    },
    "target": {
      "description": "nummer van target node van edge.",
      "format": "int64",
      "maximum": 9223372036854776000,
      "minimum": -9223372036854776000,
      "type": [
        "integer",
        "null"
      ]
    },
    "tijdskostenBeginEind": {
      "description": "tijdskosten om van begin naar eind van link te gaan in seconden.",
      "format": "double",
      "type": [
        "number",
        "null"
      ]
    },
    "tijdskostenEindBegin": {
      "description": "tijdskosten om van eind naar begin van link te gaan in seconden.",
      "format": "double",
      "type": [
        "number",
        "null"
      ]
    },
    "tunnelCategorie": {
      "description": "een Europese categorisering voor tunnels met betrekking op het vervoer van gevaarlijke stoffen.",
      "type": [
        "string",
        "null"
      ]
    },
    "tunnelNaam": {
      "description": "naam van de tunnel.",
      "type": [
        "string",
        "null"
      ]
    },
    "wegFunctie": {
      "description": "functional road class; geeft de functie van weg.",
      "format": "int64",
      "maximum": 9223372036854776000,
      "minimum": -9223372036854776000,
      "type": [
        "integer",
        "null"
      ]
    },
    "wegbeheerder": {
      "description": "wegbeheerder die hoort bij de weg.",
      "type": [
        "string",
        "null"
      ]
    },
    "wettelijkeSnelheid": {
      "description": "wettelijke Snelheid die toegestaan is op weg. Bij verschillende waarde voor de 2 rijrichtingen gaat het om maximum.",
      "format": "int64",
      "maximum": 9223372036854776000,
      "minimum": -9223372036854776000,
      "type": [
        "integer",
        "null"
      ]
    }
  },
  "required": [
    "_links",
    "id"
  ],
  "type": "object",
  "x-derived-from": [
    "https://api.data.amsterdam.nl/v1/wegenbestand/zone_zwaar_verkeer/openapi.json#/components/schemas/WegenbestandZoneZwaarVerkeerbuiten"
  ]
}

Schema gebruiken

JSON Schema

Bundled JSON Schema

Open in JSON Schema Viewer

Dependencies

Gebruikt door dit schema
Schema	Locatie
wegenbestandzonezwaarverkeerbuitenlink	`/properties/_links/properties/self/$ref`

Dit schema wordt gebruikt door
Schema	Locatie
embedded3	`/properties/buiten/items/$ref`

Health issues

Health issues
Message	Pointer
Set a concise non-empty title at the top level of the schema to explain what the definition is about
Set a non-empty examples array at the top level of the schema to illustrate the expected data
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/_links/description`
Titles should not contain leading or trailing whitespace	`/properties/_links/title`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/beleidskaderAuto/description`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/beleidskaderFiets/description`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/beleidskaderOv/description`
Keywords inside `allOf` that do not conflict with the parent schema can be elevated	`/properties/geometry/allOf/0/type – /properties/geometry/allOf/0/required – /properties/geometry/allOf/0/discriminator – /properties/geometry/allOf/0/description`
Future versions of JSON Schema will refuse to evaluate unknown keywords or custom keywords from optional vocabularies that don't have an x- prefix	`/properties/geometry/allOf/0/discriminator`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/geometry/allOf/0/properties/coordinates/description`
Setting `type` alongside `enum` is considered an anti-pattern, as the enumeration choices already imply their respective types	`/properties/geometry/allOf/0/properties/type/enum – /properties/geometry/allOf/0/properties/type/type`
Setting `type` alongside `enum` is considered an anti-pattern, as the enumeration choices already imply their respective types	`/properties/geometry/allOf/1/properties/type/enum – /properties/geometry/allOf/1/properties/type/type`
An `enum` of a single value can be expressed as `const`	`/properties/geometry/allOf/1/properties/type/enum`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/gevaarlijkeStoffenRoute/description`
Avoid keywords that don't apply to the type or types that the current subschema expects	`/properties/id/format`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/id/description`
For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification	`/properties/id/format`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/indicatieZoneAmsterdam/description`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/indicatieZoneMilieu/description`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/indicatieZoneZwaarVerkeer/description`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/laadLosRegime/description`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/laadLosVenstertijden/description`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/laadLosVerbodStilTeStaanTijden/description`
Avoid keywords that don't apply to the type or types that the current subschema expects	`/properties/lengte/format`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/lengte/description`
For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification	`/properties/lengte/format`
Avoid keywords that don't apply to the type or types that the current subschema expects	`/properties/linknummer/format`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/linknummer/description`
For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification	`/properties/linknummer/format`
Avoid keywords that don't apply to the type or types that the current subschema expects	`/properties/percLijnInPolygoonWeg/format`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/percLijnInPolygoonWeg/description`
For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification	`/properties/percLijnInPolygoonWeg/format`
Avoid keywords that don't apply to the type or types that the current subschema expects	`/properties/rijrichting/format`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/rijrichting/description`
For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification	`/properties/rijrichting/format`
Avoid keywords that don't apply to the type or types that the current subschema expects	`/properties/source/format`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/source/description`
For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification	`/properties/source/format`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/straatnaam/description`
Avoid keywords that don't apply to the type or types that the current subschema expects	`/properties/target/format`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/target/description`
For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification	`/properties/target/format`
Avoid keywords that don't apply to the type or types that the current subschema expects	`/properties/tijdskostenBeginEind/format`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/tijdskostenBeginEind/description`
For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification	`/properties/tijdskostenBeginEind/format`
Avoid keywords that don't apply to the type or types that the current subschema expects	`/properties/tijdskostenEindBegin/format`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/tijdskostenEindBegin/description`
For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification	`/properties/tijdskostenEindBegin/format`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/tunnelCategorie/description`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/tunnelNaam/description`
Avoid keywords that don't apply to the type or types that the current subschema expects	`/properties/wegFunctie/format`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/wegFunctie/description`
For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification	`/properties/wegFunctie/format`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/wegbeheerder/description`
Avoid keywords that don't apply to the type or types that the current subschema expects	`/properties/wettelijkeSnelheid/format`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/wettelijkeSnelheid/description`
For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification	`/properties/wettelijkeSnelheid/format`

Schema-register: wegenbestandzonezwaarverkeerbuiten

Details van JSON Schema: wegenbestandzonezwaarverkeerbuiten

Details van JSON Schema: wegenbestandzonezwaarverkeerbuiten

Beschrijving