eodag 3.5.1__tar.gz → 3.7.0__tar.gz

{eodag-3.5.1 → eodag-3.7.0}/CHANGES.rst

@@ -3,6 +3,130 @@ Release history
 ===============
 
 
+v3.7.0 (2025-07-31)
+===================
+
+Bug Fixes
+---------
+
+* **core**: Logging issue on entrypoint loading error (`#1728`_, `6f8e6ad`_)
+
+* **plugins**: metadata_mapping_from_product in search config (`#1737`_, `cdfe518`_)
+
+* **providers**: Allow search by id for CLMS_CORINE with wekeo_main (`#1746`_, `bfe5e71`_)
+
+* **providers**: Remove no-more-available theia provider (`#1736`_, `e81013b`_)
+
+* **providers**: Update default version for CAMS_GLOBAL_EMISSIONS (`#1738`_, `81e4b90`_)
+
+* **server**: Empty instruments mapping (`#1763`_, `11f2318`_)
+
+* **utils**: Avoid repeated SSL context creation (`#1758`_, `f93645e`_)
+
+Documentation
+-------------
+
+* Updated description, overview and ecosystem (`#1734`_, `ea929e4`_)
+
+Features
+--------
+
+* **plugins**: New search config for assets mapping (`#1711`_, `1281268`_)
+
+* **providers**: Add 2 new MSG collections to provider ``eumetsat_ds`` (`#1742`_, `801c52c`_)
+
+* **providers**: dedt_lumi search by geometry (`#1710`_, `efccdd0`_)
+
+Performance Improvements
+------------------------
+
+* **plugins**: Optimize AwsDownload streaming (`#1740`_, `48f0e4c`_)
+
+Refactoring
+-----------
+
+* Directly import urllib.parse methods (`#1761`_, `e4aca26`_)
+
+.. _#1710: https://github.com/CS-SI/eodag/pull/1710
+.. _#1711: https://github.com/CS-SI/eodag/pull/1711
+.. _#1728: https://github.com/CS-SI/eodag/pull/1728
+.. _#1734: https://github.com/CS-SI/eodag/pull/1734
+.. _#1736: https://github.com/CS-SI/eodag/pull/1736
+.. _#1737: https://github.com/CS-SI/eodag/pull/1737
+.. _#1738: https://github.com/CS-SI/eodag/pull/1738
+.. _#1740: https://github.com/CS-SI/eodag/pull/1740
+.. _#1742: https://github.com/CS-SI/eodag/pull/1742
+.. _#1746: https://github.com/CS-SI/eodag/pull/1746
+.. _#1758: https://github.com/CS-SI/eodag/pull/1758
+.. _#1761: https://github.com/CS-SI/eodag/pull/1761
+.. _#1763: https://github.com/CS-SI/eodag/pull/1763
+.. _11f2318: https://github.com/CS-SI/eodag/commit/11f2318a150982504226378110b853ca4aa644ce
+.. _1281268: https://github.com/CS-SI/eodag/commit/1281268507c3a7338be9954b403a20d5156bc527
+.. _48f0e4c: https://github.com/CS-SI/eodag/commit/48f0e4c8c82e80841b7b64bec60a251661a13d12
+.. _6f8e6ad: https://github.com/CS-SI/eodag/commit/6f8e6ad683f786286cfb36e8e22c17cfb2daf125
+.. _801c52c: https://github.com/CS-SI/eodag/commit/801c52c38124e6dfff1a5fdedeb0cbd269fc2478
+.. _81e4b90: https://github.com/CS-SI/eodag/commit/81e4b903c5474894e87e6dcb9366fdfbb152398b
+.. _bfe5e71: https://github.com/CS-SI/eodag/commit/bfe5e712087804d31fe7f057e5efbd1d2863fb36
+.. _cdfe518: https://github.com/CS-SI/eodag/commit/cdfe518f2b392b700994f93d2c2d6cafdb46b81d
+.. _e4aca26: https://github.com/CS-SI/eodag/commit/e4aca2672b156a6eb338e9e9a8277bc2895aa457
+.. _e81013b: https://github.com/CS-SI/eodag/commit/e81013b262342a0621e2018a7d917145faaa2cc7
+.. _ea929e4: https://github.com/CS-SI/eodag/commit/ea929e4339e976752bc61d1d305ad36ff1b78172
+.. _efccdd0: https://github.com/CS-SI/eodag/commit/efccdd00fbd0880344fe294dba0f4790468fd9bc
+.. _f93645e: https://github.com/CS-SI/eodag/commit/f93645ed4f09194d6c7f12a3c65b2ab3a8f9ad5a
+
+
+v3.6.0 (2025-07-01)
+===================
+
+Bug Fixes
+---------
+
+* **core**: Do not download again unextracted products (`#1717`_, `29642e8`_)
+
+* **queryables**: Improve date parameter parsing (`#1702`_, `9563d4b`_)
+
+Documentation
+-------------
+
+* Cli and stac support update (`#1707`_, `c50aae1`_)
+
+* Import_stac_items documentation update (`#1709`_, `7a04158`_)
+
+Features
+--------
+
+* **cli**: Commands chaining (`#1714`_, `754772b`_)
+
+* **cli**: Download output directory (`#1716`_, `036b86b`_)
+
+* **cli**: Download STAC items from their urls (`#1705`_, `5d598a9`_)
+
+* **core**: Import stac items as SearchResult (`#1703`_, `1d49715`_)
+
+* **providers**: Add new eurostat product types to dedl (`#1662`_, `b7192b1`_)
+
+.. _#1662: https://github.com/CS-SI/eodag/pull/1662
+.. _#1702: https://github.com/CS-SI/eodag/pull/1702
+.. _#1703: https://github.com/CS-SI/eodag/pull/1703
+.. _#1705: https://github.com/CS-SI/eodag/pull/1705
+.. _#1706: https://github.com/CS-SI/eodag/pull/1706
+.. _#1707: https://github.com/CS-SI/eodag/pull/1707
+.. _#1709: https://github.com/CS-SI/eodag/pull/1709
+.. _#1714: https://github.com/CS-SI/eodag/pull/1714
+.. _#1716: https://github.com/CS-SI/eodag/pull/1716
+.. _#1717: https://github.com/CS-SI/eodag/pull/1717
+.. _036b86b: https://github.com/CS-SI/eodag/commit/036b86bbefeed905c9962a7a4bf7bca8258246fb
+.. _1d49715: https://github.com/CS-SI/eodag/commit/1d4971560e9b789dfe96ca09b2fcd5d88cb4e30a
+.. _29642e8: https://github.com/CS-SI/eodag/commit/29642e87614b44ec3b544732ef6496ae8bf73087
+.. _5d598a9: https://github.com/CS-SI/eodag/commit/5d598a9934d36390e7b6f1ef2d746f9a9030198d
+.. _754772b: https://github.com/CS-SI/eodag/commit/754772b9e71700fb752cb632dfb66ef13cd2c743
+.. _7a04158: https://github.com/CS-SI/eodag/commit/7a041583695f71811baf56e5616415df60750814
+.. _9563d4b: https://github.com/CS-SI/eodag/commit/9563d4bccaea5a87805fff77863d14cb4b422fb7
+.. _b7192b1: https://github.com/CS-SI/eodag/commit/b7192b14840d27a3558f4dc5dff0b99ea6c0d833
+.. _c50aae1: https://github.com/CS-SI/eodag/commit/c50aae12b344d81f66fc20a9a930b7718e0b12b7
+.. _e1db471: https://github.com/CS-SI/eodag/commit/e1db47199d47c4988eaece7628005727dba2985f
+
+
 v3.5.1 (2025-06-23)
 ===================
 

{eodag-3.5.1/eodag.egg-info → eodag-3.7.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: eodag
-Version: 3.5.1
+Version: 3.7.0
 Summary: Earth Observation Data Access Gateway
 Home-page: https://github.com/CS-SI/eodag
 Author: CS GROUP - France
@@ -86,6 +86,7 @@ Requires-Dist: imageio; extra == "tutorials"
 Requires-Dist: rasterio; extra == "tutorials"
 Requires-Dist: netcdf4; extra == "tutorials"
 Requires-Dist: cartopy; extra == "tutorials"
+Requires-Dist: covjsonkit; extra == "tutorials"
 Provides-Extra: dev
 Requires-Dist: eodag[all-providers,csw,server,stubs]; extra == "dev"
 Requires-Dist: pytest; extra == "dev"
@@ -119,12 +120,13 @@ Requires-Dist: types-tqdm; extra == "stubs"
 Requires-Dist: types-urllib3; extra == "stubs"
 Provides-Extra: docs
 Requires-Dist: eodag[all,stubs]; extra == "docs"
+Requires-Dist: nbsphinx; extra == "docs"
 Requires-Dist: sphinx; extra == "docs"
+Requires-Dist: sphinx-autodoc-typehints; extra == "docs"
 Requires-Dist: sphinx-book-theme>=1.0.0; extra == "docs"
 Requires-Dist: sphinx-copybutton; extra == "docs"
 Requires-Dist: sphinx-tabs; extra == "docs"
-Requires-Dist: nbsphinx; extra == "docs"
-Requires-Dist: sphinx_autodoc_typehints; extra == "docs"
+Requires-Dist: sphinxcontrib-programoutput; extra == "docs"
 Requires-Dist: sphinxemoji; extra == "docs"
 Dynamic: license-file
 
@@ -174,23 +176,21 @@ data provider. The EODAG SDK is structured around three functions:
 
 * List product types: list of supported products and their description
 
-* Search products (by product type or uid) : searches products according to the search criteria provided
+* Search products (by product type or uid): searches products according to the search criteria provided
 
-* Download products : download product “as is"
+* Download products: download product “as is"
 
 EODAG is developed in Python. It is structured according to a modular plugin architecture, easily extensible and able to
 integrate new data providers. Three types of plugins compose the tool:
 
-* Catalog search plugins, responsible for searching data (OpenSearch, CSW, ...), building paths, retrieving quicklook,
+* Catalog search plugins, responsible for searching data (STAC, OpenSearch, OData, ...), building paths, retrieving quicklook,
   combining results
 
-* Download plugins, allowing to download and retrieve data locally (via FTP, HTTP, ..), always with the same directory
+* Download plugins, allowing to download and retrieve data locally (via HTTP, S3, ...), always with the same directory
   organization
 
 * Authentication plugins, which are used to authenticate the user on the external services used (JSON Token, Basic Auth, OAUTH, ...).
 
-Since v2.0 EODAG can be run as `STAC client or server <https://eodag.readthedocs.io/en/latest/stac.html>`_.
-
 Read `the documentation <https://eodag.readthedocs.io/en/latest/>`_ for more insights.
 
 .. image:: https://raw.githubusercontent.com/CS-SI/eodag/develop/docs/_static/eodag_overview.png
@@ -317,7 +317,7 @@ An eodag instance can be exposed through a STAC compliant REST api from the comm
 
 .. code-block:: bash
 
-    docker run -p 5000:5000 --rm csspace/eodag-server:3.5.1
+    docker run -p 5000:5000 --rm csspace/eodag-server:3.7.0
 
 You can also browse over your STAC API server using `STAC Browser <https://github.com/radiantearth/stac-browser>`_.
 Simply run:

{eodag-3.5.1 → eodag-3.7.0}/README.rst

@@ -44,23 +44,21 @@ data provider. The EODAG SDK is structured around three functions:
 
 * List product types: list of supported products and their description
 
-* Search products (by product type or uid) : searches products according to the search criteria provided
+* Search products (by product type or uid): searches products according to the search criteria provided
 
-* Download products : download product “as is"
+* Download products: download product “as is"
 
 EODAG is developed in Python. It is structured according to a modular plugin architecture, easily extensible and able to
 integrate new data providers. Three types of plugins compose the tool:
 
-* Catalog search plugins, responsible for searching data (OpenSearch, CSW, ...), building paths, retrieving quicklook,
+* Catalog search plugins, responsible for searching data (STAC, OpenSearch, OData, ...), building paths, retrieving quicklook,
   combining results
 
-* Download plugins, allowing to download and retrieve data locally (via FTP, HTTP, ..), always with the same directory
+* Download plugins, allowing to download and retrieve data locally (via HTTP, S3, ...), always with the same directory
   organization
 
 * Authentication plugins, which are used to authenticate the user on the external services used (JSON Token, Basic Auth, OAUTH, ...).
 
-Since v2.0 EODAG can be run as `STAC client or server <https://eodag.readthedocs.io/en/latest/stac.html>`_.
-
 Read `the documentation <https://eodag.readthedocs.io/en/latest/>`_ for more insights.
 
 .. image:: https://raw.githubusercontent.com/CS-SI/eodag/develop/docs/_static/eodag_overview.png
@@ -187,7 +185,7 @@ An eodag instance can be exposed through a STAC compliant REST api from the comm
 
 .. code-block:: bash
 
-    docker run -p 5000:5000 --rm csspace/eodag-server:3.5.1
+    docker run -p 5000:5000 --rm csspace/eodag-server:3.7.0
 
 You can also browse over your STAC API server using `STAC Browser <https://github.com/radiantearth/stac-browser>`_.
 Simply run:

{eodag-3.5.1 → eodag-3.7.0}/charts/eodag-server/Chart.yaml

@@ -1,5 +1,5 @@
 apiVersion: v2
-appVersion: 3.5.1
+appVersion: 3.7.0
 dependencies:
 - name: common
   repository:  oci://registry-1.docker.io/bitnamicharts
@@ -15,4 +15,4 @@ name: eodag-server
 sources:
 - https://github.com/CS-SI/eodag
 type: application
-version: 3.5.1
+version: 3.7.0

{eodag-3.5.1 → eodag-3.7.0}/docs/_static/product_types_information.csv

@@ -40,11 +40,16 @@ ERA5_PL,"ERA5 is the fifth generation ECMWF reanalysis for the global climate an
 ERA5_PL_MONTHLY,"ERA5 is the fifth generation ECMWF reanalysis for the global climate and weather for the past 8 decades. Data is available from 1940 onwards. ERA5 replaces the ERA-Interim reanalysis. Reanalysis combines model data with observations from across the world into a globally complete and consistent dataset using the laws of physics. This principle, called data assimilation, is based on the method used by numerical weather prediction centres, where every so many hours (12 hours at ECMWF) a previous forecast is combined with newly available observations in an optimal way to produce a new best estimate of the state of the atmosphere, called analysis, from which an updated, improved forecast is issued. Reanalysis works in the same way, but at reduced resolution to allow for the provision of a dataset spanning back several decades. Reanalysis does not have the constraint of issuing timely forecasts, so there is more time to collect observations, and when going further back in time, to allow for the ingestion of improved versions of the original observations, which all benefit the quality of the reanalysis product. ERA5 provides hourly estimates for a large number of atmospheric, ocean-wave and land-surface quantities. An uncertainty estimate is sampled by an underlying 10-member ensemble at three-hourly intervals. Ensemble mean and spread have been pre-computed for convenience. Such uncertainty estimates are closely related to the information content of the available observing system which has evolved considerably over time. They also indicate flow-dependent sensitive areas. To facilitate many climate applications, monthly-mean averages have been pre-calculated too, though monthly means are not available for the ensemble mean and spread. ERA5 is updated daily with a latency of about 5 days (monthly means are available around the 6th of each month). In case that serious flaws are detected in this early release (called ERA5T), this data could be different from the final release 2 to 3 months later. So far this has only been the case for the month September 2021, while it will also be the case for October, November and December 2021. For months prior to September 2021 the final release has always been equal to ERA5T, and the goal is to align the two again after December 2021. ERA5 is updated daily with a latency of about 5 days (monthly means are available around the 6th of each month). In case that serious flaws are detected in this early release (called ERA5T), this data could be different from the final release 2 to 3 months later. In case that this occurs users are notified. The data set presented here is a regridded subset of the full ERA5 data set on native resolution. It is online on spinning disk, which should ensure fast and easy access. It should satisfy the requirements for most common applications. Data has been regridded to a regular lat-lon grid of 0.25 degrees for the reanalysis and 0.5 degrees for the uncertainty estimate (0.5 and 1 degree respectively for ocean waves). There are four main sub sets: hourly and monthly products, both on pressure levels (upper air fields) and single levels (atmospheric, ocean-wave and land surface quantities). ",,ERA5,ERA5,,"Climate,ECMWF,Reanalysis,ERA5,CDS,Atmospheric,land,sea,monthly,pressure,levels",ATMOSPHERIC,other,ERA5 monthly averaged data on pressure levels from 1940 to present,1940-01-01T00:00:00Z,ERA5_PL_MONTHLY,,,available,,,,,,available,,,,,,,,,,,,,,,,,,available,
 ERA5_SL,"ERA5 is the fifth generation ECMWF reanalysis for the global climate and weather for the past 8 decades. Data is available from 1940 onwards. ERA5 replaces the ERA-Interim reanalysis. Reanalysis combines model data with observations from across the world into a globally complete and consistent dataset using the laws of physics. This principle, called data assimilation, is based on the method used by numerical weather prediction centres, where every so many hours (12 hours at ECMWF) a previous forecast is combined with newly available observations in an optimal way to produce a new best estimate of the state of the atmosphere, called analysis, from which an updated, improved forecast is issued. Reanalysis works in the same way, but at reduced resolution to allow for the provision of a dataset spanning back several decades. Reanalysis does not have the constraint of issuing timely forecasts, so there is more time to collect observations, and when going further back in time, to allow for the ingestion of improved versions of the original observations, which all benefit the quality of the reanalysis product. ERA5 provides hourly estimates for a large number of atmospheric, ocean-wave and land-surface quantities. An uncertainty estimate is sampled by an underlying 10-member ensemble at three-hourly intervals. Ensemble mean and spread have been pre-computed for convenience. Such uncertainty estimates are closely related to the information content of the available observing system which has evolved considerably over time. They also indicate flow-dependent sensitive areas. To facilitate many climate applications, monthly-mean averages have been pre-calculated too, though monthly means are not available for the ensemble mean and spread. ERA5 is updated daily with a latency of about 5 days. In case that serious flaws are detected in this early release (called ERA5T), this data could be different from the final release 2 to 3 months later. In case that this occurs users are notified. The data set presented here is a regridded subset of the full ERA5 data set on native resolution. It is online on spinning disk, which should ensure fast and easy access. It should satisfy the requirements for most common applications. Data has been regridded to a regular lat-lon grid of 0.25 degrees for the reanalysis and 0.5 degrees for the uncertainty estimate (0.5 and 1 degree respectively for ocean waves). There are four main sub sets: hourly and monthly products, both on pressure levels (upper air fields) and single levels (atmospheric,ocean-wave and land surface quantities). ",,ERA5,ERA5,,"ECMWF,Reanalysis,ERA5,CDS,Atmospheric,land,sea,hourly,single,levels",ATMOSPHERIC,other,ERA5 hourly data on single levels from 1940 to present,1940-01-01T09:00:00Z,ERA5_SL,,,available,,,,,,available,,,,,,,,,,,,,,,,,,available,
 ERA5_SL_MONTHLY,"ERA5 is the fifth generation ECMWF reanalysis for the global climate and weather for the past 8 decades. Data is available from 1940 onwards. ERA5 replaces the ERA-Interim reanalysis. Reanalysis combines model data with observations from across the world into a globally complete and consistent dataset using the laws of physics. This principle, called data assimilation, is based on the method used by numerical weather prediction centres, where every so many hours (12 hours at ECMWF) a previous forecast is combined with newly available observations in an optimal way to produce a new best estimate of the state of the atmosphere, called analysis, from which an updated, improved forecast is issued. Reanalysis works in the same way, but at reduced resolution to allow for the provision of a dataset spanning back several decades. Reanalysis does not have the constraint of issuing timely forecasts, so there is more time to collect observations, and when going further back in time, to allow for the ingestion of improved versions of the original observations, which all benefit the quality of the reanalysis product. ERA5 provides hourly estimates for a large number of atmospheric, ocean-wave and land-surface quantities. An uncertainty estimate is sampled by an underlying 10-member ensemble at three-hourly intervals. Ensemble mean and spread have been pre-computed for convenience. Such uncertainty estimates are closely related to the information content of the available observing system which has evolved considerably over time. They also indicate flow-dependent sensitive areas. To facilitate many climate applications, monthly-mean averages have been pre-calculated too, though monthly means are not available for the ensemble mean and spread. ERA5 is updated daily with a latency of about 5 days (monthly means are available around the 6th of each month). In case that serious flaws are detected in this early release (called ERA5T), this data could be different from the final release 2 to 3 months later. In case that this occurs users are notified. The data set presented here is a regridded subset of the full ERA5 data set on native resolution. It is online on spinning disk, which should ensure fast and easy access. It should satisfy the requirements for most common applications. Data has been regridded to a regular lat-lon grid of 0.25 degrees for the reanalysis and 0.5 degrees for the uncertainty estimate (0.5 and 1 degree respectively for ocean waves). There are four main sub sets: hourly and monthly products, both on pressure levels (upper air fields) and single levels (atmospheric, ocean-wave and land surface quantities). ",,ERA5,ERA5,,"Climate,ECMWF,Reanalysis,ERA5,CDS,Atmospheric,land,sea,monthly,single,levels",ATMOSPHERIC,other,ERA5 monthly averaged data on single levels from 1940 to present,1940-01-01T00:00:00Z,ERA5_SL_MONTHLY,,,available,,,,,,available,,,,,,,,,,,,,,,,,,available,
+EUSTAT_AVAILABLE_BEDS_HOSPITALS_NUTS2,"Non-expenditure healthcare data provide information on institutions providing healthcare in countries, on resources used and on output produced in the framework of healthcare provision. \nData on healthcare form a major element of public health information as they describe the capacities available for different types of healthcare provision as well as potential 'bottlenecks' observed. The quantity and quality of healthcare services provided and the work sharing established between the different institutions are a subject of ongoing debate in all countries. Sustainability - continuously providing the necessary monetary and personal resources needed - and meeting the challenges of ageing societies are the primary perspectives used when analysing and using the data. \nThe resource-related data refer to both human and technical resources, i.e. they relate to: \n- Health care staff: 'manpower' active in the health care sector (doctors, dentists, nurses, etc.);\n- Heath workforce migration: migration movements of doctors and nurses;\n- Healthcare facilities: technical capacity dimensions (hospital beds, beds in nursing and residential care facilities, etc.).\nThe output-related data ('activities') refer to contacts between patients and the healthcare system, and to the treatment thereby received. Data are available for hospital discharges of in-patients and day cases, average length of stay of in-patients, consultations with medical professionals, and medical procedures performed in hospitals.\nAnnual national and regional data are provided in absolute numbers, percentages, and in population-standardised rates (per 100 000 inhabitants).\nWherever applicable, the definitions and classifications of the System of Health Accounts (SHA) are followed, e.g. International Classification for Health Accounts - Providers of health care (ICHA-HP). For hospital discharges, the International Shortlist for Hospital Morbidity Tabulation (ISHMT) is used. Surgical procedures are classified according to a shortlist mapped to ICD-9-CM.\nThese healthcare data are largely based on administrative data sources in the countries. Therefore, they reflect the country-specific way of organising healthcare and may not always be completely comparable. ",,Eurostat,Eurostat,,"Eurostat, Health care, Hospital, Bed, Health",,proprietary,Available beds in hospitals by NUTS 2 region,2013-01-01T00:00:00Z,EUSTAT_AVAILABLE_BEDS_HOSPITALS_NUTS2,,,,,,,,,available,,,,,,,,,,,,,,,,,,,
+EUSTAT_BATHING_SITES_WATER_QUALITY,"The indicator measures the number and proportion of coastal and inland bathing sites with excellent water quality. The indicator assessment is based on microbiological parameters (intestinal enterococci and Escherichia coli). The new Bathing Water Directive requires Member States to identify and assess the quality of all inland and marine bathing waters and to classify these waters as ‘poor’, ‘sufficient’, ‘good’ or ‘excellent’. ",,Eurostat,Eurostat,,"Eurostat, Bath, Water, Water quality",,proprietary,Bathing sites with excellent water quality by location,2011-01-01T00:00:00Z,EUSTAT_BATHING_SITES_WATER_QUALITY,,,,,,,,,available,,,,,,,,,,,,,,,,,,,
 EUSTAT_GREENHOUSE_GAS_EMISSION_AGRICULTURE,"This indicator tracks trends in greenhouse gas (GHG) emissions by agriculture, estimated and reported under the United Nations Framework Convention on Climate Change (UNFCCC), the Kyoto Protocol and the Decision 525/2013/EC. The annual data collection covers in principle all Member States of the European Union as well as some other European countries ",,Eurostat,Eurostat,,"Eurostat, Agriculture, Greenhouse gas, CO2, Emission, Air pollutants",,proprietary,Eurostat - Greenhouse gas emissions from agriculture,2011-01-01T00:00:00Z,EUSTAT_GREENHOUSE_GAS_EMISSION_AGRICULTURE,,,,,,,,,available,,,,,,,,,,,,,,,,,,,
 EUSTAT_POP_AGE_GROUP_SEX_NUTS3,"Each year Eurostat collects demographic data at regional level from 37 countries as part of the Unified Demography (Unidemo) project. UNIDEMO is Eurostat's main annual demographic data collection and aims to gather information on demography and migration. This dataset contains information about the population by sex, age and region of residence (NUTS 3 level). ",,Eurostat,Eurostat,,"Eurostat, Population, Age, Sex, NUTS 3, Unidemo, Demographic",,proprietary,"Population on 1 January by age, sex and NUTS 3 region",2014-01-01T00:00:00Z,EUSTAT_POP_AGE_GROUP_SEX_NUTS3,,,,,,,,,available,,,,,,,,,,,,,,,,,,,
 EUSTAT_POP_AGE_SEX_NUTS2,"Each year Eurostat collects demographic data at regional level from 37 countries as part of the Unified Demography (Unidemo) project. UNIDEMO is Eurostat's main annual demographic data collection and aims to gather information on demography and migration. This dataset contains information about the population by sex, age and region of residence (NUTS 2 level). ",,Eurostat,Eurostat,,"Eurostat, Population, Age, Sex, NUTS 2, Unidemo, Demographic",,proprietary,"Population on 1 January by age, sex and NUTS 2 region",1990-01-01T00:00:00Z,EUSTAT_POP_AGE_SEX_NUTS2,,,,,,,,,available,,,,,,,,,,,,,,,,,,,
 EUSTAT_POP_CHANGE_DEMO_BALANCE_CRUDE_RATES_NUTS3,Each year Eurostat collects demographic data at regional level from 37 countries as part of the Unified Demography (Unidemo) project. UNIDEMO is Eurostat's main annual demographic data collection and aims to gather information on demography and migration. This dataset contains information about demographic balance and crude rates of a population at regional level (NUTS 3 level). ,,Eurostat,Eurostat,,"Eurostat, Population, Age, Sex, NUTS 3, Unidemo, Demographic",,proprietary,Population change - Demographic balance and crude rates at regional level (NUTS 3),2000-01-01T00:00:00Z,EUSTAT_POP_CHANGE_DEMO_BALANCE_CRUDE_RATES_NUTS3,,,,,,,,,available,,,,,,,,,,,,,,,,,,,
+EUSTAT_POP_DENSITY_NUTS3,"Eurostat’s annual data collections on population. Member States send population data to Eurostat data as on of 31 December for the reference year under Regulation 1260/2013 on European demographic statistics. The data are conventionally published by Eurostat as population on 1 January of the following year (reference year + 1). \nThe aim is to collect annual mandatory and voluntary demographic data from the national statistical institutes. Mandatory data are those defined by the legislation listed under ‘6.1. Institutional mandate — legal acts and other agreements’. \nThe completeness of the demographic data collected on a voluntary basis depends on the availability and completeness of information provided by the national statistical institutes.\nFor more information on mandatory/voluntary data collection, see 6.1. Institutional mandate — legal acts and other agreements. \nThe following statistics are available. \nPopulation on 1 January by sex and by:\n- single age and educational attainment / marital status / broad group of citizenship / broad group of country of birth;\n  - five-year age group and citizenship / country of birth;\n  - citizenship and broad group of country of birth / country of birth and broad group of citizenship;\n  - broad age group and NUTS 3 (under regional data population folder);\n  - single age and NUTS 2 (under regional data population folder);\n  - five-year age group and NUTS 2 / NUTS 3 (under regional data population folder).\nPopulation structure statistics: median age of population, proportion of population by various age groups, old age dependency ratio. ",,Eurostat,Eurostat,,"Eurostat, Population, Density, NUTS 3",,proprietary,Population density by NUTS 3 region,1990-01-01T00:00:00Z,EUSTAT_POP_DENSITY_NUTS3,,,,,,,,,available,,,,,,,,,,,,,,,,,,,
 EUSTAT_SHARE_ENERGY_FROM_RENEWABLE,"This dataset covers the indicator for monitoring progress towards renewable energy targets of the Europe 2020 strategy implemented by Directive 2009/28/EC on the promotion of the use of energy from renewable sources. The annual data collection covers in principle all Member States of the European Union. Time series starts in the year 2004. Due to the change of legal basis, a break in series occurs between 2020 and 2021. The calculation is based on data collected in the framework of Regulation (EC) No 1099/2008 on energy statistics and complemented by specific supplementary data transmitted by national administrations to Eurostat. In some countries the statistical systems are not yet fully developed to meet all requirements of Directive 2009/28/EC, in particular with respect to ambient heat captured from the environment by heat pumps renewable cooling or sustainability of solid and gaseous biofuels. This is indicator is a Sustainable Development Goal (SDG). It has been chosen for the assessment of the progress towards the objectives and targets of the EU Sustainable Development Strategy. The data collection covers the full spectrum of the Member States of the European Union.The share of energy from renewable sources is calculated for four indicators: Transport (RES-T), Heating and Cooling (RES-H&C), Electricity (RES-E), Overall RES share (RES) ",,Eurostat,Eurostat,,"Eurostat, Energy, Renewable, Transport, Heating, Cooling, Electricity",,proprietary,Share of energy from renewable sources,2004-01-01T00:00:00Z,EUSTAT_SHARE_ENERGY_FROM_RENEWABLE,,,,,,,,,available,,,,,,,,,,,,,,,,,,,
+EUSTAT_SOIL_SEALING_INDEX,"The indicator estimates the increase in sealed soil surfaces with impervious materials due to urban development and construction (e.g. buildings, constructions and laying of completely or partially impermeable artificial material, such as asphalt, metal, glass, plastic or concrete). This provides an indication of the rate of soil sealing, when areas change land use towards artificial and urban land use. The indicator builds on data from the imperviousness High Resolution Layer (a product of the Copernicus Land Monitoring Service). The indicator is presented in the following units: Index 2006=100 % of total surface total sealed surface in km2. ",,Eurostat,Eurostat,,"Eurostat, soil, soil sealing, SDG, EU Sustainable Development Goals",,proprietary,Soil sealing index,2006-01-01T00:00:00Z,EUSTAT_SOIL_SEALING_INDEX,,,,,,,,,available,,,,,,,,,,,,,,,,,,,
+EUSTAT_SURFACE_TERRESTRIAL_PROTECTED_AREAS,The indicator measures the surface of terrestrial protected areas. The indicator comprises nationally designated protected areas and Natura 2000 sites. A nationally designated area is an area protected by national legislation. The Natura 2000 network comprises both marine and terrestrial protected areas designated under the EU Habitats and Birds Directives with the goal to maintain or restore a favourable conservation status for habitat types and species of EU interest. ,,Eurostat,Eurostat,,"Eurostat, CO2, terrestrial, protected areas",,proprietary,Surface of the terrestrial protected areas,2013-01-01T00:00:00Z,EUSTAT_SURFACE_TERRESTRIAL_PROTECTED_AREAS,,,,,,,,,available,,,,,,,,,,,,,,,,,,,
 FIRE_HISTORICAL,"This data set provides complete historical reconstruction of meteorological conditions favourable to the start, spread and sustainability of fires. The fire danger metrics provided are part of a vast dataset produced by the Copernicus Emergency Management Service for the European Forest Fire Information System (EFFIS). The European Forest Fire Information System incorporates the fire danger indices for three different models developed in Canada, United States and Australia. In this dataset the fire danger indices are calculated using weather forecast from historical simulations provided by ECMWF ERA5 reanalysis. ERA5 by combining model data and a vast set of quality controlled observations provides a globally complete and consistent data-set and is regarded as a good proxy for observed atmospheric conditions. The selected data records in this data set are regularly extended with time as ERA5 forcing data become available. This dataset is produced by ECMWF in its role of the computational centre for fire danger forecast of the CEMS, on behalf of the Joint Research Centre which is the managing entity of the service. Variables in the dataset/application are: Build-up index, Burning index, Danger rating, Drought code, Duff moisture code, Energy release component, Fine fuel moisture code, Fire daily severity index, Fire danger index, Fire weather index, Ignition component, Initial spread index, Keetch-Byram drought index, Spread component ",,CEMS,CEMS,,"ECMWF,EFFIS,fire,historical,ERA5,european,sustainability,CEMS,system",ATMOSPHERIC,other,Fire danger indices historical data from the Copernicus Emergency Management Service,1940-03-01T00:00:00Z,FIRE_HISTORICAL,,,,,available,,,,available,,,,,,,,,,,,,,,,,,available,
 FIRE_SEASONAL,"This dataset offers modeled daily fire danger time series, driven by seasonal weather forecasts. It provides long-range predictions of meteorological conditions conducive to the initiation, spread, and persistence of fires. The fire danger metrics included in this dataset are part of an extensive dataset produced by the Copernicus Emergency Management Service (CEMS) for the European Forest Fire Information System (EFFIS) and the Global Wildfire Information System (GWIS). EFFIS and GWIS are used for monitoring and forecasting fire danger at both European and global scales. The dataset incorporates fire danger indices from the U.S. Forest Service National Fire-Danger Rating System (NFDRS), the Canadian Forest Service Fire Weather Index Rating System (FWI), and the Australian McArthur (Mark 5) rating systems. This dataset was generated by driving the Global ECMWF Fire Forecast (GEFF) model with seasonal weather ensemble forecasts from the European Centre for Medium-Range Weather Forecasts (ECMWF) System 5 (SEAS5) prediction system.These forecasts initially consist of 25 ensemble members until December 2016, referred to as re-forecasts. After that period, they consist of seasonal forecasts with 51 members. It is important to note that the re-forecast dataset was initialized using ERA-Interim analysis data, while forecast simulations from 2016 onward are initialized using ECMWF operational analysis. Therefore, it is suggested that the period 1981-2016 be used as a reference period, while the period 2017-to present as a real time forecast. For both the re-forecast (1981-2016) and forecast periods (2017-present), the temporal resolution is daily forecasts at 12:00 local time, available once a month, with a prediction horizon of 216 days (equivalent to 7 months). The data records in this dataset will be extended over time as seasonal forcing data becomes available. Once the SEAS5 operation ceases, the dataset will be updated with the next ECMWF seasonal system (SEAS6). It is essential to note that this is not a real-time service, as real-time forecasts are accessible through the EFFIS web services. These seasonal forecasts can be used to assess the performance of the forecasting system or to develop tools for statistically correcting forecast errors. ECMWF produces this dataset as the computational center for fire danger forecasting within the Copernicus Emergency Management Service (CEMS) on behalf of the Joint Research Centre, which serves as the managing entity for this service. ",,CEMS,CEMS,,"ECMWF,CEMS,EFFIS,GWIS,fire,danger,seasonal,GEFF",,other,Seasonal forecast of fire danger indices from the Copernicus Emergency Management Service,1981-02-01T00:00:00Z,FIRE_SEASONAL,,,,,available,,,,,,,,,,,,,,,,,,,,,,,
 GLACIERS_DIST_RANDOLPH,"A glacier is defined as a perennial mass of ice, and possibly firn and snow, originating on the land surface from the recrystallization of snow or other forms of solid precipitation and showing evidence of past or present flow. There are several types of glaciers such as glacierets, mountain glaciers, valley glaciers and ice fields, as well as ice caps. Some glacier tongues reach into lakes or the sea, and can develop floating ice tongues or ice shelves. Glacier changes are recognized as independent and high-confidence natural indicators of climate change. Past, current and future glacier changes affect global sea level, the regional water cycle and local hazards.\nThis dataset is a snapshot of global glacier outlines compiled from\nmaps, aerial photographs and satellite images mostly acquired in the period 2000-2010. ",,,INSITU,,"ECMWF,WGMS,INSITU,CDS,C3S,glacier,randolph,distribution,inventory",ATMOSPHERIC,other,Glaciers distribution data from the Randolph Glacier Inventory for year 2000,2000-01-01T00:00:00Z,GLACIERS_DIST_RANDOLPH,,,available,,,,,,available,,,,,,,,,,,,,,,,,,available,

{eodag-3.5.1 → eodag-3.7.0}/docs/add_provider.rst

@@ -64,7 +64,7 @@ own needs (i.e. getting data from a provider not supported by ``eodag``), you sh
 and configure them. What you are the most likely to be willing to do is either to develop a new `Search <plugins_reference/search.rst>`_ plugin or an
 `Api <plugins_reference/api.rst>`_ plugin (e.g. to create an interface with another program).
 
-`eodag-sentinelsat <https://github.com/CS-SI/eodag-sentinelsat>`_ is a good example of an Api plugin. It creates an interface with the
+`eodag-sentinelsat (archived) <https://github.com/CS-SI/eodag-sentinelsat>`_ was a good example of an Api plugin. It created an interface with the
 `sentinalsat <https://github.com/sentinelsat/sentinelsat>`_ library to search and download products from `SciHub <https://scihub.copernicus.eu/>`_.
 
 See more details about how to create a new plugin in :ref:`this dedicated section <creating_plugins>`.

{eodag-3.5.1 → eodag-3.7.0}/docs/api_reference/core.rst

@@ -76,9 +76,11 @@ Misc
    EODataAccessGateway.guess_product_type
    EODataAccessGateway.list_queryables
    EODataAccessGateway.available_sortables
+   EODataAccessGateway.import_stac_items
 
 .. autoclass:: eodag.api.core.EODataAccessGateway
    :members: add_provider, set_preferred_provider, get_preferred_provider, update_providers_config, list_product_types,
              available_providers, search, search_all, search_iter_page, crunch, download, download_all, serialize,
              deserialize, deserialize_and_register, load_stac_items, group_by_extent, guess_product_type, get_cruncher,
-             update_product_types_list, fetch_product_types_list, discover_product_types, list_queryables, available_sortables
+             update_product_types_list, fetch_product_types_list, discover_product_types, list_queryables,
+             available_sortables, import_stac_items

{eodag-3.5.1 → eodag-3.7.0}/docs/api_user_guide.rst

@@ -30,3 +30,4 @@ or run locally after being downloaded (see how to :ref:`install_notebooks`).
    notebooks/api_user_guide/7_crunch.ipynb
    notebooks/api_user_guide/8_download.ipynb
    notebooks/api_user_guide/9_post_process.ipynb
+   notebooks/tutos/tuto_stac_client.ipynb

{eodag-3.5.1 → eodag-3.7.0}/docs/cli_user_guide.rst

@@ -9,52 +9,11 @@ Then you can start playing with it:
 
 * Run ``eodag --help`` to display all the available options and commands:
 
-.. code-block:: console
-
-        Usage: eodag [OPTIONS] COMMAND [ARGS]...
-
-        Earth Observation Data Access Gateway: work on EO products from any
-        provider
-
-        Options:
-        -v, --verbose  Control the verbosity of the logs. For maximum verbosity,
-                        type -vvv
-        --help         Show this message and exit.
+.. command-output:: eodag --help
 
-        Commands:
-        deploy-wsgi-app  Configure the settings of the HTTP web app (the...
-        discover         Fetch providers to discover product types
-        download         Download a list of products from a serialized search...
-        list             List supported product types
-        search           Search satellite images by their product types,...
-        serve-rest       Start eodag HTTP server
-        version          Print eodag version and exit
+* Each command has its own help, see for instance the help of the ``list`` command with ``eodag list --help``.
 
-* Each command has its own help, see for instance the help of the ``list`` command with ``eodag list --help``:
-
-.. code-block:: console
-
-        Usage: eodag list [OPTIONS]
-
-        List supported product types
-
-        Options:
-        -p, --provider TEXT             List product types supported by this
-                                        provider
-        -i, --instrument TEXT           List product types originating from this
-                                        instrument
-        -P, --platform TEXT             List product types originating from this
-                                        platform
-        -t, --platformSerialIdentifier TEXT
-                                        List product types originating from the
-                                        satellite identified by this keyword
-        -L, --processingLevel TEXT      List product types of processing level
-        -S, --sensorType TEXT           List product types originating from this
-                                        type of sensor
-        --no-fetch                      Do not fetch providers for new product types
-        --help                          Show this message and exit.
-
-* By default the command line interface of eodag is set to the minimum verbosity level. You can print more
+* By default the command line interface of eodag is set to the minimum **verbosity level**. You can print more
   log messages by adding ``-v`` to eodag master command. The more ``v`` given (up to 3), the more verbose the tool is.
   This feature comes in handy when you want to inspect an error or an unexpected behaviour. 4 different verbosity levels
   are offered to you:
@@ -66,6 +25,11 @@ Then you can start playing with it:
         eodag -vv list
         eodag -vvv list
 
+Search
+------
+
+.. command-output:: eodag search --help
+
 * To search for products and crunch the results of the search:
 
 .. code-block:: console
@@ -105,17 +69,19 @@ string search sent to the provider. For instance, if you want to add foo=1 and b
                      --cruncher-args FilterOverlap minimum_overlap 10 \
                      --query "foo=1&bar=2"
 
-* If the product type is not known, it can also be guessed by EODAG during the search based on parameters in the search request. The possible parameters are:
+* If the product type is not known, it can also be guessed by EODAG during the search based on parameters in the search
+  request. The possible parameters are:
 
-        * `instrument` (e.g. MSI)
-        * `platform` (e.g. SENTINEL2)
-        * `platformSerialIdentifier` (e.g. S2A)
-        * `processingLevel` (e.g. L1)
-        * `sensorType` (e.g. OPTICAL)
-        * `keywords` (e.g. SENTINEL2 L1C SAFE), which is case insensitive and ignores `-` or `_` characters
+  - `instrument` (e.g. MSI)
+  - `platform` (e.g. SENTINEL2)
+  - `platformSerialIdentifier` (e.g. S2A)
+  - `processingLevel` (e.g. L1)
+  - `sensorType` (e.g. OPTICAL)
+  - `keywords` (e.g. SENTINEL2 L1C SAFE), which is case insensitive and ignores `-` or `_` characters
 
-For example, the following search request will first search for a product type for platform SENTINEL2 and processingLevel L1
-(there are several product types matching these criteria, e.g., `S2_MSI_L1C`) and then use this product type to execute the actual search.
+For example, the following search request will first search for a product type for platform SENTINEL2 and
+processingLevel L1 (there are several product types matching these criteria, e.g., `S2_MSI_L1C`) and then use this
+product type to execute the actual search.
 
 .. code-block:: console
 
@@ -125,12 +91,34 @@ For example, the following search request will first search for a product type f
         --box 1 43 2 44 \
         --start 2021-03-01 --end 2021-03-31
 
+Download
+--------
+
+.. command-output:: eodag download --help
+
 * To download the result of a previous call to ``search``:
 
 .. code-block:: console
 
         eodag download --conf my_conf.yml --search-results my_search.geojson
 
+* To download STAC items from their URL or path:
+
+.. code-block:: console
+
+        eodag download --stac-item https://foo/collections/bar/items/item-1-id --stac-item /path/to/item2.json
+
+* Using commands chaining, ``download`` can also directly be executed after a ``search`` in a single command:
+
+.. code-block:: console
+
+        eodag search --productType S2_MSI_L1C --bbox 1 43 2 44 --start 2025-03-01 download
+
+Product Types
+-------------
+
+.. command-output:: eodag list --help
+
 * To list all available product types and supported providers:
 
 .. code-block:: console
@@ -153,6 +141,10 @@ For example, the following search request will first search for a product type f
 * EODAG can fetch providers (all or only a given one) to discover available product types, using the following command.
   It will store result in a JSON file (defaults to `ext_product_types.json`):
 
+.. command-output:: eodag discover --help
+
+Examples:
+
 .. code-block:: console
 
         eodag discover
@@ -164,3 +156,22 @@ This file can then be used in EODAG using the environment variable ``EODAG_EXT_P
 Please note that if you did not customize EODAG with new providers settings, this command should not be useful.
 For more information on the product types discovery mechanism, please see
 `Python API User Guide / Providers and products / Product types discovery <notebooks/api_user_guide/2_providers_products_available.html#Product-types-discovery>`_.
+
+Server mode
+-----------
+
+EODAG has a STAC compliant REST API. It can serve configured providers data through
+this STAC API.
+
+.. command-output:: eodag serve-rest --help
+
+And for advanced configuration:
+
+.. command-output:: eodag deploy-wsgi-app --help
+
+See server mode usage examples in `STAC REST API Server <stac_rest.rst>`_.
+
+.. toctree::
+   :maxdepth: 2
+
+   stac_rest

{eodag-3.5.1 → eodag-3.7.0}/docs/conf.py

@@ -46,6 +46,7 @@ extensions = [
     "sphinx_copybutton",
     "sphinx_tabs.tabs",
     "sphinx_autodoc_typehints",
+    "sphinxcontrib.programoutput",
     "sphinxemoji.sphinxemoji",
 ]
 

{eodag-3.5.1 → eodag-3.7.0}/docs/getting_started_guide/configure.rst

@@ -175,7 +175,7 @@ Example usage:
 
 .. code-block:: bash
 
-   export EODAG_PROVIDERS_WHITELIST=peps,creodias,theia
+   export EODAG_PROVIDERS_WHITELIST=peps,creodias,cop_dataspace
    export EODAG_STRICT_PRODUCT_TYPES=true
 
 CLI configuration

eodag-3.5.1/docs/getting_started_guide/side_projects.rst → eodag-3.7.0/docs/getting_started_guide/ecosystem.rst

@@ -1,7 +1,7 @@
-.. _side_projects:
+.. ecosystem:
 
-Side projects
-=============
+Ecosystem
+=========
 
 EODAG-cube
 ----------
@@ -10,15 +10,6 @@ Data access functionalities have been split to a separate project to avoid confl
 unneeded libraries when using only EODAG basic functionalities. EODAG-cube is available
 on `github <https://github.com/CS-SI/eodag-cube>`__ and `pypi <https://pypi.org/project/eodag-cube>`__.
 
-EODAG-sentinelsat
------------------
-
-API plugin that enables to search and download EO products from catalogs implementing the
-`SciHub / Copernicus Open Access Hub interface <https://scihub.copernicus.eu/userguide/WebHome>`_.
-It is basically a wrapper around `sentinelsat <https://sentinelsat.readthedocs.io>`_, enabling it to be used with EODAG.
-EODAG-sentinelsat is available on `github <https://github.com/CS-SI/eodag-sentinelsat>`__ and
-`pypi <https://pypi.org/project/eodag-sentinelsat/>`__.
-
 EODAG-labextension
 ------------------
 

{eodag-3.5.1 → eodag-3.7.0}/docs/getting_started_guide/index.rst

@@ -16,4 +16,4 @@ it efficiently as quickly as possible.
    product_types
    product_storage_status
    configure
-   side_projects
+   ecosystem

{eodag-3.5.1 → eodag-3.7.0}/docs/getting_started_guide/overview.rst

@@ -6,7 +6,7 @@ Why EODAG?
 Nowadays, we observe a rise in publicly accessible Earth Observation (EO) data.
 Together with it, there is more and more EO data providers, each potentially having
 a different data access policy. This difference is visible at various levels:
-in the data discovery (CSW, OpenSearch more or less custom, etc.), in the
+in the data discovery (STAC, OData, OpenSearch more or less custom, etc.), in the
 product access (object storage, downloads, direct file system access, etc.), in
 the storage structure and in the authentication mechanisms (OAUTH, JWT, basic
 auth,...). All these different technologies add a knowledge overhead on a user
@@ -28,9 +28,9 @@ EODAG is developed in Python. It is structured according to a modular plugin
 architecture, easily extensible and able to integrate new data providers. Three
 types of plugins compose the tool:
 
-* Catalog search plugins, responsible for searching data (OpenSearch, CSW, ...),
+* Catalog search plugins, responsible for searching data (STAC, OpenSearch, OData, ...),
   building paths, retrieving quicklook, combining results
-* Download plugins, allowing to download and retrieve data locally (via FTP, HTTP, ..),
+* Download plugins, allowing to download and retrieve data locally (via HTTP, S3, ...),
   always with the same directory organization
 * Authentication plugins, which are used to authenticate the user on the
   external services used (JSON Token, Basic Auth, OAUTH, ...).

{eodag-3.5.1 → eodag-3.7.0}/docs/getting_started_guide/providers.rst

@@ -11,7 +11,7 @@ Products from the following providers are made avaiable through ``eodag``:
 * `aws_eos <https://eos.com/>`_: EOS search for Amazon public datasets
 * `cop_ads <https://ads.atmosphere.copernicus.eu>`_: Copernicus Atmosphere Data Store
 * `cop_cds <https://cds.climate.copernicus.eu>`_: Copernicus Climate Data Store
-* `cop_dataspace <https://dataspace.copernicus.eu/>`_: Copernicus Data Space
+* `cop_dataspace <https://dataspace.copernicus.eu/>`_: Copernicus Data Space Ecosystem
 * `cop_ewds <https://ewds.climate.copernicus.eu>`_: CEMS Early Warning Data Store
 * `cop_marine <https://marine.copernicus.eu>`_: Copernicus Marine Service
 * `creodias <https://creodias.eu/>`_: CloudFerro DIAS
@@ -30,8 +30,6 @@ Products from the following providers are made avaiable through ``eodag``:
 * `peps <https://peps.cnes.fr/rocket/#/home>`_: French National Space Agency (CNES) catalog for Sentinel products
 * `planetary_computer <https://planetarycomputer.microsoft.com/>`_: Microsoft Planetary Computer
 * `sara <https://copernicus.nci.org.au>`_: Sentinel Australasia Regional Access
-* `theia <https://theia.cnes.fr/atdistrib/rocket/>`_: French National Space Agency (CNES) value-adding products for Land
-  surfaces
 * `usgs <https://earthexplorer.usgs.gov/>`_: U.S geological survey catalog for Landsat products
 * `usgs_satapi_aws <https://landsatlook.usgs.gov/sat-api/>`_: USGS Landsatlook SAT API
 * `wekeo_cmems <https://www.wekeo.eu>`_: Copernicus Marine (CMEMS) data from WEkEO

{eodag-3.5.1 → eodag-3.7.0}/docs/getting_started_guide/register.rst

@@ -207,10 +207,6 @@ with your Microsoft account `here <https://planetarycomputer.developer.azure-api
 Create an account `here <https://copernicus.nci.org.au/sara.client/#/register>`__, then use your email as ``username`` in
 eodag credentials.
 
-``theia``
-^^^^^^^^^
-Create an account `here <https://sso.theia-land.fr/theia/register/register.xhtml>`__
-
 ``usgs``
 ^^^^^^^^
 Create an account  `here <https://ers.cr.usgs.gov/register/>`__, and

{eodag-3.5.1 → eodag-3.7.0}/docs/index.rst

@@ -47,7 +47,6 @@ types (Sentinel 1, Sentinel 2, Sentinel 3, Landsat, etc.) that can be searched a
       `peps <https://peps.cnes.fr/rocket/#/home>`_,
       `planetary_computer <https://planetarycomputer.microsoft.com>`_,
       `sara <https://copernicus.nci.org.au>`_,
-      `theia <https://theia.cnes.fr/atdistrib/rocket>`_,
       `usgs <https://earthexplorer.usgs.gov>`_,
       `usgs_satapi_aws <https://landsatlook.usgs.gov>`_,
       `wekeo_cmems <https://www.wekeo.eu>`_,
@@ -120,9 +119,8 @@ Site contents
    getting_started_guide/index
    api_user_guide
    api_reference/index
-   breaking_changes
    cli_user_guide
-   stac
+   breaking_changes
    tutos
 
 .. toctree::