-
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…
-
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…
-
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…
-
We have seen instances of WNM using `properties.content.value` to add descriptive text about a given granule/dataset. (`properties.content.value` should be used for inline data).
Add `properties.ti…
-
See an example at https://github.com/opengeospatial/ogcapi-common/blob/master/core/annex_api_guidelines.adoc
-
Implement OARec client support in Python tooling (OWSLib) and demonstrate workflow using Jupyter notebooks.
-
Feeding OGC API evolution into the BP.
An update of the API BP and the "what's wrong with SDI's" section, possibly also other sections.
situx updated
2 years ago
-
Considering that many users of OGC API - Joins are likely to want to associate the feature collections with data from third-parties, it might be worth looking into supporting some Linked Data approach…
-
Current behaviour of pycsw for rel="xxx" of ogcapi item links is: if a link contains `rel`, then this link is taken
https://github.com/geopython/pycsw/blob/3fefd4e7ac53346e21a259f437316ea97c3004c8/…
-
Quoting from geoserver-devel, @aaime mail:
> The issue with OGC APIs development is that an implementation of a service is an amalgamation
of various small specs, all of which are in different stages…
aaime updated
2 weeks ago