-
Actually, I'm not sure that accelerating the process of creating standards is a good idea.
In OGC API Common we believe that going too fast in OGC API Features ignoring the possibility to create a c…
-
It seems that there is a timeout issue with the Validator, specifically related to the OGC API - Features Test Suite.
The OGC validator fails to complete validation and the issue is impacting the I…
-
Dear helpdesk,
We are trying to validate our OGC API Features module linked to GeoServer.
However, afte…
-
Support for Filtered WFS-layers was added in #228, however the support wasn't added to OGC API Features layers. Currently a filter configured as documented here https://oskari.org/documentation/exampl…
-
Specs : https://ogcapi.ogc.org/features/
-
This public comment is respectfully submitted by the Web Service Technical Panel (WSTP) of the Defence Geospatial Information Working Group (DGIWG). This comment addresses an identified issue where *…
-
There seems to be recurring SWG standardization efforts being created that do not take into account existing work (either within OGC itself and outside OGC SWGs as well), which introduces "competing" …
-
The [OGC API - Styles](https://docs.ogc.org/DRAFTS/20-009.html) *Draft* Standard enables map servers, clients as well as visual style editors, to manage and fetch styles. The styles consist of symboli…
-
As a user, I want to submit the details of my processing graph or UDP directly to the EarthCODE catalogue from the CDSE openEO environment.
**Technical Implementation**
A new entry can be added to …
-
OGC-API Common and OGC-API EDR both are tolerant of various ways of specifying coordinate systems, leading to variations in the implementations, like:
- `crs: WGS84`
- `crs: CRS84`
- `crs: EPSG:4…