Description Usage Arguments Details Functions
Produce transportation variables by service, mode, submode, fuel, and vintage.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 | module.pass_trans_service_output(mode, allqueries, aggkeys, aggfn, years,
filters, ounit)
module.frgt_trans_service_output(mode, allqueries, aggkeys, aggfn, years,
filters, ounit)
module.pass_trans_final_energy(mode, allqueries, aggkeys, aggfn, years,
filters, ounit)
module.frgt_trans_final_energy(mode, allqueries, aggkeys, aggfn, years,
filters, ounit)
module.pass_trans_service_intensity(mode, allqueries, aggkeys, aggfn,
years, filters, ounit)
module.frgt_trans_service_intensity(mode, allqueries, aggkeys, aggfn,
years, filters, ounit)
module.pass_trans_load_factor(mode, allqueries, aggkeys, aggfn, years,
filters, ounit)
module.frgt_trans_load_factor(mode, allqueries, aggkeys, aggfn, years,
filters, ounit)
process.tr_svc_output(allqueries, aggkeys, aggfn, years, filters, ounit)
process.tr_fe_output(allqueries, aggkeys, aggfn, years, filters, ounit)
process.trans_load_factors(allqueries, aggkeys, aggfn, years, filters,
ounit)
process.tr_svc_intensity(allqueries, aggkeys, aggfn, years, filters, ounit,
nativeunit)
module.sales(mode, allqueries, aggkeys, aggfn, years, filters, ounit)
|
mode |
Either |
allqueries |
List of all the queries pulled by the system. |
aggkeys |
Character string listing the aggregation columns desired. All of these columns must be present in the table computed by the main body of the function. If empty or NULL, no aggregation will be performed. |
aggfn |
Function to use for aggregating. If none specified,
|
years |
Years to include in the output |
filters |
Character string giving a list of additional filters to be applied, in s-exp format. |
ounit |
Desired output unit. If omitted, results will be returned with no unit conversion. |
The transportation representation in GCAM is devilishly complicated, due to the pass-through sectors needed to sidestep the model's requirement that sectors have (exactly) three levels of detail. As a result, GCAM's normal designations of "sector", "subsector", and "technology" aren't really meaningful for transportation. A quantity represented as a sector could be spliced in underneath another sector, for example.
Each transporttion data module starts with a call to the
trans_standardize
function, which translates all of the GCAM output
variables to the standard taxonomy. Each module also comes in a passenger
and a freight variant. This is necessary because although the procedure for
producing the data is the same for each variant, there are some subtle
differences, especially where units are concerned that make them
incompatible. The parts of each module that are compatible are
factored into a single worker function that is called by both variants
module.pass_trans_service_output
: Passenger transportation service output data module
module.frgt_trans_service_output
: Freight transportation service output data module
module.pass_trans_final_energy
: Passenger transportation final energy module
module.frgt_trans_final_energy
: Freight transportation final energy module
module.pass_trans_service_intensity
: Passenger transportation service intensity module
module.frgt_trans_service_intensity
: Passenger transportation service intensity module
module.pass_trans_load_factor
: Passenger transportation load factor data module
module.frgt_trans_load_factor
: Freight transportation load factor data module
process.tr_svc_output
: Worker function for transportation service output modules
process.tr_fe_output
: Worker function for service output modules
process.trans_load_factors
: Worker function for load factor modules
process.tr_svc_intensity
: Worker function for transportation service
intensity
module.sales
: Vehicle sales
This module appears to be incomplete.
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.