2020.02.03 BRGM Telco

The Data Triangle: 2 Features + 1 Measurement

• Domain Feature
• Sampling Feature
• Observation

Comparing BW & BRGM Data

• BW Data
  • Water Quality for the Rhine
  • Water Quantity for the Rhine
  • Ground water? (ToDo Hylke)
  • Domain models? (ToDo Hylke)
• BRGM Data
  • Water Quantity for the Rhine
    • Features: River gauges! River network?
  • Water Quality for the Rhine (Fairies)
  • Ground Water Quantity
    • Features for Ground Water

Use Case: River sections + EF stations + river gauges Rivers are part of the transport network. River level depends the number of ships that can go through. House-boat owners also like to know when they will fall out of bed due to low water level.

• River network in OGC API - Features
• Water Quantity values in STA
• River Gauges in... ?

Simple features can't have one-to-many links, thus EF doesn't work in SF0. Can we model a river network as SF0? If so:

• EF + Samples + Observations in SensorThings
• Domain Features in OGC API - Features

Fresh JRC publications:

• General-purpose standards, terms and European Commission initiatives : APIs4DGov study — digital government APIs: the road to value-added open API-driven services - Study: https://op.europa.eu/en/publication-detail/-/publication/7144b6b0-0cf9-11ea-8c1f-01aa75ed71a1/language-en
• APIs4DGov API standards and technical specifications: https://data.jrc.ec.europa.eu/dataset/5a431f38-1e2c-449a-898e-34f2a3234c3b

Exposed Data models

• GML
• GeoJSON
• SensorThings JSON

For a client this may be a bit confusing, if GML links to STA. But there is no way around that.

Cross-reference old (WFS2) from new (OAF), so we know what the data source is

We provide docker images with pre-configures APP-Schemas. Question is... one or two?

• Simple Features & Complex features in one or
• Simple Features & Complex features as separate images?