-
Notifications
You must be signed in to change notification settings - Fork 188
enable algorithm chaining #1139
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
Comments
ref #1116 (comment) cc @jo-chemla |
Sorry in advance if this is out of the scope of this issue, but I was wondering if one could also specify where in the data pipeline an algorithm should be applied. Correct me if I'm wrong, but it seems that currently it is only possible to apply an algorithm after the data has been reprojected. But what if one wants to apply an algorithm on each tile before reprojection? Screencast.from.2025-05-08.15-26-12.webm |
Yes
Sadly this won't be possible without heavy transformation off how titiler work. The While I love that titiler can do a lot of things, sadly it won't fit 100% user needs sometimes :-(
Well right now I have no control about how the |
For my particular use-case, it seems that I'd need GDAL's GRA_Max warp resampling algorithm, but I have no idea how I could then pass it to the |
you should be able to pass |
Great! |
It would be nice if we could chain Algorithm.
Question: Some algorithms need options, how would a user pass options for specific algo?
Possible answer: In STAC we have a custom format "{asset}|{indexes}" (
red|1,2,3
) to enable indexes selection per assetsThe text was updated successfully, but these errors were encountered: