The attached zip file includes the below Cube catalog example to show how to get total transit volumes in links and total ridership at stops by merging multiple LINKO files in PT. It also includes a process to add the transit volumes and ridership into highway network as well as to create the transit line file (*.LIN) with transit estimations. Note that The ‘ONOFFS’ sub-keyword along with ‘FILEO LINKO’ should be set as ‘T’ (true) to contain link volumes (e.g. ‘VOL’), boardings (e.g. ‘ONA’) and alightings (e.g. ‘OFFA’) in the output files of transit assignment.
In the above Cube catalog example, one may modify a catalog key of ‘N_LINKO’ (number of input files) and revise the scripts of PILOT in Step 1 in order to specify the LINKO files based on your transit model. This CubeTown example currently uses only 3 LINKO files as AM peak, PM peak, and off-peak.
IN_FILE='CubeTown_PT_AMPeak_LINKO.DBF' ; table for AM peak LINKO
IN_FILE='CubeTown_PT_PMPeak_LINKO.DBF' ; table for PM peak LINKO
IN_FILE='CubeTown_PT_OffPeak_LINKO.DBF' ; table for off-peak LINKO
The input highway network can be replaced in the NETWORK program of Step 7.
As referred on the below ‘Graphics’ program, one can display total transit volumes along with highway network using the built-in options in Cube Base such as ‘Transit On/Off Bars’, ‘Transit Line Profile’, and ‘Multi-Bandwidth’. In addition, the highway network includes total transit link volumes in links and total boardings & alightings in nodes.
Note that only ‘LINKO’ files and one highway network file are required to be processed in this example.
PT_Merge_LINKO.zip (331.2 KB)