Ohio Standard Small/Medium MPO Travel Demand Forecasting Model

1. Ohio Standard Small/Medium MPO Travel Demand Forecasting Model Network Coding Training May 9th, 2006

2. Highway NetworksWhat are they? Representations of the streets, roads, thoroughfares, and freeways that make up the regional highway system.

3. Accurate Representation • If the network system data are accurate, the level of effort needed to calibrate or validate the model will be greatly reduced. • Help to avoid questions from the “non-believers”. (i.e. People who say the model is worthless when it doesn’t favor their project.) • Garbage In – Garbage Out • Intersection (Junction) Modeling

4. Network Checks & Definitions • Nodes and Links • Network Connectivity • Link Attributes • Turn Prohibitors • Transit Lines

5. Nodes and Links • Nodes are used to define intersections, merges, changes in direction, TAZ centers • Node number, X and Y coordinates • Links connect two nodes • Defined by the nodes they connect (A&B) • Many Attributes

6. Common Connectivity Errors • Missing nodes • Missing centroid connectors

7. Common Connectivity Errors Wrong way links Excess links

8. Common Connectivity Errors • Centroids at non-intersections • Connect centroids to stub links to better represent intersections

9. Common Connectivity Errors • More than 4 links per node • Will not work with intersection calculator • Turn penalty calculator will report these nodes

10. Link Attributes

11. Link Attributes

12. Link Attributes • Scrn_Pen – Screenline penalty in minutes • Dist – Distance in miles • Automatically calculated for new links, when links are split, and when nodes are moved (unless specified to Do Not Recalculate) • PostSpd - Posted speed limit in miles per hour • SpeedMod – Speed adjustment in miles per hour

13. Link Attributes • FunClass - the type of roadway based on operational characteristics - not Federal FC • Functional Class Categories: • 10 - Freeway: divided highway, full access control • 20 - Expressway: divided highway, full or partial access control; includes limited access rural arterials • 30 - Ramp: entrance/exit for limited access facility • 40 - Arterial: serves major movement of traffic • 50 - Collector: collects and distributes traffic from several access connections • 60 - Local: only provides access to abutting properties • 70 - Centroid Connector: represents local access points

14. Link Attributes • AreaType - specific location/area within network • Codes: • 1 - Rural: controlled intersections 2 miles apart • 2 - Suburban: residential development • 3 - Urban: mixed residential and commercial • 4 - Central Business District: intense business activity; usually the downtown area of a city • 5 - Outlying Business District: for roads with excessive access points compared to density (commercial strips) • 6 - Low Access Urban: for roads with limited access, such as access-controlled shopping areas

15. Link Attributes • Lanes - number of mid-link through travel lanes, and default number of intersection through lanes • Twidth - directional roadway width in feet

16. Link Attributes • TurnLane - indication of dedicated left or right turning lanes • 2-digit codes • 5-digit codes • Use 2-Digit codes when possible • First digit is the number of left turn lanes • Second digit is the number of right turn lanes • Illustrated: TURNLANE = 10

17. Link Attributes • IXtype - intersection type • 0 = Pretimed (adaptive) signal • 1 = Interconnected signal • 2 = 2-way stop (1-way stop at T-intersections) • 3 = Uncontrolled intersection • 4 = All-way stop • MedTurn - indication of a mid-link median turn lane • Codes: 1 = median turn lane, 0 = no lane • If median lane is coded, but no left turns coded at an intersection, a left turn lane is assumed

18. Link Attributes • Parking - indicates on-street parking during peak • Blank: On-street parking is prohibited • 0: Use only if Lanes field contains operating number of lanes and on-street parking • 1: 1 lane is used for parking • 2: One-way street with parking on both sides

19. Link Attributes • Terrain - accounts for link grade characteristics • Codes: • 1 = Level (<2% grade, 2-3% < 1 mi., 3-4% < 0.25 mi.) • 2 = Rolling (2-3% grade > 1 mi., 3-4% > 0.25 mi., 5-6% < 0.3 mi.) • 3 = Mountainous (>4% grade > 0.3 mi.) • Blank = accepts default code set in calculator

20. Link Attributes • CarToll – Toll per mile for autos • 3.9 cents per mile • TrkToll – Toll per mile for trucks • 12.9 cents per mile

21. Link Attributes Being Phased Out • IXTHRU • PCTTRK • CAPADJ

22. Calculated Link Attributes • LNKGRP • PEAKSPD • OFFPSPD • PEAKRSPD • OFFPRSPD • CAP24 • SAT24

23. Other Link Attributes • AADT • SCNLINE • DISTRICT • ADMCLASS • RTENAME • RTENUMB • COUNTY • FEDFUNC

24. Other Link Attributes • FedFunc - federal functional class • Don’t confuse with FunClass Rural Urban 01 - Interstate 11 - Interstate 02 - Other Principal Arterial 12 - Freeway/Expressway 06 - Major Arterial 14 - Other Principal Arterial 07 - Major Collector 16 - Minor Collector 08 - Minor Collector 17 - Collector 09 - Local 19 – Local • FunClass for rural principal arterial?

25. POHIBITORS AND TRANSIT

26. Turn Prohibitors • Text file • List of three nodes that define the turn movement prohibited • Each record also has a set number and prohibitor definition (-1) • Updating of file is semi-automatic, but for link splits only • File can also contain link penalty overrides (in minutes)

27. Turn Prohibitors • Example Listing 2576 1656 401 1 -1 2669 1657 1658 1 -1 2588 1750 2584 1 -1 2582 1756 2586 1 -1 2789 1805 2657 1 -1 2659 1807 2788 1 -1 2630 1854 2634 1 -1 2636 1856 2632 1 -1 1912 1926 1928 1 4 1928 1926 1912 1 4 1910 1930 2820 1 4 2820 1930 1910 1 4 2666 2162 2670 1 -1 2559 2563 2555 1 -1

28. Transit Lines • Text file • Route attributes and a listing of nodes that define the route • Automatic updating feature when network changed • LINE NAME="1", MODE=1, ALLSTOPS=T, HEADWAY[1]=29, ONEWAY=F, XYSPEED=20, N=1206, -1280, 1282, -1284, -1286, 1296, -1326, -1322, -1320, -1318, 936, 886, -934, -926, -906, 944, -832, -949, -830, 2878, 828, -578, -576, -574, -572, 570, 732, -568, -566, -564, 2873, 476, 501, 421, 426, -2819, -424, 419

29. Before Network Editing • Open Turn Penalty (Prohibitor) File • Display Locations • Node/Point Color • Use NumProh>0 • Use NumPenalty>0 to view prohibitor and override penalties • Penalties not used in junction modeling for nodes defined as junctions

30. Turn Prohibitors • At least one prohibitor per location shown

31. Turn Prohibitors • View (Edit) Prohibitors • First use pointer to select a node

32. Turn Prohibitors • Saving changes to the prohibitor file is separate from saving network changes • Use the disk icon in the Edit Penalties viewer to save prohibitor changes • Nodes will be temporarily be changed when splitting a link, but the prohibitor file must be saved • Deleting links will leave stranded prohibitors

33. Turn Prohibitors • To be safe, delete prohibitors first • Click the movement in the penalty matrix and delete prohibitor indicator (-1) • Add prohibitors back in after network changes • Turn penalty calculator will list turn prohibitor movements that are not in the network (turn2000.log) • Arrow diagram in viewer • Left click for From Leg • Right click for To Leg

34. Turn Penalties • Turn Penalty Calculator uses prohibitors in conjunction with default penalties based on movement direction and link functional classes • Left, Right, and Through movements calculated based on the angle between links • Use Process Template…\[Turn Calculator 2000] to view/change default values (value of 20 means 0.20 minutes) • Turn Prohibitor file can also contain Penalty override values

35. Turn Penalties • Complete penalties and prohibitors can also be viewed • In junction modeling, penalties not used at ‘valid’ intersections: • Has 3 or 4 total links • Has 3 o 4 non-centroid links • Has at least 2 non-centroid entrance links • Has at least one link of functional class 40, 50 or 60 • At least one of those non-centroid entrance links has an IXTYPE other than 3 or all IXTYPE’s are blank

36. Before Network Editing • Add Transit Layer • Layer Control \ Transit \ Layer Properties • Browse… Open Transit Line File (*.lin)

37. Transit Layer • All transit lines displayed • Transit Tools • Display Transit Line(s) • Display All Transit Lines • Transit Line Manager • Add other transit lines • Display Transit \ Clear All \ OK • Lines aren’t shown, but are still loaded

38. Transit Layer • Splitting network links used by a transit line • Must save the transit line file • Deleting network links used by a transit line • Transit line will use XYSPEED value

39. NETWORK EDITING

40. Editing Tools • Pointing Mode • Zoom In • Zoom Out • View Move (Pan) • Post 1 Node • Post 1 Link • Refresh • Zoom All • Center on Nodes • Post Node • Post Link • Node/Point Color • Link/Line Color • Band Width Settings • Layer Control

41. Geometry and Direction • Old • New

42. Intersections • 5-legged Intersections • Merge 2 legs into a stub link near the intersection • Do not code IXTYPE for these 2 links • Stub IXTYPE is uncontrolled, and Distance = 0 IXTYPE

43. Intersections • Divided Highways (at-grade signal) • Divided Highways (end of division)

44. Stop Intersections • Stop Control • All-way stop • 2-way stop • All traffic control interruptions coded for geometry, even if no significant volume exists on a leg • Do not have a centroid connected to a stopped 3-legged intersection IXTYPE

45. Stop Intersections • Stop Control HCM Limitations • For 3-legged intersections, there cannot be stops on only 2 legs • For 4-legged intersections, there cannot be two adjacent stops, unless it is an all-way stop • If reality contradicts these rules, code the reality and let the junction calculator use it’s default methodology

46. Signalized Intersections • All incoming links to a signal node should be coded • If even one leg is coded as uncontrolled, the whole intersection will be treated as partial stop • Do not have a centroid connected to a signalized 3-legged intersection

47. Intersection Turn Lanes • 2-Digit Codes • First digit = left only lanes • Second digit = right only lanes • 5-Digit Codes • First digit = left only lanes • Second digit = shared left/through lanes • Third digit = through only lanes • Fourth digit = shared right/through lanes • Fifth digit = right only lanes

48. Intersection Turn Lanes • Shared lanes assumed if movements are allowed but no exclusive lanes are specified • One approach lane : all movements allowed • Two approach lanes • One Left/Through lane • One Through/Right lane • Three approach lanes • One Left/Through lane • One Through only lane • One Through/Right lane

49. Intersection Turn Lanes • Use 2-digit code when possible • When to use 5-digit code • Dual turn lane when one is shared • Through lanes is different from LANES • Default through lanes = LANES • Eliminates the need to code IXTHRU • Try to code the middle digit (of 5)

50. 5 Digit Turn Lane Coding • LANES, PARKING, IXTHRU, and MEDTURN are all ignored • However, LANES, PARKING, and MEDTURN still affect the computation of saturation flow rate and should thus be maintained