Data to Viewer

Summary

This document addresses The following SOP address the procedure of having your data product published in VEF-based viewers such as the Marine Data Viewer ("Viewer"). Goal of these SOP is to provide automated ways of keeping your data product up-to-date – after only having one initial consultation. On SDI side, setting up a new data flow is one-time work, subsequently provided updates/changes will get incorporated automatically.

Either you provide your data (product) directly as an OGC Web Service (OWS) – most probably a Web Mapping Service (WMS) and in a VEF-based viewer (e.g. for MareHUB). There are slightly different procedures depending – which can easily be integrated into the Viewer. Or the O2A Spatial Data Infrastructure (SDI) will host an OWS based on your data. For the latter case, the "flow path" through the SOP schema depends on the type of your data (raster, vector) , the desired type/structure of OWS and your preferred way of providing/exchanging (files, services, Pangaea) it to the SDI. All of them get illustrated in a schema and have lists of tasks to be done.

Both schema and lists are colour-coded. Everything blue depicts a process inside or a part of our Spatial Data Infrastructure (SDI). Everything orange depicts stuff outside of our SDI related to raster data. Everything green depicts stuff outside of the SDI related to vector data. Red elements indicate that there are specifications to follow or some sort of input is needed. Black are data-type independent elements.

...

Schema

Image Removed

Raster data

via GeoTIFF (.sdi.tif)

• Format your raster data as GeoTIFF files, according to our Spatial Data Specifications → https://spaces.awi.de/x/Ckv-Eg
• Put it on an exchange space
  • Preferably Isilon, damspace
  • apply our Exchange Folder Specifications → https://spaces.awi.de/x/aAUtFQ
    
• Give reading access to our technical user gisadm:gisadms 
• Contact us!
  • Additional topics we will ask you about
    
    • metadata
      
    • metadata structure/representation in right sightbar
    • Affected Viewer instances (default integration into viewer configuration)
• SDI-internal steps
  • Harvesting
  • Database
  • Harmonization
  • Spatial Web Services
  • Service Catalog (ServCat)
  • VEF-based viewer(s)
  • We get back to you via email
• To update the published data: add/remove/update GeoTIFF files in the exchange folder, wait one day for our harvester to apply the changes

via Spatial Web Service (OGC WMS/WCS)

• Publish whatever you like as a WMS/WCS
  • best case: with activated DescribeLayer/DescribeCoverage
• Contact us!
  • Additional topics we will ask you about:
    • OGC Service Metadata
    • metadata structure/representation in right sightbar
    • Affected Viewer instances (default integration into viewer configuration)

Vector data

via GeoCSV (.sdi.tab)

• Format your vector data as GeoCSV files, according to our Spatial Data Specifications → https://spaces.awi.de/x/Bkv-Eg
• Put it on an exchange space
  • Preferably: Isilon, damspace
  • apply our Exchange Folder Specifications → https://spaces.awi.de/x/aAUtFQ
• Give reading access to our technical user gisadm:gisadms 
• Contact us!
  • Provide information about exchange space
  • Provide Mapping information, if necessary → https://spaces.awi.de/x/f4XIF → https://spaces.awi.de/x/CyBGF
  • Additional topics we will ask you about
    
    • OGC Service Metadata
    • metadata structure/representation in right sightbar
    • Affected Viewer instances (default integration into viewer config)
• SDI-internal workflow
  • Harvesting
  • Database
  • Harmonization
  • Spatial Web Services
  • Service Catalog (ServCat)
  • VEF-based viewer(s)
  • We get back to you via email
• To update the published data: add/remove/update GeoCSV and metadata files in the exchange folder, wait one day for our harvester to apply the changes.

via Spatial Web Service (OGC WMS/WFS)

• Publish whatever you like as a WMS/WFS
  • best case: with activated DescribeLayer/DescribeFeatureType
• Contact us!
  • Additional topics we will ask you about:
    • OGC Service Metadata
    • metadata structure/representation in right sightbar
    • Affected Viewer instances (default integration into viewer configuration)

via Sensor Observation Service (OGC SOS)

• Publish whatever you like as an SOS
• Contact us!
  • Additional topics we will ask you about:
    • if necessary provide Mapping information → https://spaces.awi.de/x/f4XIF → https://spaces.awi.de/x/CyBGF
    • metadata structure/representation in right sightbar
    • Affected Viewer instances (default integration into viewer configuration)
• SDI-internal workflow
  • Harvesting
  • Database
  • Harmonization
  • Spatial Web Services
  • Service Catalog (ServCat)
  • VEF-based viewer(s)
  • We get back to you via email

via PANGAEA

...

• Provide Pangaea Queries and/or DOI lists
• Provide Mapping information, if necessary → https://spaces.awi.de/x/f4XIF → https://spaces.awi.de/x/CyBGF
• Additional topics we will ask you about
  
  • exact WMS content ← product definition
    
  • OGC Service Metadata
  • metadata structure/representation in right sightbar
  • Affected Viewer instances (default integration into viewer config)

...

• Harvesting
• Database
• Harmonization
• Spatial Web Services
• Service Catalog (ServCat)
• VEF-based viewer(s)
• We get back to you via email

data exchange with the O2A SDI. See the Exchange Protocol section for details.

This document does not provide information on SDI-internal processing/architecture. This is covered here: Technical Infrastructure.

Schema

This schema shows possible data flows from your data to the Viewer. It is divided into SDI-external elements (depicted as black elements) and SDI-internal elements (depicted as blue elements). The former describe states/processes you will have to take care of after the Initial Consultation, the latter are designed to work fully automated and will be configured by the administrators (see Contact).

           Image Added

Initial Consultation

Make Contact. Based on a joint assessment of the data situation and the desired outcome we will decide upon an appropriate SOP flow path. The following questions will be discussed.

1. From where to where?
   
   • What data should be visualised?
   • How should it look like in the Viewer?
2. How to realise? Common decisions on
   
   • Exchange protocol
   • Viewer integration

Exchange Protocol Choices

Via Self-Hosted OWS

• Supported OWS types
  • OGC Web Map Service (WMS)
  • OGC Web Feature Service (WFS)

Via PANGAEA

• Relevant file types

  • O2A specification for PANGAEA sources (.sdi.pangaea.lst) (necessary)
  • O2A specification for Mapping Files (.sdi.mapping.tab) (if applicable)
• Supported exchange location (see Exchange Folder Specification)
  • Git repository
    • e.g. via Helmholtz GitLab → DataHub
  • Isilon project folder

Via O2A Spatial Files

• Supported file types
  • data
    • O2A specification for GeoCSV (.sdi.tab)
    • O2A specification for GeoTIFF (.sdi.tif)
  • vocabulary harmonisation (if applicable)
    • O2A specification for Mapping Files (.sdi.mapping.tab)
• Supported exchange location (see Exchange Folder Specification)
  
  • Git repository
    • e.g. via Helmholtz GitLab → DataHub
  • Isilon project folder

Viewer Integration Topics

• LayerTree positioning
• Layer styling (e.g. colours)
• Metadata representation in popups and sidebar

Contact

...