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

WV-3298 limit data availability to visible time extent #5519

Merged
merged 7 commits into from
Oct 25, 2024

Conversation

PatchesMaps
Copy link
Contributor

Description

With the goal of resolving long load times for layers with large numbers of temporal ranges (i.e. TEMPO), load only data within the currently visible temporal extent for the data availability bar. This should be completed after we replace CMR with DescribeDomains.

How To Test

  1. git checkout WV-3298-limit-data-availability
  2. npm run watch
  3. Open this link
  4. Make sure that the data availability date ranges load correctly and that scrolling and dragging performance in the timeline is unaffected.

PR Submission Checklist

This is simply a reminder of what we are going to look for before merging your code.

  • I have read the CONTRIBUTING doc
  • I have added necessary documentation (if applicable)
  • I have added tests that prove my fix is effective or that my feature works (if applicable)
  • Any dependent changes have been merged and published in downstream modules (if applicable)

Merging

Please use the squash and merge commit method unless each commit in your branch is vital to the commit history of main.

@nasa-gibs/worldview

@Tomcariello
Copy link
Contributor

This looks good however I'm missing imagery when I change dates by month.

If I load this link, then change the month to September I do not get imagery even though there is data available (as evidenced by slightly moving the slider selector). This same workflow works in current production.

@minniewong minniewong added this to the v4.51.0 milestone Oct 23, 2024
@PatchesMaps PatchesMaps merged commit d824ed4 into develop Oct 25, 2024
4 checks passed
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

Successfully merging this pull request may close these issues.

4 participants