EDR CoverageJSON conformance fixes: time axis and demo data
Overview
changes to confirm to https://schemas.opengis.net/covjson/1.0/coveragejson.json
- time axis changed to values (was interval)
- time axis first in range as expected by https://github.com/Reading-eScience-Centre/leaflet-coverage and dependancies
- parameter description as object - worked with JS visualisation but not validator and covjson playground
- range dataType as float (was number and allowed are float, integer, string) - worked with JS visualisation but not validator and covjson playground
Other:
- typo in edr/query.html template causing issues with first parameter layer
-
- Changes from https://github.com/geopython/pygeoapi/pull/1811 included
Changes shall solve issues using https://covjson.org libraries, also on pygeoapi demo site.
Related Issue / discussion
mainly https://github.com/geopython/pygeoapi/issues/1833 but pull depends on this https://github.com/geopython/pygeoapi/issues/1782
Additional information
changes is not fully backward compatible with potential non-standard client using time as interval (which is breaking coveragejson-schema).
In addition to code changes, coads_sst.nc is fixed. Demo file had COADSX shifted west but not data which looks like this:
Dependency policy (RFC2)
- [X] I have ensured that this PR meets RFC2 requirements
Updates to public demo
- [X] I have ensured that breaking changes to the pygeoapi master demo server have been addressed
- [ ] https://github.com/geopython/demo.pygeoapi.io/blob/master/services/pygeoapi_master/local.config.yml
Contributions and licensing
(as per https://github.com/geopython/pygeoapi/blob/master/CONTRIBUTING.md#contributions-and-licensing)
- [ ] I'd like to contribute [feature X|bugfix Y|docs|something else] to pygeoapi. I confirm that my contributions to pygeoapi will be compatible with the pygeoapi license guidelines at the time of contribution
- [X] I have already previously agreed to the pygeoapi Contributions and Licensing Guidelines
This Pull Request has been inactive for 90 days. As per RFC4, in order to manage maintenance burden, it will be automatically closed in 7 days.
As per RFC4, this Pull Request has been closed due to there being no activity for more than 90 days.