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 2: Conversion tools #180

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

Improve CoverageJSON Ecosystem 2: Conversion tools #180

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

Comments

@chris-little
Copy link
Contributor

chris-little commented Jul 11, 2024

  1. A Python tool that would convert CoverageJSON objects into common frameworks like xarray, geopandas, Zarr, etc, ready for analysis and plotting.

Along the way it could do validation of "the parts the schema can't reach".

And it would also write CoverageJSON from those common frameworks although that's a little trickier as not all the information may be present.

@chris-little chris-little changed the title Improve CoverageJSON ecosystem 2: Improve CoverageJSON Ecosystem 2: Jul 11, 2024
@chris-little chris-little changed the title Improve CoverageJSON Ecosystem 2: Improve CoverageJSON Ecosystem 2: Conversion tools 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
Copy link
Contributor

I think this would link closely with the validator in #179. Would probably be the same tool?

@jonblower
Copy link
Contributor

Just a note that, at first glance, it would seem to be possible to convert between CoverageJSON and vector data cubes, e.g. for PolygonSeries and other "vector" types

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

2 participants