Skip to content

Latest commit

 

History

History
92 lines (76 loc) · 5.24 KB

deployment-brgm_inside.md

File metadata and controls

92 lines (76 loc) · 5.24 KB
Raw

1. Data provider

BRGM (French Geological Survey) OFB (French Office for Biodiversity) through "INSIDE - environmental information systems research center"

2. Thematic scope

  • French Surface Water

    • River gage:
      • INSPIRE EF:EnvironmentalMonitoringFacility
        • OGC API Feature : GeoJSON, GML, JSON-LD
    • River network
      • INSPIRE HY: HydroNode, WatercourseLink, WatercourseLinkSequence, Watercourse
        • OGC API Feature : GeoJSON, GML, JSON-LD (not configured yet)
    • Water flow/height Observation
      • ISO/OGC:Observations & Measurements (INSPIRE D2.9) -> OGC SensorThings API (ST API)
    • URI : references between EF <-> ST API

  • French Hydrogeological data

    • Environmental Groundwater Quantity Monitoring Facility
      • INSPIRE EF:EnvironmentalMonitoringFacility
        • WFS 2 : DONE
        • OGC API Feature -> GeoJSON, GML, JSON-LD : conf on-going for API4INSPIRE project
    • Hydrogeological unit
      • OGC:GroundWaterML2.0 (mapped to INSPIRE GE:Hydrogeology package)
        • WFS 2 : DONE
        • OGC API Feature -> GeoJSON, GML, JSON-LD : conf on-going for API4INSPIRE project
    • Groundwater quantity Observation : groundwater level, temperature, conductivity
      • ISO/OGC:Observations & Measurements (INSPIRE D2.9) -> OGC SensorThings API (STA)
    • URI : references between EF <-> ST API

3. Envisaged use

Deployment and maturation in test environment on top of production system (data instances) within INSPIRE dynamics for API4INSPIRE project APIs will be transfered to production afterwards

4. Requirements classes

TODO SG : X-check with the others

5. Server-side technology

Geoserver 2.17.2 for WFS 2.0 and OGC API Feature

Note : SensorThings API -> Fraunhofer FROST + PostGre/GIS DB

6. Endpoints and client applications

Test Endpoints are not fully opened. However via URI it partially works.

  • Surface water example :
    • Feature Instance
      • https://iddata.eaufrance.fr/id/HydroStation/A021005050?f=application%2Fgeo%2Bjson
      • starting with HydroStation (=River gage) allows to also ask for ?f=application%2Fld%2Bjson, ou ?f=application%2Fgml%2Bxml (works also doing real content negotiation in tools like PostMan or cURL)
      • makes possible to traverse the hydro feature graph via featureOfInterest or ultimateFeatureOfInterest choosing between geojson or GML (JSON-LD not implemented yet)
      • makes it possible to access observation data using hasObservation (will provide application/JSON payload according to OGC ST API )
    • API endpoint : https://iddata.eaufrance.fr/api/hydrometryFAPI/ (not opened yet, will update this page as we go)
  • Ground water example :
    • Feature Instance : TODO SG
    • API endpoint : TODO SG

Clients :

  • Web
    • discussed in API4INSPIRE
    • dev ongoin at BRGM
  • QGIS GML Application Schema toolbox for GML
    • starting to work on allowing to work on GeoJSON (not only GeoJSON serialization but also the 'linked data' part of the plugin)

7. Issues

  • with http://inspire.ec.europa.eu/id/spec/oapif-download/1.0/req/geojson

    • provides harmonised data according to the [IRs for ISDSS -> needs to respect all the semantic work done in INSPIRE before even when moving to REST API providing other serialization as GML
    • "the Web API SHOULD follow the INSPIRE UML-to-GeoJSON encoding rule."

  • need harmonized pattern to provide references to other content in GeoJSON properties for proper client set-up

    • @id/@type/name : JSON-LD flavoured
    • id/type/name : the same but @ neutral
    • @href/@title : GML/XML flavoured (current Geoserver core heuristics for GML -> GeoJSON )

  • Another issue is choice of encoding (corresponding issue: INSPIRE-MIF#53). This is not a blocker issue but real interoperability requires harmonised encoding.