Travel Demand Model - OKI

More documents

Recommendations

Info

characters (#, *, +, ) that can accompany the dwell time option. In addition, the program reads overthe "path," "ttf," "lay," "us," and other temporary specifications. In TRANPLAN, transit stops are indicatedwith a '-' (minus sign) preceding the node number.Transit line itineraries should be supplied in EMME/2 batchout or TRANPLAN INET format. To ensure thisis the case the transit lines should be read into EMME/2 and then batched out. This will ensure that thestandard formats are abided by. An example of the transit line format is included in Appendix A forEMME/2 and in Appendix B for TRANPLAN (INET).Parameter Controls for WLKLINKS ProgramThis section describes the various parameter controls for the WLKLINKS program. It is organized by[Section Header] with the individual options listed below. The default values are given next to the equalsign.[Files]* These are the default file names.CentroidFile = cents.in Listing of centroids from which to build wlk access links.NodeFile = nodes.in Listing of node coordinates to be used in distance calculations.TransitFile = lines.in Transit line itineraries to be used to determine stop locations.ReportFile = wlklinks.rpt Report file.LinkFile = wlklinks.out Listing of walk access links.[Parameters]* These are the default parameters.NurnCentroids =2000 Number of centroids.HiNodeNumber = 10000 Highest node number.IndividualMax = no If selected, the maximum number of access links can be specifiedon an individual centroid (or node) basis. The maximum number ofaccess links should be placed in node user item 3.MaxLinks = 4 Maximum number of access links for global specification.MultipleStops = no If selected, access links will be built to multiple transit stops on thesame line itinerary. For example, two transit stops on the sametransit line one block apart could both be coded with access linksunder this scenario.SplitUnes = no If selected, the transit line itineraries will be split at the layoverpoint into two separate transit lines for purposes of creating accesslinks. This option can only be used when MultipleStops=no;otherwise it is ignored.SelectModes = no If selected, access links will be built to a subset of transit modes.These modes are listed below.Search Modes = b Subset of alphanumeric transit modes to be used. Modes can bedelimited with either spaces or commas (i.e., b xc or b,c,x).. InEMME/2, modes are defined as single alphabetic characters. InTRANPLAN the modes are defined numerically.Distance = Cartesian Calculates the link distance using the quadratic formula. If"Manhattan" is specified, the link distance is calculated as (X+Y).IndividualSearch = no If selected, the user can specify a minimum and maximum searchUser Documentation for WLKLINKS & DR VLINKS (version 2.0) Page 3
distance for each centroid or node. In addition, the maximumnumber of access links can be specified under the IndividualMaxoption. For EMME/2, the minimum should be in node user dataitem 1, the maximum in node user data item2. For TRANPLAN auser defined centroid format must be used. The minimum andmaximum values would then be placed into column format, withthe appropriate column definitions given in the control file.AverageDistance = yes If selected, the posted link distance will be the average of allaccess links (up to the maximum) for that centroid.MinDistance = 0.0 Minimum search distance for global specification.MaxDistance = 0.33 Maximum search distance for global specification.NetworkScale = 1.0 Scale factor to convert coordinate units to search distance units.WalkSpeed = 3.0 Walk speed for TRANPLAN links.[Reports]EchoTransitUnes =yes If selected, this option will echo the transit lines read in.PrintUnconnected =yes If selected, a list of unconnected centroids will be produced.PrintConnections =yes If selected, a summary of access links will be produced.PrintStats =yes If selected, summary statistics on the number of access links,minimum, maximum, and average link distances will be produced.[Centroid Format]CentroidIFormat = user Indicates format ofcentroid file. Allowable options are 'EMME/2' or'user.' Under TRANPLAN, the format must be specified as 'user"and the next three items must be completed.Number =3-8 These must be specified if CentroidFormat = userXCoord =9-16 These must be specified if CentroidFormat = userYcoord = 17-24 These must be specified if CentroidFormat = userUser1 = 26-32 Contains minimum distance if IndividualSearch = yesUser2 = 34-40 Contains maximum distance if IndividualSearch = yesUser3 = 42-48 Contains maximum links if IndividualSearch = yesFirstCentroid =1 Indicates line number where centroid listing starts.[Node Format]NodeFormat = user Indicates format of node file. Allowable options are 'EMME/2' or'user.' Under TRANPLAN, the format must be specified as 'user'and the next three items must be completed.Number =2-8 These must be specified if NodeFormat = userXCoord =9-16 These must be specified if NodeFormat = userYcoord = 17-24 These must be specified if NodeFormat = userFirstNode =1 Indicates line number where node listing starts.[Transit Format]TransitFormat = EMME/2 Format of transit line itineraries. Only 'EMME/2' and TRANPLAN'are allowed in version 2.X.[New Link Attributes]* These items specify the attributes of the new access linkDeleteLinks =no If selected, add link card will be preceded by delete link card.Direction = twoway Determines the links that are written to the new link file. If "twoway"is specified, both inbound and outbound links will be written to thenew link file. Alternatively, either "inbound" or "outbound" can bespecified for the desired link.Modesin = i Single mode on inbound link to centroid.User Documentation for WLKLINKS & DR VLINKS (version 2.0) Page 4
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 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Table A.1 (cont.)Zone System Equiva
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Table A.2Zone System Equivalences -
Page 49 and 50:
Page 51 and 52:
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 59 and 60: OKI/MVRPC Travel Demand Model - Ver
Page 103 and 104: User Documentation forAutomated Acc
Page 105: [Transit Format][New Link Attribute
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 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:
Appendix FTravel Demand ModelingTec
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:
Appendix FTravel Demand ModelingTec
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

Create successful ePaper yourself

Delete template?

Save as template?