risicozonesbedrijven | Schema-register

bedrijven

Dialect2020-12

Typeobject

Eigenschappen

Eigenschappen van het JSON Schema
Eigenschap	Type	Verplicht	Beschrijving en details
_links	`object`	Ja	The contents of the `bedrijven._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: ./risicozonesbedrijvenlink
aantalBronnen	`integer, null`	Nee	Aantal bronnen. Format: int64 Minimum: -9223372036854776000 Maximum: 9223372036854776000
adresBedrijf	`string, null`	Nee	Adres van bedrijf.
bevoegdgezag	`string, null`	Nee	Instantie (provincie of gemeente) die verantwoordelijk is voor risicobewaking.
categorieBevi	`string, null`	Nee	verwijzing naar Besluit externe veiligheid inrichtingen die van toepassing is.
geometrie	`object`	Nee	GeoJSON geometry allOf: 2 schema's
geometrie.allOf[1].coordinates	`array`	Nee	Based on the geometry type, a point or collection of points. Min items: 2 Items type: number
geometrie.allOf[1].type	`string`	Ja	the geometry type Enum: Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon
geometrie.allOf[2].coordinates	`array`	Nee	- Items type: array
geometrie.allOf[2].type	`string`	Nee	- Enum: MultiPolygon
geometriePunt	`object`	Nee	GeoJSON geometry allOf: 2 schema's
geometriePunt.allOf[1].coordinates	`array`	Nee	Based on the geometry type, a point or collection of points. Min items: 2 Items type: number
geometriePunt.allOf[1].type	`string`	Ja	the geometry type Enum: Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon
geometriePunt.allOf[2].coordinates	`array`	Nee	Point in 3D space Min items: 2 Max items: 3 Items type: number
geometriePunt.allOf[2].type	`string`	Nee	- Enum: Point
id	`integer`	Ja	Unieke identificatie record. Format: int64 Minimum: -9223372036854776000 Maximum: 9223372036854776000
naamBedrijf	`string, null`	Nee	Bedrijfsnaam.
opmerkingen	`string, null`	Nee	Opmerkingen
stadsdeel	`string, null`	Nee	Naam stadsdeel waar bedrijf onder valt.
typeBedrijf	`string, null`	Nee	Typering /aard van het bedrijf.

JSON Schema

{
  "$id": "https://schemas.don.projects.digilab.network/schemas/api-register/gemeente-amsterdam/risicozones-ruvsbueng/risicozonesbedrijven",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "description": "bedrijven",
  "properties": {
    "_links": {
      "description": "The contents of the `bedrijven._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": "./risicozonesbedrijvenlink"
        }
      },
      "required": [
        "schema",
        "self"
      ],
      "title": " links",
      "type": "object"
    },
    "aantalBronnen": {
      "description": "Aantal bronnen.",
      "format": "int64",
      "maximum": 9223372036854776000,
      "minimum": -9223372036854776000,
      "type": [
        "integer",
        "null"
      ]
    },
    "adresBedrijf": {
      "description": "Adres van bedrijf.",
      "type": [
        "string",
        "null"
      ]
    },
    "bevoegdgezag": {
      "description": "Instantie (provincie of gemeente) die verantwoordelijk is voor risicobewaking.",
      "type": [
        "string",
        "null"
      ]
    },
    "categorieBevi": {
      "description": "verwijzing naar Besluit externe veiligheid inrichtingen die van toepassing is.",
      "type": [
        "string",
        "null"
      ]
    },
    "geometrie": {
      "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": {
                  "items": {
                    "description": "Point in 3D space",
                    "items": {
                      "type": "number"
                    },
                    "maxItems": 3,
                    "minItems": 2,
                    "type": "array"
                  },
                  "type": "array"
                },
                "type": "array"
              },
              "type": "array"
            },
            "type": {
              "enum": [
                "MultiPolygon"
              ],
              "type": "string"
            }
          }
        }
      ],
      "description": "GeoJSON geometry",
      "type": "object"
    },
    "geometriePunt": {
      "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": {
              "description": "Point in 3D space",
              "items": {
                "type": "number"
              },
              "maxItems": 3,
              "minItems": 2,
              "type": "array"
            },
            "type": {
              "enum": [
                "Point"
              ],
              "type": "string"
            }
          }
        }
      ],
      "description": "GeoJSON geometry",
      "type": "object"
    },
    "id": {
      "description": "Unieke identificatie record.",
      "format": "int64",
      "maximum": 9223372036854776000,
      "minimum": -9223372036854776000,
      "type": "integer"
    },
    "naamBedrijf": {
      "description": "Bedrijfsnaam.",
      "type": [
        "string",
        "null"
      ]
    },
    "opmerkingen": {
      "description": "Opmerkingen",
      "type": [
        "string",
        "null"
      ]
    },
    "stadsdeel": {
      "description": "Naam stadsdeel waar bedrijf onder valt.",
      "type": [
        "string",
        "null"
      ]
    },
    "typeBedrijf": {
      "description": "Typering /aard van het bedrijf.",
      "type": [
        "string",
        "null"
      ]
    }
  },
  "required": [
    "_links",
    "id"
  ],
  "type": "object",
  "x-derived-from": [
    "https://api.data.amsterdam.nl/v1/risicozones/openapi.json#/components/schemas/Risicozonesbedrijven"
  ]
}

Schema gebruiken

JSON Schema

Bundled JSON Schema

Open in JSON Schema Viewer

Dependencies

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

Dit schema wordt gebruikt door
Schema	Locatie
embedded3	`/properties/bedrijven/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`
Avoid keywords that don't apply to the type or types that the current subschema expects	`/properties/aantalBronnen/format`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/aantalBronnen/description`
For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification	`/properties/aantalBronnen/format`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/adresBedrijf/description`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/bevoegdgezag/description`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/categorieBevi/description`
Keywords inside `allOf` that do not conflict with the parent schema can be elevated	`/properties/geometrie/allOf/0/type – /properties/geometrie/allOf/0/required – /properties/geometrie/allOf/0/discriminator – /properties/geometrie/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/geometrie/allOf/0/discriminator`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/geometrie/allOf/0/properties/coordinates/description`
Setting `type` alongside `enum` is considered an anti-pattern, as the enumeration choices already imply their respective types	`/properties/geometrie/allOf/0/properties/type/enum – /properties/geometrie/allOf/0/properties/type/type`
Setting `type` alongside `enum` is considered an anti-pattern, as the enumeration choices already imply their respective types	`/properties/geometrie/allOf/1/properties/type/enum – /properties/geometrie/allOf/1/properties/type/type`
An `enum` of a single value can be expressed as `const`	`/properties/geometrie/allOf/1/properties/type/enum`
Keywords inside `allOf` that do not conflict with the parent schema can be elevated	`/properties/geometriePunt/allOf/0/type – /properties/geometriePunt/allOf/0/required – /properties/geometriePunt/allOf/0/discriminator – /properties/geometriePunt/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/geometriePunt/allOf/0/discriminator`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/geometriePunt/allOf/0/properties/coordinates/description`
Setting `type` alongside `enum` is considered an anti-pattern, as the enumeration choices already imply their respective types	`/properties/geometriePunt/allOf/0/properties/type/enum – /properties/geometriePunt/allOf/0/properties/type/type`
Setting `type` alongside `enum` is considered an anti-pattern, as the enumeration choices already imply their respective types	`/properties/geometriePunt/allOf/1/properties/type/enum – /properties/geometriePunt/allOf/1/properties/type/type`
An `enum` of a single value can be expressed as `const`	`/properties/geometriePunt/allOf/1/properties/type/enum`
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/naamBedrijf/description`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/stadsdeel/description`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/typeBedrijf/description`

Schema-register: risicozonesbedrijven

Details van JSON Schema: risicozonesbedrijven

Details van JSON Schema: risicozonesbedrijven

Beschrijving