Skip to content
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

renaming the primary grid parameter from resolution to level #64

Open
keewis opened this issue Sep 26, 2024 · 1 comment · May be fixed by #65
Open

renaming the primary grid parameter from resolution to level #64

keewis opened this issue Sep 26, 2024 · 1 comment · May be fixed by #65

Comments

@keewis
Copy link
Collaborator

keewis commented Sep 26, 2024

From #62:

We've decided to go with level instead of resolution or refinement_level / reflevel etc. in the meeting, as the context is enough to disambiguate between other kinds of levels. In particular, "processing level" to me is a property of the data / dataset, not the grid (not sure what you're referring to with "maturity level", but if it has to do with the data maturity I would also call that a property of the data or dataset, not the grid).

This issue is to track that change.

@keewis keewis linked a pull request Sep 26, 2024 that will close this issue
1 task
@strobpr
Copy link

strobpr commented Sep 27, 2024

Thanks, level is definitely better than resolution! A move in the right direction and when used in grid hierarchy context such as DGGS APIs, the term is not really ambiguous. I added a comment on the general wording to #65.

There are plenty of other 'levels' in EO and related geospatial sciences, I was referring to the levels of the WGISS Data Management and Stewardship Maturity Matrix just pointing at the fact that if the context is not crystal clear, speaking of 'data levels' might be interpretable.

@keewis keewis mentioned this issue Oct 16, 2024
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants