brt50hoogtes | Schema-register

Virtuele objecten met informatie over de hoogte van het terrein of de diepte van het water.

Dialect2020-12

Typeobject

Eigenschappen

Eigenschappen van het JSON Schema
Eigenschap	Type	Verplicht	Beschrijving en details
_links	`object`	Ja	The contents of the `hoogtes._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: ./brt50hoogteslink
bronactualiteit	`string, null`	Nee	De actualiteit van de gebruikte bron. Format: date
bronbeschrijving	`string, null`	Nee	De beschrijving van de gebruikte bron.
brontype	`string, null`	Nee	Het type van de gebruikte bron.
geometrie	`$ref`	Nee	- $ref: ../_shared/geometry
geometrieLijn	`object`	Nee	GeoJSON geometry allOf: 2 schema's
geometrieLijn.allOf[2].coordinates	`array`	Nee	- Items type: array
geometrieLijn.allOf[2].type	`string`	Nee	- Enum: LineString
geometriePunt	`object`	Nee	GeoJSON geometry allOf: 2 schema's
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
hoogte	`number, null`	Nee	Hoogte van het object t.o.v. het referentievlak in meters met een nauwkeurigheid van 1 decimeter. / De diepte van het water. Format: double
identificatie	`string`	Ja	De unieke identiteit van het geo-object.
objectBeginTijd	`string, null`	Nee	Tijdstip waarop het object ontstaan is. Format: date
tdnCode	`integer, null`	Nee	Code die het object in TOP10vector had. Format: int64 Minimum: -9223372036854776000 Maximum: 9223372036854776000
type	`string, null`	Nee	Het soort hoogte.
visualisatieCode	`integer, null`	Nee	Code voor het visualiseren van het object. Format: int64 Minimum: -9223372036854776000 Maximum: 9223372036854776000

JSON Schema

{
  "$id": "https://schemas.don.projects.digilab.network/schemas/api-register/gemeente-amsterdam/brt-50-nxes1ueng/brt50hoogtes",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "description": "Virtuele objecten met informatie over de hoogte van het terrein of de diepte van het water.",
  "properties": {
    "_links": {
      "description": "The contents of the `hoogtes._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": "./brt50hoogteslink"
        }
      },
      "required": [
        "schema",
        "self"
      ],
      "title": " links",
      "type": "object"
    },
    "bronactualiteit": {
      "description": "De actualiteit van de gebruikte bron.",
      "format": "date",
      "title": "Bron actualiteit datum",
      "type": [
        "string",
        "null"
      ]
    },
    "bronbeschrijving": {
      "description": "De beschrijving van de gebruikte bron.",
      "title": "Bron beschrijving",
      "type": [
        "string",
        "null"
      ]
    },
    "brontype": {
      "description": "Het type van de gebruikte bron.",
      "title": "Bron type",
      "type": [
        "string",
        "null"
      ]
    },
    "geometrie": {
      "$ref": "../_shared/geometry"
    },
    "geometrieLijn": {
      "allOf": [
        {
          "$ref": "../_shared/geometry"
        },
        {
          "properties": {
            "coordinates": {
              "items": {
                "description": "Point in 3D space",
                "items": {
                  "type": "number"
                },
                "maxItems": 3,
                "minItems": 2,
                "type": "array"
              },
              "type": "array"
            },
            "type": {
              "enum": [
                "LineString"
              ],
              "type": "string"
            }
          }
        }
      ],
      "description": "GeoJSON geometry",
      "type": "object"
    },
    "geometriePunt": {
      "allOf": [
        {
          "$ref": "../_shared/geometry"
        },
        {
          "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"
    },
    "hoogte": {
      "description": "Hoogte van het object t.o.v. het referentievlak in meters met een nauwkeurigheid van 1 decimeter. / De diepte van het water.",
      "format": "double",
      "title": "Object referentievlak hoogte",
      "type": [
        "number",
        "null"
      ]
    },
    "identificatie": {
      "description": "De unieke identiteit van het geo-object.",
      "title": "Object ID",
      "type": "string"
    },
    "objectBeginTijd": {
      "description": "Tijdstip waarop het object ontstaan is.",
      "format": "date",
      "title": "Object geldigheid begintijd",
      "type": [
        "string",
        "null"
      ]
    },
    "tdnCode": {
      "description": "Code die het object in TOP10vector had.",
      "format": "int64",
      "maximum": 9223372036854776000,
      "minimum": -9223372036854776000,
      "title": "Object TOP10vector code",
      "type": [
        "integer",
        "null"
      ]
    },
    "type": {
      "description": "Het soort hoogte.",
      "title": "Hoogte type",
      "type": [
        "string",
        "null"
      ]
    },
    "visualisatieCode": {
      "description": "Code voor het visualiseren van het object.",
      "format": "int64",
      "maximum": 9223372036854776000,
      "minimum": -9223372036854776000,
      "title": "Object visualisatie code",
      "type": [
        "integer",
        "null"
      ]
    }
  },
  "required": [
    "_links",
    "identificatie"
  ],
  "type": "object",
  "x-derived-from": [
    "https://api.data.amsterdam.nl/v1/brt50/openapi.json#/components/schemas/Brt50hoogtes"
  ]
}

Schema gebruiken

JSON Schema

Bundled JSON Schema

Open in JSON Schema Viewer

Dependencies

Gebruikt door dit schema
Schema	Locatie
brt50hoogteslink	`/properties/_links/properties/self/$ref`
geometry	`/properties/geometrie/$ref`

Dit schema wordt gebruikt door
Schema	Locatie
embedded3	`/properties/hoogtes/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	`/description`
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/bronactualiteit/description`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/bronbeschrijving/description`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/brontype/description`
Wrapping `$ref` in `allOf` was only necessary in JSON Schema Draft 7 and older	`/properties/geometrieLijn/allOf/0/$ref`
Keywords inside `allOf` that do not conflict with the parent schema can be elevated	`/properties/geometrieLijn/allOf/1/properties`
Setting `type` alongside `enum` is considered an anti-pattern, as the enumeration choices already imply their respective types	`/properties/geometrieLijn/allOf/1/properties/type/enum – /properties/geometrieLijn/allOf/1/properties/type/type`
An `enum` of a single value can be expressed as `const`	`/properties/geometrieLijn/allOf/1/properties/type/enum`
Wrapping `$ref` in `allOf` was only necessary in JSON Schema Draft 7 and older	`/properties/geometriePunt/allOf/0/$ref`
Keywords inside `allOf` that do not conflict with the parent schema can be elevated	`/properties/geometriePunt/allOf/1/properties`
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/hoogte/format`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/hoogte/description`
For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification	`/properties/hoogte/format`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/identificatie/description`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/objectBeginTijd/description`
Avoid keywords that don't apply to the type or types that the current subschema expects	`/properties/tdnCode/format`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/tdnCode/description`
For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification	`/properties/tdnCode/format`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/type/description`
Avoid keywords that don't apply to the type or types that the current subschema expects	`/properties/visualisatieCode/format`
Descriptions should not end with a period to give user interfaces flexibility in presenting the text	`/properties/visualisatieCode/description`
For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification	`/properties/visualisatieCode/format`

Schema-register: brt50hoogtes

Details van JSON Schema: brt50hoogtes

Details van JSON Schema: brt50hoogtes

Beschrijving