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

implement TCW, TCG, TCB in SpectralIndice Process #26

Open
Florian-Katerndahl opened this issue Sep 5, 2022 · 3 comments
Open

implement TCW, TCG, TCB in SpectralIndice Process #26

Florian-Katerndahl opened this issue Sep 5, 2022 · 3 comments
Assignees

Comments

@Florian-Katerndahl
Copy link
Collaborator

a simple if-else-check should suffice; add call to another EMB module which allows the creation of tasseled cap rasters.

@Florian-Katerndahl Florian-Katerndahl self-assigned this Sep 28, 2022
@Florian-Katerndahl
Copy link
Collaborator Author

GRASS offers a way to calculate the TC-Components. However, all are output at once and with the current approach, the calculations are done three times anyway, just to return a single band. This structure is currently expected by the workflow but neither elegant nor wise regarding resource consumption.

@Florian-Katerndahl
Copy link
Collaborator Author

The process needs single band files as inputs. This would require the explosion of the input file and thus duplicate processing (because it is done later on anyways).

@Florian-Katerndahl
Copy link
Collaborator Author

Creating a different "route" for the creation of Tasseled Cap bands (maybe in the form of a different sub-workflow) and merging the channel later on into the "normal" indice-channel would work.
The process would emit a four-layer-file which would then be split up into three single-layer-files (last band is not needed currently, assuming we're working with grass7:i.tasscap) and some channel-shenanigans (duplicating some elements of channel entries -> metadata).

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

No branches or pull requests

1 participant