130 likes | 308 Views
Hennepin County Transportation Systems Plan (HC-TSP) Traffic Forecasting Model. Background. Model initially developed in 1997-98 Derived from Met Council Regional Model Minor Updates in 2000 & 2002 Conversion from TRANPLAN / TransPro to TransCAD begun in 2004. Model Features.
E N D
Hennepin County Transportation Systems Plan (HC-TSP)Traffic Forecasting Model
Background • Model initially developed in 1997-98 • Derived from Met Council Regional Model • Minor Updates in 2000 & 2002 • Conversion from TRANPLAN / TransPro to TransCAD begun in 2004
Model Features • Land Use Based (sq-ft, Dwelling Units, etc.) – linked to Countywide parcel database • Strong GIS Linkage (ArcGIS) • Only Vehicle Trips Modeled • 3-Purposes for Trip Productions / Attractions (HBW, HBO, NHB) • Trip Generation via ITE trip rates
Model Characteristics • To accurately depict Arterials – must model one level below (to collector street level) – this requires 50% increase in nodes / links
Model Characteristics • Huge databases to manage (parcel database 350,000+ records)
Model Characteristics • Met Council TAZ’s split about 3:1 500 Met Council TAZ -> 1,500 HC TAZ
Model Characteristics • High level of ADT calibration
Why TransCAD ? • Some previous familiarity with the package –had dabbled with Demo copy in 2003-04 • Local Road Research Board Project in 2004 –Snowplow routing (2 licenses purchased) • Package had ITE Trip Generation built-in • Good GIS compatibility with ArcView
Status of Model Refinements • Existing Land Use verification completed (required 1-1/2 year effort) • TAZ’s refined – parcels allocated to both Met Council and Hennepin County TAZ’s • First attempt for existing trip generation completed