🧹 Chore: Change I/O of Vehicle Trip Demand from OMX to EMME #219
Description
The goal is to avoid intermediately outputting vehicle trip matrices to OMX just to then read them back into EMME.
There are currently four demand markets in tm2py: resident, truck, airport, and external. The resident model runs in CT-RAMP and writes out persons trip list CSV, which is then consumed by tm2py to write out vehicle trips in OMX. The truck, airport, and external models all run in tm2py Python, which all then write out vehicle trips in OMX. The tm2py assignment module then reads from various vehicle trip OMX files and assembles the final trip table in EMME for assignment.
Proposal: since we are using tm2py Python to create vehicle trip tables, why don't we just directly save them in EMMEBANK or some EMME format via tm2py EMME API and get rid of the intermediate OMX files?
This means we will need to change the vehicle trips I/O in various places in tm2py.
Progress:
- Sufficiently defined
- Approach decided
- Implemented