Skip to content

Exploring platforms #147

@sunnydean

Description

@sunnydean

doing this in JS or even a visual would require quite a bit of work (and detailed information from the platforms); would be a mini application by itself so I'm turning this into a new ticket

Add guidance on how to explore available data. give an overview of all the data collections available; give an overview of all the available data, how you access data? Image or something to - maybe it’s here in working with Data - JS boxes when you click on them you select the platform/data to light up the

semi-structured data inputs from platforms when we're asking about documentation - look like:

Platform Data Access Specialized Hardware & Services Compatible Workflows
Copernicus Data Space Ecosystem (CDSE) openEO Federation Offers unified access to a broad selection of Earth Observation (EO) datasets, such as Sentinel-1, Sentinel-2, Sentinel-3, Sentinel-5p, Copernicus Services, Landsat, WorldCover, and more. Users can also process their own data using openEO’s load_stac function. For a comprehensive list of available datasets, visit openeofed.dataspace.copernicus.eu. Leverages cloud infrastructure across multiple openEO backends within the federation. Details about available backends are provided on the openEO Federation page. Built on the openEO API, the platform supports execution of openEO Process Graphs and User Defined Processes.

FAIR Open Science Development Capabilities

Platform Development Tools Supported Languages Visualization Tools Workflow Type
Copernicus Data Space Ecosystem (CDSE) openEO Federation openEO offers multiple tools for workflow and experiment development, including the openEO Web Editor and platform independent client libraries. These libraries can be used in various environments, such as the CDSE Jupyter Notebooks or on a user's local machine. Python, R, JavaScript The openEO Web Editor enables users to visualize processing job results. openEO process graphs as standardized, interoperable workflows/experiments

structured data needs to look like:
Platforms (id/name)

  • datasets available - unique strings - Sentinel-1, Sentinel-2, Sentinel-5, Landsat, etc...
  • language - Python, R, JavaScript, etc...
  • access and processing - OpenEO, SentinelHub API, Dask, etc....

output visual can look something like this (+ styling) - or maybe drop downs would look better:

Image

  • simplest thing is to store data in folder with jsons for all platforms and ask them to create a new one when they document their platform

Metadata

Metadata

Assignees

No one assigned

    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