Traffic model - Revision history

Frank@tygron.nl at 08:06, 13 March 2026

2026-03-13T08:06:02Z

← Older revision		Revision as of 08:06, 13 March 2026
Line 53:		Line 53:
	* [[Traffic Noise Overlay]]		* [[Traffic Noise Overlay]]
	* [[Traffic NO2 Overlay]]		* [[Traffic NO2 Overlay]]
			*[[Traffic Plugin]]
	}}		}}

Rudolf@tygron.nl at 16:26, 16 December 2025

2025-12-16T16:26:58Z

← Older revision		Revision as of 16:26, 16 December 2025
Line 53:		Line 53:
	* [[Traffic Noise Overlay]]		* [[Traffic Noise Overlay]]
	* [[Traffic NO2 Overlay]]		* [[Traffic NO2 Overlay]]
	~~\|videos=~~
	~~{{video\|language=dutch\|link=https://www.tygron.com/nl/2020/04/17/wat-zijn-de-bronnen-voor-de-verkeersgegevens-in-tygron/\|description=Traffic data sources Q&A.}}~~
	~~{{video\|language=dutch\|link=https://www.tygron.com/nl/2020/04/17/hoe-kan-ik-mijn-eigen-verkeersmodel-koppelen-mbv-nwb-id/\|description=Dynamic traffic model coupling via NWB-IDs.}}~~
	}}		}}

Frank@tygron.nl at 16:27, 27 January 2023

2023-01-27T16:27:48Z

← Older revision		Revision as of 16:27, 27 January 2023
Line 15:		Line 15:
	{{main\|Function Value#Traffic}}		{{main\|Function Value#Traffic}}

	The data concerning traffic is, by default, available as [[Function Value]]s and by extension as [[Attribute]]s related to road-type [[Building]]s in the [[~~3D World~~]].		The data concerning traffic is, by default, available as [[Function Value]]s and by extension as [[Attribute]]s related to road-type [[Building]]s in the [[project]].

	Function Values related to traffic describe, for each road:		Function Values related to traffic describe, for each road:
Line 25:		Line 25:
	===Grids===		===Grids===
	{{main\|Prequels (Traffic Overlay)}}		{{main\|Prequels (Traffic Overlay)}}
	Other than traffic intensity values linked to specific [[Building]]s in the [[~~3D World~~]], it is entirely permitted to store traffic data in other forms as well. Some of the {{software}}'s built-in calculation models can make use of [[Prequel]]s as their inputs.		Other than traffic intensity values linked to specific [[Building]]s in the [[project]], it is entirely permitted to store traffic data in other forms as well. Some of the {{software}}'s built-in calculation models can make use of [[Prequel]]s as their inputs.

	[[Prequel]]s can also make use of [[Function Value#Traffic\|Function Value]] based data indirectly, by rasterizing the data using an [[Average Overlay]].		[[Prequel]]s can also make use of [[Function Value#Traffic\|Function Value]] based data indirectly, by rasterizing the data using an [[Average Overlay]].
Line 31:		Line 31:
	==Dynamic traffic data==		==Dynamic traffic data==
	{{anchor\|dynamic traffic model}}		{{anchor\|dynamic traffic model}}
	Traffic data can also be computed dynamically, either completely based on the current state of the [[Project]], or relatively, basing new traffic values on a set of original traffic values, and computing a change in traffic based on changes in the ~~[[3D World]]~~.		Traffic data can also be computed dynamically, either completely based on the current state of the [[Project]], or relatively, basing new traffic values on a set of original traffic values, and computing a change in traffic based on changes in the project.

	==Calculations==		==Calculations==
Line 42:		Line 42:
	{{main\|Traffic visualization}}		{{main\|Traffic visualization}}

	Traffic data is also visualized in the [[3D ~~World~~]], based directly on the data present in the [[Project]]. Based on that data, [[Unit]]s are visualized on road [[Building]]s. Although derived from data, visualized traffic is not data in and of itself, and is included for verisimilitude only.		Traffic data is also visualized in the [[3D Visualization]], based directly on the data present in the [[Project]]. Based on that data, [[Unit]]s are visualized on road [[Building]]s. Although derived from data, visualized traffic is not data in and of itself, and is included for verisimilitude only.

	{{article end		{{article end

Frank@tygron.nl: /* Data */

2022-10-28T11:09:10Z

Data

← Older revision		Revision as of 11:09, 28 October 2022
Line 4:		Line 4:
	{{anchor\|static traffic model}}		{{anchor\|static traffic model}}
	The {{software}} uses the following data sources to initialize yearly averaged hourly traffic intensities for work days:		The {{software}} uses the following data sources to initialize yearly averaged hourly traffic intensities for work days:
			* [[Project Sources#BGT\|BGT]] or [[Project Sources#Top10NL\|Top10NL]]: Feature services which contains road features as polygons, sometimes with additional information on the amount of lanes.
	* BGT or Top10NL: ~~A feature service~~ which contains road features as polygons, sometimes with additional information on the amount of lanes.		* [[Project Sources#NWB\|NWB]] (Nationaal Wegen Bestand): A WFS which contains road features, as lines, with NWB IDs, names and traffic direction information. This source is used to set the NWB ID for obtained road features from the BGT or Top10NL.
	* NWB (Nationaal Wegen Bestand): A WFS which contains road features, as lines, with NWB IDs, names and traffic direction information.		* [[Project Sources#INWEVA\|INWEVA 2020]]: A csv file with yearly averaged, hourly traffic intensities for roads with NWB ids.
	* INWEVA 2020~~, NWB (Nationaal Wegen Bestand)~~: A csv file with yearly averaged, hourly traffic intensities for roads with NWB ids.		* [[Project Sources#NSL\|NLS]] Monitoring tool: A [[WFS]] service with yearly averaged daily traffic intensities, known for roads where traffic intensities are measured.
	* NSL Monitoring tool: A [[WFS]] service with yearly averaged daily traffic intensities, known for roads where traffic intensities are measured.		* [[Project Sources#Infomil\|Infomil]]: Estimated traffic intensities for roads which do not have known traffic intensities. Estimations are done based on the maximum traffic speed allowed on that type of road, the urban degree of the location of the road, number of lanes, traffic direction (one way or not) and if there are nearby parking lots and cycling lanes. These combinations are taken from the Excel ''vi-lucht_geluid_v4.xls''.
	* Infomil: Estimated traffic intensities for roads which do not have known traffic intensities. Estimations are done based on the maximum traffic speed allowed on that type of road, the urban degree of the location of the road, number of lanes, traffic direction (one way or not) and if there are nearby parking lots and cycling lanes. These combinations are taken from the Excel ''vi-lucht_geluid_v4.xls''.

	See also [[Traffic Plugin]] for more information.		See also [[Traffic Plugin]] for more information.

Frank@tygron.nl: /* Data */

2022-10-28T11:06:00Z

Data

← Older revision		Revision as of 11:06, 28 October 2022
Line 3:		Line 3:
	==Data==		==Data==
	{{anchor\|static traffic model}}		{{anchor\|static traffic model}}
	The {{software}} uses the following data sources to initialize yearly averaged traffic intensities:		The {{software}} uses the following data sources to initialize yearly averaged hourly traffic intensities for work days:
	~~<!--List of sources for the default values for function values. The following are known sources but details are unclear.-->~~
	* BGT or Top10NL: A feature service which contains road features as polygons, sometimes with additional information on the amount of lanes.		* BGT or Top10NL: A feature service which contains road features as polygons, sometimes with additional information on the amount of lanes.
	* NWB (Nationaal Wegen Bestand): A WFS which contains road features, as lines, with NWB IDs, names and traffic direction information.		* NWB (Nationaal Wegen Bestand): A WFS which contains road features, as lines, with NWB IDs, names and traffic direction information.

Frank@tygron.nl: /* Data */

2022-10-28T11:05:04Z

Data

← Older revision		Revision as of 11:05, 28 October 2022
Line 10:		Line 10:
	* NSL Monitoring tool: A [[WFS]] service with yearly averaged daily traffic intensities, known for roads where traffic intensities are measured.		* NSL Monitoring tool: A [[WFS]] service with yearly averaged daily traffic intensities, known for roads where traffic intensities are measured.
	* Infomil: Estimated traffic intensities for roads which do not have known traffic intensities. Estimations are done based on the maximum traffic speed allowed on that type of road, the urban degree of the location of the road, number of lanes, traffic direction (one way or not) and if there are nearby parking lots and cycling lanes. These combinations are taken from the Excel ''vi-lucht_geluid_v4.xls''.		* Infomil: Estimated traffic intensities for roads which do not have known traffic intensities. Estimations are done based on the maximum traffic speed allowed on that type of road, the urban degree of the location of the road, number of lanes, traffic direction (one way or not) and if there are nearby parking lots and cycling lanes. These combinations are taken from the Excel ''vi-lucht_geluid_v4.xls''.

			See also [[Traffic Plugin]] for more information.

	===Function Values===		===Function Values===

Frank@tygron.nl: /* Data */

2022-10-27T14:46:27Z

Data

← Older revision		Revision as of 14:46, 27 October 2022
Line 7:		Line 7:
	* BGT or Top10NL: A feature service which contains road features as polygons, sometimes with additional information on the amount of lanes.		* BGT or Top10NL: A feature service which contains road features as polygons, sometimes with additional information on the amount of lanes.
	* NWB (Nationaal Wegen Bestand): A WFS which contains road features, as lines, with NWB IDs, names and traffic direction information.		* NWB (Nationaal Wegen Bestand): A WFS which contains road features, as lines, with NWB IDs, names and traffic direction information.
	* INWEVA ~~2015~~, NWB (Nationaal Wegen Bestand): A csv file with yearly averaged, hourly traffic intensities for roads with NWB ids.		* INWEVA 2020, NWB (Nationaal Wegen Bestand): A csv file with yearly averaged, hourly traffic intensities for roads with NWB ids.
	* NSL Monitoring tool: A [[WFS]] service with yearly averaged daily traffic intensities, known for roads where traffic intensities are measured.		* NSL Monitoring tool: A [[WFS]] service with yearly averaged daily traffic intensities, known for roads where traffic intensities are measured.
	* Infomil: Estimated traffic intensities for roads which do not have known traffic intensities. Estimations are done based on the maximum traffic speed allowed on that type of road, the urban degree of the location of the road, number of lanes, traffic direction (one way or not) and if there are nearby parking lots and cycling lanes. These combinations are taken from the Excel ''vi-lucht_geluid_v4.xls''.		* Infomil: Estimated traffic intensities for roads which do not have known traffic intensities. Estimations are done based on the maximum traffic speed allowed on that type of road, the urban degree of the location of the road, number of lanes, traffic direction (one way or not) and if there are nearby parking lots and cycling lanes. These combinations are taken from the Excel ''vi-lucht_geluid_v4.xls''.

Maxim@tygron.com at 11:47, 7 October 2022

2022-10-07T11:47:06Z

← Older revision		Revision as of 11:47, 7 October 2022
Line 1:		Line 1:
	The {{software}} has special facility to include, visualize, modify, and use traffic data. [[~~Construction~~]]s have [[Function Value#traffic\|Function Value]]s, can be updated in a variety of ways, and built-in [[Traffic Overlay]]s use this data directly to perform spatial calculations. The entirety of all traffic data in a [[Project]], and the rules dictating how traffic data changes through [[Action]]s taken in a [[Session]], are collectively referred to as the {{software}}'s traffic model.		The {{software}} has special facility to include, visualize, modify, and use traffic data. [[Building]]s have [[Function Value#traffic\|Function Value]]s, can be updated in a variety of ways, and built-in [[Traffic Overlay]]s use this data directly to perform spatial calculations. The entirety of all traffic data in a [[Project]], and the rules dictating how traffic data changes through [[Action]]s taken in a [[Session]], are collectively referred to as the {{software}}'s traffic model.

	==Data==		==Data==
Line 14:		Line 14:
	{{main\|Function Value#Traffic}}		{{main\|Function Value#Traffic}}

	The data concerning traffic is, by default, available as [[Function Value]]s and by extension as [[Attribute]]s related to road-type [[~~Construction~~]]s in the [[3D World]].		The data concerning traffic is, by default, available as [[Function Value]]s and by extension as [[Attribute]]s related to road-type [[Building]]s in the [[3D World]].

	Function Values related to traffic describe, for each road:		Function Values related to traffic describe, for each road:
Line 24:		Line 24:
	===Grids===		===Grids===
	{{main\|Prequels (Traffic Overlay)}}		{{main\|Prequels (Traffic Overlay)}}
	Other than traffic intensity values linked to specific [[~~Construction~~]]s in the [[3D World]], it is entirely permitted to store traffic data in other forms as well. Some of the {{software}}'s built-in calculation models can make use of [[Prequel]]s as their inputs.		Other than traffic intensity values linked to specific [[Building]]s in the [[3D World]], it is entirely permitted to store traffic data in other forms as well. Some of the {{software}}'s built-in calculation models can make use of [[Prequel]]s as their inputs.

	[[Prequel]]s can also make use of [[Function Value#Traffic\|Function Value]] based data indirectly, by rasterizing the data using an [[Average Overlay]].		[[Prequel]]s can also make use of [[Function Value#Traffic\|Function Value]] based data indirectly, by rasterizing the data using an [[Average Overlay]].
Line 41:		Line 41:
	{{main\|Traffic visualization}}		{{main\|Traffic visualization}}

	Traffic data is also visualized in the [[3D World]], based directly on the data present in the [[Project]]. Based on that data, [[Unit]]s are visualized on road [[~~Construction~~]]s. Although derived from data, visualized traffic is not data in and of itself, and is included for verisimilitude only.		Traffic data is also visualized in the [[3D World]], based directly on the data present in the [[Project]]. Based on that data, [[Unit]]s are visualized on road [[Building]]s. Although derived from data, visualized traffic is not data in and of itself, and is included for verisimilitude only.

	{{article end		{{article end

Rudolf@tygron.nl at 14:38, 3 March 2022

2022-03-03T14:38:12Z

← Older revision		Revision as of 14:38, 3 March 2022
Line 1:		Line 1:
	~~#REDIRECT [[Traffic Model]]~~

	~~{{stub}}~~

	The {{software}} has special facility to include, visualize, modify, and use traffic data. [[Construction]]s have [[Function Value#traffic\|Function Value]]s, can be updated in a variety of ways, and built-in [[Traffic Overlay]]s use this data directly to perform spatial calculations. The entirety of all traffic data in a [[Project]], and the rules dictating how traffic data changes through [[Action]]s taken in a [[Session]], are collectively referred to as the {{software}}'s traffic model.		The {{software}} has special facility to include, visualize, modify, and use traffic data. [[Construction]]s have [[Function Value#traffic\|Function Value]]s, can be updated in a variety of ways, and built-in [[Traffic Overlay]]s use this data directly to perform spatial calculations. The entirety of all traffic data in a [[Project]], and the rules dictating how traffic data changes through [[Action]]s taken in a [[Session]], are collectively referred to as the {{software}}'s traffic model.

Rudolf@tygron.nl: /* Grids */

2022-03-03T14:36:28Z

Grids

← Older revision		Revision as of 14:36, 3 March 2022
Line 28:		Line 28:
	===Grids===		===Grids===
	{{main\|Prequels (Traffic Overlay)}}		{{main\|Prequels (Traffic Overlay)}}
	Other than traffic intensity values linked to specific [[~~Cosntruction~~]]s in the [[3D World]], it is entirely permitted to store traffic data in other forms as well. Some of the {{software}}'s built-in calculation models can make use of [[Prequel]]s as their inputs.		Other than traffic intensity values linked to specific [[Construction]]s in the [[3D World]], it is entirely permitted to store traffic data in other forms as well. Some of the {{software}}'s built-in calculation models can make use of [[Prequel]]s as their inputs.

	[[Prequel]]s can also make use of [[Function Value#Traffic\|Function Value]] based data indirectly, by rasterizing the data using an [[Average Overlay]].		[[Prequel]]s can also make use of [[Function Value#Traffic\|Function Value]] based data indirectly, by rasterizing the data using an [[Average Overlay]].