feat: add parameters to pass datetime through to sel in time series#76
Closed
feat: add parameters to pass datetime through to sel in time series#76
Conversation
|
📚 Documentation preview will be available at: https://developmentseed.github.io/titiler-cmr/pr-previews/pr-76/ Status: ✅ Preview is ready! |
Contributor
Author
|
Closing in favor of #78 |
This was referenced Oct 9, 2025
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
2 participants
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.
This adds a pair of new parameters to the /timeseries endpoints:
use_sel_for_datetimeandsel_time_dim. These parameters allow users to have thedatetimevalues get passed to the sel parameter in the lower-level requests like this:sel={sel_time_dim}={datetime}. This unblocks the use-case where granules cover a datetime range and have a time dimension within each file.I also had to update the test cassettes for reasons that I don't fully understand, but I successfully created a fixture that actually routes the lower-level time series requests to the test app instead of just mocking that response (which was important to test this new complex case).