Simple OGC API

In addition to providing deployments of OGC API and STA based on existing open source solutions, a simple prototype of the OGC API should be created that provide simplified features. Some relevant thoughts:

• While the formal INSPIRE Data Specifications require the use of complex features, work has been done on evaluating the usefulness of providing at least some themes using simple features [1]. More detail on the Page on "Repository for action 2017.2 on alternative encodings": https://github.com/INSPIRE-MIF/2017.2
• Initially, the data model could be driven by the database as follows:
  • Collection Name is the name of the DB table
  • Attribute Name is the name of the DB column
• Ideally, in a 2nd phase, it would be possible to define aliases for collection and attribute names via a configuration file
• Filter Encoding for queries is still a work-in-progress, the only filter functionality specified on OGC API Core pertains to the Bounding Box. In order to make the API usable, it would be nice to foresee a bit of the filter functionality in the emerging standard part on filtering
• Database: for the moment PostGIS should be the target DB. Nice would be if JDBC would support conversion of the geometry requests, but do not believe currently possible. One alternative could be the additional support of SpatiaLite or GeoPackage.

[1]: Complex features utilized nested data structures. Simple features consist of a geometry and a flat list of attributes. Often provided in the form of a ShapeFile, whereby the attributes are contained in an integrated excel table