You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we first added the RES regions to the ETM these geo IDs were not yet available, so we made them up ourselves. Now that there are 'official' IDs it would be nice to use them in our datasets.
The text was updated successfully, but these errors were encountered:
This issue has had no activity for 60 days and will be closed in 7 days. Removing the "Stale" label or posting a comment will prevent it from being closed automatically. You can also add the "Pinned" label to ensure it isn't marked as stale in the future.
@kndehaan can pick this up at some point. Would be good to check for fallout with @Charlottevm and @noracato. We would definitely need to write an ETEngine migration to change the geo_id for all relevant scenarios. We would also have to update the locales in ETModel.
This issue is updated to address using official IDs for:
RES regions: based on the region IDs used by CBS (ESXX1)
EU27 dataset: should be labelled EU27_2020 on ETLocal, in line with the label used by Eurostat. The dataset should also be renamed on ETSource to for instance EU27_2020_european_union
CBS now has geo IDs for RES regions:

When we first added the RES regions to the ETM these geo IDs were not yet available, so we made them up ourselves. Now that there are 'official' IDs it would be nice to use them in our datasets.
The text was updated successfully, but these errors were encountered: