-
-
Notifications
You must be signed in to change notification settings - Fork 269
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
EDR CoverageJSON conformance fixes: time axis and demo data #1814
base: master
Are you sure you want to change the base?
Conversation
Reading from query bbox and reversing the order would not work anyway if not followed by reversing data (which is not cheap and would not do on default. It is visible on the sample data tests/data/coads_sst.nc where the start-stop swapping turn the data upside down.
there is no sense in reading it from source file once again
Edr fixed axis
1. time axis shall be 't' in covjson, for backward compliance it can be set with 'time_axis_covjson' provider variable. if time_axis_covjson is not set the value is read from time_field which has default value read from the source file. 2. time axis is now list of values according to specification and it is now properly rendered on the html view of the query 3. typo in query.html to fix error with first layer being not generated
1.integrated changes from axis fix 2. dataType is float according to schema https://schemas.opengis.net/covjson/1.0/coveragejson.json (number is not valid, float, integer, string are) 3. parameter description as object according to schema https://schemas.opengis.net/covjson/1.0/coveragejson.json
coards_sst.nc data was shifted around 180 deg
Edr fixed axis
* Update compliance for OGC API - Processes * Update introduction.rst
* fix queryables provider handling * fix test
* Manage non-cf-compliant time dimension * Manage datasets without a time dimension * Allow reversed slices also for axes * Convert also metadata to float64 for json output * Use named temporary file to enable netcdf4 engine * Make float64 conversion faster * Add netcdf output to xarray provider * Flake8 fixes * Fix bug when no time axis in data * Use new xarray interface * Add test for zarr dataset without time dimension * Avoid errors if missing long_name * Manage zarr and netcdf output in the same way * Revert "Manage zarr and netcdf output in the same way" This reverts commit 0b09281. * Revert "Add netcdf output to xarray provider" This reverts commit 9f72bf7.
* Added ability for self-hosted token service to be specified. * Update documentation to show the available parameters * Update pygeoapi/provider/esri.py Co-authored-by: Benjamin Webb <[email protected]> * Update pygeoapi/provider/esri.py Co-authored-by: Benjamin Webb <[email protected]> * Update pygeoapi/provider/esri.py Co-authored-by: Benjamin Webb <[email protected]> * Update pygeoapi/provider/esri.py Co-authored-by: Benjamin Webb <[email protected]> * Update pygeoapi/provider/esri.py * Update ogcapi-features.rst --------- Co-authored-by: Benjamin Webb <[email protected]> Co-authored-by: Tom Kralidis <[email protected]>
… need to use the MemoryFile. (geopython#1824)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Please rebase!
# assert time_dict['start'] == '2000-08-16T07:23:42.000000000' | ||
# assert time_dict['stop'] == '2000-12-16T01:20:05.999999996' | ||
# assert time_dict['num'] == 7 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# assert time_dict['start'] == '2000-08-16T07:23:42.000000000' | |
# assert time_dict['stop'] == '2000-12-16T01:20:05.999999996' | |
# assert time_dict['num'] == 7 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be already addressed in upstream pygeoapi
# assert time_dict['start'] == '2000-06-16T10:25:30.000000000' | ||
# assert time_dict['stop'] == '2000-08-16T07:23:42.000000000' | ||
# assert time_dict['num'] == 3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# assert time_dict['start'] == '2000-06-16T10:25:30.000000000' | |
# assert time_dict['stop'] == '2000-08-16T07:23:42.000000000' | |
# assert time_dict['num'] == 3 |
# assert time_dict['start'] == '2000-06-16T10:25:30.000000000' | ||
# assert time_dict['stop'] == '2000-08-16T07:23:42.000000000' | ||
# assert time_dict['num'] == 3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# assert time_dict['start'] == '2000-06-16T10:25:30.000000000' | |
# assert time_dict['stop'] == '2000-08-16T07:23:42.000000000' | |
# assert time_dict['num'] == 3 |
self.time_axis_covjson = provider_def.get('time_axis_covjson') \ | ||
or self.time_field |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the point of adding this? Can we add a test case that uses this field. Suggest to potentially rename in pygeoapi, but will defer to @tomkralidis. This addition should also be noted in the docs (OACoverages and OAEDR
time dimension in configuration just for backward compatibility, it is expected in covjson to be 't'
Overview
changes to confirm to https://schemas.opengis.net/covjson/1.0/coveragejson.json
Other:
Changes shall solve issues using https://covjson.org libraries, also on pygeoapi demo site.
Related Issue / discussion
mainly #1833
but pull depends on this
#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)
Updates to public demo
Contributions and licensing
(as per https://github.com/geopython/pygeoapi/blob/master/CONTRIBUTING.md#contributions-and-licensing)