* bbox query parameter support for EDR cube queries
As per Requirement A.61 C, D and E, as well as A.7 in the EDR standard.
* bbox queries support z-axis dimension
* xarray-edr provider cube query support, edr cube unit tests
---------
Co-authored-by: Peter Garnæs <pga@dmi.dk>
* Render template if specified in config and provide example config
Update linked_data.py
Merge branch 'geopython:master' into jsonld
Rended from json-ld output
Render jinja2 json-ld template from json-ld output instead of json output
Merge branch 'geopython:master' into jsonld
Add documentation
- Add documentation
- Add test to workflow
Update pygeoapi-test-config.yml
Update test_api.py
Update api.py
Update linked_data.py
Move template declaration in configuration
Update docs
Update configuration.rst
Update configuration.rst
* Updates per requested changes
* Fix spelling
* Fix json-ld template pathing
* Remove root path for the templating
* Move json-ld template from api.py
- Move single item json-ld templating to inside geojson2jsonld
- Reformat json-ld configuration for context and item_template to children of json-ld block
- Update docs and example configurations
* Fix ref
* Use FileSystemLoader to control template search path
search for templates is in order of `template_paths` list
* s/json-ld/linked-data/ig
rename json-ld to more generic name
* feat(OGRProvider): allow to use 'geom_field' in the config for OGR provider
* docs: show an example of using OGR for publishing data from a PostGIS database
* fix: does not check for empty geometry in this PR
* docs: add back ESRIJSON source_type
* fix(geom2schemageo): use only x,y dimensions when rendering GeoShape
Ignore possible third dimension when unpacking the coordinates of shapely
geometrical object in function 'geom2schemageo'. This fixes the ValueError
thrown when requesting features in JSON-LD format with 3D geometries.
* fixing unpacking of multipoint coordinates
As for the 'layer' attribute, the 'id_field' should be specified in the
configuration file for the OGRProvider. The 'get' method of a OGRProvider
instance (e.g. when requesting a single feature) needs the feature ID when
setting an attribute filter on the layer. If the 'id_field' attribute is
omitted in the configuration file, the error thrown is more explicit.
* Edr Providers can raise Request Entity Too Large HTTP status
* Rename and move entity too large exception to provider base module
* Get request too large exception message from base exception message
* Rename request to large exception
---------
Co-authored-by: Peter Garnæs <pga@dmi.dk>
Even Rouault