EDR API compliance with CoverageJSON and tools #1833
Description
Description
Following inconsistencies with the https://schemas.opengis.net/covjson/1.0/coveragejson.json:
- time axis is rendered as interval (start, stop, num), while schema allows only values - brakes covjson JS tools to properly render time slices (e.g. for grids)
- time axis shall be 't', current implementation take source dimension (like TIME), JS client does not interpret it correctly so mapping in configuration is needed.
- parameter description are string, while expected object - worked with JS visualisation but not validator and covjson playground
- range dataType shall not be number; allowed are float, integer, string - string works with JS visualisation but not validator and covjson playground
Other:
- JS tools https://github.com/Reading-eScience-Centre/leaflet-coverage expect time axis first in range - not required by standard but enable time dimension visualisation
Changes proposed in #1814 would solve issues using https://covjson.org/ and JS libraries, also on pygeoapi demo site. Changes are not fully backward compatible with potential non-standard client using time as interval.
Related Issue / discussion
#1782
Additional information
In addition to code changes and test if working, pull request containt coads_sst.nc fixed. Demo file had COADSX shifted west but not data.
Steps to Reproduce
open
https://demo.pygeoapi.io/master/collections/icoads-sst/cube?bbox=0,0,10,10
and check that time slices are not rendered at all in the UI while available and in principle supported by the JS libraries used
https://demo.pygeoapi.io/master/collections/icoads-sst/cube?bbox=0,0,10,10&f=json
Expected behavior
integration of the changes proposed here:
#1814
would solve issues
Screenshots/Tracebacks
If applicable, add screenshots to help explain your problem.
this is how it looks now under
https://demo.pygeoapi.io/master/collections/icoads-sst/cube?bbox=-180,-90,180,90&datetime=2000-01-16/2000-12-16
and this is how it looks with changes
Environment
- OS: MacOS
- Python version: 3.11
- pygeoapi version: recent
Additional context
Some more issues with test data in the pull request.