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

forge-py: Add support for collections with bad footprints #12

Open
jamesfwood opened this issue Jul 2, 2024 · 0 comments
Open

forge-py: Add support for collections with bad footprints #12

jamesfwood opened this issue Jul 2, 2024 · 0 comments
Assignees
Labels

Comments

@jamesfwood
Copy link
Collaborator

jamesfwood commented Jul 2, 2024

  • Add footprint algorithm for these collections:

    • AVHRR19_G-NAVO-L2P-v1.0 (Ended)
    • AVHRRMTA_G-NAVO-L2P-v1.0 (Ended)
    • AVHRRMTA_G-NAVO-L2P-v2.0 (Ended)
    • AVHRRMTB_G-NAVO-L2P-v1.0 (Ended)
    • AVHRRMTB_G-NAVO-L2P-v2.0 (Forward Processing)
    • SMAP_RSS_L2_SSS_V5 (Ended)
    • SMAP_RSS_L2_SSS_V6 (Forward Processing)
    • PRIM_SMAP_L2_V1 (Ended)
  • Update forge-tig-configs for backfill-tool to use forge-py on above collections

  • Estimating 2 sprints

Tickets:

Timeline:

  • Release forge-py 0.2.0 to OPS - Sprint 4

  • Release backfill-tool to OPS - Sprint 4

  • Update configs in OPS on all "Ended" collections - Sprint 4

  • Backfill all Ended collections in OPS - Sprint 4/5

  • Release forge-py 0.2.0 to Cumulus (TBD)

  • Update remainder configs in OPS

  • Backfill FP collections

@jamesfwood jamesfwood added the Epic label Jul 2, 2024
@jamesfwood jamesfwood self-assigned this Jul 2, 2024
@jamesfwood jamesfwood changed the title Add support for collections with bad footprints forge-py: Add support for collections with bad footprints Jul 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants