-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change name to area_name #234
Change name to area_name #234
Conversation
Opened IAMconsortium/nomenclature#197 to address the currently failing tests. After this is merged we can check again if the tests run. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, good to be merged once the other issue in nomenclature is fixed and the tests pass…
Looks like there's a few gremlins left. I'll investigate further. |
Maybe a good idea for the future for any nomenclature unit/integration test would be to run against openENTRANCE. |
Looks like there's a few last issues to fix. I'm taking a look. |
Looks like it's all good now. @danielhuppmann, I'll go ahead with the merge to restore the service. |
Changing the attribute
name
in the region codelist filesnuts1.yaml
,nuts2.yaml
andnuts3.yaml
toarea_name
.An attribute named
name
causes issues with the latest nomenclature release.Running the tests, it seems we have another issue that will need to be fixed on the nomenclature side concerning multiple units.