-
From Testbed 18 GDC ER Critical Feedack:
> 6. Currently, the user needs to select which way of processing method to follow: the OGC API - Processes or the openEO approach
Ideally the "user" shou…
-
Our [CITE configuration](https://github.com/geopython/pygeoapi/blob/master/tests/cite/cite.config.yml) defines all standards which we support/are compliant to/are an RI for. We need to add an appropr…
-
*Originally created by KayodeBakker (https://github.com/VNG-Realisatie/BAG-Gemeentelijke-wensen-tav-BAG-Bevragingen/issues/544):*
**Beschrijf de bug**
De adresseerbaarobject en pand bevragingsmogeli…
-
Add pipeline(s) to:
- ingest water quantity data (NetCDF), publish to WaterML2
- ingest water quantity data (WaterML), publish to WaterML2
- ingest water quality data (CSV), publish to WaterML2
…
-
The OGC standards for APIs is the globally accepted standard for spatial data. To be able to dynamically include GBIF data into GIS systems and services the GBIF API should be compatible with OGC stan…
-
We recently concluded Testbed 19 and had a work item where we tried to combine openEO and OGC API - Processes. I worked on a visual client https://m-mohr.github.io/gdc-web-editor/
What we realized …
-
Configure the SPS load balancers (for Airflow and OGC API) to only accept SSL connections.
Dependency: SE to provide instructions
-
Now that OGC API Common is on the verge of being released by the SWG to the TC for an adoption vote I wanted to create this issue as a reminder that we need to align Parts 1 & 2 with common. There ar…
-
In Section 3, there is a gaping hole – no reference to the conceptual model that this API realizes.
I acknowledge that such a document does not exist today and that rectifying that is out of scope …
-
See an example at https://github.com/opengeospatial/ogcapi-common/blob/master/core/annex_api_guidelines.adoc