Skip to content

Export import varaibles / based on NAVIGATE / ENGAGE#286

Open
FlorianLeblancDr wants to merge 16 commits intoIAMconsortium:mainfrom
FlorianLeblancDr:export_import
Open

Export import varaibles / based on NAVIGATE / ENGAGE#286
FlorianLeblancDr wants to merge 16 commits intoIAMconsortium:mainfrom
FlorianLeblancDr:export_import

Conversation

@FlorianLeblancDr
Copy link
Contributor

This PR adds Export Import variables from NAVIGATE / ENGAGE

Some macro sectors are missing but will dynamically change by updating the tag (#279 )
Export|Energy
Export|Industry|Chemicals
Export|Industry|Manufacturing
Export|Industry|Energy
Export|Other
Export|Industry|Energy Intensive

Discarded (can be computed within the database):
Exports|% change per GDP
Export|Developing Country Share
Exports|% change from Ref

@FlorianLeblancDr FlorianLeblancDr requested a review from a team February 19, 2025 13:58
@FlorianLeblancDr
Copy link
Contributor Author

Having second thoughts, I am moving export and import variables to the trade.yaml files
and improve clarity of the use of variable name with a header

@FlorianLeblancDr FlorianLeblancDr marked this pull request as draft February 19, 2025 15:22
@FlorianLeblancDr
Copy link
Contributor Author

Looking at NAVIGATE and ENGAGE "Trade" variables, I further discarded:
"Trade|Emissions|Value|Carbon*" variables (redundant with "Trade|Emissions Allowances*"
"Trade|Gross Import|Secondary Energy|Electricity|*": we can add Export and Import of energy in a further release

@FlorianLeblancDr FlorianLeblancDr marked this pull request as ready for review February 19, 2025 15:54
@FlorianLeblancDr
Copy link
Contributor Author

@volker-krey @macflo8
This a good example on implementing both ISIC sector nomenclature and biophysical nomenclature.
The same can be done for Production, for exampel.

@FlorianLeblancDr FlorianLeblancDr removed the request for review from macflo8 March 3, 2025 14:00
Copy link
Member

@danielhuppmann danielhuppmann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few suggestions and comments inline, and a more general question: do we really need to have aggregate Import and Export variables as tier 1? There have been some concerns expressed by modeling teams that there are too many tier-1 variables for that category to be useful.

FlorianLeblancDr and others added 2 commits March 21, 2025 10:50
approved sugegstions

Co-authored-by: Daniel Huppmann <dh@dergelbesalon.at>
change tiers to 2
@FlorianLeblancDr
Copy link
Contributor Author

Done,
I also changed tier to Tier 2
@danielhuppmann

@FlorianLeblancDr
Copy link
Contributor Author

@danielhuppmann I think this has been reviewed and coul dbe merged

@FlorianLeblancDr
Copy link
Contributor Author

@danielhuppmann A kind reminder to merge this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants