Mismatched borders for regional, ehighways and country resolutions

[irm-codebase]

What happened?

This issue was found by @brynpickering in calliope-project/clio#3

Euro-calliope's current approach to produce shape files leads to broken borders.

This is caused by mismatches between NUTS and GDAM, and by mismatches between different resolutions of the same dataset (e.g., GDAM level-0 and level-1).

Proposed solution: using a validated edge-matched source like https://fieldmaps.io/data

Version

1.2.0.dev

Relevant log output

[brynpickering]

Links to #237

[irm-codebase]

I've found the cause: using anything but the '01M' resolution causes this.
calliope-project/module_geo_boundaries#6

I also suspect that the euro-calliope algorithm might have mismatching EPSGs for different datasets, as GADM and NUTS use different ones. It would explain why some countries end up 'shifted'. I have not confirmed this, though.