...
Author | |
---|---|
Technical Contacts | |
Version | 01.91 |
Date | August 2023March 2024 |
Table of Contents |
---|
...
In order to import the data into the GeoServer database and to allow the highest possible flexibility for the data provider, the O2A specification for GeoCSV (.sdi.csv) format was agreed upon.
Example files for media data:
View file | ||||
---|---|---|---|---|
|
View file | ||||
---|---|---|---|---|
|
View file | ||||
---|---|---|---|---|
|
View file | ||||
---|---|---|---|---|
|
View file | ||||
---|---|---|---|---|
|
View file | ||||
---|---|---|---|---|
|
Various options for data exchange are possible, such as shared projects in the cloud or , git repositories or OAI-PMH.
For inquiries about exchange location and database ingestion frequency, please reach out to the GeoServer team.
...
You can find out more about this topic in the O2A Data Product Configuration SOP. The corresponding configuration repository is O2A Spatial Data Products. For access and further permissions, please contact one of the technical contacts.
...
These data provisioning configuration files, along with their respective arrangements, are built on a predefined structure. You can find the documentation in the O2A Data Product Configuration SOP.
The repository for sharing your configuration files is located in the O2A Spatial Data Products repository. For access and further permissions, please contact one of the technical contacts.
...
View file | ||||
---|---|---|---|---|
|
The vef documentation Metadata Templates documentation contains a comprehensive list of all functions available for displaying data. In case anything is missing, please get in touch with the viewer team.
...
The required functions and all other template functions are available in the vef Metadata Templates documentation.
Example:
View file | ||||
---|---|---|---|---|
|
...
Query Parameter | Query Value | Required | Note |
---|---|---|---|
site | gallery | ✔️ | fixed query value |
ows | <ows_uri> | ✔️ | identifier used to find the gallery configuration in the catalogue (i.e., https://marine-data.de/rest/search/) via the resources.uri field. |
layer | <layer_name> | ✔️ | depend on the name of the layer in the GeoServer database |
filter | <cql-filter> | ✔️ | required to select a subset of the layer table, i.e., based on dataset, event, author etc. CQL and ECQL syntax can be are used (more infos) |
shareID | <persistent_identifier> | ❌ | if the persistent_identifier field is blank or does not exist in the gallery mapping file, the name field serves as the identifier, or if not present, a combination of location and time is used |
Example:
A gallery mapping file needs to be present to enable flexible data structures and provide full functionality inside the gallery. It maps the dataset vocabulary (values in mapping dict) to the gallery vocabulary (keys in mapping dict) and is required for each GeoServer media layer.
All fields inside the mapping file are optional. If any field is missing, its corresponding functionality will not be enabled in the gallery.
Example: View file
Like all other configuration files, the gallery mapping file is part of the configuration repository and should be provided in O2A Spatial Data Products.
...