- SourceMeta name
- queryables
- Base dialect
- https://json-schema.org/draft/2020-12/schema
- SourceMeta dialect
- https://json-schema.org/draft/2020-12/schema
- Bytes
- 21.419 bytes
- Bytes bundled
- 21.419 bytes
- Health
- 66%
- Dependencies
- -
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_description
- Message
- Set a non-empty description at the top level of the schema to explain what the definition is about in detail
- 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
- unnecessary_allof_wrapper
- Message
- Keywords inside `allOf` that do not conflict with the parent schema can be elevated
- Pointers
- /properties/queryables/items/oneOf/0/allOf/0/required - /properties/queryables/items/oneOf/0/allOf/0/discriminator
- Name
- unknown_keywords_prefix
- Message
- Future versions of JSON Schema will refuse to evaluate unknown keywords or custom keywords from optional vocabularies that don't have an x- prefix
- Pointers
- /properties/queryables/items/oneOf/0/allOf/0/discriminator
- Name
- description_trailing_period
- Message
- Descriptions should not end with a period to give user interfaces flexibility in presenting the text
- Pointers
- /properties/queryables/items/oneOf/0/allOf/0/properties/mediaTypes/description
- 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/queryables/items/oneOf/0/allOf/0/properties/type/enum - /properties/queryables/items/oneOf/0/allOf/0/properties/type/type
- Name
- unnecessary_allof_wrapper
- Message
- Keywords inside `allOf` that do not conflict with the parent schema can be elevated
- Pointers
- /properties/queryables/items/oneOf/1/allOf/0/discriminator
- Name
- unknown_keywords_prefix
- Message
- Future versions of JSON Schema will refuse to evaluate unknown keywords or custom keywords from optional vocabularies that don't have an x- prefix
- Pointers
- /properties/queryables/items/oneOf/1/allOf/0/discriminator
- Name
- description_trailing_period
- Message
- Descriptions should not end with a period to give user interfaces flexibility in presenting the text
- Pointers
- /properties/queryables/items/oneOf/1/allOf/0/properties/mediaTypes/description
- 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/queryables/items/oneOf/1/allOf/0/properties/type/enum - /properties/queryables/items/oneOf/1/allOf/0/properties/type/type
- Name
- unnecessary_allof_wrapper
- Message
- Keywords inside `allOf` that do not conflict with the parent schema can be elevated
- Pointers
- /properties/queryables/items/oneOf/2/allOf/0/required - /properties/queryables/items/oneOf/2/allOf/0/discriminator
- Name
- unknown_keywords_prefix
- Message
- Future versions of JSON Schema will refuse to evaluate unknown keywords or custom keywords from optional vocabularies that don't have an x- prefix
- Pointers
- /properties/queryables/items/oneOf/2/allOf/0/discriminator
- Name
- description_trailing_period
- Message
- Descriptions should not end with a period to give user interfaces flexibility in presenting the text
- Pointers
- /properties/queryables/items/oneOf/2/allOf/0/properties/mediaTypes/description
- 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/queryables/items/oneOf/2/allOf/0/properties/type/enum - /properties/queryables/items/oneOf/2/allOf/0/properties/type/type
- Name
- unknown_keywords_prefix
- Message
- Future versions of JSON Schema will refuse to evaluate unknown keywords or custom keywords from optional vocabularies that don't have an x- prefix
- Pointers
- /properties/queryables/items/oneOf/3/discriminator
- Name
- description_trailing_period
- Message
- Descriptions should not end with a period to give user interfaces flexibility in presenting the text
- Pointers
- /properties/queryables/items/oneOf/3/properties/mediaTypes/description
- 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/queryables/items/oneOf/3/properties/type/enum - /properties/queryables/items/oneOf/3/properties/type/type
- Name
- unnecessary_allof_wrapper
- Message
- Keywords inside `allOf` that do not conflict with the parent schema can be elevated
- Pointers
- /properties/queryables/items/oneOf/4/allOf/0/required - /properties/queryables/items/oneOf/4/allOf/0/discriminator
- Name
- unknown_keywords_prefix
- Message
- Future versions of JSON Schema will refuse to evaluate unknown keywords or custom keywords from optional vocabularies that don't have an x- prefix
- Pointers
- /properties/queryables/items/oneOf/4/allOf/0/discriminator
- Name
- description_trailing_period
- Message
- Descriptions should not end with a period to give user interfaces flexibility in presenting the text
- Pointers
- /properties/queryables/items/oneOf/4/allOf/0/properties/mediaTypes/description
- 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/queryables/items/oneOf/4/allOf/0/properties/type/enum - /properties/queryables/items/oneOf/4/allOf/0/properties/type/type
- Name
- unnecessary_allof_wrapper
- Message
- Keywords inside `allOf` that do not conflict with the parent schema can be elevated
- Pointers
- /properties/queryables/items/oneOf/5/allOf/0/required - /properties/queryables/items/oneOf/5/allOf/0/discriminator
- Name
- unknown_keywords_prefix
- Message
- Future versions of JSON Schema will refuse to evaluate unknown keywords or custom keywords from optional vocabularies that don't have an x- prefix
- Pointers
- /properties/queryables/items/oneOf/5/allOf/0/discriminator
- Name
- description_trailing_period
- Message
- Descriptions should not end with a period to give user interfaces flexibility in presenting the text
- Pointers
- /properties/queryables/items/oneOf/5/allOf/0/properties/mediaTypes/description
- 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/queryables/items/oneOf/5/allOf/0/properties/type/enum - /properties/queryables/items/oneOf/5/allOf/0/properties/type/type
{
"$id": "https://schemas.don.projects.digilab.network/schemas/api-register/pdok/_shared/queryables",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"queryables": {
"items": {
"oneOf": [
{
"allOf": [
{
"discriminator": {
"mapping": {
"boolean": "queryable-boolean",
"date": "queryable-date",
"dateTime": "queryable-dateTime",
"enum": "queryable-enum",
"integer": "queryable-number",
"number": "queryable-number",
"string": "queryable-string",
"uri": "queryable-string"
},
"propertyName": "type"
},
"properties": {
"description": {
"description": "a description of the property",
"type": [
"string",
"null"
]
},
"id": {
"description": "the property name for use in expressions",
"type": [
"string",
"null"
]
},
"mediaTypes": {
"description": "In cases where a property is available only in a subset of the\nsupported feature encodings, the list of the media types of the\nencodings can be specified.\n\nThis capabilitiy is also needed for cases where the names of\nproperties may differ between feature encodings. For example, \nidentifiers in an XML/GML encoding may include a namespace, \nin GeoJSON or MVT this is not the case. \n\nThere are other reasons, too. For example, the property identifier\nin a Shapefile may be different because of length restrictions.",
"items": {
"type": "string"
},
"type": [
"array",
"null"
]
},
"required": {
"default": false,
"description": "indicator whether the property is always present in features",
"type": [
"boolean",
"null"
]
},
"title": {
"description": "the title of the property for presentation to a human user",
"type": [
"string",
"null"
]
},
"type": {
"description": "the data type of the property",
"enum": [
"string",
"uri",
"enum",
"number",
"integer",
"date",
"dateTime",
"boolean"
],
"type": [
"string",
"null"
]
}
},
"required": [
"id",
"type"
],
"type": [
"object",
"null"
]
},
{
"properties": {
"pattern": {
"description": "a regular expression to validate the values of the property",
"type": [
"string",
"null"
]
}
},
"type": [
"object",
"null"
]
}
],
"examples": [
{
"description": "the name of the vegetation area",
"examples": [
"[A-Z0-9]{5}"
],
"id": "name",
"required": true,
"type": "string"
}
]
},
{
"allOf": [
{
"discriminator": {
"mapping": {
"boolean": "queryable-boolean",
"date": "queryable-date",
"dateTime": "queryable-dateTime",
"enum": "queryable-enum",
"integer": "queryable-number",
"number": "queryable-number",
"string": "queryable-string",
"uri": "queryable-string"
},
"propertyName": "type"
},
"properties": {
"description": {
"description": "a description of the property",
"type": [
"string",
"null"
]
},
"id": {
"description": "the property name for use in expressions",
"type": [
"string",
"null"
]
},
"mediaTypes": {
"description": "In cases where a property is available only in a subset of the\nsupported feature encodings, the list of the media types of the\nencodings can be specified.\n\nThis capabilitiy is also needed for cases where the names of\nproperties may differ between feature encodings. For example, \nidentifiers in an XML/GML encoding may include a namespace, \nin GeoJSON or MVT this is not the case. \n\nThere are other reasons, too. For example, the property identifier\nin a Shapefile may be different because of length restrictions.",
"items": {
"type": "string"
},
"type": [
"array",
"null"
]
},
"required": {
"default": false,
"description": "indicator whether the property is always present in features",
"type": [
"boolean",
"null"
]
},
"title": {
"description": "the title of the property for presentation to a human user",
"type": [
"string",
"null"
]
},
"type": {
"description": "the data type of the property",
"enum": [
"string",
"uri",
"enum",
"number",
"integer",
"date",
"dateTime",
"boolean"
],
"type": [
"string",
"null"
]
}
},
"required": [
"id",
"type"
],
"type": [
"object",
"null"
]
},
{
"properties": {
"values": {
"description": "the list of values of the property",
"items": {
"type": "string"
},
"type": [
"array",
"null"
]
}
},
"required": [
"values"
],
"type": [
"object",
"null"
]
}
],
"examples": [
{
"description": "the dominant charcteristic of vegetation area",
"id": "type",
"type": "enum",
"values": [
"grassland",
"forest",
"farmland"
]
}
]
},
{
"allOf": [
{
"discriminator": {
"mapping": {
"boolean": "queryable-boolean",
"date": "queryable-date",
"dateTime": "queryable-dateTime",
"enum": "queryable-enum",
"integer": "queryable-number",
"number": "queryable-number",
"string": "queryable-string",
"uri": "queryable-string"
},
"propertyName": "type"
},
"properties": {
"description": {
"description": "a description of the property",
"type": [
"string",
"null"
]
},
"id": {
"description": "the property name for use in expressions",
"type": [
"string",
"null"
]
},
"mediaTypes": {
"description": "In cases where a property is available only in a subset of the\nsupported feature encodings, the list of the media types of the\nencodings can be specified.\n\nThis capabilitiy is also needed for cases where the names of\nproperties may differ between feature encodings. For example, \nidentifiers in an XML/GML encoding may include a namespace, \nin GeoJSON or MVT this is not the case. \n\nThere are other reasons, too. For example, the property identifier\nin a Shapefile may be different because of length restrictions.",
"items": {
"type": "string"
},
"type": [
"array",
"null"
]
},
"required": {
"default": false,
"description": "indicator whether the property is always present in features",
"type": [
"boolean",
"null"
]
},
"title": {
"description": "the title of the property for presentation to a human user",
"type": [
"string",
"null"
]
},
"type": {
"description": "the data type of the property",
"enum": [
"string",
"uri",
"enum",
"number",
"integer",
"date",
"dateTime",
"boolean"
],
"type": [
"string",
"null"
]
}
},
"required": [
"id",
"type"
],
"type": [
"object",
"null"
]
},
{
"properties": {
"range": {
"description": "a range of valid values; open range can be expressed using `null`",
"items": {
"type": [
"number",
"null"
]
},
"maxItems": 2,
"minItems": 2,
"type": [
"array",
"null"
]
}
},
"type": [
"object",
"null"
]
}
],
"examples": [
{
"description": "the number of cattle",
"id": "count",
"range": [
0,
null
],
"type": "integer"
}
]
},
{
"discriminator": {
"mapping": {
"boolean": "queryable-boolean",
"date": "queryable-date",
"dateTime": "queryable-dateTime",
"enum": "queryable-enum",
"integer": "queryable-number",
"number": "queryable-number",
"string": "queryable-string",
"uri": "queryable-string"
},
"propertyName": "type"
},
"examples": [
{
"description": "indicator whether the area is walled or fenced",
"id": "fenced",
"type": "boolean"
}
],
"properties": {
"description": {
"description": "a description of the property",
"type": [
"string",
"null"
]
},
"id": {
"description": "the property name for use in expressions",
"type": [
"string",
"null"
]
},
"mediaTypes": {
"description": "In cases where a property is available only in a subset of the\nsupported feature encodings, the list of the media types of the\nencodings can be specified.\n\nThis capabilitiy is also needed for cases where the names of\nproperties may differ between feature encodings. For example, \nidentifiers in an XML/GML encoding may include a namespace, \nin GeoJSON or MVT this is not the case. \n\nThere are other reasons, too. For example, the property identifier\nin a Shapefile may be different because of length restrictions.",
"items": {
"type": "string"
},
"type": [
"array",
"null"
]
},
"required": {
"default": false,
"description": "indicator whether the property is always present in features",
"type": [
"boolean",
"null"
]
},
"title": {
"description": "the title of the property for presentation to a human user",
"type": [
"string",
"null"
]
},
"type": {
"description": "the data type of the property",
"enum": [
"string",
"uri",
"enum",
"number",
"integer",
"date",
"dateTime",
"boolean"
],
"type": [
"string",
"null"
]
}
},
"required": [
"id",
"type"
],
"type": [
"object",
"null"
]
},
{
"allOf": [
{
"discriminator": {
"mapping": {
"boolean": "queryable-boolean",
"date": "queryable-date",
"dateTime": "queryable-dateTime",
"enum": "queryable-enum",
"integer": "queryable-number",
"number": "queryable-number",
"string": "queryable-string",
"uri": "queryable-string"
},
"propertyName": "type"
},
"properties": {
"description": {
"description": "a description of the property",
"type": [
"string",
"null"
]
},
"id": {
"description": "the property name for use in expressions",
"type": [
"string",
"null"
]
},
"mediaTypes": {
"description": "In cases where a property is available only in a subset of the\nsupported feature encodings, the list of the media types of the\nencodings can be specified.\n\nThis capabilitiy is also needed for cases where the names of\nproperties may differ between feature encodings. For example, \nidentifiers in an XML/GML encoding may include a namespace, \nin GeoJSON or MVT this is not the case. \n\nThere are other reasons, too. For example, the property identifier\nin a Shapefile may be different because of length restrictions.",
"items": {
"type": "string"
},
"type": [
"array",
"null"
]
},
"required": {
"default": false,
"description": "indicator whether the property is always present in features",
"type": [
"boolean",
"null"
]
},
"title": {
"description": "the title of the property for presentation to a human user",
"type": [
"string",
"null"
]
},
"type": {
"description": "the data type of the property",
"enum": [
"string",
"uri",
"enum",
"number",
"integer",
"date",
"dateTime",
"boolean"
],
"type": [
"string",
"null"
]
}
},
"required": [
"id",
"type"
],
"type": [
"object",
"null"
]
},
{
"properties": {
"range": {
"description": "a range of valid values; open range can be expressed using `null`",
"items": {
"format": "date",
"type": [
"string",
"null"
]
},
"maxItems": 2,
"minItems": 2,
"type": [
"array",
"null"
]
}
},
"type": [
"object",
"null"
]
}
],
"examples": [
{
"description": "the date of the last inspection",
"id": "inspectionDate",
"range": [
"2010-01-01",
null
],
"type": "date"
}
]
},
{
"allOf": [
{
"discriminator": {
"mapping": {
"boolean": "queryable-boolean",
"date": "queryable-date",
"dateTime": "queryable-dateTime",
"enum": "queryable-enum",
"integer": "queryable-number",
"number": "queryable-number",
"string": "queryable-string",
"uri": "queryable-string"
},
"propertyName": "type"
},
"properties": {
"description": {
"description": "a description of the property",
"type": [
"string",
"null"
]
},
"id": {
"description": "the property name for use in expressions",
"type": [
"string",
"null"
]
},
"mediaTypes": {
"description": "In cases where a property is available only in a subset of the\nsupported feature encodings, the list of the media types of the\nencodings can be specified.\n\nThis capabilitiy is also needed for cases where the names of\nproperties may differ between feature encodings. For example, \nidentifiers in an XML/GML encoding may include a namespace, \nin GeoJSON or MVT this is not the case. \n\nThere are other reasons, too. For example, the property identifier\nin a Shapefile may be different because of length restrictions.",
"items": {
"type": "string"
},
"type": [
"array",
"null"
]
},
"required": {
"default": false,
"description": "indicator whether the property is always present in features",
"type": [
"boolean",
"null"
]
},
"title": {
"description": "the title of the property for presentation to a human user",
"type": [
"string",
"null"
]
},
"type": {
"description": "the data type of the property",
"enum": [
"string",
"uri",
"enum",
"number",
"integer",
"date",
"dateTime",
"boolean"
],
"type": [
"string",
"null"
]
}
},
"required": [
"id",
"type"
],
"type": [
"object",
"null"
]
},
{
"properties": {
"range": {
"description": "a range of valid values; open range can be expressed using `null`",
"items": {
"format": "date-time",
"type": [
"string",
"null"
]
},
"maxItems": 2,
"minItems": 2,
"type": [
"array",
"null"
]
}
},
"type": [
"object",
"null"
]
}
],
"examples": [
{
"description": "the date of the last update of the feature",
"id": "lastUpdate",
"range": [
"2018-01-01T00:00:00Z",
null
],
"type": "dateTime"
}
]
}
]
},
"type": [
"array",
"null"
]
}
},
"required": [
"queryables"
],
"type": "object",
"x-derived-from": [
"https://api.pdok.nl/brt/top10nl/ogc/v1/openapi.json#/components/schemas/queryables",
"https://api.pdok.nl/kadaster/bestuurlijkegebieden/ogc/v1/openapi.json#/components/schemas/queryables",
"https://api.pdok.nl/kadaster/brk-kadastrale-kaart/ogc/v1/openapi.json#/components/schemas/queryables",
"https://api.pdok.nl/kadaster/brt-achtergrondkaart/ogc/v1/openapi.json#/components/schemas/queryables",
"https://api.pdok.nl/lv/bag/ogc/v1-demo/openapi.json#/components/schemas/queryables",
"https://api.pdok.nl/lv/bag/ogc/v1/openapi.json#/components/schemas/queryables",
"https://api.pdok.nl/lv/bgt/ogc/v1/openapi.json#/components/schemas/queryables"
]
}