Appendix G: Error Checking Process – Coded Input Data Checklist

1. Model run parameters:

Check time periods and durations to ensure full extent of congestion is captured.

Verify fill time is long enough for network to become fully loaded.

2. Link and node network geometry:

Check basic network connectivity (are all connections present?).

Check link geometry (lengths, number of lanes, free-flow speed, facility type, etc.).

Check for prohibited turns, lane closures, and lanerestrictions at the intersections and on the links.

3. Demand:

Check vehicle mix proportions at each entry node.

Check identified sources and sinks for traffic.

Verify volumes against traffic counts.

Check vehicle occupancy distribution (if modeling HOV vehicles).

Check turning percentages.

Check origin-destinations of trips on the network (if coded).

4. Control:

Check intersection controls (control type, control data).

Check ramp meter controls (control type, control data).

5. Traffic operations and management data:

Verify bus operations, such as dwell times and bus paths.

Check parking operations.

Verify pedestrian operations and delays are properly accounted for in the model.

6. Driver behavior and vehicle characteristics:

Check and revise, as necessary, the default vehicle types and dimensions.

Check and revise the default vehicle performance specifications.

Check and revise the default driver behavior specifications.