-
Notifications
You must be signed in to change notification settings - Fork 180
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
Bands RFC #1213 #1254
base: dev
Are you sure you want to change the base?
Bands RFC #1213 #1254
Conversation
a1f038f
to
e505e6e
Compare
Concerning the last commit, there is no way to make suggestions on unchanged file so I simply committed it. Let me know. |
We should discuss whether we want to explicitly disallow to use of "bands" for single-band use-cases where instead people must provide the properties at the asset/item properties level directly. |
I vote +1 for disallowing unique band |
Related Issue(s): #1213
Proposed Changes:
bands
is a new field in common metadata to replaceeo:bands
andraster:bands
(#1213)data_type
,nodata
,statistics
andunit
have been added to common metadata (#1213)This PR needs to wait for the EO and Raster Extension PRs.
ToDo:
PR Checklist:
or a CHANGELOG entry is not required.
and I have opened issue/PR #XXX to track the change.