* Added support for table synonyms
* Added new parameters to query and manipulator call
* Changed error types
* Mount volumes to oracle container
* workflow part 2
* workflow part 3
* workflow part 4
* Changed file permissions to 777
* Deleted folder
* Recreated folder
* Changed to official Oracle Docker-Image
* Added Chown user
* back to gvenzl/oracle-xe:latest
* Tried docker-entrypoint-startdb.d
* Added addnab/docker-run-action@v3
* Added port and deamon mode
* next try
* added job.container.network
* next try
* + docker ps
* next try
* using docker run
* next try
* next try
* Changed len of array to 11
* Use sdo_util.from_geojsonfor create and update
* Flake8 changes
* Fixed error with views
* Added crs_transform_spec support
* Without default_crs
* Updated documentation for Oracle Provider
* changes for flake8
* Added crs_transform_spec support to get function
* review changes
* Added configurable SDO operator
This now fixes the issue that the `Accept` header wasn't considered for
format selection.
This adds netcdf as a known mime type in order to be able to test this,
but also for actual clients to use.
Note that if we want to allow other mime types such as `application/x-grib2`,
we also have to add them to `FORMAT_TYPES`.
Fixes#1390
* Refactored get_collection_coverage tests
Using pytest's parametrize mark. This makes it easier to isolate test cases in order to fix the errors that are showing up when running under Python3.8
* Add Python 3.8 to the CI matrix
* Reverted tests back to non-parametrized form
* Dropped Python 3.7 from main github CI workflow
* replaced ubuntu 20.04 with ubuntu 22.04 in CI workflow files
---------
Co-authored-by: Ricardo Garcia Silva <ricardo@kartoza.com>
* Refactored get_collection_coverage tests
Using pytest's parametrize mark. This makes it easier to isolate test cases in order to fix the errors that are showing up when running under Python3.8
* Refactor tests from test_api.py that were failing under Python 3.8
* Fix flake8 issues
* Add Python 3.8 to the CI matrix
* Replaced pandas usage with numpy for datetime
* Reverted tests back to non-parametrized form
* Dropped Python 3.7 from main github CI workflow
---------
Co-authored-by: Ricardo Garcia Silva <ricardo@kartoza.com>
* - added condition to avoid doing operations on the geometry, when the geometry is null (case of records)
* - moving id out of the geometry condition
* - removed commented line
---------
Co-authored-by: doublebyte1 <info@doublebyte.net>
* - on MVTilejson model, set default value on optional fields, so that they are not required.
* - fixed formatting (flake8)
* Update base.py
---------
Co-authored-by: doublebyte1 <info@doublebyte.net>
Co-authored-by: Francesco Bartoli <xbartolone@gmail.com>
* resolving case when lat dimensions are decreasing
CF conventions state only that a "coordinate variable must have values that are strictly monotonic (increasing or decreasing)." In the case of PRISM, the lat coordinates are decreasing. pygeoapi failed due to the lat dimension being empty with existing implementation; this update addresses the issue.
* remove blank space
* resolving case when lat dimensions are decreasing
CF conventions state only that a "coordinate variable must have values that are strictly monotonic (increasing or decreasing)." In the case of PRISM, the lat coordinates are decreasing. pygeoapi failed due to the lat dimension being empty with existing implementation; this update addresses the issue.
* remove blank space
* test decreasing latitude
The new test will now uncover if you can successfully serve data stored on S3 AND test if you can perform a cube query on data with monotonically decreasing latitude coordinates at the same time.
* flake8 py3 fixes
* commented elastic ports in example docker-compose and added warning about opening ports in production
* commented elastic ports in example docker-compose and added warning about opening ports in production
* Update README (issue #1374): Add descriptions for configuration files and fix broken links
* Fix README based on feedback #1376 from issue #1374
* Update README title for better clarity.
* Update the README title while addressing the suggestion.
This is necessary for a more consistent error handling,
where providers can raise ProviderInvalidQueryError for any
`query()` call and the API will correspondingly return a code in the 4xx
range with an error message.
* read from s3 bucket
* fix formatting for build workflow
* add s3fs to provider requirements
* storage options for fsspec
* Revert "storage options for fsspec"
This reverts commit dcfaceedd78d0f0e0dc3e38610958671c27b06a6.
* Revert "storage options for fsspec"
This reverts commit dcfaceedd78d0f0e0dc3e38610958671c27b06a6.
* delete extraneous code for cloud storage read
* update documentation
* add ci testing
* update test suite config file
* update number of collections
* update test query for s3
* ci testing updates
* read from s3 bucket
* fix formatting for build workflow
* add s3fs to provider requirements
* storage options for fsspec
* Revert "storage options for fsspec"
This reverts commit dcfaceedd78d0f0e0dc3e38610958671c27b06a6.
* Revert "storage options for fsspec"
This reverts commit dcfaceedd78d0f0e0dc3e38610958671c27b06a6.
* delete extraneous code for cloud storage read
* update documentation
* add ci testing
* update test suite config file
* update number of collections
* update test query for s3
* ci testing updates
* documentation updates
* config updates
* flake8
* modify sfs3 version
installing requirements threw an error when specifying 2023.6.0 (only identifies up through 2023.1.0). Had added the sfs3 requirement to deal with issues thrown when the 2023.9.0 release came out.
* updated coverages documentation
Ricardo Garcia Silva