You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe a single harmonisation project that is used to transform one data set
Implementation state
The tracing transformation project is currently in progress.
Use Case Scope
The harmonized tracing datasets will facilitate cross-border tracing of water contamination to estimate and limit the effects of the pollution as well to find the source of the pollution. By back tracing, possible sources of the pollution can be identified and search for the origin can be guided. By tracing downstream, the possible spreading of the pollution can be predicted, and measures can be taken (e.g. closing valves in sewer networks) to limit this spreading or take actions to prevent extensive damage. All this is done by the Graph Tracing Engine developed for the Flanders Environmental Agency (VMM).
Spatial Scope / Priority Scope
Belgium: Regional data from Flanders, Wallonia, Brussels
Cross border to various identified countries.
Source Schema and Format
Format: Shapefiles | GML | GeoJSON
Source Dataset(s)
The datasets being transformed are hydro networks, sewer networks and locations of interest, which include polluting sources and protected sites.
Dataset
Scope
Type
Description
Water network
Regional, national
node-edge network
Edges connect to each other through nodes that are shared between multiple edges as begin- and endpoint. The direction from the point referred in the begin point attribute to the one referred in the end point attribute will be considered by the GTE as the dominant flow direction, the downstream flow direction.
Sewer network
Regional
node-edge network
Edges connect to each other through nodes that are shared between multiple edges as begin- and endpoint. The direction from the point referred in the begin point attribute to the one referred in the end point attribute will be considered by the GTE as the dominant flow direction, the downstream flow direction.
Locations of interest
National
Point
Locations of interest such as production facilities, represented by point geometry, to be projected onto the network as a simple point reference
Locations of interest
National
Polygon
Locations of interest represented by polygon geometry configured in the GTE as overlay areas, and referenced linearly onto the networks.
Source Data Size
+50MB
Target Schemas
The target schemas are derived from the tracing data model, and divided into two major schemas, Hydro and Sewer network schemas.
Tracing Data Model
The Tracing Data Model is based on the INSPIRE Generic Network Model which defines the application schema for network data themes, in this case, both the hydro and sewer networks.
Tracing_HydroNetwork Target schema
The hydro-network model is an extension of the network model. To derive a Tracing data model, the hydro-network model was extended and can be found here
The Tracing target schema was developed using a Hale studio schema definition files, from which a Geopackage template was derived to transform surface water networks into the Tracing Watercourse datasets.
Tracing_SewerNetwork Data Model
The sewer-network model is an extension of the network model. To derive a Tracing data model, the sewer-network model was extended and can be found here
The Tracing target schema was developed using a Hale studio schema definition files, from which a Geopackage template was derived to transform sewer networks into the Tracing Sewer Network datasets.
Transformed Data size
The transformed datasets are in Geopackage encoding, and for each region not exceeding 65MB. A Geopackage includes for example, a hydro-nodes layer, an edges layer, Codelist properties, Default and Voidable properties tables/layers.
Target Data set resources
Prior to publishing, target datasets can be found here
Effort / Time Spent
Provide information on the amount of time you needed to create the transformation project. (in hh:mm)
Transformation Project
The notebooks, python files, data models and hale studio schema definition files and alignment project files can be found here
The text was updated successfully, but these errors were encountered:
Describe a single harmonisation project that is used to transform one data set
Implementation state
The tracing transformation project is currently in progress.
Use Case Scope
The harmonized tracing datasets will facilitate cross-border tracing of water contamination to estimate and limit the effects of the pollution as well to find the source of the pollution. By back tracing, possible sources of the pollution can be identified and search for the origin can be guided. By tracing downstream, the possible spreading of the pollution can be predicted, and measures can be taken (e.g. closing valves in sewer networks) to limit this spreading or take actions to prevent extensive damage. All this is done by the Graph Tracing Engine developed for the Flanders Environmental Agency (VMM).
Spatial Scope / Priority Scope
Source Schema and Format
Source Dataset(s)
The datasets being transformed are hydro networks, sewer networks and locations of interest, which include polluting sources and protected sites.
Source Data Size
Target Schemas
The target schemas are derived from the tracing data model, and divided into two major schemas, Hydro and Sewer network schemas.
Tracing Data Model
The Tracing Data Model is based on the INSPIRE Generic Network Model which defines the application schema for network data themes, in this case, both the hydro and sewer networks.
Tracing_HydroNetwork Target schema
The hydro-network model is an extension of the network model. To derive a Tracing data model, the hydro-network model was extended and can be found here
The Tracing target schema was developed using a Hale studio schema definition files, from which a Geopackage template was derived to transform surface water networks into the Tracing Watercourse datasets.
Tracing_SewerNetwork Data Model
The sewer-network model is an extension of the network model. To derive a Tracing data model, the sewer-network model was extended and can be found here
The Tracing target schema was developed using a Hale studio schema definition files, from which a Geopackage template was derived to transform sewer networks into the Tracing Sewer Network datasets.
Transformed Data size
The transformed datasets are in Geopackage encoding, and for each region not exceeding 65MB. A Geopackage includes for example, a hydro-nodes layer, an edges layer, Codelist properties, Default and Voidable properties tables/layers.
Target Data set resources
Prior to publishing, target datasets can be found here
Effort / Time Spent
Provide information on the amount of time you needed to create the transformation project. (in hh:mm)
Transformation Project
The notebooks, python files, data models and hale studio schema definition files and alignment project files can be found here
The text was updated successfully, but these errors were encountered: