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

Implement backend logic to suggest valid cycle/pass/scene to end user and validate the cycle/pass/scene inputs #71

Closed
viviant100 opened this issue Jun 23, 2023 · 4 comments
Assignees

Comments

@viviant100
Copy link
Collaborator

Build a microservice that receives the CNM messages from IA and perform analysis on the CNM messages in order to provide valid cycle/pass/scene for the users (3sp)

  • Attach a new SQS queue to I&A SNS topic for the CNM messages.

Pre-verification for client-side to validate the input (2sp),

@joshgarde
Copy link
Member

joshgarde commented Sep 5, 2023

The suggestion feature does not seem reasonable to implement as currently proposed. The current state of this feature proposes that:

  • when nothing is provided, a list of valid cycles is returned
  • when a cycle is provided, a list of valid passes is returned
  • when a cycle + pass is provided, a list of valid scenes is returned

For context: each variable in the search is dependent on the variable before it. If a list of valid passes and scenes is generated from a cycle, the combination of both the pass + scene as a pair must be utilized together to form a valid CPS combo.

The SWOT satellite is expected to generate a lot of PIXC/PIXCVec tiles which are used to generate scenes when combined together. As a result, valid combinations generated could potentially reach the hundreds/thousands on each variable. In order to support this functionality, we would need to build out a process within ingest-to-sds which generates search indices for each of these parameters for the API to utilize.

For example:

  • an index entry of (null,null,null) -> [list of valid cycles]
  • an index entry of (123,null,null) -> [list of valid passes]
  • an index entry of (123,123,null) -> [list of valid scenes]
  • an index entry of (123,123,123) -> [(123,123,123)] (Just as a way to verify this entry is valid)

Each of these indices would need to be updated as a granule is ingested through the SDS. Performing this work would be fairly non-trivial for a feature that doesn't seem like it would be useful once Earthdata Search integration is implemented.

@joshgarde
Copy link
Member

@joshgarde
Copy link
Member

Hotfix created:

podaac/swodlr-ingest-to-sds#11

@joshgarde
Copy link
Member

Merged

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

No branches or pull requests

2 participants