Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update REMIND-MAgPIE_3.4-4.8.yml #266

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

jkikstra
Copy link
Contributor

Suggestion for e.g. @merfort to look at.

Not the most urgent, but good to align.

@jkikstra jkikstra changed the title Add Kosovo Update REMIND-MAgPIE_3.4-4.8.yml Jan 29, 2025
@merfort
Copy link
Contributor

merfort commented Jan 30, 2025

Since Kosovo is not part of the ISO country list, we don't have it in our internal region mappings, and usually map input data to Serbia, afaik.
So I guess it's fine to add it here to Non-EU28 Europe.

@jkikstra
Copy link
Contributor Author

usually map input data to Serbia

Yeah in general this was my assumption at first, too.
However, the data providers of GDP and Population SSP data told me that Kosovo is NOT part of Serbia.
They're working on adding it in the next version.
So even if not an internationally recognised ISO, with data there, I think it's probably useful to have it as an additional territory with ISO in our mappings?

@merfort
Copy link
Contributor

merfort commented Jan 30, 2025

Ah, interesting. Yes, then I guess it makes sense to add that to the list of countries.
But shouldn't we wait then, until the SSP update is there?
@johanneskoch94, maybe interesting for you.

@jkikstra
Copy link
Contributor Author

But shouldn't we wait then, until the SSP update is there?

For the aggregation of CEDS (&GFED) emissions I already need to decide where emissions from Kosovo go (i.e. to which REMIND region should I add it when making the history-vs-scenario comparison plots, and similar for harmonizing a regional pathway regions).
Therefore I'm trying to already get them in to the region that is most applicable.

@merfort
Copy link
Contributor

merfort commented Jan 30, 2025

Thanks! Makes sense. Then putting it to Non-EU28 Europe is definitely the right choice.

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.

2 participants