-
Notifications
You must be signed in to change notification settings - Fork 8
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
Satellite image band list #23
Comments
You could solve this with enums again. |
Good idea. Will give it a try. Thanks! |
Do we address this for 0.5.0 or shall we release? |
Would be great to put this into this release. Will try to find time this week to work on it. Deadline Friday 3 July alright? |
Let's move it to the next release. I simply can't find enough time these days to dedicate to develop it. |
This will be fixed as part of #98 once we have implemented the sensor-specific STAC standard suggestions |
@MWieland what is the status on this? |
This is not resolved yet. Moving an updated roadmap from #98 to here for completeness: Roadmap to move
|
@shiwakotisurendra can you take care of that? |
We will try to follow best practices more in the future -> #155 |
For any image preprocessing and analysis steps we should be able to store and keep track of the band information of a satellite image. In particular, we should know which band index refers to which wavelength and which unit (e.g. digital numbers, top of atmosphere, sigma naught, etc.). This is essential to be able to compute even the simplest band indices (e.g. NDVI) or to select an appropriate band subset during preprocessing.
We have already a dedicated metadata attribute for this ("bandlist") but do not fill it upon metadata creation, because this information is not directly provided by the source metadata (e.g. EarthExplorer). It could like the following for a band subset of a Sentinel-2 image:
'bandlist': [{'index':0, 'name':'B02', 'wavelength':'blue', 'unit':'DN'}, {'index':1, 'name':'B03', 'wavelength':'green', 'unit':'DN'}, {'index':2, 'name':'B04', 'wavelength':'red', 'unit':'DN'}, {'index':3, 'name':'B08', 'wavelength':'nir', 'unit':'DN'}, {'index':4, 'name':'B11', 'wavelength':'swir1', 'unit':'DN'}, {'index':5, 'name':'B12', 'wavelength':'swir2', 'unit':'DN'}]
We could compile this ourselves from a bunch of lookup tables for unique combinations of "Platform" and "Producttype". We basically do this already here for Landsat.
This should be put in a public place (possibly here) and be expanded upon. Then we can compile the respective bandlist "on the fly" when we query the satellite image metadata. This would also allow a user to simply update it in a standardized way later on as part of a more complex processing chain.
The text was updated successfully, but these errors were encountered: