Update meesa_v1.1.yaml

[tatar99]

INNOPATHS mapping for MEESA. @danielhuppmann, @Renato-Rodrigues. I'm still a little bit confused here. Do I have to add this mapping also into "openentrance/definitions/region/model_native_regions/meesa_v1.1.yaml" file?

[danielhuppmann]

Thanks for the PR @tatar99 - sorry for the confusion.

It is not necessary to define the IP regions in the "openentrance/definitions/region/model_native_regions/meesa_v1.1.yaml".

If you upload data for the region "ECE", this will be renamed to "Eastern Europe (IP)" for MEESA v1.1 and ECE will not be stored to the database.

Alternatively, you could let the IIASA database infrastructure to the aggregation for by specifying the mapping, e.g.,

  - Germany (IP):
      - DEU
  - Eastern Europe (IP):
      - CEU
      - POL
  ...

The docs of the region-processing machinery are available at https://nomenclature-iamc.readthedocs.io/en/stable/user_guide/model-mapping.html

Let me know whether you want to submit INNOPATHS-aggregates directly, or if you want to provide the mapping - then please update this PR accordingly.

[tatar99]

I want to submit new mapping directly. Maybe for the sake of clarity I should explain the situation in detail. Currently MEESA can produce results in it's original mapping:

• MEESA v1.1|BEN

• MEESA v1.1|CEU

• MEESA v1.1|IBI

• MEESA v1.1|NTH

• MEESA v1.1|STH

• MEESA v1.1|UKI

• MEESA v1.1|DEU

• MEESA v1.1|FRA

• MEESA v1.1|POL

  or in the new mapping:

• MEESA v1.1|DEU

• MEESA v1.1|FRA

• MEESA v1.1|UKI

• MEESA v1.1|ECE

• MEESA v1.1|ECS

• MEESA v1.1|ENC

• MEESA v1.1|ESC

• MEESA v1.1|ESW

• MEESA v1.1|EWN

• MEESA v1.1|NEN

Some of this regions are defined exactly the same way (even with the same names like DEU, FRA, UKI) as in our original aggregation but most are not. Currently I'm only able to upload data in the original mapping and I need a solution to be able to upload also in this alternative mapping, directly from MEESA, without aggregation on database level. After reading docs about region processing you linked, I belive I should simply define additional regions as MEESA native in the "openentrance/definitions/region/model_native_regions/meesa_v1.1.yaml". Sorry to take your time, but I'm still not 100% sure how to proceed.

[danielhuppmann]

closing in favor of #251