Basics tutorial - Revision history

Maxim@tygron.com at 15:54, 9 June 2026

2026-06-09T15:54:41Z

Frank@tygron.nl at 07:50, 9 June 2026

2026-06-09T07:50:42Z

← Older revision		Revision as of 07:50, 9 June 2026
Line 112:		Line 112:
	Click on "Generate". This will start the data import process on the {{software}} server.		Click on "Generate". This will start the data import process on the {{software}} server.

	[[File:basics-editor-project-newproject-loader-small.jpg\|frame\|center\|The {{software~~\|engine~~}} is retrieving all the neccesary data. You can see the progress locally.]]		[[File:basics-editor-project-newproject-loader-small.jpg\|frame\|center\|The {{software server}} is retrieving all the neccesary data. You can see the progress locally.]]

	After the generation process completes, the editor environment and [[3D Visualization]] will load.		After the generation process completes, the editor environment and [[3D Visualization]] will load.

Rudolf@tygron.nl: /* Recalculation mode */

2026-05-04T08:27:01Z

Recalculation mode

← Older revision		Revision as of 08:27, 4 May 2026
Line 601:		Line 601:
	Using the information learned in this tutorial, and with an initial [[Project]] created specifically for experimentation, try the following editing actions and explore the results.		Using the information learned in this tutorial, and with an initial [[Project]] created specifically for experimentation, try the following editing actions and explore the results.

	# Hover over the Overlays button in the ribbon so that the drop-down opens. In the list of Overlay categories, select "Topographical", and then click on "Digital Terrain Model". Explore the resulting [[Digital Terrain Model Overlay]]		# Hover over the Overlays button in the ribbon so that the drop-down opens. In the list of Overlay categories, select "Topographical", and then click on "Digital Terrain Model".
	# Hover over the Indicators button in the ribbon so that the drop-down opens. In the list of folders, select "Urban Planning", and then click on "Density". Explore the resulting indicator added in the [[top bar]].		#* If the Project is not set to automatically recalculate, use the recalculation dropdown and click on "Update now".
			#* Explore the resulting [[Digital Terrain Model Overlay]].
			# Hover over the Indicators button in the ribbon so that the drop-down opens. In the list of folders, select "Urban Planning", and then click on "Density".
			#* If the Project is not set to automatically recalculate, use the recalculation dropdown and click on "Update now".
			#* Explore the resulting indicator added in the [[top bar]].

	{{Tutorial completed		{{Tutorial completed

Frank@tygron.nl at 14:16, 13 April 2026

2026-04-13T14:16:34Z

← Older revision		Revision as of 14:16, 13 April 2026
Line 228:		Line 228:

	* The data present in the [[Project]] is made to be more representative of reality.		* The data present in the [[Project]] is made to be more representative of reality.
	* Calculation models are added to analyse the data, resulting in information on a variety of theme's such as [[Heat Overlay\|heat]], [[Water Overlay\|water]], and [[Traffic Noise Overlay\|traffic effects]].		* Calculation models are added to analyse the data, resulting in information on a variety of theme's such as [[Heat Stress Overlay\|heat]], [[Water Overlay\|water]], and [[Traffic Noise Overlay\|traffic effects]].
	* Tools for adding changes, from individual options for free-form drawing to complete urban plans which can be implemented integrally, are available for exploring and analyzing potential scenarios.		* Tools for adding changes, from individual options for free-form drawing to complete urban plans which can be implemented integrally, are available for exploring and analyzing potential scenarios.

Frank@tygron.nl at 13:39, 13 April 2026

2026-04-13T13:39:10Z

Frank@tygron.nl at 14:53, 6 March 2026

2026-03-06T14:53:34Z

← Older revision		Revision as of 14:53, 6 March 2026
Line 233:		Line 233:
	===Structure of the editor===		===Structure of the editor===
	The editor can be considered to consist of 2 levels of interface:		The editor can be considered to consist of 2 levels of interface:
	* The 3D visualization and related [[~~user interface~~]] in the center of the screen, with mostly dark-colored interface elements.		* The 3D visualization and related [[User Interface]] in the center of the screen, with mostly dark-colored interface elements.
	* The surrounding/overlaid [[editor\|editing interface]], with mostly bright-colored interface elements.		* The surrounding/overlaid [[editor\|editing interface]], with mostly bright-colored interface elements.

	[[File:basics-editor-interacting-editor.jpg\|frame\|center\|The editor, with the bright editing interface elements at the top, and the darker [[~~user interface~~]] over the [[3D Visualization]].]]		[[File:basics-editor-interacting-editor.jpg\|frame\|center\|The editor, with the bright editing interface elements at the top, and the darker [[User Interface]] over the [[3D Visualization]].]]
	{{page_break}}		{{page_break}}

Line 251:		Line 251:
	{{page_break}}		{{page_break}}

	There are multiple camera modes available, which can be switched between. Find the camera icon at the top right side of the [[~~user interface~~]].		There are multiple camera modes available, which can be switched between. Find the camera icon at the top right side of the [[User Interface]].

	[[File:basics-editor-interacting-camera-icon.jpg\|frame\|center\|The camera icon allows switching between camera modes.]]		[[File:basics-editor-interacting-camera-icon.jpg\|frame\|center\|The camera icon allows switching between camera modes.]]

Frank@tygron.nl at 14:50, 6 March 2026

2026-03-06T14:50:35Z

← Older revision		Revision as of 14:50, 6 March 2026
Line 1:		Line 1:
	{{tutorial prerequisites		{{tutorial prerequisites
	\|time=3 hours		\|time=3 hours
	\|domain=Ensure your ~~organisation~~'s [[account management\|domain administrator]] has created an account for you. This must be an account with at least "EDITOR" rights.		\|domain=Ensure your organization's [[account management\|domain administrator]] has created an account for you. This must be an account with at least "EDITOR" rights.
	\|project=This tutorial will involve the creation of a new [[Project]]. This [[Project]] is intended for experimentation with the features the {{software}} offers.		\|project=This tutorial will involve the creation of a new [[Project]]. This [[Project]] is intended for experimentation with the features the {{software}} offers.
	}}		}}

Frank@tygron.nl: /* Areas */

2026-03-05T12:45:08Z

Areas

← Older revision		Revision as of 12:45, 5 March 2026
Line 531:		Line 531:
	[[File:basics-editor-essentials-areas.jpg\|thumb\|right\|[[Area]]s are custom data, and not present in a [[Project]] by default. But they offer a flexible extra spatial data layer.]]		[[File:basics-editor-essentials-areas.jpg\|thumb\|right\|[[Area]]s are custom data, and not present in a [[Project]] by default. But they offer a flexible extra spatial data layer.]]
	{{main\|Area}}		{{main\|Area}}
	[[Area]]s are a vague but useful datatype which can best be summarized as "arbitrary [[Polygon]]s with [[Attribute]]s". They are shapes which can be placed anywhere in the [[Project ~~Area~~]] to represent data. They have no inherent meaning in the {{software}}, but can be used for any number of definitions which do not fit neatly into other categories of data provided. Some uses include:		[[Area]]s are a vague but useful datatype which can best be summarized as "arbitrary [[Polygon]]s with [[Attribute]]s". They are shapes which can be placed anywhere in the [[Project area]] to represent data. They have no inherent meaning in the {{software}}, but can be used for any number of definitions which do not fit neatly into other categories of data provided. Some uses include:
	* Indicating locations of spatial interest, such as archeology of subsoil contamination		* Indicating locations of spatial interest, such as archeology of subsoil contamination
	* Creating additional/alternative spatial subdivisions with which to calculate data or aggregate results, instead of on a [[Neighborhood]] level.		* Creating additional/alternative spatial subdivisions with which to calculate data or aggregate results, instead of on a [[Neighborhood]] level.

Frank@tygron.nl: /* Neighborhoods */

2026-03-05T12:44:53Z

Neighborhoods

← Older revision		Revision as of 12:44, 5 March 2026
Line 521:		Line 521:
	[[File:basics-editor-essentials-neighborhoods.jpg\|thumb\|right\|[[Neighborhood]]s are present in just about all [[Project]]s, and form usable administrative subdivisions of any [[Project]]'s extent.]]		[[File:basics-editor-essentials-neighborhoods.jpg\|thumb\|right\|[[Neighborhood]]s are present in just about all [[Project]]s, and form usable administrative subdivisions of any [[Project]]'s extent.]]
	{{main\|Neighborhoods}}		{{main\|Neighborhoods}}
	[[Neighborhood]]s have already been briefly touched upon, but warrant some additional attention. [[Neighborhood]]s are administrative subdivisions. They are generally used as a default way to divide the [[Project ~~Area~~]] up into smaller sections to aggregate results for, so that any results or changes become more manageable. In addition, for [[Project]]s in the Netherlands the CBS datasource will also provide a wide range of demographic attributes about the [[Neighborhood]]s when a new [[Project]] is generated.		[[Neighborhood]]s have already been briefly touched upon, but warrant some additional attention. [[Neighborhood]]s are administrative subdivisions. They are generally used as a default way to divide the [[Project area]] into smaller sections to aggregate results for, so that any results or changes become more manageable. In addition, for [[Project]]s in the Netherlands the CBS datasource will also provide a wide range of demographic attributes about the [[Neighborhood]]s when a new [[Project]] is generated.

	Every location has at most one [[Neighborhood]], and the entire [[Project area]] should be covered by the complete set of known [[Neighborhood]]s. It is possible for a location to not be covered by a [[Neighborhood]], but this is not a usual situation.		Every location has at most one [[Neighborhood]], and the entire [[Project area]] should be covered by the complete set of known [[Neighborhood]]s. It is possible for a location to not be covered by a [[Neighborhood]], but this is not a usual situation.

Frank@tygron.nl: /* Neighborhoods */

2026-03-05T12:44:30Z

Neighborhoods

← Older revision		Revision as of 12:44, 5 March 2026
Line 523:		Line 523:
	[[Neighborhood]]s have already been briefly touched upon, but warrant some additional attention. [[Neighborhood]]s are administrative subdivisions. They are generally used as a default way to divide the [[Project Area]] up into smaller sections to aggregate results for, so that any results or changes become more manageable. In addition, for [[Project]]s in the Netherlands the CBS datasource will also provide a wide range of demographic attributes about the [[Neighborhood]]s when a new [[Project]] is generated.		[[Neighborhood]]s have already been briefly touched upon, but warrant some additional attention. [[Neighborhood]]s are administrative subdivisions. They are generally used as a default way to divide the [[Project Area]] up into smaller sections to aggregate results for, so that any results or changes become more manageable. In addition, for [[Project]]s in the Netherlands the CBS datasource will also provide a wide range of demographic attributes about the [[Neighborhood]]s when a new [[Project]] is generated.

	Every location has at most one [[Neighborhood]], and the entire [[Project ~~Area~~]] should be covered by the complete set of known [[Neighborhood]]s. It is possible for a location to not be covered by a [[Neighborhood]], but this is not a usual situation.		Every location has at most one [[Neighborhood]], and the entire [[Project area]] should be covered by the complete set of known [[Neighborhood]]s. It is possible for a location to not be covered by a [[Neighborhood]], but this is not a usual situation.

	[[Neighborhood]]s can be visualized using a [[Neighborhoods Overlay]].		[[Neighborhood]]s can be visualized using a [[Neighborhoods Overlay]].

← Older revision		Revision as of 15:54, 9 June 2026
Line 257:		Line 257:
	Change the camera mode by clicking on the icon, and again try to move, rotate, and zoom the camera.		Change the camera mode by clicking on the icon, and again try to move, rotate, and zoom the camera.

	Move the focal point of the camera as far to the side as possible. Notice that when the edge of the [[Project ~~area~~]] is reached, it is not possible to move any further. The camera is always directed at a location inside the [[Project ~~area~~]].		Move the focal point of the camera as far to the side as possible. Notice that when the edge of the [[Project map]] is reached, it is not possible to move any further. The camera is always directed at a location inside the [[Project map]].

	[[File:basics-editor-interacting-camera-edge.jpg\|frame\|center\|The camera cannot move beyond the [[Project ~~Area~~]]s edge.]]		[[File:basics-editor-interacting-camera-edge.jpg\|frame\|center\|The camera cannot move beyond the [[Project map]]s edge.]]
	{{page_break}}		{{page_break}}

Line 321:		Line 321:
	[[File:basics-editor-editing-cs.jpg\|frame\|center\|A colored "Current Situation" tab means it is selected.]]		[[File:basics-editor-editing-cs.jpg\|frame\|center\|A colored "Current Situation" tab means it is selected.]]

	Directly underneath the tabs in the [[ribbon]] is an overview of the data and tools which are relevant for the selected tab. In this case, the "Current Situation" provides access to data like the [[Building]]s in the [[Project ~~Area~~]], terrain information such as [[elevation model\|elevation]] and [[Terrain Type]]s, and the [[Overlay]]s which can be viewed.		Directly underneath the tabs in the [[ribbon]] is an overview of the data and tools which are relevant for the selected tab. In this case, the "Current Situation" provides access to data like the [[Building]]s in the [[Project map]], terrain information such as [[elevation model\|elevation]] and [[Terrain Type]]s, and the [[Overlay]]s which can be viewed.

	[[File:basics-editor-editing-cs-ribbon.jpg\|frame\|center\|Options in the ribbon offer access to specific data types and functions of the editor.]]		[[File:basics-editor-editing-cs-ribbon.jpg\|frame\|center\|Options in the ribbon offer access to specific data types and functions of the editor.]]
Line 521:		Line 521:
	[[File:basics-editor-essentials-neighborhoods.jpg\|thumb\|right\|[[Neighborhood]]s are present in just about all [[Project]]s, and form usable administrative subdivisions of any [[Project]]'s extent.]]		[[File:basics-editor-essentials-neighborhoods.jpg\|thumb\|right\|[[Neighborhood]]s are present in just about all [[Project]]s, and form usable administrative subdivisions of any [[Project]]'s extent.]]
	{{main\|Neighborhoods}}		{{main\|Neighborhoods}}
	[[Neighborhood]]s have already been briefly touched upon, but warrant some additional attention. [[Neighborhood]]s are administrative subdivisions. They are generally used as a default way to divide the [[Project ~~area~~]] into smaller sections to aggregate results for, so that any results or changes become more manageable. In addition, for [[Project]]s in the Netherlands the CBS datasource will also provide a wide range of demographic attributes about the [[Neighborhood]]s when a new [[Project]] is generated.		[[Neighborhood]]s have already been briefly touched upon, but warrant some additional attention. [[Neighborhood]]s are administrative subdivisions. They are generally used as a default way to divide the [[Project map]] into smaller sections to aggregate results for, so that any results or changes become more manageable. In addition, for [[Project]]s in the Netherlands the CBS datasource will also provide a wide range of demographic attributes about the [[Neighborhood]]s when a new [[Project]] is generated.

	Every location has at most one [[Neighborhood]], and the entire [[Project ~~area~~]] should be covered by the complete set of known [[Neighborhood]]s. It is possible for a location to not be covered by a [[Neighborhood]], but this is not a usual situation.		Every location has at most one [[Neighborhood]], and the entire [[Project map]] should be covered by the complete set of known [[Neighborhood]]s. It is possible for a location to not be covered by a [[Neighborhood]], but this is not a usual situation.

	[[Neighborhood]]s can be visualized using a [[Neighborhoods Overlay]].		[[Neighborhood]]s can be visualized using a [[Neighborhoods Overlay]].
Line 531:		Line 531:
	[[File:basics-editor-essentials-areas.jpg\|thumb\|right\|[[Area]]s are custom data, and not present in a [[Project]] by default. But they offer a flexible extra spatial data layer.]]		[[File:basics-editor-essentials-areas.jpg\|thumb\|right\|[[Area]]s are custom data, and not present in a [[Project]] by default. But they offer a flexible extra spatial data layer.]]
	{{main\|Area}}		{{main\|Area}}
	[[Area]]s are a vague but useful datatype which can best be summarized as "arbitrary [[Polygon]]s with [[Attribute]]s". They are shapes which can be placed anywhere in the [[Project ~~area~~]] to represent data. They have no inherent meaning in the {{software}}, but can be used for any number of definitions which do not fit neatly into other categories of data provided. Some uses include:		[[Area]]s are a vague but useful datatype which can best be summarized as "arbitrary [[Polygon]]s with [[Attribute]]s". They are shapes which can be placed anywhere in the [[Project map]] to represent data. They have no inherent meaning in the {{software}}, but can be used for any number of definitions which do not fit neatly into other categories of data provided. Some uses include:
	* Indicating locations of spatial interest, such as archeology of subsoil contamination		* Indicating locations of spatial interest, such as archeology of subsoil contamination
	* Creating additional/alternative spatial subdivisions with which to calculate data or aggregate results, instead of on a [[Neighborhood]] level.		* Creating additional/alternative spatial subdivisions with which to calculate data or aggregate results, instead of on a [[Neighborhood]] level.
Line 543:		Line 543:
	[[Overlays]]s have already been touched upon in a previous step, but are one of the most important types of data in any [[Project]]. As a first principle, they are map layers which display information already present in a [[Session]], but which may not be directly visible in the [[3D Visualization]] as is, such as the division of [[Neighborhood]]s.		[[Overlays]]s have already been touched upon in a previous step, but are one of the most important types of data in any [[Project]]. As a first principle, they are map layers which display information already present in a [[Session]], but which may not be directly visible in the [[3D Visualization]] as is, such as the division of [[Neighborhood]]s.

	[[Overlay]]s can also perform spatial calculations. These [[Overlay]]s are known as [[Grid Overlay]]s, as they function by interpreting the [[Project ~~area~~]] as a grid consisting of a large number of cells. A calculation is then run for every individual cell.		[[Overlay]]s can also perform spatial calculations. These [[Overlay]]s are known as [[Grid Overlay]]s, as they function by interpreting the [[Project map]] as a grid consisting of a large number of cells. A calculation is then run for every individual cell.

	Some [[Grid Overlay]]s are relatively simple, such as the [[Digital Surface Model Overlay\|Elevation Overlay]]s or the [[Average Overlay\|Average Overlay]]. Other [[Grid Overlay]]s are the practical implementations of fully-fledged calculation models, such as the [[Water Overlay]] or the [[Heat Stress Overlay]].		Some [[Grid Overlay]]s are relatively simple, such as the [[Digital Surface Model Overlay\|Elevation Overlay]]s or the [[Average Overlay\|Average Overlay]]. Other [[Grid Overlay]]s are the practical implementations of fully-fledged calculation models, such as the [[Water Overlay]] or the [[Heat Stress Overlay]].

	[[Overlay]]s are a form of data which is part of the [[Session]], but are not themselves geographical data in the [[Project ~~area~~]]. Instead they are definitions for available map layers and calculation models, the output of which are geographically visible.		[[Overlay]]s are a form of data which is part of the [[Session]], but are not themselves geographical data in the [[Project map]]. Instead they are definitions for available map layers and calculation models, the output of which are geographically visible.
	{{clear}}{{page_break}}		{{clear}}{{page_break}}

← Older revision		Revision as of 13:39, 13 April 2026
Line 535:		Line 535:
	* Creating additional/alternative spatial subdivisions with which to calculate data or aggregate results, instead of on a [[Neighborhood]] level.		* Creating additional/alternative spatial subdivisions with which to calculate data or aggregate results, instead of on a [[Neighborhood]] level.
	* Defining geographical policy areas for, for example, the [[Water Module]]. This includes [[Water area (Water Overlay)\|Water Area]]s and [[Sewer area (Water Overlay)\|Sewer area]]s.		* Defining geographical policy areas for, for example, the [[Water Module]]. This includes [[Water area (Water Overlay)\|Water Area]]s and [[Sewer area (Water Overlay)\|Sewer area]]s.
	* Defining geographical spatial features without affecting the [[Building]]s layer, such as [[Foliage areas (Heat Overlay)\|Foliage]] for the [[Heat Module]].		* Defining geographical spatial features without affecting the [[Building]]s layer, such as [[Foliage areas (Heat Stress Overlay)\|Foliage]] for the [[DPRA Heat Stress Module]].
	{{clear}}		{{clear}}

Line 545:		Line 545:
	[[Overlay]]s can also perform spatial calculations. These [[Overlay]]s are known as [[Grid Overlay]]s, as they function by interpreting the [[Project area]] as a grid consisting of a large number of cells. A calculation is then run for every individual cell.		[[Overlay]]s can also perform spatial calculations. These [[Overlay]]s are known as [[Grid Overlay]]s, as they function by interpreting the [[Project area]] as a grid consisting of a large number of cells. A calculation is then run for every individual cell.

	Some [[Grid Overlay]]s are relatively simple, such as the [[Digital Surface Model Overlay\|Elevation Overlay]]s or the [[Average Overlay\|Average Overlay]]. Other [[Grid Overlay]]s are the practical implementations of fully-fledged calculation models, such as the [[Water Overlay]] or the [[Heat Overlay]].		Some [[Grid Overlay]]s are relatively simple, such as the [[Digital Surface Model Overlay\|Elevation Overlay]]s or the [[Average Overlay\|Average Overlay]]. Other [[Grid Overlay]]s are the practical implementations of fully-fledged calculation models, such as the [[Water Overlay]] or the [[Heat Stress Overlay]].

	[[Overlay]]s are a form of data which is part of the [[Session]], but are not themselves geographical data in the [[Project area]]. Instead they are definitions for available map layers and calculation models, the output of which are geographically visible.		[[Overlay]]s are a form of data which is part of the [[Session]], but are not themselves geographical data in the [[Project area]]. Instead they are definitions for available map layers and calculation models, the output of which are geographically visible.
Line 578:		Line 578:
	[[File:basics-editor-calculation-icon-auto.jpg\|frame\|center\|The recalculation menu icon.]]		[[File:basics-editor-calculation-icon-auto.jpg\|frame\|center\|The recalculation menu icon.]]

	One of the strengths of the {{software}} is that new data can be very easily ~~analysed~~ and recalculated. It is possible to recalculate a [[Session]] at any time by hovering over the recalculation symbol, and then clicking the "Update" option.		One of the strengths of the {{software}} is that new data can be very easily analyzed and recalculated. It is possible to recalculate a [[Session]] at any time by hovering over the recalculation symbol, and then clicking the "Update" option.

	[[File:basics-editor-calculation-update.jpg\|frame\|center\|"Update" recalculates all models, such as [[Overlay]]s and [[Indicator]]s, in the [[Session]].]]		[[File:basics-editor-calculation-update.jpg\|frame\|center\|"Update" recalculates all models, such as [[Overlay]]s and [[Indicator]]s, in the [[Session]].]]
Line 595:		Line 595:
	When the [[Session]] is not configured to recalculate automatically, newly added [[Grid Overlay]]s will be initialized with a value of "0" everywhere, and [[Indicator]]s and other computed interface elements will not updating or present as empty.		When the [[Session]] is not configured to recalculate automatically, newly added [[Grid Overlay]]s will be initialized with a value of "0" everywhere, and [[Indicator]]s and other computed interface elements will not updating or present as empty.

	When this happens, a recalculation of all calculation models in a [[Session]] can be triggered from the recalculation ~~dropdown~~.		When this happens, a recalculation of all calculation models in a [[Session]] can be triggered from the recalculation drop-down.
	{{page_break}}		{{page_break}}

Line 601:		Line 601:
	Using the information learned in this tutorial, and with an initial [[Project]] created specifically for experimentation, try the following editing actions and explore the results.		Using the information learned in this tutorial, and with an initial [[Project]] created specifically for experimentation, try the following editing actions and explore the results.

	# Hover over the Overlays button in the ribbon so that the ~~dropdown~~ opens. In the list of Overlay categories, select "Topographical", and then click on "Digital Terrain Model". Explore the resulting [[Digital Terrain Model Overlay]]		# Hover over the Overlays button in the ribbon so that the drop-down opens. In the list of Overlay categories, select "Topographical", and then click on "Digital Terrain Model". Explore the resulting [[Digital Terrain Model Overlay]]
	# Hover over the Indicators button in the ribbon so that the ~~dropdown~~ opens. In the list of folders, select "Urban Planning", and then click on "Density". Explore the resulting indicator added in the [[top bar]].		# Hover over the Indicators button in the ribbon so that the drop-down opens. In the list of folders, select "Urban Planning", and then click on "Density". Explore the resulting indicator added in the [[top bar]].

	{{Tutorial completed		{{Tutorial completed