opengeospatial / opengeospatial/CoverageJSON
CoverageJSON schema mismatched with OpenAPI 3.1 document
@chris-little is already working on this.
Since May 12, 2026.
- Dominant language
- HTML
- Stars
- 15
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
The OpenAPI 3.1.1 document references a CoverageJSON JSON-schema document via url, like $ref: https://covjson.org/schema/dev/coveragejson.json in core/standard/openapi/oas31/responses/queries/200.yaml.
However, this causes a problem with the resulting bundled OpenAPI document.
OpenAPI 3.1 base their schema on JSON Schema Specification Draft 2020-12, as far as I can tell. But https://covjson.org/schema/dev/coveragejson.json is based on http://json-schema.org/draft-07/schema, which is an older version of JSON-Schema. And it uses terms that seem to no longer validate, like dependencies (which was deprecated in 2019 as far as I understand). This results in an invalid openapi document for EDR. At least that is what I am seeing when I bundle this with redocly-cli and then validate the resulting document.
Is it possible to reference a schema for CoverageJSON which is updated to the same JSON-schema version that OpenAPI 3.1.1 uses?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.