Page History
...
Configuration files:Anchor toml toml - TOML → https://toml.io
Layer StylingAnchor sld-links sld-links - OGC SLD specification → https://www.ogc.org/standard/sld/
- GeoServer SLD reference
- https://docs.geoserver.org/2.21.x/en/user/styling/sld/index.html (release currently used by O2A SDI )
- https://docs.geoserver.org/main/en/user/styling/sld/index.html (current stable release)
VEF Metadata Templates: Markdown-based (→ documentation coming soon)Anchor vef-meta-temp vef-meta-temp
VEF Mapping Files: JSON-basedAnchor vef-map-files vef-map-files - Gallery Mapping (→ documentation coming soon)
- Filter Mapping → https://spaces.awi.de/x/TQLeGwFilter Mapping (→ documentation coming soon)
Version 0.1
Repository Schema
...
- VEF Metadata Template files (
*.md), to configure presentation of your data in popups and sidebar → (documentation coming soon) - VEF Filter Mapping files (
*.mapping.json) → (documentation coming soon) - VEF Gallery Mapping files (
*.mapping.json) → → see https://spaces.awi.de/x/TQLeGwVEF Gallery Mapping files (*.mapping.json) → (documentation coming soon)
In general files with specific names inside resources folders will get used automatically. These names are:
...
A service folder refers to a workspace within a GeoServer instance/label and results in an OWS of the same name. Additionally an OWS has a human-readable title, an abstract and optional keywords – just like a scientific paper. These metadata can be specified in <label>/<service>/owner.service.toml. There's also a <service>/_resources subfolder which can be used to provide resources which should be shared among multiple layers of this service (see section on resource handling).
| section | key | value type | required/optional/default | value description |
|---|---|---|---|---|
SERVICE | title | string | yes | human-readable title of the workspace (used as title for all contained OWS: WMS, WFS, WCS) |
abstract | string | yes | abstract, describing the service's content. VEF (Marine Data Viewer) supports Markdown URL representation (<http://www.marine-data.de>, [Marine Data](http://www.marine-data.de>)) and HTML (like <br><br>, <a></a>) | |
keywords | string list | no | ||
owner.layer.tomlAnchor owner.layer owner.layer
| Anchor | ||||
|---|---|---|---|---|
|
A layer folder results in a layer of the same name withing the OWS representet by its parent service-layer folder. A layer has a human-readable title, an abstract and optional keywords – just like a scientific paper. These metadata can be specified in <label>/<service>/<layer>/owner.layer.toml. Additionally default and alternative styles (referencing SLD files in <label>/_styles/) and VEF resources can be specified. If desired the default mechanism of auto-deploying changes to the GeoServer (styles, metadata) and/or VEF (recoures) can be deactivated.
| section | key | value type | required/optional/default | value description |
|---|---|---|---|---|
LAYER | title | string | yes | human-readable title of the layer |
abstract | string | yes | abstract, describing the layer's content. VEF (Marine Data Viewer) supports Markdown URL representation (<http://www.marine-data.de>, [Marine Data](http://www.marine-data.de>)) and HTML (like <br><br>, <a></a>) | |
keywords | string list | no | ||
LAYER_SETTINGS | style_default | string | yes | name of the SLD file (including file extension) to use as default style. The filename need to match the actual style name. SLD files need to go here: <label>/_styles/*.sld |
style_alternatives | string list | no | names of SLD files (including file extension) to use as alternative styles. The filename need to match the actual style name. SLD files need to go here: | |
RESOURCES | gallery_mapping | string | no (defaults togallery.mapping.json) | name of gallery mapping file. Only required if deviating from |
filter_mapping | string | no (defaults tofilter.mapping.json) | name of gallery mapping file. Only required if deviating from | |
popup | string | no (defaults topopup.md) | nam of popup metadata template file. Only required if deviating from | |
sidebar | string | no (defaults tosidebar.md) | name of sidebar metadata template file. Only required if deviating from | |
AUTODEPLOY | resources | boolean | no (defaults to true) | whether to autodeploy (accepted merge requests will trigger instant updates in AWI-hosted VEF-based viewers, applying changes in resource files) changes for this layer to production. If set to false, triggering updates otherwise is encouraged. Talk to your SDI admins! |
geoserver | boolean | no (defaults to true) | whether to autodeploy (accepted merge requests will trigger instant updates in O2A GeoServers, applying changes in styles, service/layer metadata) changes for this layer in production. If set to false, triggering updates otherwise is encouraged. Talk to your SDI admins! |
_other Folder
The _other subfolder is the place to store resources for services/layers which are not hosted in the GeoServer part of the O2A SDI to be used within VEF-based viewers. This subtree only contains resource files (see above for specs), owner.urls files but neither SLD nor any other configuration files.
...
Overview
Content Tools