Build ehighways resolution units

[brynpickering]

What can be improved?

Take regional level NUTS3 data using the correct NUTS year and aggregate up to eHighways resolution. See "data/statistical_units_to_ehighways_regions.csv" in sector-coupled repo for aggregation mapping

Version

1.2.0.dev

[jnnr]

How are ehighways units prepared in Sector-coupled EC currently? They are prepared by the rule custom_units, which calls the script aggregate_statistical_units_to_custom_regions.py

[timtroendle]

This seems to be a duplicate of #319, do you agree? Building the shapes seems to be 90% of #319 and because #319 is a feature while this here is not, I'd close this in favour of #318.

[jonathan-peel]

Terminology:
NUTS3 spatial units (in polygon data types) -> eHighways spatial units (polygons)

[jonathan-peel]

Desired output: units.geojson file with MultiPolygons all the spatial units for the chosen spatial resolution (regional, national, continental, ehighways, etc.)

[timtroendle]

I am continuing my nagging here: in the sake of working feature-driven, I would aim for this issue (or #319) to build in eHighways as a feature, not as some data that possibly may be used as a model feature in the future.

Building the shapes sounds like 90% of the way anyway.

[jnnr]

I agree, @timtroendle. Closing this in favor of #319