Measures tutorial - Revision history

Maxim@tygron.com at 13:19, 15 July 2026

2026-07-15T13:19:21Z

← Older revision		Revision as of 13:19, 15 July 2026
Line 75:		Line 75:
	Notice that the effects of the added [[Building]] are taken into account in the spatial calculation of the [[Heat Stress Overlay]].		Notice that the effects of the added [[Building]] are taken into account in the spatial calculation of the [[Heat Stress Overlay]].

	In the top bar of the [[Viewer ~~interface~~]], an option has appeared which allows switching between the "original" and "planned" states of the Project. Click on the "Original" option to see the base situation.		In the top bar of the [[Viewer]] interface, an option has appeared which allows switching between the "original" and "planned" states of the Project. Click on the "Original" option to see the base situation.

	[[File:measure tutorial measure heat stress timestate switch.jpg\|frame\|center\|Option to switch between original and future state.]]		[[File:measure tutorial measure heat stress timestate switch.jpg\|frame\|center\|Option to switch between original and future state.]]

Frank@tygron.nl at 07:21, 14 July 2026

2026-07-14T07:21:35Z

← Older revision		Revision as of 07:21, 14 July 2026
Line 110:		Line 110:
	A number of [[Geo Data]] file formats are supported. Conventionally, most urban plans are available as 2D data.		A number of [[Geo Data]] file formats are supported. Conventionally, most urban plans are available as 2D data.

	'''Important note''': ~~It is also a very common occurrence that plans~~ are provided ~~not~~ as ~~a [[Geo Data]] file, but as an image~~, ~~pdf~~, or other non-data ~~format~~. To load in an urban plan, it must be provided in a data-format which clearly defines features, related meta data, coordinate systems, etc.		'''Important note''': Plans are often provided as images, PDFs, or other non-data formats rather than [[Geo Data]] files. To load in an urban plan, it must be provided in a data-format which clearly defines features, related meta data, coordinate systems, etc.

	{{#ifeq: {{{filetype\|GeoJSON}}}\|GeoJSON\|<!--		{{#ifeq: {{{filetype\|GeoJSON}}}\|GeoJSON\|<!--
Line 426:		Line 426:
	[[File:measure tutorial demo geoplugin imported.jpg\|frame\|center\|The Measure imported via a Geo Plugin.]]		[[File:measure tutorial demo geoplugin imported.jpg\|frame\|center\|The Measure imported via a Geo Plugin.]]

	The result is the urban plan loaded in, mapped by the definition of the [[Geo Plugin]]. This means that without having to select or configure anything ~~specificly~~ for this plan, the plan has been loaded in with all the intended detail.		The result is the urban plan loaded in, mapped by the definition of the [[Geo Plugin]]. This means that without having to select or configure anything specifically for this plan, the plan has been loaded in with all the intended detail.

	{{page break}}		{{page break}}

Frank@tygron.nl at 13:06, 8 July 2026

2026-07-08T13:06:50Z

← Older revision		Revision as of 13:06, 8 July 2026
Line 17:		Line 17:

	==Introduction to Measures==		==Introduction to Measures==
	[[Measure]]s are ~~the data type in~~ the {{software}} ~~most closely aligned with the concept of~~ urban development plans~~. [[Measure]]s are a data type which form a definition for a~~ future ~~plan, potentially consisting of a variety of~~ geographical and non-geographical elements.		[[Measure]]s are the {{software}} data type used for urban development plans, defining future scenarios through various geographical and non-geographical elements.

	==Creating a Measure manually==		==Creating a Measure manually==
Line 61:		Line 61:

	The following things will happen in short order:		The following things will happen in short order:
	# The [[Editor]] will enter a [[Test Run]] mode. ~~This means that anything and everything that defined the~~ base ~~of the~~ Project ~~(the~~ features ~~in the 3D world~~, ~~the~~ calculation models, ~~the options~~ available~~, etc), are~~ now fixed ~~in place~~. All options in the [[Editor]] related to parts of the "[[Current Situation]]" are disabled.		# The [[Editor]] will enter a [[Test Run]] mode. All base Project definitions—including 3D features, calculation models, and available options—are now fixed. All options in the [[Editor]] related to parts of the "[[Current Situation]]" are disabled.
	# A second ~~version of the~~ 3D world ~~is loaded~~ into memory ~~in the {{software}}~~. The original ~~situation is kept as~~ the "current~~" or "original" view. This will represent the~~ situation ~~of the location "now"~~, ~~without any additional future actions taken. A second view is~~ the "maquette" or "planned~~", which represents~~ the ~~state of the same~~ location after ~~actions and interventions have taken place, such as the development of urban plans~~.		# The {{software}} loads a second 3D world version into memory. The 'original' view represents the current situation, while the 'maquette' (or planned) view shows the location after proposed developments.
	# The [[Measure]] will be set to active. ~~It is the request to activate the~~ [[Measure]] ~~that also instructed the {{software}} to start the~~ [[Test Run]], as [[Measure]]s can only be ~~activated as part of~~ a future perspective~~, in a [[Test Run]]~~. Because the [[Measure]] is now active, its effects are applied and any geographical features are visualized.		# The [[Measure]] will be set to active. Activating a [[Measure]] triggers a [[Test Run]], as [[Measure]]s can only be active within a future perspective. Because the [[Measure]] is now active, its effects are applied and any geographical features are visualized.
	# All calculation models are rerun, and take the effects of the [[Measure]] into account.		# All calculation models are rerun, and take the effects of the [[Measure]] into account.

Line 96:		Line 96:
	The future state of the [[Project]] has been cleared. The {{software}} now displays only the base situation again.		The future state of the [[Project]] has been cleared. The {{software}} now displays only the base situation again.

	~~An important primary~~ benefit of ~~using~~ [[Measure]]~~s over other editing options for testing future scenario'~~s is ~~the fact~~ that ~~while it is~~ persistently ~~stored as data in a Project (and therefore need not be recreated whenever it is to be tested), it is not stored as part of~~ the base set of [[Building]]s. This means that plans can be created or loaded in or modified, while leaving the base situation intact.		A key benefit of [[Measure]]s is that they are stored persistently without altering the base set of [[Building]]s. This means that plans can be created or loaded in or modified, while leaving the base situation intact.

	An additional important benefit of [[Measure]]s is their reproducibility. [[Action]]s can be manually planned during a testrun but are not stored in the project data once a testrun ends. This means that if the same plan has to be recalculated or demonstrated, it is difficult and cumbersome to reconstruct the planned actions manually. In contrast, a [[Measure]] can simply be activated or deactivated in full, at will, yielding the exact same future plan every time.		An additional important benefit of [[Measure]]s is their reproducibility. [[Action]]s can be manually planned during a testrun but are not stored in the project data once a testrun ends. This means that if the same plan has to be recalculated or demonstrated, it is difficult and cumbersome to reconstruct the planned actions manually. In contrast, a [[Measure]] can simply be activated or deactivated in full, at will, yielding the exact same future plan every time.
Line 103:		Line 103:

	==Loading in a Measure==		==Loading in a Measure==
	~~Manually creating a~~ [[Measure]] ~~and~~ manually ~~drawing in its various features is technically an option, but rarely the best way to create or use the [[Measure]]s functionality. In most cases~~, ~~the term "[[Measure]]" is used interchangeably with "urban plan". This is because~~ they are ~~mostly used~~ to set up ~~and calculate entire future plans of urban~~ developments. The {{software}} makes it possible to load in [[Geo Data]] files of urban development plans.		While [[Measure]]s can be created manually, they are typically imported as 'urban plans' to efficiently set up complex developments. The {{software}} makes it possible to load in [[Geo Data]] files of urban development plans.

	Before loading in such a file, it is important to emphasize the requirements such a file should meet to be loaded in properly.		Before loading in such a file, it is important to emphasize the requirements such a file should meet to be loaded in properly.
Line 440:		Line 440:

	==Composite spatial features for Measures==		==Composite spatial features for Measures==
	[[Measure]]s ~~can be composed of a variety of Item~~ types. During this tutorial the focus has been on the importing of Buildings, which form the largest part of the majority of urban development plans. However, many plans also contain additional information on aspects of development which are not strictly new [[Building]]s, ~~and related to~~ that~~, elements other than [[Building]]s which can affect the~~ results ~~of calculation models~~.		[[Measure]]s support various item types beyond [[Building]]s, allowing for other developmental elements that influence calculation model results.

	===Buildings===		===Buildings===

Rudolf@tygron.nl: Reverted addition of default_floors remark, as its more likely to cause confusion than resolve issues

2026-07-08T10:51:47Z

Reverted addition of default_floors remark, as its more likely to cause confusion than resolve issues

← Older revision		Revision as of 10:51, 8 July 2026
Line 264:		Line 264:
	* Amount of floors a building has: Rename to DEFAULT_FLOORS		* Amount of floors a building has: Rename to DEFAULT_FLOORS
	* Height of floors: Rename to FLOOR_HEIGHT_M		* Height of floors: Rename to FLOOR_HEIGHT_M
	* Height of loose objects such as trees: Rename to FLOOR_HEIGHT_M ~~(and ensure DEFAULT_FLOORS is set to 1)~~		* Height of loose objects such as trees: Rename to FLOOR_HEIGHT_M

	{{page break}}		{{page break}}

Frank@tygron.nl at 09:43, 8 July 2026

2026-07-08T09:43:39Z

← Older revision		Revision as of 09:43, 8 July 2026
Line 264:		Line 264:
	* Amount of floors a building has: Rename to DEFAULT_FLOORS		* Amount of floors a building has: Rename to DEFAULT_FLOORS
	* Height of floors: Rename to FLOOR_HEIGHT_M		* Height of floors: Rename to FLOOR_HEIGHT_M
	* Height of loose objects such as trees: Rename to FLOOR_HEIGHT_M		* Height of loose objects such as trees: Rename to FLOOR_HEIGHT_M (and ensure DEFAULT_FLOORS is set to 1)

	{{page break}}		{{page break}}

Maxim@tygron.com at 13:36, 6 July 2026

2026-07-06T13:36:36Z

Maxim@tygron.com at 07:32, 2 July 2026

2026-07-02T07:32:33Z

← Older revision		Revision as of 07:32, 2 July 2026
Line 195:		Line 195:

	====Select File====		====Select File====
	A file can be selected from the [[~~Geo Share~~]] or [[Public Share]], or from the local machine.		A file can be selected from the [[GeoShare]] or [[Public Share]], or from the local machine.

	; If you have your own file:		; If you have your own file:

Rudolf@tygron.nl at 11:52, 17 June 2026

2026-06-17T11:52:59Z

← Older revision		Revision as of 11:52, 17 June 2026
Line 4:		Line 4:
	\|additional=A [[Geo Data]] file with information regarding a plan for future urban development. If such a plan is absent, the demo-data of the [[Demo Dxf Import Project]] can be used instead.		\|additional=A [[Geo Data]] file with information regarding a plan for future urban development. If such a plan is absent, the demo-data of the [[Demo Dxf Import Project]] can be used instead.
	**Ideally, such a plan is as a 2D [[Geo Data]] file format. 3D formats are also possible, but are more complex and are not considered in detail in this tutorial.		**Ideally, such a plan is as a 2D [[Geo Data]] file format. 3D formats are also possible, but are more complex and are not considered in detail in this tutorial.

	\|variants info={{#if:{{{filetype\|}}}		\|variants info={{#if:{{{filetype\|}}}
	\| This variant of the tutorial is tuned for {{{filetypename\|}}} files. For a generic version, see the [[Measures tutorial]].		\| This variant of the tutorial is tuned for {{{filetypename\|}}} files. For a generic version, see the [[Measures tutorial]].
	\| The following variants are available for more specifically guided information on those exact filetypes:		\| The following variants are available for more specifically guided information on those exact filetypes:
	** [[Measures tutorial (DXF)]]		* [[Measures tutorial (DXF)]]
	** [[Measures tutorial (GeoJSON)]]		* [[Measures tutorial (GeoJSON)]]
	}}		}}

Rudolf@tygron.nl at 11:50, 17 June 2026

2026-06-17T11:50:51Z

← Older revision		Revision as of 11:50, 17 June 2026
Line 4:		Line 4:
	\|additional=A [[Geo Data]] file with information regarding a plan for future urban development. If such a plan is absent, the demo-data of the [[Demo Dxf Import Project]] can be used instead.		\|additional=A [[Geo Data]] file with information regarding a plan for future urban development. If such a plan is absent, the demo-data of the [[Demo Dxf Import Project]] can be used instead.
	**Ideally, such a plan is as a 2D [[Geo Data]] file format. 3D formats are also possible, but are more complex and are not considered in detail in this tutorial.		**Ideally, such a plan is as a 2D [[Geo Data]] file format. 3D formats are also possible, but are more complex and are not considered in detail in this tutorial.

			\|variants info={{#if:{{{filetype\|}}}
			\| This variant of the tutorial is tuned for {{{filetypename\|}}} files. For a generic version, see the [[Measures tutorial]].
			\| The following variants are available for more specifically guided information on those exact filetypes:
			** [[Measures tutorial (DXF)]]
			** [[Measures tutorial (GeoJSON)]]
			}}

	\| If you have your own Project and urban plan file for that location available, open that Project. If you do not have your own Project or urban plan file available, open the [[Demo Dxf Import Project]].		\| If you have your own Project and urban plan file for that location available, open that Project. If you do not have your own Project or urban plan file available, open the [[Demo Dxf Import Project]].
	\| Ensure a [[Heat Stress Overlay]] is present in the [[Project]]. This is not inherently required for [[Measure]]s, but will be used in this tutorial for demonstrating effects of [[Measure]]s. It does not need to be specifically configured.		\| Ensure a [[Heat Stress Overlay]] is present in the [[Project]]. This is not inherently required for [[Measure]]s, but will be used in this tutorial for demonstrating effects of [[Measure]]s. It does not need to be specifically configured.
	\| Ensure the urban plan file (if any) to be used is available as a local file on your computer. If you do not have your own urban plan file available and you are using the [[Demo Dxf Import Project]], follow the instructions for obtaining the file from the Public Share when prompted instead.		\| Ensure the urban plan file (if any) to be used is available as a local file on your computer. If you do not have your own urban plan file available and you are using the [[Demo Dxf Import Project]], follow the instructions for obtaining the file from the Public Share when prompted instead.
	~~\| {{#if:{{{filetype\|}}}~~
	~~\|This variant of the tutorial is tuned for {{{filetypename\|}}} files. For a generic version, see the [[Measures tutorial]].~~
	~~\|Variant of this tutorial exist for specific filetypes. The following variants are available:~~
	** [[Measures tutorial (DXF)]]
	** [[Measures tutorial (GeoJSON)]]
	}}
	}}		}}

Rudolf@tygron.nl at 11:42, 17 June 2026

2026-06-17T11:42:56Z

← Older revision		Revision as of 11:42, 17 June 2026
Line 6:		Line 6:
	\| If you have your own Project and urban plan file for that location available, open that Project. If you do not have your own Project or urban plan file available, open the [[Demo Dxf Import Project]].		\| If you have your own Project and urban plan file for that location available, open that Project. If you do not have your own Project or urban plan file available, open the [[Demo Dxf Import Project]].
	\| Ensure a [[Heat Stress Overlay]] is present in the [[Project]]. This is not inherently required for [[Measure]]s, but will be used in this tutorial for demonstrating effects of [[Measure]]s. It does not need to be specifically configured.		\| Ensure a [[Heat Stress Overlay]] is present in the [[Project]]. This is not inherently required for [[Measure]]s, but will be used in this tutorial for demonstrating effects of [[Measure]]s. It does not need to be specifically configured.
	\| Ensure the urban plan file to be used is available as a local file on your computer. If you do not have your own urban plan file available and you are using the [[Demo Dxf Import Project]], follow the instructions for obtaining the file from the Public Share when ~~applicable~~.		\| Ensure the urban plan file (if any) to be used is available as a local file on your computer. If you do not have your own urban plan file available and you are using the [[Demo Dxf Import Project]], follow the instructions for obtaining the file from the Public Share when prompted instead.
	\| {{#if:{{{filetype\|}}}		\| {{#if:{{{filetype\|}}}
	\|This variant of the tutorial is tuned for {{{filetypename\|}}} files. For a generic version, see the [[Measures tutorial]].		\|This variant of the tutorial is tuned for {{{filetypename\|}}} files. For a generic version, see the [[Measures tutorial]].

← Older revision		Revision as of 13:36, 6 July 2026
Line 96:		Line 96:
	The future state of the [[Project]] has been cleared. The {{software}} now displays only the base situation again.		The future state of the [[Project]] has been cleared. The {{software}} now displays only the base situation again.

	An important primary benefit of using [[Measure]]s over other editing options for testing future scenario's is the fact that while it is persistently stored as data in a Project (and ~~therefor~~ need not be recreated whenever it is to be tested), it is not stored as part of the base set of [[Building]]s. This means that plans can be created or loaded in or modified, while leaving the base situation intact.		An important primary benefit of using [[Measure]]s over other editing options for testing future scenario's is the fact that while it is persistently stored as data in a Project (and therefore need not be recreated whenever it is to be tested), it is not stored as part of the base set of [[Building]]s. This means that plans can be created or loaded in or modified, while leaving the base situation intact.

	An additional important benefit of [[Measure]]s is their reproducibility. [[Action]]s can be manually planned during a testrun but are not stored in the project data once a testrun ends. This means that if the same plan has to be recalculated or demonstrated, it is difficult and cumbersome to reconstruct the planned actions manually. In contrast, a [[Measure]] can simply be activated or deactivated in full, at will, yielding the exact same future plan every time.		An additional important benefit of [[Measure]]s is their reproducibility. [[Action]]s can be manually planned during a testrun but are not stored in the project data once a testrun ends. This means that if the same plan has to be recalculated or demonstrated, it is difficult and cumbersome to reconstruct the planned actions manually. In contrast, a [[Measure]] can simply be activated or deactivated in full, at will, yielding the exact same future plan every time.
Line 103:		Line 103:

	==Loading in a Measure==		==Loading in a Measure==
	Manually creating a [[Measure]] and manually drawing in its various features is technically an option, but rarely the best way to create or use the [[Measure]]s functionality. In most cases, the term "[[Measure]]" is used ~~interchangabily~~ with "urban plan". This is because they are mostly used to set up and calculate entire future plans of urban developments. The {{software}} makes it possible to load in [[Geo Data]] files of urban development plans.		Manually creating a [[Measure]] and manually drawing in its various features is technically an option, but rarely the best way to create or use the [[Measure]]s functionality. In most cases, the term "[[Measure]]" is used interchangeably with "urban plan". This is because they are mostly used to set up and calculate entire future plans of urban developments. The {{software}} makes it possible to load in [[Geo Data]] files of urban development plans.

	Before loading in such a file, it is important to emphasize the requirements such a file should meet to be loaded in properly.		Before loading in such a file, it is important to emphasize the requirements such a file should meet to be loaded in properly.
Line 135:		Line 135:
	A [[DXF]] file is an open exchange format of commonly used .dwg AutoCAD files. Most CAD packages which can export a .dwg file, can also export the same data as a .dxf file.		A [[DXF]] file is an open exchange format of commonly used .dwg AutoCAD files. Most CAD packages which can export a .dwg file, can also export the same data as a .dxf file.

	For completeness' sake: a DXF file can be formatted with either 2D or 3D data. The {{software}} only supports 2D ~~fata~~ from DXF files.		For completeness' sake: a DXF file can be formatted with either 2D or 3D data. The {{software}} only supports 2D data from DXF files.

	[[File:measure tutorial dxf file example.jpg\|frame\|center\|DXF features and their layers. The layers and styling shown are examples.]]		[[File:measure tutorial dxf file example.jpg\|frame\|center\|DXF features and their layers. The layers and styling shown are examples.]]

	For a plan to be loaded in from a DXF file, it should meet the following requirements:		For a plan to be loaded in from a DXF file, it should meet the following requirements:
	* A single file, of DXF format and with the ~~extention~~ .dxf.		* A single file, of DXF format and with the extension .dxf.
	* A geo location has been set, to relate it to a real world location		* A geo location has been set, to relate it to a real world location
	* All features are grouped into layers. The layer a feature is in indicates the kind of feature it is.		* All features are grouped into layers. The layer a feature is in indicates the kind of feature it is.
	* All features should be drawn as hatches, so that their polygons can be interpreted ~~drectly~~.		* All features should be drawn as hatches, so that their polygons can be interpreted directly.
	* All features are actual features which are a physical part of the intended plan. (No texts, icons, diagrams, etc)		* All features are actual features which are a physical part of the intended plan. (No texts, icons, diagrams, etc)
	* All features should have additional attributes should be set up as BLOCKs with attributes.		* All features should have additional attributes should be set up as BLOCKs with attributes.
Line 239:		Line 239:

	====Filter features====		====Filter features====
	When importing a file, but with the intent of only importing a subset of the included features, it is possible to apply a filter on the features. The filter functions as a ~~whiletlist~~. I.e. when a filter is applied, the features matching the filter are imported. A common occurrence can be that the plan also includes [[Water]], which should not be imported as a [[Building]]. If this is the case, set up a filter which checks the attribute indicating whether or not a feature has water, and ensure that the filter matches features which are ''not'' water.		When importing a file, but with the intent of only importing a subset of the included features, it is possible to apply a filter on the features. The filter functions as a whitelist. I.e. when a filter is applied, the features matching the filter are imported. A common occurrence can be that the plan also includes [[Water]], which should not be imported as a [[Building]]. If this is the case, set up a filter which checks the attribute indicating whether or not a feature has water, and ensure that the filter matches features which are ''not'' water.

	[[File:measure tutorial import 3 filter {{{filetype\|GeoJSON}}}.jpg\|frame\|center\|Example of a filter to exclude data from an import.]]		[[File:measure tutorial import 3 filter {{{filetype\|GeoJSON}}}.jpg\|frame\|center\|Example of a filter to exclude data from an import.]]
Line 283:		Line 283:

	; Function Geo Plugin Matching		; Function Geo Plugin Matching
	: [[~~Geoplugin~~]]s are a more advanced but most preferred route for importing data. They are a separate type of [[Item]] which are specifically a collection of rules to match/translate incoming data to specific [[Item]]s in the {{software}}.		: [[Geo Plugin]]s are a more advanced but most preferred route for importing data. They are a separate type of [[Item]] which are specifically a collection of rules to match/translate incoming data to specific [[Item]]s in the {{software}}.

	{{page break}}		{{page break}}
Line 444:		Line 444:
	===Buildings===		===Buildings===
	; Building		; Building
	: [[Building]]s are the main feature of a [[Measure]]. They~~'re most-~~all built elements in a project area, ranging from ~~appartment~~ complexes to roads to trees.		: [[Building]]s are the main feature of a [[Measure]]. They are almost all built elements in a project area, ranging from apartment complexes to roads to trees.

	:Any place where [[Building]]s are placed, pre-existing [[Building]]s are removed, considered demolished. New [[Building]]s are placed regardless of the ownership situation currently in place.		:Any place where [[Building]]s are placed, pre-existing [[Building]]s are removed, considered demolished. New [[Building]]s are placed regardless of the ownership situation currently in place.