chore(configs): Aggregate CL

[VIKTORVAV99]

Aggregates CL by creating a top level config and creating a exchange config for the country level exchange.

I'll follow up with updating the translations in the new app.

[BastienBigue]

LGTM 👍
@PaulRoms told me we had monthly/yearly data through IEA/EMBER.
How do we want to handle the country-level flowtraced data ? Through sub zones aggregation or through country-level data (which we don't currently handle in the flowtracing algo) ?

[VIKTORVAV99]

For now it only works through the subZones as you are mentioning.

I think we need to be careful about changing that because for some aggregated zones we are fetching both country level data and subzone data (could be useful for the validation project though).

[BastienBigue]

Agree that we have to be careful about changing this too 👍
Since some zone have no data, sub zones aggregation won't work.
If we want to compute CL aggregate from the only the zone that we currently have data, we might want to add the bypassedzones here too

[VIKTORVAV99]

Yeah we can do that, I thought we would use GPZD on the missing subzones but maybe I misunderstood and we only have top level data?

[PaulRoms]

Do we need the subZone for Chile?
It might be simpler to only have CL and no subzone

[PaulRoms]

Let me ask via Slack

[BastienBigue]

South Chile has very few inhabitants. https://upload.wikimedia.org/wikipedia/commons/b/b7/Cl-cities.png
My gut feeling would say to aggregate the country with zones for which we have data.
But I think we would compare EMBER/IEA data with what we currently have and decide based on this.

[BastienBigue]

Because yeah, we only have country level yearly/monthly data

[VIKTORVAV99]

Could we do GPZD - measured data = remaining zones and combine them into one subzone?

Then we would have a mix of measured and GPZD subzones and the parent would be a composite with the best of both worlds?

[PaulRoms]

We are doing it for Malasia, it is true!