Hennepin County Transportation Systems Plan HCTSP Traffic Forecasting Model

1
Hennepin County Transportation Systems Plan
(HC-TSP)Traffic Forecasting Model
2
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

3
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

4
(No Transcript)
5
Model Characteristics

• To accurately depict Arterials must model one
  level below (to collector street level) this
  requires 50 increase in nodes / links

6
Model Characteristics

• Huge databases to manage
• (parcel database 350,000 records)

7
Model Characteristics

• Met Council TAZs split about 31
• 500 Met Council TAZ -gt 1,500 HC TAZ

8
Model Characteristics

• High level of ADT calibration

9
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

10
Status of Model Refinements

• Existing Land Use verification completed
• (required 1-1/2 year effort)
• TAZs refined parcels allocated to both
• Met Council and Hennepin County TAZs
• First attempt for existing trip generation
  completed

11
(No Transcript)
12
(No Transcript)
13
Schedule