Travel Demand Model - OKI

More documents

Recommendations

Info

OKI/MVRPC Travel Demand Model – Version 6.0Walk access and egress connectors are generated automatically using a utility previouslydeveloped for Model 54 (WalkCn11). This program was revised to search for additional walkconnectors even when the zone's highway centroid connectors can be used as transit accessconnectors. The revised utility is named WalkCn12.4.5 Drive Access ConnectorsTransit drive access connectors are used to allow passengers to access the transit network at thepark-and-ride stations. Drive access connectors are generated automatically using a utility calledDrvLinks. This program has been setup to build one connector per TAZ, linking each zone to itsnearest park and ride lot. An accompanying utility, AccSpeed, is used to post highway networktravel times to the links built by DrvLinks. In this way, drive access times are directly skimmedfrom the peak and off peak highway networks. A detailed description of these utilities isavailable in the User's Guide for model version 6.0.4.6 Transit Access BarriersTransit access barriers are used in the OKI model to prevent walk access links across rivers,freeways or similar geographical features. No transit barriers were required for the Daytonportion of the network. The transit barriers already developed for the OKI Council regionnetwork (Model 5.4) were included in the consolidated model.4.7 Transit Network SummaryThe major identifying characteristics of the consolidated transit network are summarized below inTable 4-6.Table 4-6 Consolidated Transit Network CharacteristicsMode Lines Company Description1 - - Walk connector2 - - Drive connector3 1-255 - Sidewalk4 1-255 1 SORTA/METRO local service5 1-100, 150-199 1 SORTA/METRO express service5 101-149, 200-255 2 TANK express service6 30-255 2 TANK local service6 1-10 3 Middletown local service6 11-29 4 Hamilton local service7 1-255 5 Light Rail (non-existent in 1995)8 1-255 5 Commuter rail (non-existent in 1995)9 1-255 6 MVRPC local service10 1-255 6 MVRPC express serviceZones and Networks / 4 - Transit Networks18
OKI/MVRPC Travel Demand Model – Version 6.05. Transit Network SkimmingThe procedures for building transit paths and calculating walk, in-vehicle, transfer and wait timesfor all transit modes were significantly overhauled as part of the Version 6.0 model developmenteffort. The new path building procedures are consistent with the nested structure adopted forthe consolidated mode choice model (see Figure 5-1). In addition, the procedure for estimatingzonal fares was updated to reflect the zone system of the consolidated region.Figure 5-1 Consolidated Model Mode Choice StructureChoiceAutoTransitDrive Alone Shared Ride Local Express Urban CommuterBus Bus Rail Rail2-Person 3+ Person Walk Park Kiss Walk Park Kiss Walk Park Kiss Walk Park KissAuto Auto Ride Ride Ride Ride Ride Ride RideRideHOV NonHOVHOV NonHOV5.1 Transit Path BuildingThe path building routine constructs eight sets of transit paths, two per transit mode, and foreach transit mode one per access mode, resulting in the following sets: local bus (walk access,drive access), express bus (walk access, drive access), light rail (walk access, drive access), andcommuter rail (walk access, drive access). Light and commuter rail are not valid transit modes inthe base year (1995), but they are included for testing alternative transit scenarios. In the eventthat these modes were available, it is expected that the local bus system will feed trips into therail system. Thus transit paths for which express bus, light rail or commuter rail is the maintransit mode are allowed to transfer to/from the local bus system. The parameters used toweight wait, walk, run and transfer times are listed in Table 5-1. Please see Appendix D for acopy of the path building Tranplan control files.Zones and Networks / 5 - Transit Network Skimming19
Page 1 and 2: APPENDIX F • TRAVEL DEMAND MODEL
Page 3 and 4: OKI/MVRPCTravel Demand ModelVersion
Page 5 and 6: Table of ContentsPart IPart IIPart
Page 7 and 8: OKI/MVRPC Travel Demand Model - Ver
Page 27: OKI/MVRPC Travel Demand Model - Ver
Page 37 and 38: Table A.1 (cont.)Zone System Equiva
Page 47 and 48: Table A.2Zone System Equivalences -
Page 53 and 54: Table A.3Zone System Equivalences -
Page 55 and 56: Table B.1External Stations in the C
Page 57 and 58: Table B.1External Stations in the C
Page 79 and 80:
OKI/MVRPC Travel Demand Model - Ver
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
User Documentation forAutomated Acc
Page 105 and 106:
[Transit Format][New Link Attribute
Page 107 and 108:
distance for each centroid or node.
Page 109 and 110:
Figure 1Example Control File for th
Page 111 and 112:
LinkType = 99VolumeDelay = 99Lanes
Page 113 and 114:
NetworkScale = 1.0 Scale factor to
Page 115 and 116:
Figure 4Example Output from DRVLINK
Page 117 and 118:
Appendix ASample EMME/2 Transit Lin
Page 119 and 120:
Appendix FTravel Demand ModelingTec
Page 121 and 122:
Index of TablesTable 2-1 Socio-Econ
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Index of TablesTable 2-1 Trip Lengt
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Table of Contents1. Background ....
Page 229 and 230:
Index of FiguresFigure 2-1 Alternat
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
NORTH-SOUTH TRANSPORTATION INITIATI
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Run # 63: Start with 7.17 estimatio
Page 283 and 284:
Run # 67:Split parking cost from ot
Page 285 and 286:
Run # 70a:Include zero-auto segment
Page 287 and 288:
Run # 71c:Repeat #71a with zero aut
Page 289 and 290:
Run # 71g:Repeat #71d with wait tim
Page 291 and 292:
Run # 73:Include residential densit
Page 293 and 294:
Run # 76:Nest: auto vs transitVaria
Page 295 and 296:
Run # 79:Repeat #72 with zero autos
Page 297 and 298:
Run # 80:Nest: auto vs. all othersV
Page 299 and 300:
Run # 82:(071h) nested: auto vs tra
Page 301 and 302:
Run #3VariableModeDrive Shared Ride
Page 303 and 304:
Run #8VariableModeDrive Shared Ride
Page 305 and 306:
Run #12 test: make aoc=10.5 instead
Page 307 and 308:
Run #29VariableModeDrive Shared Rid
Page 309 and 310:
Run #33VariableModeDrive Shared Rid
Page 311 and 312:
Run #37vot constrained to $7.00Vari
Page 313 and 314:
Run #30bSame as #30a, combine cost
Page 315 and 316:
Run #140 (same as run #40)vot const
Page 317 and 318:
Run #140b (same as run #40)vot cons
Page 319 and 320:
Run #141avot constrained to $3.00 &
Page 321 and 322:
Run #141cvot constrained to $3.00 &
Page 323 and 324:
Run # 1:Base RunVariablesModesDA Sh
Page 325 and 326:
Run # 5:Base Run with walk time set
Page 327 and 328:
Run # 8:Base Run, split walkVariabl
Page 329 and 330:
Run # 10: Nested structure (autos v
Page 331 and 332:
Part VITRIP ASSIGNMENT ANDVALIDATIO
Page 333 and 334:
Index of TablesTable 2-1 Average Ve
Page 335 and 336:
Page 337 and 338:
Page 339 and 340:
Page 341 and 342:
Page 343 and 344:
Page 345 and 346:
Page 347 and 348:
Page 349 and 350:
Page 351 and 352:
Page 353 and 354:
Page 355 and 356:
VOBFigure 4-8 Screenline Location -
Page 357 and 358:
2759OKI/MVRPC Travel Demand Model -
Page 359 and 360:
Page 361 and 362:
Page 363 and 364:
Page 365 and 366:
Page 367 and 368:
Page 369 and 370:
Page 371 and 372:
Page 373 and 374:
Page 375 and 376:
Page 377 and 378:
Page 379 and 380:
Page 381 and 382:
Page 383 and 384:
Page 385 and 386:
Page 387 and 388:
Page 389 and 390:
Page 391 and 392:
Table of Contents1. Introduction...
Page 393 and 394:
Page 395 and 396:
Page 397 and 398:
Page 399 and 400:
Page 401 and 402:
Page 403 and 404:
Page 405 and 406:
Page 407 and 408:
Page 409 and 410:
Page 411 and 412:
Page 413 and 414:
Page 415 and 416:
Page 417 and 418:
Page 419 and 420:
Page 421 and 422:
Page 423 and 424:
Page 425 and 426:
Page 427 and 428:
Page 429 and 430:
Page 431 and 432:
Page 433 and 434:
Page 435 and 436:
Page 437 and 438:
Page 439 and 440:
Page 441 and 442:
Page 443 and 444:
Page 445 and 446:
Page 447 and 448:
Page 449 and 450:
Table of Contents1. Introduction...
Page 451 and 452:
2. Surveys and Other Datasets2.1 OK
Page 453 and 454:
Table 2-1 OKI Home Interview Survey
Page 455 and 456:
Page 457 and 458:
Page 459 and 460:
Table 1-4 On-Board Survey Data Dict
Page 461 and 462:
2.3 External Station Survey - Conso
Page 463 and 464:
2.4 External Cordon Survey - Consol
Page 465 and 466:
2.5 External-External Trip Table fr
Page 467 and 468:
2.20 Screenline Shape File - Screen
show all

Travel Demand Model - OKI

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?