Levels of Detail for Traffic Signal Modelling Jonathan Slason (Beca) Presented: SNUG 16 November 2010. Wellington, NZ The views expressed are those of the author and do not necessarily reflect those of Beca or any other organisation or agency. Further detail behind the issues raised is available by contacting email@example.com
Traffic Modelling Concept Regional travel demands (public and private) for network/project planning; Travel costs for economic evaluation; and Transport demands and effects of specific infrastructure; Traffic flows for design of infrastructure; Transport demands and effects of specific land use development. Operations and Optimisation Accuracy Detail
Those forecasts were developed for testing and developing regional policy and strategies and are hence focussed on longer-term (e.g. 30 year) planning horizons.
Most project evaluations require shorter-term forecasts, typically 5-25 years. For example, assessment of environment effects on major infrastructure (such as noise and emissions), require travel forecasts for opening and 10-years post-opening.
Analysis Flows Development of design flows from model forecasts is a distinct process that should be recognised in the study process. That process should consider other data (such as counts), additional model output (such as validation data and path analysis) in determining appropriate design flows from model forecasts. Wherever possible, intersection design should be based on surveyed flows, modified based on the change predicted by the models, rather than based directly on raw model forecasts (i.e. Pivoting)
PM Peak Data – Kopu SH25a TelemetryAnnual (Seasonal) Variation
15min variation in flowsInter and Intra Hour Variation AM & PM Peak Hour Factor = 0.88
Traffic Engineer Role The development of design flows for the operational assessment and design of roading facilities should be recognised as a distinct task from travel forecasting. That is, there is a distinct and crucial process involved in taking data from various sources (such as model forecasts and count data), and creating a set of flows suitable for the design process. It should be the responsibility of the person doing the operational assessment and/or design to prepare those design flows, rather than simply adopting outputs from traffic models without consideration of the model type, detail, age and level of local validation.
Traffic Engineer: Flow analysis tasks While design flows for new facilities will generally require input from models, available survey data and data from similar locations should also be considered. In using traffic model outputs to create design flows the following should be considered: The level of network detail in the model. Specifically, if the zone and network detail is low, than forecast turning movements may not be accurate, even if link flows are considered appropriate. Judgements should be made about the precision of turning flows, especially where the modelled flows appear unrealistically low; The age and level of local validation. Additional data or information form the model should be obtained to estimate the likely impact of any material validation discrepancies; The choice of design horizon and design-hour, and how these relate to the modelled years and periods; The time periods being represented, and what peaking factors should be applied to the forecast flows; What upstream/downstream constraints may influence the forecast flows; What level of delay is predicted at the facility being designed, and hence if predicted flows are likely to be influenced by those modelled delays. For example, if the model has high delays at the facility of interest, then the predicted flows could be lower than is likely to occur if the final design has reduced those delays; The sensibility of the flows, when considering existing travel patterns. Various outputs from the models can be requested to gauge the sensibility of the forecasts, including select-link analysis, flow difference plots, delay and/or Volume/Capacity ratio plots etc. As a general rule, survey data should be used wherever practical to validate the forecast flows. Wherever appropriate, local survey data should be used directly, with design flows created by pivoting off those flows using the predicted change in behaviour forecast by the model (i.e. the models are used to predict the change in flows, rather than the absolute design flows).
When to use what Model: Planning Purpose & Need: Enable project designations to be established. Create long-term project price estimates, scale of work, etc..
Focus on Peak hour(s) of operations
Can assume certain sub-groups are operating (tidal flows?)
Input: Planning flows into the future (10+ years). Can assume similar seasonal peaking as today. Use PHF of 1.0. Analysis:
Only appropriate used is to use deterministic.
Variation or lack of small confidence intervals in inputs suggest little real value in other stochastic or micro models
When to use what Model: Design Purpose & Need: Meet design year performance targets put forth by stakeholders and RCAs.