How to make the Green Garden Indicator: Difference between revisions

From Tygron Support wiki
Jump to navigation Jump to search
No edit summary
 
(24 intermediate revisions by 4 users not shown)
Line 1: Line 1:
==Introduction==
This How-to will explain how the [[Indicator]] in the [https://www.tygron.com/en/2020/10/16/neighbourhood-peak-precipitation-mitigation/ Neighborhood Green Garden Meter] use case was made and which steps were needed to create it. To successfully implement this indicator, knowledge about the [[Tygron_Query_Language | Tygron Query Language]] and the use of [[Excel|Excel in the Tygron platform]] is required.
This wiki How-To will try to explain to you, how to make your indicator and more importantly which steps are needed to make it work.
The steps in this wiki-how are based upon the case study of the [https://www.tygron.com/en/2020/10/16/neighbourhood-peak-precipitation-mitigation/|Neighbourhood Green Garden Meter]


==Steps==
==Steps==
===First Steps===
===First steps===
The first step of designing the indicator existed out of defining the boundary conditions. Hereby you need to clearly define what do you want to get out of your indicator, in other words, what do you want it to show. Once this is clear you can start working towards shaping your indicator. The reason Amersfoort was chosen as the location for the digital twin, was because of the availability of data of neighbourhood composition. The neighbourhood Leusderskwartier and some other neighbourhoods where mapped by the municipality of Amersfoort in a previous Case Study about urban precipitation water.
The first step of designing the indicator existed out of defining the boundary conditions. Hereby you need to clearly define what do you want to get out of your indicator, in other words, what do you want it to show. Once this is clear you can start working towards shaping your indicator. The reason Amersfoort was chosen as the location for the digital twin, was because of the availability of data of neighborhood composition. The neighborhood Leusderkwartier and some other neighborhoods where mapped by the municipality of Amersfoort in a previous. The last step of the use case was implementing the measures so during a session it would be possible to adjust the gardens.
[https://www.stowa.nl/sites/default/files/assets/PUBLICATIES/Publicaties%202000-2010/Publicaties%202005-2009/STOWA%202009-02%20RIONED.pdf Case Study] about urban precipitation water.
[[File:Use_case_piek.png|thumb|500px|right|Example of garden improvemenent in Leusderkwartier, Amersfoort.]]   
[[File:Use_case_piek.png|thumb|500px|right|Example of garden improvemenent in Leusderkwartier, Amersfoort.]]   
===Setting Up the Parameters===
===Setting up the parameters===
This case study by the municipality of Amersfoort gave a rough direction to the values the indicator had to show and also helped in the categorisation of the parameters. For the green garden use case, the five parameters that the indicator intends to show are:
This case study by the municipality of Amersfoort gave a rough direction to the values the indicator had to show and also helped in the categorization of the parameters. For the green garden use case, the five parameters that the indicator intends to measure are:
{| class="wikitable"
{| class="wikitable"
|+ Parameterisation of the Neighbourhood
|+ Parameterisation of the Neighbourhood
Line 20: Line 19:
| Public Pavement || Public Green
| Public Pavement || Public Green
|}
|}
Hereby, the goal is that the values of the parameters are expressed in percentages of the total measures surface of the digital twin.
Hereby, the goal is that the values of the parameters are expressed in percentages of the total to be measured area of the digital twin.
After defining the boundary conditions the next step is to translate the parameters into working [[queries]]. This is the step where the indicator gets shaped and defined. To understand the functioning of indicators better it can be useful to look at the set-up of other simular indicators, the Green Garden indicator was inspired partially on the [[Housing_(Indicator)|Housing Indicator]]. This indicator shows some overlap in its fundamentals with the green garden indicator and was therefor chosen and some of its frameworks could be recycled.  
After defining the boundary conditions the next step is to translate the parameters into working [[queries]]. This is the step where the indicator gets shaped and defined. To understand the functioning of indicators better it can be useful to look at the set-up of other similar indicators, the Green Garden indicator was inspired partially on the [[Housing_(Indicator)|Housing Indicator]]. This indicator shows some overlap in its fundamentals with the green garden indicator and was therefor chosen and some of its frameworks could be reused.


==Queries==  
==Queries==  
The final step of realising the indicator was defining the queries. An import tool with helping to shape indicators is the [[query tool]], this tool can also directly shows the generated values of the query. The queries used in the Green Garden indicator are summed up in this chapter with an explanation of their formation.  
The final step of realizing the indicator was defining the queries. An import tool with helping to shape indicators is the [[query tool]]. This tool can also directly shows the calculated outcomes of the query. The queries used in the Green Garden indicator are summed up below an explanation of their creation.  
====Roofs====  
====Roofs====  
The roofs were the first surface that was shaped in the indicator. The first step in defying the indicator was setting up the query for the roofs. To obtain this information from the platform, the query selects all the structures in the digital twin with at least one floor (hence:FLOOR_HEIGH_M) and a minimum floor height of 2m. This floor height was obtained from the model, by making an [[Average_Overlay|average overlay]] based on the FLOOR_HEIGH_M attribute. This is also a useful tool to visualize the area that will be selected.  
The first step in shaping the indicator was setting up the query for the roofs. To obtain this information from the platform, the query selects all the [[Buildings]] in the [[project]] with at least one floor (hence:[[Floor height m (Function Value)|FLOOR_HEIGHT_M]]) and a minimum floor height of 2m. This floor height was obtained from the model, by making an [[Average_Overlay|Average Overlay]] based on the [[Floor height m (Function Value)|FLOOR_HEIGHT_M]] attribute. This is also a useful tool to visualize the area that will be selected.


====Garden (Paved)====  
====Garden (paved)====  
The paved garden parameter is based on a new object function made for this Use Case. This parameter is based on a new object function designed for the green garden use case. Gardens in the platform are standardised and do not yet make a difference between ''green'' and ''paved'' gardens, so this query obtains the area value of all the ''normal'' gardens. Green gardens are currently the default gardens of the {{software}}. So for this garden, a new garden type was created by editing [[function values]], .  
The paved garden parameter is based on a new [[Function]] made for this use case. Gardens in the {{software}} are by default green gardens, so this query obtains the area value of all the gardens. For paved gardens, a new garden type was created by duplicating a [[Function]] and editing the [[function values]], .  


====Public Pavement====  
====Public Pavement====  
The third parameter is public pavement, this includes all the public ''hard'' surfaces, like sidewalks and roads. The query, therefore, is a SUM statement in Excel with all the public hard surfaces used in the digital twin of Leuderkwartier. These parameters included the values of bridge, road, paved area and intersections.  
The third parameter is public pavement, this includes all the public ''hard'' surfaces, like sidewalks and roads. The query, therefore, is a SUM statement in Excel with all the public hard surfaces used in the [[project]] of Leusderkwartier. These parameters included values of bridge, road, paved area and intersections.


====Garden (Green)====  
====Garden (green)====  
As explained in [[How_to_make_your_own_indicator#Garden_(Paved)|garden (paved)]] green gardens are currently the standard garden of the platform. This query, therefore, obtains the lotsize of all the gardens in a model. Subsequently, the lotsize value of the paved garden is substracted of the total. This is done because paved gardens are still categorised in the garden category.  
As explained above, green gardens are currently the default type of garden in the {{software}}. This query, therefore, obtains the lotsize of all the gardens in the model. Subsequently, the area value of the paved garden is substracted of this total.


====Public Green====  
====Public Green====  
The last category is public green, this category is also a sum function. This parameter sums the lotzises of the categories parks and nature and also add the area of terrain that has no function, this is often greenfield land. The query of greenfield land first defines everything that has a lotsize, so is categorised and defines the total area of the model. By subtracting the total area with total lotsize, the difference will show the greenfield land.  
The last category is public green, this category is also a sum function. This parameter sums the surfaces of the categories parks and nature and also add the area of terrain that has no function, this is often grassland. By subtracting the total area with the total built environment, the difference will show the undeveloped land.  
[[File:Querries.JPG|framed|left|The Queries used in the Green Garden meter.]]
[[File:Querie2.JPG|framed|left|The Queries used in the Green Garden meter.]]
<br clear=all>
<br clear=all>
===Defining the output===
===Defining the output===
The visible output of the indicator uses standardised HTML scripts for indicators. The values in the {{software}} are, as said, percentages, these percentages are obtained by dividing each value with the total area of the map. During a session, measures are possible, like transforming a paved garden into a green garden, because the indicator both measures the current and maquette data, the difference between those two parameters can show possible progress and shows what the consequences of a measure can be.  
The visible output of the indicator uses a HTML table to show the output. The values in the output are percentages, these percentages are obtained by dividing each value with the total area of the project. In the project [[Measures]] were created. During a [[session]], for example transforming a paved garden into a green garden could be done. Because the indicator both calculates the current and future design, the difference between those two parameters shows possible progress and what consequences of a certain measure can be.  


==Implementing the Indicator==
The last step was using the step in a scenario session, therefor I needed as previously said adjust the standard garden of the platform, to make a distinction between paved and green gardens. The [[How_to_change_Function_Values_for_a_Function|function]] values of the paved garden are now similar to those of an urban square. In the scenario created for the Amersfoort Green Garden Use Case, it was possible for inhabitants and the municipality to ''upgrade'' their paved gardens to green garden.


{{article end
{{article end
|notes=
|notes=
|seealso=
|seealso=
* [[Indicator]]
* [[Indicator]]
* [[Practice#Adding, removing and adjusting an indicator|Adjusting an Indicator]]
* [[Practice#Adding, removing and adjusting an indicator|Adjusting an Indicator]]
|howtos=
* [[How to configure a Query for an Excel Indicator]]
* [[How to implement an Excel Indicator]]
* [[How to manually adjust Indicators in Excel]]
* [[How to use the Query Tool to test queries from an Excel Indicator spreadsheet]]
* [[How to change Function Values for a Function]], to adjust the effects actions have on Indicators.
}}
}}
[[Category:How-to's]][[Category:Indicator]]

Latest revision as of 10:32, 10 January 2024

This How-to will explain how the Indicator in the Neighborhood Green Garden Meter use case was made and which steps were needed to create it. To successfully implement this indicator, knowledge about the Tygron Query Language and the use of Excel in the Tygron platform is required.

Steps

First steps

The first step of designing the indicator existed out of defining the boundary conditions. Hereby you need to clearly define what do you want to get out of your indicator, in other words, what do you want it to show. Once this is clear you can start working towards shaping your indicator. The reason Amersfoort was chosen as the location for the digital twin, was because of the availability of data of neighborhood composition. The neighborhood Leusderkwartier and some other neighborhoods where mapped by the municipality of Amersfoort in a previous. The last step of the use case was implementing the measures so during a session it would be possible to adjust the gardens. Case Study about urban precipitation water.

Example of garden improvemenent in Leusderkwartier, Amersfoort.

Setting up the parameters

This case study by the municipality of Amersfoort gave a rough direction to the values the indicator had to show and also helped in the categorization of the parameters. For the green garden use case, the five parameters that the indicator intends to measure are:

Parameterisation of the Neighbourhood
Paved Areas Green Areas
Roofs
Garden (Paved) Garden (Green)
Public Pavement Public Green

Hereby, the goal is that the values of the parameters are expressed in percentages of the total to be measured area of the digital twin. After defining the boundary conditions the next step is to translate the parameters into working queries. This is the step where the indicator gets shaped and defined. To understand the functioning of indicators better it can be useful to look at the set-up of other similar indicators, the Green Garden indicator was inspired partially on the Housing Indicator. This indicator shows some overlap in its fundamentals with the green garden indicator and was therefor chosen and some of its frameworks could be reused.

Queries

The final step of realizing the indicator was defining the queries. An import tool with helping to shape indicators is the query tool. This tool can also directly shows the calculated outcomes of the query. The queries used in the Green Garden indicator are summed up below an explanation of their creation.

Roofs

The first step in shaping the indicator was setting up the query for the roofs. To obtain this information from the platform, the query selects all the Buildings in the project with at least one floor (hence:FLOOR_HEIGHT_M) and a minimum floor height of 2m. This floor height was obtained from the model, by making an Average Overlay based on the FLOOR_HEIGHT_M attribute. This is also a useful tool to visualize the area that will be selected.

Garden (paved)

The paved garden parameter is based on a new Function made for this use case. Gardens in the Tygron Platform are by default green gardens, so this query obtains the area value of all the gardens. For paved gardens, a new garden type was created by duplicating a Function and editing the function values, .

Public Pavement

The third parameter is public pavement, this includes all the public hard surfaces, like sidewalks and roads. The query, therefore, is a SUM statement in Excel with all the public hard surfaces used in the project of Leusderkwartier. These parameters included values of bridge, road, paved area and intersections.

Garden (green)

As explained above, green gardens are currently the default type of garden in the Tygron Platform. This query, therefore, obtains the lotsize of all the gardens in the model. Subsequently, the area value of the paved garden is substracted of this total.

Public Green

The last category is public green, this category is also a sum function. This parameter sums the surfaces of the categories parks and nature and also add the area of terrain that has no function, this is often grassland. By subtracting the total area with the total built environment, the difference will show the undeveloped land.

The Queries used in the Green Garden meter.


Defining the output

The visible output of the indicator uses a HTML table to show the output. The values in the output are percentages, these percentages are obtained by dividing each value with the total area of the project. In the project Measures were created. During a session, for example transforming a paved garden into a green garden could be done. Because the indicator both calculates the current and future design, the difference between those two parameters shows possible progress and what consequences of a certain measure can be.

Implementing the Indicator

The last step was using the step in a scenario session, therefor I needed as previously said adjust the standard garden of the platform, to make a distinction between paved and green gardens. The function values of the paved garden are now similar to those of an urban square. In the scenario created for the Amersfoort Green Garden Use Case, it was possible for inhabitants and the municipality to upgrade their paved gardens to green garden.