Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve CoverageJSON Ecosystem 1: Python Validator #179

Open
chris-little opened this issue Jul 11, 2024 · 3 comments
Open

Improve CoverageJSON Ecosystem 1: Python Validator #179

chris-little opened this issue Jul 11, 2024 · 3 comments
Assignees
Labels
Priority 2 Dsesirable V1.0.0 Non-breaking change needed for initial Community Standard

Comments

@chris-little
Copy link
Contributor

  1. To improve the CoverageJSON ecosystem, a python validation tool to validate values and aspects that the JSON Schema cannot would be useful.

(In the longer term, if CoverageJSON becomes a full OGC Standard, the validator would be written in Java.)

@chris-little chris-little changed the title Improving CoverageJSON Ecosystem 1: Python Validator Improve CoverageJSON Ecosystem 1: Python Validator Jul 11, 2024
@chris-little chris-little added V1.0.0 Non-breaking change needed for initial Community Standard and removed V1.2 labels Jul 11, 2024
@jonblower jonblower self-assigned this Aug 21, 2024
@jonblower
Copy link
Contributor

This comment is a note-to-self to define the requirements for this, with a view to defining a project. Could include requirements for validation and conversion between xarray, pandas, etc.

Would need to build on existing work with the schema.

@murithigeo
Copy link

I think one exists at covjson-validator although not for conversions

@jonblower
Copy link
Contributor

Yes, that one validates against the schema, but there are other rules that the schema can't cover, which we would have to validate some other way. And you're right, it doesn't do conversions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority 2 Dsesirable V1.0.0 Non-breaking change needed for initial Community Standard
Development

No branches or pull requests

3 participants