My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
5.2. SR 07-24-2000
ElkRiver
>
City Government
>
City Council
>
Council Agenda Packets
>
2000 - 2010
>
2000
>
07/24/2000
>
5.2. SR 07-24-2000
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/21/2008 8:33:49 AM
Creation date
6/28/2004 1:21:40 PM
Metadata
Fields
Template:
City Government
type
SR
date
7/24/2000
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
118
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
Accident data for the prior three years was gleaned from our current database. We <br />combined this data with the traffic count data to calculate accidents per million vehicles <br />entering. <br /> <br />The City of Arcata has an excellent Geographic Information system (GIS), so we used <br />ArcVIEW to spatially represent both traffic volume and accident rates. Varying the width <br />of each street link in relation to the volume graphically displayed traffic flows. Separate <br />views were prepared for ADT, AMPHT and PMPHT. Accidents per year and per million <br />vehicles entering were represented with various sized dots at the intersections. <br /> <br />The traffic and accident data was provided to the committee in both graphical and <br />tabular form. We were very happy with how the Task Force received these exhibits. <br />The ArcVIEW presentations provided the Task Force with a dynamic overview of the <br />area and the tabular information was referred to often as their deliberation progressed. <br /> <br />Examples of ArcView Maps <br /> <br />Traffic Engineering 101 <br /> <br />Traffic Task Force began meeting twice per month beginning in June 1998. At the first <br />meeting, introductions were made and a chair and vice-chair were selected. The <br />elected chairperson was the Planning Commission representative. He brought to the <br />task force a great deal of experience in running public meetings. <br /> <br />Each task force member was provided with a "Committee Syllabus". This 3-ring binder <br />contained all appropriate background materials; membership addresses and phone <br />numbers; and task force policies and procedures. A nice binder goes a long way as this <br />binder proved to be a real hit. It let the task force know that I was taking them seriously. <br />See ExhibitA. A copy of this syllabus was placed in our local library so those interested <br />neighbors could keep informed. This binder was routinely kept current by public works <br />staff. The task force reviewed the proposed work plan and committed themselves to the <br />proposed schedule. <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.