How to make the Green Garden Indicator - Revision history

Frank@tygron.nl: /* Roofs */

2024-01-10T10:32:47Z

Roofs

← Older revision		Revision as of 10:32, 10 January 2024
Line 25:		Line 25:
	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.		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 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\|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.		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)====

Frank@tygron.nl at 10:32, 10 January 2024

2024-01-10T10:32:28Z

← Older revision		Revision as of 10:32, 10 January 2024
Line 25:		Line 25:
	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.		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 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\|Average Overlay]] based on the FLOOR_HEIGHT_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) 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)====

Frank@tygron.nl at 10:31, 10 January 2024

2024-01-10T10:31:56Z

← Older revision		Revision as of 10:31, 10 January 2024
Line 25:		Line 25:
	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.		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 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_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) 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 attribute. This is also a useful tool to visualize the area that will be selected.

	====Garden (paved)====		====Garden (paved)====

Frank@tygron.nl at 10:31, 10 January 2024

2024-01-10T10:31:00Z

← Older revision		Revision as of 10:31, 10 January 2024
Line 1:		Line 1:
	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]].		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.

	==Steps==		==Steps==

Frank@tygron.nl: /* Public Pavement */

2023-02-28T16:06:16Z

Public Pavement

← Older revision		Revision as of 16:06, 28 February 2023
Line 31:		Line 31:

	====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 [[~~3D model~~]] of Leusderkwartier. These parameters included 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)====

Frank@tygron.nl at 12:04, 30 January 2023

2023-01-30T12:04:42Z

← Older revision		Revision as of 12:04, 30 January 2023
Line 25:		Line 25:
	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.		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 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 [[~~3D world~~]] 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_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.

	====Garden (paved)====		====Garden (paved)====

Frank@tygron.nl: /* Implementing the Indicator */

2023-01-27T08:38:22Z

Implementing the Indicator

← Older revision		Revision as of 08:38, 27 January 2023
Line 59:		Line 59:
	* [[How to change Function Values for a Function]], to adjust the effects actions have on Indicators.		* [[How to change Function Values for a Function]], to adjust the effects actions have on Indicators.
	}}		}}
	[[Category:Indicator]]		[[Category:How-to's]][[Category:Indicator]]

Frank@tygron.nl at 08:38, 27 January 2023

2023-01-27T08:38:00Z

← Older revision		Revision as of 08:38, 27 January 2023
Line 59:		Line 59:
	* [[How to change Function Values for a Function]], to adjust the effects actions have on Indicators.		* [[How to change Function Values for a Function]], to adjust the effects actions have on Indicators.
	}}		}}
			[[Category:Indicator]]

Frank@tygron.nl: /* Implementing the Indicator */

2023-01-27T08:36:46Z

Implementing the Indicator

← Older revision		Revision as of 08:36, 27 January 2023
Line 49:		Line 49:
	{{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.
	}}		}}

Maxim@tygron.com at 16:03, 7 October 2022

2022-10-07T16:03:34Z

← Older revision		Revision as of 16:03, 7 October 2022
Line 1:		Line 1:
	This How-to will explain how the [[Indicator]] in the [https://www.tygron.com/en/2020/10/16/neighbourhood-peak-precipitation-mitigation/ ~~Neighbourhood~~ 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]].		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]].

	==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~~ Leusderkwartier and some other ~~neighbourhoods~~ 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.		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.		[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 measure 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 20:
	\|}		\|}
	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.		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 reused.		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 calculated outcomes of the query. The queries used in the Green Garden indicator are summed up below an explanation of their creation.		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 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 [[~~Constructions~~]] in the [[3D world]] 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 [[3D world]] 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.

	====Garden (paved)====		====Garden (paved)====