Traffic model: Difference between revisions

From Tygron Support wiki
Jump to navigation Jump to search
No edit summary
Line 8: Line 8:
{{anchor|static traffic model}}
{{anchor|static traffic model}}
{{stub|type=section}}
{{stub|type=section}}
The {{software}} uses the following data sources to establish basic assumptions of traffic intensities:
The {{software}} uses the following data sources to initialize yearly averaged traffic intensities:
<!--List of sources for the default values for function values. The following are known sources but details are unclear.-->
<!--List of sources for the default values for function values. The following are known sources but details are unclear.-->
* NWB (Nationaal Wegen Bestand)
* INWEVA 2015, NWB (Nationaal Wegen Bestand): A csv file with yearly averaged, hourly traffic intensities for roads with NWB ids.
* NSL Monitoring tool
* NSL Monitoring tool: A [[WFS]] service with yearly averaged daily traffic intensities, known for roads where traffic intensities are measured.
* INWEVA 2015
* 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''.


In addition to these default assumptions, roads for which measured traffic intensities are known will have those default values overwritten with road-specific values from the following sources:
In addition to these default assumptions, roads for which measured traffic intensities are known will have those default values overwritten with road-specific values from the following sources:

Revision as of 10:49, 3 March 2022

Redirect to:

This article is a stub.

The Tygron Platform has special facility to include, visualize, modify, and use traffic data. Constructions 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

This section is a stub.

The Tygron Platform uses the following data sources to initialize yearly averaged traffic intensities:

  • INWEVA 2015, 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.
  • 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.

In addition to these default assumptions, roads for which measured traffic intensities are known will have those default values overwritten with road-specific values from the following sources:

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 Constructions in the 3D World.

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 Cosntructions in the 3D World, 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 3D World.

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

How-to's

Videos

Traffic data sources Q&A. (In dutch)
Dynamic traffic model coupling via NWB-IDs. (In dutch)

See also