We currently write out trace files for 4step as follows;
for demographic and zone processor - a taz csv file with all zones and calculations
for links - a link csv file with all links in the trace zones and calculations
for od - aggregation across columns (i.e rowSums) for all od calculations
What we want to do instead for the od processor is write a sum for each origin district to destination district pair. We will code the districts at the TAZ level, probably in the COCs definition file. We will then trace out a FROM DISTRICT, TO DISTRICT, aggregated calculation result for expression 1, aggregated calculation result for expression 2, etc. The output file will look something like this:
We currently write out trace files for 4step as follows;
What we want to do instead for the od processor is write a sum for each origin district to destination district pair. We will code the districts at the TAZ level, probably in the COCs definition file. We will then trace out a FROM DISTRICT, TO DISTRICT, aggregated calculation result for expression 1, aggregated calculation result for expression 2, etc. The output file will look something like this: