From 54033b0fa86bd7a230372440fbd9ea0c26ce9c0f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Stephan=20Mei=C3=9Fl?= Date: Tue, 16 Sep 2025 17:54:50 +0200 Subject: [PATCH] chore: fixing links --- data.md | 4 ++-- welcome.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/data.md b/data.md index 3697354..55f4ac2 100644 --- a/data.md +++ b/data.md @@ -1,6 +1,6 @@ # Data configuration -An eodash instance expects to load its content from a STAC catalog. This catalog can be generated using the [eodash_catalog](https://github.com/eodash/eodash_catalog). As can be seen in the [catalog wiki](https://github.com/eurodatacube/eodash-catalog/wiki/Resource) there are multiple services supported. +An eodash instance expects to load its content from a STAC catalog. This catalog can be generated using the [eodash_catalog](https://github.com/eodash/eodash_catalog). As can be seen in the [catalog wiki](https://github.com/eodash/eodash_catalog/wiki/Resource) there are multiple services supported. We consider eodash to be a data integrator, so we find a "serverless" approach for data integration to be a great opportunity to not require more complex setups when wanting to share your data, apart from making them reachable online. For this we want to give explanations and examples of how this can be done for raster and vector data. Currently we support Cloud Optimized GeoTIFFs (COGs) for raster and GeoJSON files for vector data. We want to support cloud optimized formats for vector data as soon as possible. @@ -182,4 +182,4 @@ Here is how that translates to a visualization in the eodash instance: ![raster data interaction rendering example](./assets/raster_interaction_example.gif) -This covers the basics for "serverless" data integration. Integration of datasets provided through services do not use a style file, each endpoint provides their own configuration options which can be defined in the data definition configuration file. For more information please go to the [resource section](https://github.com/eurodatacube/eodash-catalog/wiki/Resource) of the catalog wiki. \ No newline at end of file +This covers the basics for "serverless" data integration. Integration of datasets provided through services do not use a style file, each endpoint provides their own configuration options which can be defined in the data definition configuration file. For more information please go to the [resource section](https://github.com/eodash/eodash_catalog/wiki/Resource) of the catalog wiki. diff --git a/welcome.md b/welcome.md index 17d669f..d8e4fa9 100644 --- a/welcome.md +++ b/welcome.md @@ -27,7 +27,7 @@ The main tools are a web client dashboard library (eodash) as well as a catalog The figure above shows the main components of the eodash ecosystem, as well as how they interact with each other. The **eodash [catalog](https://github.com/eodash/eodash_catalog)** is a helper python package which supports a series of commonly used serverless EO data endpoints as well as service endpoints, such as [OGC](https://www.ogc.org/) services, [ViewServer](https://gitlab.eox.at/vs), STAC catalogs, and others. -By defining a collection configuration file an end user can provide a wide range of visualization and analysis definitions to describe how the data should be visualized on the eodash web client. The supported resources are described [here](https://github.com/eurodatacube/eodash-catalog/wiki/Resource). The output of the catalog helper package is a static catalog (series of files), that can be hosted on any web server. +By defining a collection configuration file an end user can provide a wide range of visualization and analysis definitions to describe how the data should be visualized on the eodash web client. The supported resources are described [here](https://github.com/eodash/eodash_catalog/wiki/Resource). The output of the catalog helper package is a static catalog (series of files), that can be hosted on any web server. The generated static catalog is the input used by an **[eodash](https://eodash.github.io/eodash/)** instance to populate the information shown. This includes descriptive text, assets, analysis functions and most importantly customizable EO data visualization through a series of configurable widgets. eodash provides a set of **core widgets** that can be configured to navigate and interact with the data. Third party widgets can be developed and integrated through the configuration by (for example) reacting to specific **STAC extensions** in the catalog.