- SourceMeta name
- brt10functionelegebieden
- Base dialect
- https://json-schema.org/draft/2020-12/schema
- SourceMeta dialect
- https://json-schema.org/draft/2020-12/schema
- Bytes
- 5.276 bytes
- Bytes bundled
- 17.315 bytes
- Health
- 74%
- Dependencies
- 2
Dependencies
- At
- /properties/_links/properties/self/$ref
- At
- /properties/geometrie/$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
- /description
- 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/bronnauwkeurigheid/format
- 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/bronnauwkeurigheid/format
- Name
- unnecessary_allof_ref_wrapper_modern
- Message
- Wrapping `$ref` in `allOf` was only necessary in JSON Schema Draft 7 and older
- Pointers
- /properties/geometriePunt/allOf/0/$ref
- Name
- unnecessary_allof_wrapper
- Message
- Keywords inside `allOf` that do not conflict with the parent schema can be elevated
- Pointers
- /properties/geometriePunt/allOf/1/properties
- Name
- enum_with_type
- Message
- Setting `type` alongside `enum` is considered an anti-pattern, as the enumeration choices already imply their respective types
- Pointers
- /properties/geometriePunt/allOf/1/properties/type/enum - /properties/geometriePunt/allOf/1/properties/type/type
- Name
- enum_to_const
- Message
- An `enum` of a single value can be expressed as `const`
- Pointers
- /properties/geometriePunt/allOf/1/properties/type/enum
- Name
- unnecessary_allof_ref_wrapper_modern
- Message
- Wrapping `$ref` in `allOf` was only necessary in JSON Schema Draft 7 and older
- Pointers
- /properties/geometrieVlak/allOf/0/$ref
- Name
- unnecessary_allof_wrapper
- Message
- Keywords inside `allOf` that do not conflict with the parent schema can be elevated
- Pointers
- /properties/geometrieVlak/allOf/1/properties
- Name
- enum_with_type
- Message
- Setting `type` alongside `enum` is considered an anti-pattern, as the enumeration choices already imply their respective types
- Pointers
- /properties/geometrieVlak/allOf/1/properties/type/enum - /properties/geometrieVlak/allOf/1/properties/type/type
- Name
- enum_to_const
- Message
- An `enum` of a single value can be expressed as `const`
- Pointers
- /properties/geometrieVlak/allOf/1/properties/type/enum
- 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/tdnCode/format
- 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/tdnCode/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/visualisatieCode/format
- 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/visualisatieCode/format
{
"$id": "https://schemas.don.projects.digilab.network/schemas/api-register/gemeente-amsterdam/brt-10-_uamfx6hg/brt10functionelegebieden",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"description": "Begrensd en benoemd gebied dat door een functionele eenheid beschreven wordt.",
"properties": {
"_links": {
"description": "The contents of the `functionelegebieden._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": "./brt10functionelegebiedenlink"
}
},
"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"
]
},
"bronnauwkeurigheid": {
"description": "De nauwkeurigheid van de gebruikte bron in meters",
"format": "double",
"title": "Bron nauwkeurigheid meters",
"type": [
"number",
"null"
]
},
"brontype": {
"description": "Het type van de gebruikte bron",
"title": "Bron type",
"type": [
"string",
"null"
]
},
"geometrie": {
"$ref": "../_shared/geometry"
},
"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"
},
"geometrieVlak": {
"allOf": [
{
"$ref": "../_shared/geometry"
},
{
"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"
},
"identificatie": {
"description": "De unieke identiteit van het geo-object",
"title": "Geo object ID",
"type": "string"
},
"mutatietype": {
"description": "Het soort mutatie dat een object als laatste ondergaan heeft",
"title": "Object mutatie type",
"type": [
"string",
"null"
]
},
"naamFries": {
"description": "De Friese naam van het gebied",
"title": "Gebied Friese naam",
"type": [
"string",
"null"
]
},
"naamNl": {
"description": "De Nederlandse naam van het gebied",
"title": "Gebied Nederlandse naam",
"type": [
"string",
"null"
]
},
"objectBeginTijd": {
"description": "Tijdstip waarop het object ontstaan is",
"format": "date",
"title": "Object geldigheid begintijd",
"type": [
"string",
"null"
]
},
"soortnaam": {
"description": "Verdere specificatie van het type functioneel gebied",
"title": "Functioneel gebied soort naam",
"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"
]
},
"tijdstipRegistratie": {
"description": "Tijdstip waarop een versie van het object ontstaan is",
"format": "date",
"title": "Object registratie tijdstip",
"type": [
"string",
"null"
]
},
"type": {
"description": "Het soort functioneel gebied",
"title": "Functioneel gebied 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/brt10/openapi.json#/components/schemas/Brt10functionelegebieden"
]
}