Documentation of APIs for INSPIRE
In order to simplify the often painful process of App Schema configuration, we have created a tutorial based on a simple example that serves to illustrate the various options available without burdoning the user with a complex data model as often utilized in such tutorials. The individual sections of this tutorial are described below
For the purpose of this tutorial, we have created a set of GML featureTypes and dataTypes with various associations between them. These serve to illustrate the various options available within GeoServer App Schema configuration.
This example consists of:
All information available under Example FeatureType and Database
Here two endpoints providing the OGC API - Features output of the Example types:
The base information within the App Schema configuration always follows the same pattern, providing information on the following concepts:
All information available under App Schema Base
Within the Feature Mapping section of the App Schema configuration one must specify the source for each individual element and attribute within the target XML. GeoServer App Schema configuration supports a wide range of options depending on the user requirements, e.g. pertaining to the cardinality of nested types. In the following section, we provide basic configuration options.
All information for basic feature mapping available under Basic Feature Mapping
Feature Chaining is the mechanism for more complex mapping within GeoServer App Schema. This is utilized when one feature includes or references multiple instances of a different featureType or dataType as well as in those cases where two featureTypes are provided individually, but with reference to the other.
All information for mapping utilizing feature chaining available under Feature Chaining Mapping
Usually, feature chaining is used to include additional features with a multiplicity above one within a feature. However, this functionality can also be used to provide a list of xlinks referencing a related feature or alternative resource such as a codelist.
All information for linking features and providing multiple xlinks available under Linking Features and Multiple xlinks
In order to assure that references to other features resolve, care must be taken in the underlying URL scheme. For more information on this topic, please see: