search

opengeospatial / CoverageJSON

Public repo for CoverageJSON project
Apache License 2.0
10 stars 8 forks source link

What tools are needed to make CoverageJSON more successful? #123

Closed chris-little closed 1 month ago

chris-little commented 2 years ago
  1. A python validation tool to validate values and aspects that the JSON Schema cannot.
  2. ??
jonblower commented 2 years ago

To add to this, my idea for the Python tool is that it would convert CovJSON objects into common frameworks like xarray, geopandas etc, ready for analysis and plotting. Along the way it would do validation of "the parts the schema can't reach".

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

chris-little commented 2 years ago

@jonblower Maybe Zarr should be on the framework list? And the validation component could be reuseable elsewhere?

jonblower commented 2 years ago

Yes, agreed on both points

edzer commented 2 years ago

A GDAL CovJSON read & create driver, supporting the GDAL multidimensional array API. That would allow conversion to and from other MDA types (NetCDF, Zarr) using gdalmdimtranslate, and easier uptake in OSGEO software building on GDAL.

jonblower commented 2 years ago

Great idea @edzer! Would such a driver have to be written in C, or could it be done in Python?

edzer commented 2 years ago

I think easiest is in C++ - the NetCDF, Zarr and MEM driver implementations could work as examples.

chris-little commented 2 years ago

It may be worth investigating whether CoverageJSON (and API EDR) could be a useful adjunct to ERDDAP

chris-little commented 1 year ago

How about some closer interaction between CoverageJSON and the STAC ecosystem? STAC is rather space imagery orientated, but perhaps CoverageJSON could fill some gaps around GeoTIFF and COG?

jonblower commented 1 year ago

I think CoverageJSON could be a useful format for an "asset" in a STAC catalogue. STAC can point to pretty much any format (using the media type, which is one reason why #135 is important). So GeoTIFFs and CoGs can already be arranged in a STAC catalogue.

I may be wrong, but I don't think anything further needs to be done to integrate CoverageJSON with STAC as they are neatly complementary. But it would be cool to build in some CoverageJSON visualisation into the STAC browser so data can be automatically previewed, in the same way that GeoTIFF can be.

chris-little commented 1 month ago

@jonblower @edzer The above issues have now been separated into single topic issues, so closing this generic issue.