You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
EO time series observations, e.g. BOA images, often comes with other (auxilliary) files, e.g.
(taken from FORCE docs):
Product
Description
BOA
Bottom-of-Atmosphere Reflectance
TOA
Top-of-Atmosphere Reflectance
QAI
Quality Assurance Information
AOD
Aerosol Optical Depth
DST
Cloud / Cloud shadow /Snow distance
WVP
Water vapor
VZN
View zenith
HOT
Haze Optimized Transformation
Let the BOA be the "core" product of the time-series source. It is reuqested to allow each core product to be accompanied by auxilliary products, here "TOA", "QAI" etc.
Implementation ideas:
Data Model:
each SensorInstrument instance defines a "core" product and, optionally, multiple "auxilliary" products
aux rasters need to match the core raster in: samples, lines, pixel size, spatial extent and CRS
aux rasters can differe in number of bands
each Time Series Source defines:
a core raster source
a list of optional aux raster sources
during loading only thos aux rasters are loaded, which are predefined in the EOTSV settings
Visualization
Enhance the Map View layer tree by showing each sensor type as group node and core and aux sources in child nodes:
EO time series observations, e.g. BOA images, often comes with other (auxilliary) files, e.g.
(taken from FORCE docs):
Let the BOA be the "core" product of the time-series source. It is reuqested to allow each core product to be accompanied by auxilliary products, here "TOA", "QAI" etc.
Implementation ideas:
Data Model:
Visualization
Enhance the Map View layer tree by showing each sensor type as group node and core and aux sources in child nodes:
Change it from now
to:
Layers below a Sensor Layer group should be arrangable in a flexible way:
The text was updated successfully, but these errors were encountered: