-
Notifications
You must be signed in to change notification settings - Fork 18
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
Rename units
to locations
#349
Comments
This is up for discussions. @calliope-project/euro-calliope-devs happy to hear your opinions. |
@timtroendle I believe the preferred naming in Calliope 0.7 is nodes. So perhaps we should use that? |
I agree that a consistent naming will help. However, 'node' is a graph theory term and doesn't really fit in the context geospatial data processing of euro-calliope, in my view. I propose either regions or spatial_units, which were both terms we used consistently in our sprint week spatial resolution team. |
As of Calliope 0.7 we do use |
Distinguishing the |
|
How about
|
The name
units
that is used heavily in the workflow stems from "administrative units". We may want to consider renaming them tolocations
.These are the reasons:
units
for "administrative units" isn't clear and many people may not even know what it means.locations
and we would be consistent.locations
in some places, leading to inconsistent code likelocations = rules.units
.The text was updated successfully, but these errors were encountered: