My WebLink
|
Help
|
About
|
Sign Out
AGENDA REPORT
City of Pleasanton
>
CITY CLERK
>
AGENDA PACKETS
>
2007
>
042407
>
JOINT WORKSHOP CC/PC - GP
>
AGENDA REPORT
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/26/2007 1:20:16 PM
Creation date
4/6/2007 2:59:15 PM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
STAFF REPORTS
DOCUMENT DATE
4/24/2007
DESTRUCT DATE
15 Y
DOCUMENT NO
04
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
49
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
<br />It should be noted that the travel system in and through the City of Pleasanton is a <br />highly complex interaction of excessive demand on overcapacity roadways with the <br />interplay and balance of regional travel on regional facilities vs. cutting-through the <br />cities of Pleasanton as well as Dublin and Livermore. In this kind of system, it is <br />extremely difficult to simultaneously validate to ITE trip generation, traffic counts, <br />travel surveys, and cut-through estimates. However, the City of Pleasanton model <br />does reasonably and acceptably well on all aspects. <br /> <br />Traffic Count Validation <br /> <br />The City of Pleasanton provided traffic count information from a variety of source, <br />including automatic street segment counts, monitoring at major intersections, and <br />peak hour intersection volumes from traffic impact studies. Additional detailed <br />traffic count information on state routes was obtained from Caltrans. <br /> <br />Traffic validation was determined reasonable and well within the acceptable limits <br />on nine screenlines throughout the City. Screenlines are imaginary lines, often <br />along natural or man-made physical barriers (e.g., rivers, railroad tracks) that have <br />a limited number of crossings. The screenlines should "cut" the entire study area, <br />intercepting all travel across them, thereby eliminating issues about individual <br />route choice. Use of a system of screenlines allows systematic comparison of total <br />model estimated versus observed travel in different parts of the model area. <br /> <br />The City of Pleasanton is within 10% on nearly every screenline by direction and all <br />percent RMSEs are well under the target 30% (see Appendix for details). <br /> <br />Matrix Estimation <br /> <br />Model validation results can be significantly improved by using the traffic counts as <br />one of the inputs to the model process. After estimation of trips using conventional <br />procedures (trip generation, distribution and assignment), the matrix of trip origins <br />and destinations can be factored to more closely replicate the traffic counts. For <br />example, if the conventional model process results in estimated traffic volumes that <br />are 20 percent too high on a freeway segment, the matrix estimation process can <br />adjust all of the origin-destination pairs using that segment by a factor of 0.8. This <br />is a complex iterative process, as every adjustment affects many segments with <br />traffic counts. <br /> <br />Matrix estimation can improve the validation statistics, but it adjusts the trip <br />origins and destinations in ways that cannot be easily explained or replicated. The <br />recommended application is to perform matrix estimation to provide a more <br />accurate base year result, but use the conventional model procedures to forecast <br />increments between the base year and future years. <br /> <br />Matrix estimation was applied to the Pleasanton Model 2005/6 peak hour trip <br />estimates. Total trip estimates to and from each zone were maintained at the ITE <br />trip generation rates. <br /> <br />City of Pleasanton <br />Trauel Demand Forecasting and Micro-Simulation Models <br /> <br />Page 12 <br />January 23, 2007 <br />
The URL can be used to link to this page
Your browser does not support the video tag.