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-3380 show no-data granules outside of data availability ranges #5530

Merged
merged 5 commits into from
Oct 31, 2024

Conversation

PatchesMaps
Copy link
Contributor

Description

There is a ~15 minute period on October 15, 2024 12:14-12:38, where there is no L2 data in WV prod (which I believe is expected because the bad imagery was filtered out so there was no imagery sent to WV). But I do not see any blue footprint boundaries like used to show up. I was wondering if the change in how WV was hosting the L2 meant that there would no longer be footprint boundaries for granules that don't have imagery. https://go.nasa.gov/48hE8YO

How To Test

  1. git checkout WV-3380-footprints-with-no-granule
  2. npm run watch
  3. Go to this link
  4. There should be a granule footprint visible on hover over North America that doesn't have any imagery available. Granule footprints should be available outside of data availability ranges.

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

@PatchesMaps PatchesMaps self-assigned this Oct 25, 2024
@PatchesMaps PatchesMaps marked this pull request as draft October 25, 2024 14:31
@minniewong minniewong added this to the v4.51.0 milestone Oct 25, 2024
@PatchesMaps PatchesMaps marked this pull request as ready for review October 28, 2024 17:40
@PatchesMaps PatchesMaps merged commit 949aeea into develop Oct 31, 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.

3 participants