The WA government outlines its plan to monitor traffic volumes before and after the opening of a new railway line, using various data collection methods and timeframes to assess the impact.

AnsweredQoN 2706Legislative Assembly
Asked
20 September 2007
Portfolio
Planning and Infrastructure

QuestionView source ↗

(a) if so, how?
(2) Will those volumes be monitored before and after the opening of the railway; and
(a) if so, for what period; and
(b) if not, why not?

AnswerView source ↗

Answered
16 October 2007
Responded by
Minister for Planning and Infrastructure
Response time
26 days
(1) Yes.
(a) A number of traffic collection methodologies will be utilised including pneumatic rubber tubes stretched across the road surface, inductive loop traffic detectors on Kwinana Freeway and at various signalised intersections providing continuous data input.
(2) Yes.
(a) The Perth Metropolitan 2006/07 short term program counted in excess of 1000 locations south of the river between July 2006 and June 2007. These locations provide sufficient 'before' data. In addition historic intersection data is available for trend analysis as required, and the Intelligent Transport System data will provide traffic volumes for the months immediately prior to the rail opening.
'After' counts will be conducted at selected strategic locations in the weeks immediately following the opening, and longer term monitoring (1-2+ years) is also planned. The 2008/09 program will revisit the majority of the sites counted in 2006/07 giving an indication of changes in traffic volumes.
In addition, Travel Time surveys on Kwinana Freeway will be conducted before and after the opening.
(b) Not applicable.
Notice: This document is created or edited using unregistered or evaluation copy of rtLib valid for testing or development purposes only. To use it for productive or any other purposes please register it. You may purchase the license on
http://www.rtlib.com

Explore WA Government Data

Search the full archive in the free dashboard, or query programmatically via API.

Explore more