Extend TileJSON response with custom keys #1242
Description
The Mapbox TileJSON spec is fairly simple and was created before dynamic tiling was popular.
BUT the spec also says:
The following describes the structure of a TileJSON object. Implementations MUST treat unknown keys as if they weren't present. However, implementations MUST expose unknown key value pairs so users can optionally handle these keys. Implementations MUST treat invalid values for keys as if they were not present. If the key is optional and the value is invalid, the default value MAY be applied. If the key is required, implementations MUST treat the entire TileJSON manifest file as invalid and refuse operation.
The word "implementation" in the following sections refers to services or tools that serve, generate, or validate TileJSON objects.
Which mean that a tool like TiTiler could add more key/values to the response.
Example:
- count / band descriptions
- min/max value for each band
- data type
- renders (example of rendering)