Skip to content

Harmonize subcategories for transportation variables #400

@danielhuppmann

Description

@danielhuppmann

As part of #398, I noticed that the transportation-sector subcategories are not well structured. They were imported transferred directly from NAVIGATE and ENGAGE as one of the first actions in common-definitions (#3).

Specifically, the imported variables were

  • Emissions|CO2|Energy|Demand|Transportation|Bus
  • Emissions|CO2|Energy|Demand|Transportation|Light-Duty Vehice
  • Emissions|CO2|Energy|Demand|Transportation|Truck

and similar variables for energy demand, but no corresponding variables for cars or motorcycles.

We also have

  • Energy Service|Transportation|Freight|Truck
  • Energy Service|Transportation|Passenger|Road|Light-Duty Vehicle:

and similar variables with the Freight category.

This inconsistency is not helpful.

I suggest to restructure the emissions- and energy-demand variables by adding "Road" or "Road|Passenger" or "Road|Freight" to improve consistency of the variable tree, and to add a complete set of road-transportation modes.

Implementation-wise, we could rename the variables in all IIASA-hosted databases (that are still in active use) at the same time as updating common-definitions, to minimize the disruptions to modelling teams and users.

Any comments @IAMconsortium/common-definitions-transport @IAMconsortium/common-definitions-coordination

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions