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

create mapping for historical data #36

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

eahoegner
Copy link
Collaborator

@eahoegner eahoegner commented Jan 14, 2025

creates the mapping for aggregating the historical data from countries to to the common definitions regions for the IAMs

  • create mapping file History.yaml
  • check for missing countries (see #30)
  • do the aggregation per species and sector to IAM regions
    this may include more sub-points, but I haven't gotten around to figuring out how exactly this is done
  • resolve minor data inconsistencies
    • differences in countries available in CEDS, GFED, and the common definitions (see #30)
    • available time frames; 1997 onwards for GFED, until we use gridded data
    • unify units (GFED did not include /yr)

@eahoegner eahoegner changed the title created mapping for historical data create mapping for historical data Jan 14, 2025
@eahoegner
Copy link
Collaborator Author

so far I've only done this for CEDS alone, but GFED should work similarly. both can be added together in a next step. is there any need down the line to keep track of whether specific data came from CEDS or GFED?

@chrisroadmap
Copy link
Collaborator

so far I've only done this for CEDS alone, but GFED should work similarly. both can be added together in a next step. is there any need down the line to keep track of whether specific data came from CEDS or GFED?

My feeling is that if it's not a pain to do, it might save us a lot of headaches in the future when we come to update these datasets; so inclined to say yes

@jkikstra
Copy link
Collaborator

I've put an example of roughly what I had in mind for this in #37 (it was a lot simpler than what you started here)

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