Skip to content

Make PointSeries CoverageJSON spec compliant#125

Open
andreas-grafberger wants to merge 2 commits into
mainfrom
feat/122-point-series-spec-compliant
Open

Make PointSeries CoverageJSON spec compliant#125
andreas-grafberger wants to merge 2 commits into
mainfrom
feat/122-point-series-spec-compliant

Conversation

@andreas-grafberger

@andreas-grafberger andreas-grafberger commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Description

Proposes a relatively minimal fix for #122, and changes the PointSeries domainType / TimeSeries encoder/decoder to be CoverageJSON spec compliant.

To keep this focused, I did not experiment with adding back pydantic support, and I only implemented this for TimeSeries, not other encoders/decoders. Those should probably follow in future PRs to avoid any inconsistencies long-term.

Changes:

  • Domain axes are now x (longitude), y (latitude), and t. A z axis appears only when there's a real vertical level. A synthetic 0 that was added so far stays in mars:metadata but not in the domain.
  • Range axisNames is ["t"] instead of the parameter short name.
  • References are split into CRS84 for [x, y], Gregorian TemporalRS for [t], optional VerticalCRS for [z].

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.

@andreas-grafberger andreas-grafberger changed the title feat: make PointSeries CoverageJSON spec compliant Make PointSeries CoverageJSON spec compliant Jul 17, 2026
@andreas-grafberger
andreas-grafberger marked this pull request as ready for review July 17, 2026 08:22
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.

1 participant