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

mapping object to go in raster or its own extension? #6

Closed
cholmes opened this issue Jun 22, 2021 · 3 comments · Fixed by #11
Closed

mapping object to go in raster or its own extension? #6

cholmes opened this issue Jun 22, 2021 · 3 comments · Fixed by #11

Comments

@cholmes
Copy link

cholmes commented Jun 22, 2021

It looks like we took out most of the raster fields, but the 'mapping object' seems to be an advanced raster thing - I think it tells you what different values of pixels actually mean? It doesn't seem like a generic 'file' thing. It perhaps could go in its own extension, but I think it's confusing in the file extension.

@m-mohr
Copy link
Contributor

m-mohr commented Jun 23, 2021

I planned to transfer the field to https://github.com/stac-extensions/classification, but I doubt I'll get to it in the next months.

@m-mohr
Copy link
Contributor

m-mohr commented Jul 23, 2021

See also the discussions in stac-extensions/raster#17

@m-mohr
Copy link
Contributor

m-mohr commented Nov 1, 2021

I think the best idea would be to deprecate file:values here once classification is out, but still leave it in for a while as this is already used in a couple of applications and the field specs may be a bit different in complexity.

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