Travel Demand Model - OKI

More documents

Recommendations

Info

OKI/MVRPC Travel Demand Model – Version 6.02.4.2 Multi-stage implementation of synthetic matrix estimationSynthetic matrix estimation procedures attempt to adjust the interchange values in a trip table throughan iterative process of assigning the table to the network, calculating deviations from coded trafficcounts, and using this information to re-factor the trip table. Since the traffic counts coded to thenetwork represent daily link flows that include both trips with both internal and external origins anddestinations, the seed matrix used to initiate the process should also include both internal and externalorigins and destinations.Initial development of the truck model using the SME procedure in TransCAD was based on a seed matrixin which the internal-internal trip tables generated through the Quick Response truck trip generation anddistribution processes were combined with the EE/EI truck trip tables that were formed from the ODOTexternal station survey. A thorough analysis of changes between these initial trip table estimates and theoutput of the SME procedure revealed that some significant changes were being made to the EE/EI flowpatterns. Despite excellent matches to the count data, it was decided that the EE/EI trip flow patternsformed from the expanded ODOT external station survey should be preserved to the extent possible. Toremedy the situation, a multi-stage approach to SME was developed whereby only the internal-internalseed matrix tables would be calibrated and the external station tables left intact. The steps in this multistageSME procedure are as follows:1. Perform a preliminary assignment of the internal-internal seed matrix and save the resultingflows in a new data field.2. Perform a preliminary assignment of the EE/IE truck trip tables and save the resulting flowsin a new data field.3. For each link, calculate the ratio of saved internal-internal truck volume to total saved truckvolumes (internal-internal plus EE/EI).4. For links with daily traffic counts, multiply these ratio times the traffic count totals toapproximate the proportion of count volume that represents internal O-D demand and savethis in a new field as a new calibration count target value.5. Add the saved EE/IE truck trips to the pre-loaded auto volumes for each link, creating a newfield for pre-loaded vehicle volumes.6. Apply the SME procedure to the internal-internal O-D seed matrix, using the new calibrationcount values and the new pre-loaded vehicle volumes.7. Combine the adjusted internal-internal truck trip O-D matrix with the EE/EI truck trip tablesfrom the ODOT external station survey to form the final trip table.Despite the loss of information from using partial count data for calibration, this multi-stage approachresulted in a good fit to the full count data, while producing reasonable zonal trip ends and interchangeflow values.Truck Model - Base-Year Truck Model Development 23
OKI/MVRPC Travel Demand Model – Version 6.02.5 Post-ProcessingTo produce truck trip tables for assignment to the network of the consolidated modeling system requiredthe re-allocation of FAZ-to-FAZ flows to TAZ-to-TAZ flows and the distribution of these flows across thefour time periods of interest. Figure 2-9 illustrates these processes, which are described in this section.SU, MU TripGenerationby TAZEmployment Data(2-digit SIC)Household TotalsDaily SU, MUTruck Trip TablesFAZ-to-FAZSU, MU Production-Attraction WeightsWeighted Allocation ofFAZ-to-FAZ flows toTAZ-to-TAZ flowsDiurnalDistributionFactors (QRFM)Daily SU, MUTruck Trip TablesTAZ-to-TAZAllocation to FourTime PeriodsSU, MU Truck TripTables TAZ-to-TAZby Time Period ofDaySU, MU PCE TripTables TAZ-to-TAZby Time Period ofDayFigure 2-8. Steps followed to distribute daily FAZ-to-FAZ truck flows to TAZ-to-TAZ flows by timeperiodTruck Model - Base-Year Truck Model Development 24
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:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
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:
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: OKI/MVRPC Travel Demand Model - Ver
Page 391 and 392: Table of Contents1. Introduction...
Page 413: OKI/MVRPC Travel Demand Model - Ver
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 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?