Traffic model: Difference between revisions
(→Data) |
No edit summary |
||
| (10 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
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. | |||
The {{software}} has special facility to include, visualize, modify, and use traffic data. [[ | |||
==Data== | ==Data== | ||
{{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 traffic intensities: | * [[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. | ||
* [[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. | |||
* BGT or Top10NL: | * [[Project Sources#INWEVA|INWEVA 2020]]: A csv file with yearly averaged, hourly traffic intensities for roads with NWB ids. | ||
* NWB (Nationaal Wegen Bestand): A WFS which contains road features, as lines, | * [[Project Sources#NSL|NLS]] Monitoring tool: A [[WFS]] service with yearly averaged daily traffic intensities, known for roads where traffic intensities are measured. | ||
* INWEVA | * [[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''. | ||
* 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''. | See also [[Traffic Plugin]] for more information. | ||
===Function Values=== | ===Function Values=== | ||
{{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 [[ | 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 29: | Line 25: | ||
===Grids=== | ===Grids=== | ||
{{main|Prequels (Traffic Overlay)}} | {{main|Prequels (Traffic Overlay)}} | ||
Other than traffic intensity values linked to specific [[ | 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 35: | 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 | 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 45: | Line 41: | ||
==Visualization== | ==Visualization== | ||
{{main|Traffic visualization}} | {{main|Traffic visualization}} | ||
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 | ||
Latest revision as of 16:27, 27 January 2023
The Tygron Platform has special facility to include, visualize, modify, and use traffic data. Buildings have Function Values, can be updated in a variety of ways, and built-in Traffic Overlays 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 Actions taken in a Session, are collectively referred to as the Tygron Platform's traffic model.
Data
The Tygron Platform uses the following data sources to initialize yearly averaged hourly traffic intensities for work days:
- BGT or Top10NL: Feature services 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. This source is used to set the NWB ID for obtained road features from the BGT or Top10NL.
- INWEVA 2020: A csv file with yearly averaged, hourly traffic intensities for roads with NWB ids.
- NLS 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.
See also Traffic Plugin for more information.
Function Values
- Main article: Function Value#Traffic
The data concerning traffic is, by default, available as Function Values and by extension as Attributes related to road-type Buildings in the project.
Function Values related to traffic describe, for each road:
- Road-traffic intensities (such as buses, cars, trucks, and vans)
- Traffic intensities other that road-traffic (such as airplanes, bicycles, pedestrians, and ships)
- Speed limits and amount of lanes
- Jam factors for road-traffic
Grids
- Main article: Prequels (Traffic Overlay)
Other than traffic intensity values linked to specific Buildings in the project, it is entirely permitted to store traffic data in other forms as well. Some of the Tygron Platform's built-in calculation models can make use of Prequels as their inputs.
Prequels can also make use of Function Value based data indirectly, by rasterizing the data using an Average Overlay.
Dynamic traffic data
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
- Main article: Traffic Overlay
Traffic data can be relevant for a wide range of calculations and use-cases. The Tygron Platform already contains several Traffic Overlays which compute the effects of traffic, on for example the topics of noise and NO2.
Traffic data, like any other Project data, can also be used in user-defined calculation models.
Visualization
- Main article: Traffic visualization
Traffic data is also visualized in the 3D Visualization, based directly on the data present in the Project. Based on that data, Units are visualized on road Buildings. Although derived from data, visualized traffic is not data in and of itself, and is included for verisimilitude only.
