{{ message }}
#778 Support TiTiler expressions#779
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Closes #778
With Claude (bedrock)
Expression Syntax
Expressions seem to be mainly a standard math expression ()+-/* where bX (or BX) (where X is the band number) are the variables for bands. I'm not sure if you'll need to worry about this part but, when constructing an RGB image from an expression, it would use ; to denote each output band (so red_expression;green_expression;blue_expression). To represent a different asset within the STAC item, use a
_between the asset name and band:assetname_bXExample:
asset1_b1 + asset2_b1 / assest3_b1 + 50Images