RE:PEAT: Difference between revisions

From Tygron Support wiki
Jump to navigation Jump to search
No edit summary
mNo edit summary
Line 116: Line 116:
The files can be loaded in by dragging them into the engine, and opting to load them in as areas. Do not merge the polygons. Use the name attribute as the name for the data, and load in all the attributes listed above.
The files can be loaded in by dragging them into the engine, and opting to load them in as areas. Do not merge the polygons. Use the name attribute as the name for the data, and load in all the attributes listed above.


After the data has been loaded in, additional data has to be created.  
After the data has been loaded in, additional data has to be created. In the menu for areas, the option for creating Border Areas can be selected. This will create the border areas between the various level areas, for calculations of required weirs. The borders have to be created between areas with the "PEILGEB" attribute. The attribute "BORDER" must be added to the new areas. The width of the border area should be set to 30 meters. (The width can also be set to a different value to allow for level areas which are further apart, but this will require adjusting the CONFIG_AUTOMATIC_BORDER_WIDTH global accordingly.)


===Exact data calculations===
===Exact data calculations===

Revision as of 10:31, 21 March 2017

This article is a stub.

RE:PEAT is a project created by the Hoogheemraadschap De Stichtse Rijnlanden, who are a water authority in the Netherlands. The project is concerned with the problems surrounding subsidence in areas with significant peat soil, and the means to remedy or work around the problems surrounding it.

General information

The project is currently only available in Dutch. It has 2 levels.

Stakeholders

There are 4 stakeholders present in this project:

Municipality: The municipality is the government body who is concerned with the general care for the area, including but not limited to the livability for the residents, the viability of the agricultural sector, and the affordability of the maintenance of the local infrastructure.

Residents: The residents are the citizens in the area, who are concerned with the livability of the area. Their concerns are with their standards of living, and the costs associated with them.

Farmers: The farmers are the commercial/agricultural party concerned with revenue, but secondarily also with the quality of their land, both for their crops and the general livability.

Water authority: The water authority is the party in control of the water levels in the area, and with that the main tool for combating subsidence. However, they are also responsible for the costs associated with water management, and other hydrological aspects such as water safety and water quality.

Indicators

Overlays

Applying the template

Required data

To make use of this template, two GeoJSON files are expected:

"Percelen" file, for defining plots within an area with discrete data, in the form of "plots".

Attribute Description Example Remark
NAAM The name of the plot. PERCEEL: 1008 This attribute is not loaded in as attribute, but will be the name of the loaded in data.
MVH_NAP Height of the ground level, measured from Amsterdam Ordnance Datum (NAP). 0.45
KLEIDEKM The depth of the clay soil layer. 0.45
GLG The average lowest ground water level, in meters as measured from ground level. 0.75 This water level is used by the engine to calculate actual ground water levels, in combination with water level changes.
GHG The average highest ground water level, in meters as measured from ground level. 0.35 This water level is used by the engine to calculate actual ground water levels, in combination with water level changes.
PEILGEB_N The identification number of the level area which the plot belongs to. 268
BODEM_N The type of soil primarily present in the plot 1 = peat, 2 = clay, 3 = clay on peat, 4 = sand 3
SUBSIDENCE Whether this plot is subject to subsidence. 1 When this attribute is not present, subsidence is calculated. When this attribute is present and it's value is 0, subsidence is not calculated. When this attribute is present and it's value is not 0, subsidence is calculated.
PEIL_LAGER The level area to which excess water is pumped off. 268 If this value is not present, water is presumed to be pumped out of the plan area.

"Peilgebieden" file, for grouping plots together and setting of water levels, in the form of "level areas".

Attribute Description Example Remark
PEIL_NAAM The name of the level area. PEILGEBIED: PG0268 This attribute is not loaded in as attribute, but will be the name of the loaded in data.
GEM_PEIL The average water level in this level area, measured from Amsterdam Ordnance Datum (NAP). -2.90
PEILGEB_N The depth of the clay soil layer. 0.45
URBANIZATION How urban this level area is. Lower values are a more urban area. Higher values are a more rural area. 3

Setting up a new project

Wizard

In the main menu, select the option "Start new project". Choose a name for the new project, and select the RE:PEAT template as the template to use. Select the area you wish to include in your project, and select "Generate Map". Depending on the size and complexity of the selected area, loading in an area may take some time. This step is completed when the 3D world becomes visible.

Loading in data

The GeoJSON files can now be loaded in. It's not required to load them in in any particular order, but loading in the "percelen" file first and the "peilgebieden" file second is preferred. The files can be loaded in by dragging them into the engine, and opting to load them in as areas. Do not merge the polygons. Use the name attribute as the name for the data, and load in all the attributes listed above.

After the data has been loaded in, additional data has to be created. In the menu for areas, the option for creating Border Areas can be selected. This will create the border areas between the various level areas, for calculations of required weirs. The borders have to be created between areas with the "PEILGEB" attribute. The attribute "BORDER" must be added to the new areas. The width of the border area should be set to 30 meters. (The width can also be set to a different value to allow for level areas which are further apart, but this will require adjusting the CONFIG_AUTOMATIC_BORDER_WIDTH global accordingly.)

Exact data calculations