As described in #56, Gelato builds an in-memory activities table based on the MATSim output trips file.
However, some MATSim simulations generate most of the same activity data in an output_activities.csv.gz file (depending on the version of MATSim, I think, and possibly config settings). It would be more efficient to use this file when it is detected in the MATSim output directory rather than generating it ourselves from trips. Where the file is unavailable, we should fall back to generating the data as we do now.
One thing to iron out: in our activities table, we augment the activity data with two new columns to represent access/egress trip and mode for each activity (which is used for one of the KPIs). Those values are not present in the MATSim activities table, so we will need to augment the parsed data with these two columns.
As described in #56, Gelato builds an in-memory activities table based on the MATSim output trips file.
However, some MATSim simulations generate most of the same activity data in an
output_activities.csv.gzfile (depending on the version of MATSim, I think, and possibly config settings). It would be more efficient to use this file when it is detected in the MATSim output directory rather than generating it ourselves from trips. Where the file is unavailable, we should fall back to generating the data as we do now.One thing to iron out: in our activities table, we augment the activity data with two new columns to represent access/egress trip and mode for each activity (which is used for one of the KPIs). Those values are not present in the MATSim activities table, so we will need to augment the parsed data with these two columns.