Skip to content

Deploy Vlaamse Water Data Space (VWDS) #4

@brechtvdv

Description

@brechtvdv

1. Use Case Title:

  • Deploy Vlaamse Water Data Space (VWDS)

2. User Story/Scenario:

  • Policymakers on all governmental levels (local, provincial, Flemish)
  • Farmers
  • Industry
  • As a policymaker, what is the state of the water quality in the region?
  • As a company, what is the impact of my emissions on the surrounding water bodies?
  • As a farmer, what is the evolution of the water quality around my parcels?
  • As a data analyst, I need to discover all relevant datasets that have "a" link with water bodies in a certain region.

3. Problem Statement:

  • Relevant data for monitoring water quality is being held by different organizations, making it difficult to provide a holistic view.
  • Automatic discovery will hopefully stimulate organizations to share their data with other organizations and thus solve environmental challenges together through data.

4. Desired Outcome/Goal:

  • based on a certain region, I can discover which water bodies are active
  • I can discover datasets that generate observations about these water bodies
  • I can discover datasets that contain indicators for the water quality on these water bodies (sewer overflow, discharge of waste, number of tourists...)

5. Data Catalog(s) Involved:

6. Data/Service Requirements:

  • Data can be static (water bodies - GIS)
  • Data can be dynamic (LDES)
  • No SHACL currently

7. Discovery Criteria/Filters:

  • Temporal: mainly historical to analyze evolution
  • Spatial: city -> regional
  • Keywords: "water", "overflow", "tourists", "observation"
  • License: Open Data, but also closed

8. Expected Output/Results:

  • What is the expected output or result of the automatic discovery process?
  • Should the output be a list of datasets/services, metadata records, or direct data access?

See 4.

9. Additional Information:

  • Include any other relevant information or context that may be helpful for understanding and implementing this use case.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions