Traffic Model: Difference between revisions

From Tygron Preview Support Wiki
Jump to navigation Jump to search
(Replaced content with "#REDIRECT Traffic model")
Tag: Replaced
 
(72 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{being updated}}
#REDIRECT [[Traffic model]]
{{learned|file=|what a Traffic Model is|how a Traffic Model relates to the {{software}}|about the different Traffic Models in the {{software}}|how to add a Custom Traffic Model to your project|how to change the Traffic Model dynamically in your project}}
 
== What is a Traffic Model ==
''From Wikipedia, the free encyclopedia''
 
A traffic model is a mathematical model of real-world traffic, usually, but not restricted to, road traffic. Traffic modeling draws heavily on theoretical foundations like network theory and certain theories from physics like the kinematic wave model. The interesting quantity being modeled and measured is the [[Traffic Flow (Overlay)|traffic flow]], i.e. the throughput of mobile [[units]] (e.g. vehicles) per time and transportation medium capacity (e.g. [[Constructions#Roads|road]] or lane width).
 
== How does a Traffic Model relate to the {{software}}? ==
The main purpose of the default traffic model in the {{software}} is to calculate the effects of traffic on the [[3D World]] through traffic densities. In order to calculate this impact, data such as the number of traffic lanes, the traffic speed and the traffic flow on a particular lane can be added to the project. The traffic model is a static model that does not change by carrying out [[Actions]], [[Upgrades]] or [[Measures]] for example. Read below how to create your own dynamic traffic model and use it in the {{software}}.
The following overlays show data from/effects of the traffic model:
* [[Traffic Density (Overlay)]]
* [[Traffic NO2(Overlay)]]
* [[Traffic Noise (Overlay)]]
 
==Traffic Data==
When creating a [[Main Menu#New Project|new project]] a traffic model is generated for the selected project area, based on available open data sources. The following datasets are used:
 
* [[GEO_Data#Used_Datasets|NSL Monitoringstool]]
* [[GEO_Data#Used_Datasets|NWB (Nationaal Wegen Bestand)]]
* [[GEO_Data#Used_Datasets|INWEVA 2015]]
* [[GEO_Data#Used_Datasets|VI-Lucht & Geluid]]
<!--
====INWEVA 2015====
:INWEVA is short for INtensiteiten op WEgVAkken (traffic intensities on road sections). Traffic intensities are measured on ca. 3000 road sections. For the other sections intensities are estimated, based on traffic modeling. The data are yearly averages per road section, and updated each year.
:'' See also: https://nis.rijkswaterstaat.nl/portalcontent/logon/p2_33.html
 
====VI-Lucht & Geluid====
:VI-Lucht en Geluid is a Dutch tool that provides the following data for a specific section of a road:
*An average traffic intensity expressed in motor vehicles per week day, per average daytime hour, per average evening hour, per average nighttime hour
*The share and size of medium heavy and heavy freight traffic
*The share and size of bus traffic
:In januari 2016 the application was updated and actualized for the last time.
:'' See also: https://www.infomil.nl/onderwerpen/klimaat-lucht/luchtkwaliteit/slag/hulpmiddelen/inschatten/
-->
 
===Edit Traffic data===
[[File:Traffic_data.jpg|thumb|200px|left|The right panel shows details about the selected road part]]
====Height offset====
''This field specifies the height offset of a bridge''
====Units per hour====
''This field specifies the number of units that can drive on a road in an hour''
====Lanes====
''This field specifies the number of lanes that a road can have''
====Noise Sigma====
''This field specifies the correction factor at reference traffic speed[http://wetten.overheid.nl/BWBR0031722/2015-07-01#BijlageIII]''
 
====Noise Tau====
''This field specifies the correction factor per 10 km/hour deviation from reference traffic speed[https://www.infomil.nl/onderwerpen/geluid/regelgeving/wet-geluidhinder/wegverkeerslawaai/akoestisch-rapport/cwegdek/]''
 
====Speedlimit====
''This field specifies the max allowed speedlimit on road or part of a road''
<br  clear= all>
 
==Add a custom Traffic Model==
It is also possible to creata and add a custom traffic model, better suited for your use case. The traffic model can be either a static model (the model and data do not change in the project) or a dynamic model (the model and data change when something in the 3D world changes).
 
===Static Traffic Model ===
''A static model does not change (over time), when changes occur in the 3D world. 
This type of model can be used when you for example have a scenario for 2030 ready that contains the traffic intensities then and want to use this data in your project.
To upload the dataset, create a [[Geojson]] file of the data and make sure the features contain an attribute with the number of [[units]]/hour. This attribute will overwrite the current TRAFFIC_FLOW attribute of the roads.
When importing this data, [[Constructions]] that are intersected by sections of the imported data are given the new traffic flow attribute of imported data.
<br>
{{Editor ribbon|header=Geo Data|bar= Geo Import}}
{{Editor steps|title=add a Static Traffic Model using the Geo Data Wizard|Select the Geo Data header|Select the Geo Import bar|Notice that a Geo Data Wizard window appears|In the data wizard select the type 'Buildings'|Select the 'Import a GeoJson file' option in step 1|Select the GeoJson file you wish to add in step 1|View the features of the selected GeoJson file in step 2|Select the 'No Filtering' option in step 3|Select the option 'Import as New Buildings with attributes' in step 4|Select an option on how you want to name the features in step 5|Ensure that the attribute TRAFFIC_FLOW is activated in the list of attributes in step 6|Select the 'One Function' option in step 7|Select the 'One Stakeholder' option in step 8|Select 'Finish' in step 9}}
<br>
 
<gallery>
File:Geo_data_0.jpg | 4.  Select 'Buildings' type
File:Geo_data_1.jpg | 5.  Select the 'Import a GeoJson file option'
File:Geo_data_3.jpg | 6.  Select the GeoJson file you wish to add
File:Geo_data_4.jpg | 7.  View the features of the selected GeoJson file
File:Geo_data_5.jpg | 8.  Select the 'No Filtering option'
File:Geo_data_6.jpg | 9.  Select the 'Import as New Buildings with attributes' option
File:Geo_data_7.jpg | 10. Choose how you want to name the features
File:Geo_data_8.jpg | 11. Select the TRAFFIC_FLOW attribute
File:Geo_data_9.png | 12. Select the 'One Function' option
File:Geo_data_10.jpg| 13. Select the 'One Stakeholder' option
File:Geo_data_11.jpg| 14. Select 'Finish'
</gallery>
 
===Dynamic traffic model===
''A dynamic model changes (over time), according to changes in the 3D world.
An example of a dynamic traffic model is a model in where is calculated how the traffic intensity changes when building a certain amount of houses. Effectively the TRAFFIC_FLOW attribute of the roads will be updated with a new value, when building houses in the {{software}}.
To create such a model, first create a [[Geojson]] file with the roads that will be changed by a certain [[Action]] or [[Measure]] and import the file.
In an [[Excel|Excel]] file, the calculation for how much and when the traffic intensity changes has to be made. This file can be uploaded as either an [[indicator]] or [[panel]]. The indicator or panel explanation text in this case is not relevant. The Excel is only used to define the model and import it in the {{software}}.
The Excel implementation of a simple dynamic traffic model, consists of the following consecutive steps:
:* Retrieval of the original traffic density in Area X - <code>SELECT_ATTRIBUTE_WHERE_NAME_IS_TRAFFIC_FLOW_AND_AREA_IS_X</code>
:* Calculation in an excel file, with the new traffic density as outcome - <code>original traffic density + change</code>
:* Output of the new traffic density for constructions in Area X - <code>UPDATE_BUILDING_TRAFFIC_FLOW_WHERE_AREA_IS_X</code>
<br>
 
{{Editor ribbon|header=Geo Data|bar= Geo Import}}
{{Editor steps|title=add a Dynamic Custom Traffic Model using the Geo Data Wizard|Select the Geo Data header|Select the Geo Import bar|Notice that a Geo Data Wizard window appears|Select the type 'Areas' in the Geo Data Wizard|Select the 'Import a GeoJson file' option in step 1| Select the GeoJson file you wish to add in step 1|View the features of the selected GeoJson file in step 2|Select the 'No Filtering' option in step 3|Select 'Import a New Area with attributes' in step 4|Select an option on how you want to name the features in step 5|Ensure that the attribute TRAFFIC_FLOW is activated in the list of attributes in step 6||Select 'Finish' in step 7}}
<br>
 
<gallery>
File:Geo_data_areas.jpg    |4.  Select the type 'Areas'
File:Geo_data_1.jpg        |5.  Select the 'Import a GeoJson file' option
File:Geo_data_3.jpg        |6.  Select the GeoJson file you wish to add
File:Geo_data_4.jpg        |7.  View  the features of the selected GeoJson file
File:Geo_data_5.jpg        |8.  Select the 'No filtering' option
File:Geo_data_areas_1.jpg  |9.  Select 'Import a New Area with attributes'
File:Geo_data_7.jpg        |10. Choose how you want to name the features
File:Geo_data_8.jpg        |11. Select the TRAFFIC_FLOW attribute
File:Geo_data_11.jpg      |12. Select 'Finish'
</gallery>
<br>
 
<!--<gallery mode="nolines">
File:editor.jpg|Drag and drop a prepared Geojson file on the Editor
File:ImportAreas-FileHandler.jpg|Select "Import Areas" from the "File Handler" panel
File:ImportAreaFile.jpg|Ensure the attribute TRAFFIC_FLOW is activated
File:ImportAreaFileSend.jpg|Select the "Send" button
</gallery>
-->

Latest revision as of 16:32, 27 January 2023

Redirect to:

Retrieved from "https://previewsupport.tygron.com/w/index.php?title=Traffic_Model&oldid=50492"