Skip to content

ASCEND Use Cases - Bringing Earth Explorer data into EarthCODE #155

@GarinSmith

Description

@GarinSmith

The following high level points were noted during an exploratory meeting to discuss Bringing Earth Explorer data into EarthCODE.
They help clarify the approach to Bringing Earth Explorer data into EarthCODE.

The Service (MAAP) can use GitHub authentication which is currently used by EarthCODE users.
The Service (MAAP) can authorise open access to all metadata for the purpose of searching/discovery.
The Service (MAAP) needs to authorise access to assets referenced by metadata on a case by case basis.

This should help establish a technical strategy to enable Bringing Earth Explorer data into EarthCODE
Maybe

Potential User Stories

  1. As a User on Named Platform, I make a search request to the MAAP for specific metadata relating to an AOI for a specific date and I get a response with the metadata I need, so that I know the location of the assets I want.

  2. As a User on Named Platform, I request access to the assets above in the MAAP and I a granted access because my GitHub ID is authorised to access these assets, so that I can use them for processing in my Platform.

Do any platforms have a specific ASCEND / Earth Explorer data Use Case?

Note, we can consider Authentication as a building block plug in strategically (maybe EOPCA)

Note that I have updated the Architecture document to identify platform hosted backends which may be a Federation consideration. See Figure 11.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions