Load transect data frame by frame #191
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
Contributor
Author
NH4_transect_20220101130000_20220201130000.mp4 |
david-sh-csiro
approved these changes
Sep 4, 2025
Collaborator
david-sh-csiro
left a comment
david-sh-csiro
left a comment
There was a problem hiding this comment.
Tested locally with both automatic and manually specified clim. We no longer receive errors from the thredds server with regards to request too large a size of data. Doing something like the K'gari transect example as an animation now actually completes!
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.
There is no nice way to index when taking a transect, it is essentially random access. Loading the data before indexing will make it faster, but loading the entire animation dataset can fail if remote servers have request size limits. By loading the data frame by frame we reach a middle ground: the data will still be indexed relatively quickly but remote servers won't baulk at sending half a gig of data at a time.