- SourceMeta name
- milieuzones2025personenauto
- Base dialect
- https://json-schema.org/draft/2020-12/schema
- SourceMeta dialect
- https://json-schema.org/draft/2020-12/schema
- Bytes
- 2.944 bytes
- Bytes bundled
- 4.158 bytes
- Health
- 53%
- Dependencies
- 1
Dependencies
- At
- /properties/_links/properties/self/$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
- /properties/_links/description
- Name
- title_trim
- Message
- Titles should not contain leading or trailing whitespace
- Pointers
- /properties/_links/title
- Name
- unnecessary_allof_wrapper
- Message
- Keywords inside `allOf` that do not conflict with the parent schema can be elevated
- Pointers
- /properties/geometry/allOf/0/type - /properties/geometry/allOf/0/required - /properties/geometry/allOf/0/discriminator - /properties/geometry/allOf/0/description
- 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/geometry/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/geometry/allOf/0/properties/coordinates/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/geometry/allOf/0/properties/type/enum - /properties/geometry/allOf/0/properties/type/type
- 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/geometry/allOf/1/properties/type/enum - /properties/geometry/allOf/1/properties/type/type
- Name
- enum_to_const
- Message
- An `enum` of a single value can be expressed as `const`
- Pointers
- /properties/geometry/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/id/format
- Name
- description_trailing_period
- Message
- Descriptions should not end with a period to give user interfaces flexibility in presenting the text
- Pointers
- /properties/id/description
- 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/id/format
{
"$id": "https://schemas.don.projects.digilab.network/schemas/api-register/gemeente-amsterdam/milieuzones-4ryl1xenr/milieuzones2025personenauto",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"description": "personenauto",
"properties": {
"_links": {
"description": "The contents of the `personenauto._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": "./milieuzones2025personenautolink"
}
},
"required": [
"schema",
"self"
],
"title": " links",
"type": "object"
},
"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": {
"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"
},
"id": {
"description": "Unieke aanduiding van het milieuzone gebied voor personenauto's.",
"format": "int64",
"maximum": 9223372036854776000,
"minimum": -9223372036854776000,
"title": "Personenauto milieuzone ID",
"type": "integer"
}
},
"required": [
"_links",
"id"
],
"type": "object",
"x-derived-from": [
"https://api.data.amsterdam.nl/v1/milieuzones2025/openapi.json#/components/schemas/Milieuzones2025personenauto"
]
}