Skip to content

Bring all features in line with OGC CoverageJSON spec - #131

Merged
awarde96 merged 6 commits into
mainfrom
129-fix-coverages-not-conforming-to-ogc-specification
Sep 8, 2026
Merged

Bring all features in line with OGC CoverageJSON spec#131
awarde96 merged 6 commits into
mainfrom
129-fix-coverages-not-conforming-to-ogc-specification

Conversation

@awarde96

@awarde96 awarde96 commented Sep 4, 2026

Copy link
Copy Markdown
Collaborator

Description

Address issue #129

Contributor Declaration

By opening this pull request, I affirm the following:

  • All authors agree to the Contributor License Agreement.
  • The code follows the project's coding standards.
  • I have performed self-review and added comments where needed.
  • I have added or updated tests to verify that my changes are effective and functional.
  • I have run all existing tests and confirmed they pass.

@awarde96 awarde96 linked an issue Sep 4, 2026 that may be closed by this pull request
10 tasks

@andreas-grafberger andreas-grafberger left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @awarde96 for these changes!

I tried the major feature types for our data and the generated coverages look correct to me. I didn't look at the concrete code changes in great detail and didn't e.g. try with data that uses levelist. Let me know if I should do a more careful review, but LGTM from my side. :)

@awarde96
awarde96 merged commit 9a44de8 into main Sep 8, 2026
123 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix coverages not conforming to OGC specification

2 participants