Freight Skims - CMAP-REPOS/MFN_Programs-and-skims GitHub Wiki

Freight Skims

The Freight Skims currently support two different model run scenarios:

  • 100: logistics node 140 not active any years
  • 200: logistics node 140 active all years

The Freight Skims are executed with different scenarios in EMME, where # reflects the model run scenario (100, 200):

  • #00: Base Freight Network
  • #01: Skim Network for Trucks
  • #02: Skim Network for Inland Waterways
  • #10: Crude Oil Pipeline Network
  • #11: Petroleum Pipeline Network
  • #12: Coal NEC Pipeline Network

The 'Meso_Freight_Skim_Setup_c##q#_YYYY' folder contains the basic setup to run the freight skimming procedures. The file, 'Run_Freight_Skims.bat' executes the freight skimming procedures for the user specified inputs.

Generally the procedures are as follows:

  1. Populate 'Meso_Freight_Skim_Setup_c##q#_YYY/Database' with input data that is constant for any skim model run. This includes

    • emmebank
    • Pipeline network batchin files
    • Rail lines batchin file
    • Modes, matrices, volume-delay functions, poe nodes, and vehicle
    • Post processing files including data about warehouses, airports, and water ports

  2. Generate copies of the skim setup for each analysis year

  3. Populate year-specific skim setups with year and scenario-specific data

  4. Execute skims and post-processing procedures for each year, each scenario

  5. Internal data QA/QC to ensure the current set of skim results are internally consistent

  6. Comparison data QA/QC to compare freight skim results to a user specified previous set

Data Inputs Freight skim inputs are obtained from three primary sources

  1. MFN batchin files - obtained from the MFN geodatabase and batchin network tools
  2. CMAP's TBM - obtained from running a script on a recent TBM copy
  3. Static inputs - stored in CMAP's V drive and gets auto copied into the setup