eodag 3.10.0__tar.gz → 3.10.1__tar.gz

eodag-3.10.1/.github/workflows/package.yml

@@ -0,0 +1,57 @@
+name: Build and publish a container image
+
+on:
+  push:
+    branches: ['master']
+    tags: ['v*']
+  workflow_dispatch:
+  repository_dispatch:
+    types: [release]
+
+env:
+  REGISTRY: ghcr.io
+  IMAGE_NAME: ${{ github.repository }}
+
+jobs:
+  build-and-push-image:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      packages: write
+      id-token: write
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v6
+
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v3
+
+      - name: Log in to the container registry
+        uses: docker/login-action@v3
+        with:
+          registry: ${{ env.REGISTRY }}
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Extract container metadata
+        id: meta
+        uses: docker/metadata-action@v5
+        with:
+          images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
+          labels: |
+            org.opencontainers.image.title=eodag
+            org.opencontainers.image.description=Earth Observation Data Access Gateway
+            org.opencontainers.image.url=https://github.com/{{ github.repository }}
+            org.opencontainers.image.source=https://github.com/{{ github.repository }}.git
+            org.opencontainers.image.licenses=Apache-2.0
+            org.opencontainers.image.authors=CS GROUP - France (CSSI) <eodag@csgroup.space>
+
+      - name: Build and push container image
+        id: push
+        uses: docker/build-push-action@v6
+        with:
+          context: .
+          push: true
+          tags: ${{ steps.meta.outputs.tags }}
+          labels: ${{ steps.meta.outputs.labels }}

{eodag-3.10.0 → eodag-3.10.1}/.github/workflows/test.yml

@@ -2,9 +2,9 @@ name: Run Tests
 
 on:
   push:
-    branches: [master, develop]
+    branches: [master, develop, v3.10.x]
   pull_request:
-    branches: [master, develop]
+    branches: [master, develop, v3.10.x]
   schedule:
     - cron: "0 7 * * 1"
   workflow_dispatch:
@@ -33,7 +33,7 @@ jobs:
     runs-on: ${{ matrix.os }}
     strategy:
       matrix:
-        python-version: [3.9, "3.13"]
+        python-version: [3.9, "3.14"]
         os: [ubuntu-latest, windows-latest]
     steps:
     - name: Checkout the repo
@@ -80,7 +80,7 @@ jobs:
       uses: insightsengineering/coverage-action@v2
       with:
         # Path to the Cobertura XML report.
-        path: artifacts/unit-test-results-python3.13-ubuntu-latest/coverage.xml
+        path: artifacts/unit-test-results-python3.14-ubuntu-latest/coverage.xml
         # Minimum total coverage, if you want to the
         # workflow to enforce it as a standard.
         # This has no effect if the `fail` arg is set to `false`.
@@ -112,7 +112,7 @@ jobs:
       uses: insightsengineering/coverage-action@v2
       with:
         # Path to the Cobertura XML report.
-        path: artifacts/unit-test-results-python3.13-windows-latest/coverage.xml
+        path: artifacts/unit-test-results-python3.14-windows-latest/coverage.xml
         # Minimum total coverage, if you want to the
         # workflow to enforce it as a standard.
         # This has no effect if the `fail` arg is set to `false`.

{eodag-3.10.0 → eodag-3.10.1}/CHANGES.rst

@@ -2,6 +2,73 @@
 Release history
 ===============
 
+.. _changelog-unreleased:
+
+v3.10.1 (2025-12-11)
+====================
+
+Bug Fixes
+---------
+
+* **core**: Queryables alias usage (`#1893`_, `fd00403`_)
+
+* **core**: Skip None EOProduct.properties (`9264e54`_)
+
+* **plugins**: Add temporal resolution to ecmwf properties (`6c82a1e`_)
+
+* **plugins**: Cop_marine search by id (`a10d509`_)
+
+* **plugins**: Dates formatting and missing param in ECMWFSearch queryables (`b36db01`_)
+
+* **plugins**: Ecmwf geometries support (`8a14151`_)
+
+* **providers**: Geodes max_items_per_page down to 80 (`0bb913b`_)
+
+* **providers**: Renamed THEIA collections on geodes (`cba02fc`_)
+
+Build System
+------------
+
+* Add docker image (`52e6088`_)
+
+* Add python3.14 support (`57b7260`_)
+
+Chores
+------
+
+* Allow pydantic >= 2.12.0 by buiding docs with python3.13 (`6be0eb7`_)
+
+Documentation
+-------------
+
+* Docker image (`352607c`_)
+
+Refactoring
+-----------
+
+* **collections**: CLMS and MetOp updates (`8808c5f`_)
+
+* **core**: Whole world as default product geometry and shapely stubs (`c49e26d`_)
+
+* **plugins**: Boto3 ServiceResource type check (`6b78dae`_)
+
+.. _#1893: https://github.com/CS-SI/eodag/pull/1893
+.. _0bb913b: https://github.com/CS-SI/eodag/commit/0bb913b7582fee5dad1d1d22961906e336f81719
+.. _352607c: https://github.com/CS-SI/eodag/commit/352607cc751a7dd45d6bd905a8f92723f00ae5bd
+.. _52e6088: https://github.com/CS-SI/eodag/commit/52e60885e72608f9b215f4f8a5b4f4ae177e8f87
+.. _57b7260: https://github.com/CS-SI/eodag/commit/57b72600d5cd9b99427a758ad058dac3a298f26e
+.. _6b78dae: https://github.com/CS-SI/eodag/commit/6b78dae5e76847887ca2823d36507845e557db6a
+.. _6be0eb7: https://github.com/CS-SI/eodag/commit/6be0eb713df1aac8382f1f359335560ac413272c
+.. _6c82a1e: https://github.com/CS-SI/eodag/commit/6c82a1ea0c46057145ff1662ba43403eff69fbca
+.. _8808c5f: https://github.com/CS-SI/eodag/commit/8808c5fd603a838c1f7be0f2c710a85babb3f7d7
+.. _8a14151: https://github.com/CS-SI/eodag/commit/8a14151a4c1b320191bd9ba963201520512988d7
+.. _9264e54: https://github.com/CS-SI/eodag/commit/9264e54f5765af356d14c129a2718ee91c1adf00
+.. _a10d509: https://github.com/CS-SI/eodag/commit/a10d509baeca36d0602bbd22c62bb06fbc13d79c
+.. _b36db01: https://github.com/CS-SI/eodag/commit/b36db0109d4b9969835a63787a867cd0702e05c8
+.. _c49e26d: https://github.com/CS-SI/eodag/commit/c49e26d71d5b8e8f4408be07f63cf3d2dd414a90
+.. _cba02fc: https://github.com/CS-SI/eodag/commit/cba02fc453f435d617f24161d6d716095071f2b9
+.. _fd00403: https://github.com/CS-SI/eodag/commit/fd004035d1415421bfb55356e9dad4ead83734ba
+
 
 v3.10.0 (2025-10-20)
 ====================

{eodag-3.10.0 → eodag-3.10.1}/CONTRIBUTING.rst

@@ -75,7 +75,7 @@ To run the entire tests (units, integration and end-to-end):
       you, please `install <https://pandoc.org/installing.html>`_ pandoc and try
       again.
 
-    * eodag is tested against python versions 3.9, 3.10, 3.11, 3.12 and 3.13. Ensure you have
+    * eodag is tested against python versions 3.9, 3.10, 3.11, 3.12, 3.13 and 3.14. Ensure you have
       these versions installed before you run tox. You can use
       `pyenv <https://github.com/pyenv/pyenv>`_ to manage many different versions
       of python

eodag-3.10.1/Dockerfile

@@ -0,0 +1,41 @@
+# Copyright 2025, CS GROUP - France, https://www.csgroup.eu/
+#
+# This file is part of EODAG project
+#     https://www.github.com/CS-SI/EODAG
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#     http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+FROM python:alpine3.13
+
+LABEL author="CS GROUP - France"
+
+WORKDIR /app
+
+COPY eodag/ eodag/
+COPY setup.cfg pyproject.toml README.rst LICENSE MANIFEST.in ./
+
+# build-base is required to enable logging
+RUN apk add --no-cache build-base && \
+    pip install --no-cache-dir ".[all-providers]" && \
+    apk del build-base
+
+# Create a non-root user to run the application
+RUN addgroup -g 1000 eodag && \
+    adduser -u 1000 -G eodag \
+        -h /home/eodag \
+        -s /bin/sh \
+        -D eodag
+USER eodag
+
+ENTRYPOINT ["eodag"]
+CMD ["--help"]

{eodag-3.10.0/eodag.egg-info → eodag-3.10.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: eodag
-Version: 3.10.0
+Version: 3.10.1
 Summary: Earth Observation Data Access Gateway
 Home-page: https://github.com/CS-SI/eodag
 Author: CS GROUP - France
@@ -23,6 +23,7 @@ Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
 Classifier: Programming Language :: Python :: Implementation :: CPython
 Classifier: Topic :: Internet :: WWW/HTTP :: Indexing/Search
 Classifier: Topic :: Scientific/Engineering :: GIS
@@ -40,7 +41,7 @@ Requires-Dist: importlib_metadata>=5.0
 Requires-Dist: jsonpath-ng
 Requires-Dist: lxml
 Requires-Dist: orjson
-Requires-Dist: pydantic!=2.10.0,<2.12.0,>=2.1.0
+Requires-Dist: pydantic!=2.10.0,>=2.1.0
 Requires-Dist: pydantic_core
 Requires-Dist: PyJWT[crypto]>=2.5.0
 Requires-Dist: pyproj>=2.1.0
@@ -115,6 +116,7 @@ Requires-Dist: types-requests; extra == "stubs"
 Requires-Dist: types-python-dateutil; extra == "stubs"
 Requires-Dist: types-PyYAML; extra == "stubs"
 Requires-Dist: types-setuptools; extra == "stubs"
+Requires-Dist: types-shapely; extra == "stubs"
 Requires-Dist: types-tqdm; extra == "stubs"
 Requires-Dist: types-urllib3; extra == "stubs"
 Provides-Extra: docs
@@ -317,7 +319,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.10.0
+    docker run -p 5000:5000 --rm csspace/eodag-server:3.10.1
 
 You can also browse over your STAC API server using `STAC Browser <https://github.com/radiantearth/stac-browser>`_.
 Simply run:
@@ -377,6 +379,15 @@ Start playing with the CLI:
 
 - To print log messages, add ``-v`` to eodag master command. e.g. ``eodag -v list``. The more ``v`` given (up to 3), the more verbose the tool is. For a full verbose output, do for example: ``eodag -vvv list``
 
+Docker image
+------------
+
+A Docker image is available via the `GitHub Container Registry <https://github.com/CS-SI/eodag/pkgs/container/eodag>`_:
+
+.. code-block:: bash
+
+    docker pull ghcr.io/cs-si/eodag:v3.10.x
+
 Contribute
 ==========
 

{eodag-3.10.0 → eodag-3.10.1}/README.rst

@@ -185,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.10.0
+    docker run -p 5000:5000 --rm csspace/eodag-server:3.10.1
 
 You can also browse over your STAC API server using `STAC Browser <https://github.com/radiantearth/stac-browser>`_.
 Simply run:
@@ -245,6 +245,15 @@ Start playing with the CLI:
 
 - To print log messages, add ``-v`` to eodag master command. e.g. ``eodag -v list``. The more ``v`` given (up to 3), the more verbose the tool is. For a full verbose output, do for example: ``eodag -vvv list``
 
+Docker image
+------------
+
+A Docker image is available via the `GitHub Container Registry <https://github.com/CS-SI/eodag/pkgs/container/eodag>`_:
+
+.. code-block:: bash
+
+    docker pull ghcr.io/cs-si/eodag:v3.10.x
+
 Contribute
 ==========
 

{eodag-3.10.0 → eodag-3.10.1}/charts/eodag-server/Chart.yaml

@@ -1,5 +1,5 @@
 apiVersion: v2
-appVersion: 3.10.0
+appVersion: 3.10.1
 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.10.0
+version: 3.10.1

{eodag-3.10.0 → eodag-3.10.1}/docs/_static/product_types_information.csv

@@ -22,6 +22,10 @@ CLMS_GLO_GDMP_333M,"Gross dry matter Productivity (GDMP) is an indication of the
 CLMS_GLO_LAI_333M,"LAI was defined by CEOS as half the developed area of the convex hull wrapping the green canopy elements per unit horizontal ground. This definition allows accounting for elements which are not flat such as needles or stems. LAI is strongly non linearly related to reflectance. Therefore, its estimation from remote sensing observations will be scale dependant over heterogeneous landscapes. When observing a canopy made of different layers of vegetation, it is therefore mandatory to consider all the green layers. This is particularly important for forest canopies where the understory may represent a very significant contribution to the total canopy LAI. The derived LAI corresponds therefore to the total green LAI, including the contribution of the green elements of the understory. The product at 333m resolution is provided in Near Real Time and consolidated in the next six periods. ","OLCI,PROBA-V",Sentinel-3,,,"Land,Leaf-area-index,LAI,OLCI,PROBA-V,Sentinel-3",,other,Global 10-daily Leaf Area Index 333m,2014-01-10T00:00:00Z,CLMS_GLO_LAI_333M,,,,,,,,,available,,,,,,,,,,,,,,,,,,available
 CLMS_GLO_NDVI_1KM_LTS,"The Normalized Difference Vegetation Index (NDVI) is a proxy to quantify the vegetation amount. It is defined as NDVI=(NIR-Red)/(NIR+Red) where NIR corresponds to the reflectance in the near infrared band, and Red to the reflectance in the red band. The time series of dekadal (10-daily) NDVI 1km version 2 observations over the period 1999-2017 is used to calculate Long Term Statistics (LTS) for each of the 36 10-daily periods (dekads) of the year. The calculated LTS include the minimum, median, maximum, average, standard deviation and the number of observations in the covered time series period. These LTS can be used as a reference for actual NDVI observations, which allows evaluating whether vegetation conditions deviate from a 'normal' situation. ","VEGETATION,PROBA-V",SPOT,,,"Land,NDVI,LTS,SPOT,VEGETATION,PROBA-V",,other,"Normalized Difference Vegetation Index: global Long Term Statistics (raster 1km) - version 2, Apr 2019",1999-01-01T00:00:00Z,CLMS_GLO_NDVI_1KM_LTS,,,,,,,,,available,,,,,,,,,,,,,,,,,,available
 CLMS_GLO_NDVI_333M,"The Normalized Difference Vegetation Index (NDVI) is a proxy to quantify the vegetation amount. It is defined as NDVI=(NIR-Red)/(NIR+Red) where NIR corresponds to the reflectance in the near infrared band, and Red to the reflectance in the red band. It is closely related to FAPAR and is little scale dependant. ",PROBA-V,,,,"Land,NDVI,PROBA-V",,other,Global 10-daily Normalized Difference Vegetation Index 333M,2014-01-01T00:00:00Z,CLMS_GLO_NDVI_333M,,,,,,,,,available,,,,,,,,,,,,,,,,,,available
+CLMS_HRVPP_ST,"The Seasonal Trajectories product is a filtered time series of Plant Phenology Index (PPI), with regular time step, part of the Copernicus Land Monitoring Service (CLMS) HR-VPP product suite. Plant Phenology Index (PPI) is a physically based vegetation index that is optimized for monitoring vegetation phenology and has a linear relationship with green leaf area index. The Seasonal Trajectories (ST) products are derived from a function fitting of the time series of the PPI vegetation index and hence provide a filtered PPI time series, with regular 10-day time step, together with related quality information (QFLAG). The PPI Seasonal Trajectories are derived from the PPI vegetation index and hence based on Copernicus Sentinel-2 satellite observations. The ST products are made available as a set of raster files with 10m and 100m resolution, in ETRS89/LAEA projection corresponding to the High Resolution Layers tiling grid, for those tiles that cover the EEA38 countries and the United Kingdom, and for the period from 2017 until today, with yearly updates. These Seasonal Trajectories are part of the pan-European High Resolution Vegetation Phenology and Productivity (HR-VPP) component of the Copernicus Land Monitoring Service (CLMS). ",,Sentinel-2,"S2A,S2B,S2C",,"Land,Plant-phenology-index,Phenology,Vegetation,Sentinel-2,S2A,S2B,S2C",,other,"Seasonal Trajectories, 10-daily, ST projection",,CLMS_HRVPP_ST,,,,,,,,,,,,,,,,,,,,,,,,,,,available
+CLMS_HRVPP_ST_LAEA,"The Seasonal Trajectories product is a filtered time series of Plant Phenology Index (PPI), with regular time step, part of the Copernicus Land Monitoring Service (CLMS) HR-VPP product suite. Plant Phenology Index (PPI) is a physically based vegetation index that is optimized for monitoring vegetation phenology and has a linear relationship with green leaf area index. The Seasonal Trajectories (ST) products are derived from a function fitting of the time series of the PPI vegetation index and hence provide a filtered PPI time series, with regular 10-day time step, together with related quality information (QFLAG). The PPI Seasonal Trajectories are derived from the PPI vegetation index and hence based on Copernicus Sentinel-2 satellite observations. The ST products are made available as a set of raster files with 10m and 100m resolution, in ETRS89/LAEA projection corresponding to the High Resolution Layers tiling grid, for those tiles that cover the EEA38 countries and the United Kingdom, and for the period from 2017 until today, with yearly updates. These Seasonal Trajectories are part of the pan-European High Resolution Vegetation Phenology and Productivity (HR-VPP) component of the Copernicus Land Monitoring Service (CLMS). ",,Sentinel-2,"S2A,S2B,S2C",,"Land,Plant-phenology-index,Phenology,Vegetation,Sentinel-2,S2A,S2B,S2C",,other,"Seasonal Trajectories, 10-daily, LAEA projection",,CLMS_HRVPP_ST_LAEA,,,,,,,,,,,,,,,,,,,,,,,,,,,available
+CLMS_HRVPP_VPP,"Vegetation Phenology and Productivity (VPP) comprise 13 parameters up to 2 seasons that characterize the vegetation growth cycle. It is part of the Copernicus Land Monitoring Service (CLMS) HR-VPP product suite. A set of 13 Vegetation Phenology and Productivity parameters are derived, for up to two growing seasons. These parameters include the start, end and length of the growing season, the dates when the vegetation index reaches its minimum and maximum values, the maximum value itself and its distance to the minimum (amplitude), the slopes of the green-up and green-down periods and the seasonal and total productivity. The Vegetation and Productivity parameters are extracted from the filtered PPI time-series, the HR-VPP Seasonal Trajectories, and hence based on Copernicus Sentinel-2 satellite observations. The VPP parameters are made available as a set of raster files with 10m and 100m resolution, in ETRS89/LAEA projection corresponding to the High Resolution Layers tiling grid, for those tiles that cover the EEA38 countries and the United Kingdom and for the period from 2017 until today, with yearly updates. This VPP product is part of the pan-European High Resolution Vegetation Phenology and Productivity (HR-VPP) component of the Copernicus Land Monitoring Service (CLMS). ",,Sentinel-2,"S2A,S2B,S2C",,"Land,Plant-phenology-index,Phenology,Vegetation,Sentinel-2,S2A,S2B,S2C",,other,"Vegetation Phenology and Productivity, yearly, UTM projection",,CLMS_HRVPP_VPP,,,,,,,,,,,,,,,,,,,,,,,,,,,available
+CLMS_HRVPP_VPP_LAEA,"Vegetation Phenology and Productivity (VPP) comprise 13 parameters up to 2 seasons that characterize the vegetation growth cycle. It is part of the Copernicus Land Monitoring Service (CLMS) HR-VPP product suite. A set of 13 Vegetation Phenology and Productivity parameters are derived, for up to two growing seasons. These parameters include the start, end and length of the growing season, the dates when the vegetation index reaches its minimum and maximum values, the maximum value itself and its distance to the minimum (amplitude), the slopes of the green-up and green-down periods and the seasonal and total productivity. The Vegetation and Productivity parameters are extracted from the filtered PPI time-series, the HR-VPP Seasonal Trajectories, and hence based on Copernicus Sentinel-2 satellite observations. The VPP parameters are made available as a set of raster files with 10m and 100m resolution, in ETRS89/LAEA projection corresponding to the High Resolution Layers tiling grid, for those tiles that cover the EEA38 countries and the United Kingdom and for the period from 2017 until today, with yearly updates. This VPP product is part of the pan-European High Resolution Vegetation Phenology and Productivity (HR-VPP) component of the Copernicus Land Monitoring Service (CLMS). ",,Sentinel-2,"S2A,S2B,S2C",,"Land,Plant-phenology-index,Phenology,Vegetation,Sentinel-2,S2A,S2B,S2C",,other,"Vegetation Phenology and Productivity, yearly, LAEA projection",,CLMS_HRVPP_VPP_LAEA,,,,,,,,,,,,,,,,,,,,,,,,,,,available
 CMIP6_CLIMATE_PROJECTIONS,"This catalogue entry provides daily and monthly global climate projections data from a large number of experiments, models and time periods computed in the framework of the sixth phase of the Coupled Model Intercomparison Project (CMIP6). CMIP6 data underpins the Intergovernmental Panel on Climate Change 6th Assessment Report. The use of these data is mostly aimed at:\n\naddressing outstanding scientific questions that arose as part of the IPCC reporting process; improving the understanding of the climate system; providing estimates of future climate change and related uncertainties; providing input data for the adaptation to the climate change; examining climate predictability and exploring the ability of models to predict climate on decadal time scales; evaluating how realistic the different models are in simulating the recent past.\n\nThe term ""experiments"" refers to the three main categories of CMIP6 simulations:\n\nHistorical experiments which cover the period where modern climate observations exist. These experiments show how the GCMs performs for the past climate and can be used as a reference period for comparison with scenario runs for the future. The period covered is typically 1850-2014. Climate projection experiments following the combined pathways of Shared Socioeconomic Pathway (SSP) and Representative Concentration Pathway (RCP). The SSP scenarios provide different pathways of the future climate forcing. The period covered is typically 2015-2100.\n\nThis catalogue entry provides both two- and three-dimensional data, along with an option to apply spatial and/or temporal subsetting to data requests. This is a new feature of the global climate projection dataset, which relies on compute processes run simultaneously in the ESGF nodes, where the data are originally located. The data are produced by the participating institutes of the CMIP6 project. ",CMIP6,CMIP6,CMIP6,,"ECMWF,CDS,C3S,CMIP6,historical,projection,global",,other,CMIP6 climate projections,1850-01-01T00:00:00Z,CMIP6_CLIMATE_PROJECTIONS,,,available,,,,,,,,,,,,,,,,,,,,,,,,
 COP_DEM_GLO30_DGED,"Defence Gridded Elevation Data (DGED, 32 Bit floating point) formatted Copernicus DEM GLO-30 data. The Copernicus Digital Elevation Model is a Digital Surface Model (DSM) that represents the surface of the Earth including buildings, infrastructure and vegetation. The Copernicus DEM is provided in 3 different instances: EEA-10, GLO-30 and GLO-90. GLO-30 provides worldwide coverage at 30 meters.Data were acquired through the TanDEM-X mission between 2011 and 2015. The datasets were made available for use in 2019 and will be maintained until 2026. ",,TerraSAR,,,"TerraSAR,TanDEM-X,DEM,surface,GLO-30,DSM,GDGED",ALTIMETRIC,other,Copernicus DEM GLO-30 DGED,2010-06-21T00:00:00Z,COP_DEM_GLO30_DGED,,,,,,,available,available,available,,available,,,,,,,,,,,,,,,,available
 COP_DEM_GLO30_DTED,"Digital Terrain Elevation Data (DTED, 16 Bit signed integer) formatted Copernicus DEM GLO-30 data. The Copernicus Digital Elevation Model is a Digital Surface Model (DSM) that represents the surface of the Earth including buildings, infrastructure and vegetation. The Copernicus DEM is provided in 3 different instances: EEA-10, GLO-30 and GLO-90. GLO-30 provides worldwide coverage at 30 meters.Data were acquired through the TanDEM-X mission between 2011 and 2015. The datasets were made available for use in 2019 and will be maintained until 2026. ",,TerraSAR,,,"TerraSAR,TanDEM-X,DEM,surface,GLO-30,DSM,DTED",ALTIMETRIC,other,Copernicus DEM GLO-30 DTED,2010-06-21T00:00:00Z,COP_DEM_GLO30_DTED,,,,,,,available,available,available,,,,,,,,,,,,,,,,,,available
@@ -29,7 +33,6 @@ COP_DEM_GLO90_DGED,"Defence Gridded Elevation Data (DGED, 32 Bit floating point)
 COP_DEM_GLO90_DTED,"Digital Terrain Elevation Data (DTED, 16 Bit signed integer) formatted Copernicus DEM GLO-90 data. The Copernicus Digital Elevation Model is a Digital Surface Model (DSM) that represents the surface of the Earth including buildings, infrastructure and vegetation. The Copernicus DEM is provided in 3 different instances: EEA-10, GLO-30 and GLO-90. GLO-90 provides worldwide coverage at 90 meters.Data were acquired through the TanDEM-X mission between 2011 and 2015. The datasets were made available for use in 2019 and will be maintained until 2026. ",,TerraSAR,,,"TerraSAR,TanDEM-X,DEM,surface,GLO-90,DSM,DTED",ALTIMETRIC,other,Copernicus DEM GLO-90 DTED,2010-06-21T00:00:00Z,COP_DEM_GLO90_DTED,,,,,,,available,available,available,,,,,,,,,,,,,,,,,,available
 DT_CLIMATE_ADAPTATION,"The Digital Twin on Climate Change Adaptation support the analysis and testing of scenarios. This in turn will support sustainable development and climate adaptation and mitigation policy-making at multi-decadal timescales, at regional and national levels. ",,Digital Twin,DT,,"DT,DE,LUMI,Destination-Earth,Digital-Twin,Climate,Change,Adaptation",ATMOSPHERIC,other,Climate Change Adaptation Digital Twin (DT),2020-01-01T00:00:00Z,DT_CLIMATE_ADAPTATION,,,,,,,,,available,available,,,,,,,,,,,,,,,,,
 DT_EXTREMES,The Digital Twin on Weather-Induced and Geophysical Extremes provides capabilities for the assessment and prediction of environmental extremes in support of risk assessment and management. ,,Digital Twin,DT,,"DT,DE,LUMI,Destination-Earth,Digital-Twin,Weather,Geophysical,Extremes",ATMOSPHERIC,other,Weather and Geophysical Extremes Digital Twin (DT),2024-04-04T00:00:00Z,DT_EXTREMES,,,,,,,,,available,available,,,,,,,,,,,,,,,,,
-EEA_DAILY_VI,"Vegetation Indices (VI) comprises four daily vegetation indices (PPI, NDVI, LAI and FAPAR) and quality information, that are part of the Copernicus Land Monitoring Service (CLMS) HR-VPP product suite. The 10m resolution, daily updated Plant Phenology Index (PPI), Normalized Difference Vegetation Index (NDVI), Leaf Area Index (LAI) and Fraction of Absorbed Photosynthetically Active Radiation (fAPAR) are derived from Copernicus Sentinel-2 satellite observations. They are provided together with a related quality indicator (QFLAG2) that flags clouds, shadows, snow, open water and other areas where the VI retrieval is less reliable. These Vegetation Indices are made available as a set of raster files with 10 x 10m resolution, in UTM/WGS84 projection corresponding to the Sentinel-2 tiling grid, for those tiles that cover the EEA38 countries and the United Kingdom and for the period from 2017 until today, with daily updates. The Vegetation Indices are part of the pan-European High Resolution Vegetation Phenology and Productivity (HR-VPP) component of the Copernicus Land Monitoring Service (CLMS). ",,Sentinel-2,"S2A,S2B,S2C",,"Land,Plant-phenology-index,Phenology,Vegetation,Sentinel-2,S2A,S2B,S2C",RADAR,other,"Vegetation Indices, daily, UTM projection",,EEA_DAILY_VI,,,,,,,,,available,,,,,,,,,,,,,,,,,,available
 EEA_HRL_TCF,Tree Cover Fraction (TCF) is defined as the percentage of ground covered by tree canopy when viewed from above. It is a biophysical variable that characterizes the land surface and is important for many applications in environmental and climate studies. TCF is derived from Sentinel-2 imagery at 20m resolution using a machine learning approach. The TCF product is part of the pan-European High Resolution Vegetation Phenology and Productivity (HR-VPP) component of the Copernicus Land Monitoring Service (CLMS). ,,Sentinel-2,"S2A,S2B,S2C",,"Land,Tree-cover-fraction,TCF,Sentinel-2,S2A,S2B,S2C",RADAR,other,"Tree Cover Fraction, UTM projection",2017-01-01T00:00:00Z,EEA_HRL_TCF,,,,,,,,,,,,,,,,,,,,,,,,,,,available
 EFAS_FORECAST,"This dataset provides gridded modelled hydrological time series forced with medium-range meteorological forecasts. The data is a consistent representation of the most important hydrological variables across the European Flood Awareness System (EFAS) domain. The temporal resolution is sub-daily high-resolution and ensemble forecasts of:\n\nRiver discharge\nSoil moisture for three soil layers\nSnow water equivalent\n\nIt also provides static data on soil depth for the three soil layers. Soil moisture and river discharge data are accompanied by ancillary files for interpretation (see related variables and links in the documentation).\nThis data set was produced by forcing the LISFLOOD hydrological model at a 5x5km resolution with meteorological forecasts. The forecasts are initialised twice daily at 00 and 12 UTC with time steps of 6 or 24 hours and lead times between 5 and 15 days depending on the forcing numerical weather prediction model. The forcing meteorological data are high-resolution and ensemble forecasts from the European Centre of Medium-range Weather Forecasts (ECMWF) with 51 ensemble members, high-resolution forecasts from the Deutsches Wetter Dienst (DWD) and the ensemble forecasts from the COSMO Local Ensemble Prediction System (COSMO-LEPS) with 20 ensemble members. The hydrological forecasts are available from 2018-10-10 up until present with a 30-day delay. The real-time data is only available to EFAS partners.\nCompanion datasets, also available through the CDS, are historical simulations which can be used to derive the hydrological climatology and for verification; reforecasts for research, local skill assessment and post-processing; and seasonal forecasts and reforecasts for users looking for longer leadtime forecasts. For users looking for global hydrological data, we refer to the Global Flood Awareness System (GloFAS) forecasts and historical simulations. All these datasets are part of the operational flood forecasting within the Copernicus Emergency Management Service (CEMS).\n\nVariables in the dataset/application are:\nRiver discharge in the last 24 hours, River discharge in the last 6 hours, Snow depth water equivalent, Soil depth, Volumetric soil moisture\n\nVariables in the dataset/application are:\nOrography, Upstream area ",,CEMS,CEMS,,"ECMWF,CEMS,EFAS,forecast,river,discharge",ATMOSPHERIC,other,River discharge and related forecasted data by the European Flood Awareness System,2018-10-11T00:00:00Z,EFAS_FORECAST,,,,,available,,,,available,,,,,,,,,,,,,,,,,,
 EFAS_HISTORICAL,"This dataset provides gridded modelled daily hydrological time series forced with meteorological observations. The data set is a consistent representation of the most important hydrological variables across the European Flood Awareness System (EFAS) domain. The temporal resolution is up to 30 years modelled time series of:\n\nRiver discharge\nSoil moisture for three soil layers\nSnow water equivalent\n\nIt also provides static data on soil depth for the three soil layers. Soil moisture and river discharge data are accompanied by ancillary files for interpretation (see related variables and links in the documentation).\nThis dataset was produced by forcing the LISFLOOD hydrological model with gridded observational data of precipitation and temperature at a 5x5 km resolution across the EFAS domain. The most recent version\nuses a 6-hourly time step, whereas older versions uses a 24-hour time step. It is available from 1991-01-01 up until near-real time, with a delay of 6 days. The real-time data is only available to EFAS partners.\nCompanion datasets, also available through the CDS, are forecasts for users who are looking medium-range forecasts, reforecasts for research, local skill assessment and post-processing, and seasonal forecasts and reforecasts for users looking for long-term forecasts. For users looking for global hydrological data, we refer to the Global Flood Awareness System (GloFAS) forecasts and historical simulations. All these datasets are part of the operational flood forecasting within the Copernicus Emergency Management Service (CEMS).\n\nVariables in the dataset/application are:\nRiver discharge in the last 24 hours, River discharge in the last 6 hours, Snow depth water equivalent, Soil depth, Volumetric soil moisture\n\nVariables in the dataset/application are:\nOrography, Upstream area ",,CEMS,CEMS,,"ECMWF,CEMS,EFAS,historical,river,discharge",ATMOSPHERIC,other,River discharge and related historical data from the European Flood Awareness System,1991-01-01T06:00:00Z,EFAS_HISTORICAL,,,,,available,,,,available,,,,,,,,,,,,,,,,,,
@@ -67,7 +70,7 @@ GSW_OCCURRENCE,The Global Surface Water Occurrence shows where surface water occ
 GSW_RECURRENCE,The Global Surface Water Recurrence provides information concerning the inter-annual behaviour of water surfaces and captures the frequency with which water returns from year to year. ,,GSW,GSW,,"PEKEL, Global Surface Water, Recurrence, Landsat",HYDROLOGICAL,proprietary,Global Surface Water Recurrence 1984-2021,1984-01-01T00:00:00Z,GSW_RECURRENCE,,,,,,,,,available,,,,,,,,,,,,,,,,,,
 GSW_SEASONALITY,The Global Surface Water Seasonality map provides information concerning the intra-annual behaviour of water surfaces for a single year (2021) and shows permanent and seasonal water and the number of months water was present. ,,GSW,GSW,,"PEKEL, Global Surface Water, Seasonality, Landsat",HYDROLOGICAL,proprietary,Global Surface Water Seasonality 2014-2020,2014-01-01T00:00:00Z,GSW_SEASONALITY,,,,,,,,,available,,,,,,,,,,,,,,,,,,
 GSW_TRANSITIONS,"The Global Surface Water Transitions map provides information on the change in surface water seasonality between the first and last years (between 1984 and 2021) and captures changes between the three classes of not water, seasonal water and permanent water. ",,GSW,GSW,,"PEKEL, Global Surface Water, Transitions, Landsat",HYDROLOGICAL,proprietary,Global Surface Water Transitions 1984-2021,1984-01-01T00:00:00Z,GSW_TRANSITIONS,,,,,,,,,available,,,,,,,,,,,,,,,,,,
-HIRS_FDR_1_MULTI,"This is Release 1 of the Fundamental Data Record (FDR) brightness temperatures from the High Resolution Infrared Radiation Sounder (HIRS) on board NOAA and Metop satellites. The data record covers more than 40 years from 29 October 1978 to 31 December 2020. Release 1 provides recalibrated Level 1c brightness temperatures based on the V4.0 calibration method developed by Cao et al. (2007). This method was implemented into the NWP-SAF software ATOVS and AVHRR processing Package (AAPP). This software was consistently used to recalibrate and reprocess data from all HIRS instruments on board TIROS-N, NOAA-06 to NOAA-19, Metop-A, and Metop-B. The polygons, required for the data tailoring, show problems with non-continues data. Some polygons of the HIRS data record are found to be incorrect. However, this does not affect the correctness of the data itself. This is a Fundamental Data Record (FDR). ",HIRS,"Metop,TIROS,NOAA","Metop,TIROS,NOAA",L1C,"HIRS,L1C,HIRS,TIROS,Metop,NOAA,Sounder,FDR",Sounder,other,HIRS Level 1C Fundamental Data Record Release 1 - Multimission - Global,1978-10-29T00:00:00Z,HIRS_FDR_1_MULTI,,,,,,,,,,,,,,available,,,,,,,,,,,,,
+HIRS_FDR_1_MULTI,"This is Release 2 of the Fundamental Data Record (FDR) brightness temperatures from the High Resolution Infrared Radiation Sounder (HIRS) on board NOAA and Metop satellites. The data record covers more than 40 years from 29 October 1978 to 31 December 2022. Release 2 provides recalibrated Level 1c brightness temperatures based on the V4.0 calibration method developed by Cao et al. (2007). This method was implemented into the NWP-SAF software ATOVS and AVHRR processing Package (AAPP). This software was consistently used to recalibrate and reprocess data from all HIRS instruments on board TIROS-N, NOAA-06 to NOAA-19, Metop-A, and Metop-B. Input HIRS data were collected from NOAA/CLASS and ECMWF archives and merged to produce a longer time series of some of the satellites. ",HIRS,"Metop,TIROS,NOAA","Metop,TIROS,NOAA",L1C,"HIRS,L1C,HIRS,TIROS,Metop,NOAA,Sounder,FDR",Sounder,other,HIRS Level 1C Fundamental Data Record Release 2 - Multimission - Global,1978-10-29T00:00:00Z,HIRS_FDR_1_MULTI,,,,,,,,,,,,,,available,,,,,,,,,,,,,
 ISIMIP_CLIMATE_FORCING_ISIMIP3B,"The Inter-Sectoral Impact Model Intercomparison Project (ISIMIP) provides a framework for the collation of a consistent set of climate impact data across sectors and scales. It also provides a unique opportunity for considering interactions between climate change impacts across sectors through consistent scenarios.\n\nThe ISIMIP3b part of the third simulation round is dedicated to a quantification of climate-related risks at different levels of global warming and socio-economic change. ISIMIP3b group I simulations are based on historical climate change as simulated in CMIP6 combined with observed historical socio-economic forcing. ISIMIP3b group II simulations are based on climate change according to the CMIP6 future projections combined with socio-economic forcings fixed at 2015 levels. ISIMIP3b group III simulations additionally account for future changes in socio-economic forcing.\n\nThis collection contains bias-adjusted atmospheric climate input data, atmospheric composition input data as well as ocean and lightning input data. ",,ISIMIP,ISIMIP,,"ISIMIP, CLIMATE-FORCING, ISIMIP3b, atmospheric, climate, HRMC",,other,ISIMIP3b climate input data,1601-01-01T00:00:00Z,ISIMIP_CLIMATE_FORCING_ISIMIP3B,,,,,,,,,available,,,,,,,,,,,,,,,,,,
 ISIMIP_SOCIO_ECONOMIC_FORCING_ISIMIP3B,"The Inter-Sectoral Impact Model Intercomparison Project (ISIMIP) provides a framework for the collation of a consistent set of climate impact data across sectors and scales. It also provides a unique opportunity for considering interactions between climate change impacts across sectors through consistent scenarios.\n\nThe ISIMIP3b part of the third simulation round is dedicated to a quantification of climate-related risks at different levels of global warming and socio-economic change. ISIMIP3b group I simulations are based on historical climate change as simulated in CMIP6 combined with observed historical socio-economic forcing. ISIMIP3b group II simulations are based on climate change according to the CMIP6 future projections combined with socio-economic forcings fixed at 2015 levels. ISIMIP3b group III simulations additionally account for future changes in socio-economic forcing. This collection contains fishing, lake fraction, land use, land transition, water abstraction and wood harvesting input data as well as information about crops and fertilizers ",,ISIMIP,ISIMIP,,"ISIMIP, SOCIO-ECONOMIC-FORCING, ISIMIP3b, socioeconomic",,other,ISIMIP3b socio-economic input data,1601-01-01T00:00:00Z,ISIMIP_SOCIO_ECONOMIC_FORCING_ISIMIP3B,,,,,,,,,available,,,,,,,,,,,,,,,,,,
 L8_OLI_TIRS_C1L1,Landsat 8 Operational Land Imager and Thermal Infrared Sensor Collection 1 Level-1 products. Details at https://landsat.usgs.gov/sites/default/files/documents/LSDS-1656_Landsat_Level-1_Product_Collection_Definition.pdf ,"OLI,TIRS",LANDSAT8,L8,L1,"OLI,TIRS,LANDSAT,LANDSAT8,L8,L1,C1,COLLECTION1",OPTICAL,other,Landsat 8 Level-1,2013-02-11T00:00:00Z,L8_OLI_TIRS_C1L1,available,,,,,,,,,,,available,,,,,,,,,,,,,,,

{eodag-3.10.0 → eodag-3.10.1}/docs/cli_user_guide.rst

@@ -157,6 +157,15 @@ Please note that if you did not customize EODAG with new providers settings, thi
 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>`_.
 
+Docker image
+------------
+
+A Docker image is available via the `GitHub Container Registry <https://github.com/CS-SI/eodag/pkgs/container/eodag>`_:
+
+.. code-block:: bash
+
+    docker pull ghcr.io/cs-si/eodag:v3.10.x
+
 Server mode
 -----------
 

{eodag-3.10.0 → eodag-3.10.1}/docs/stac_rest.rst

@@ -99,7 +99,7 @@ available on `https://hub.docker.com/r/csspace/eodag-server <https://hub.docker.
 
 .. code-block:: bash
 
-    $ docker run -p 5000:5000 --rm csspace/eodag-server:3.10.0
+    $ docker run -p 5000:5000 --rm csspace/eodag-server:3.10.1
 
 Example
 -------

{eodag-3.10.0 → eodag-3.10.1}/eodag/api/core.py

@@ -56,7 +56,7 @@ from eodag.plugins.search import PreparedSearch
 from eodag.plugins.search.build_search_result import MeteoblueSearch
 from eodag.plugins.search.qssearch import PostJsonSearch
 from eodag.types import model_fields_to_annotated
-from eodag.types.queryables import CommonQueryables, QueryablesDict
+from eodag.types.queryables import CommonQueryables, Queryables, QueryablesDict
 from eodag.utils import (
     DEFAULT_DOWNLOAD_TIMEOUT,
     DEFAULT_DOWNLOAD_WAIT,
@@ -2318,8 +2318,14 @@ class EODataAccessGateway:
                         plugin.provider,
                     )
 
+            # use queryables aliases
+            kwargs_alias = {**kwargs}
+            for search_param, field_info in Queryables.model_fields.items():
+                if search_param in kwargs and field_info.alias:
+                    kwargs_alias[field_info.alias] = kwargs_alias.pop(search_param)
+
             plugin_queryables = plugin.list_queryables(
-                kwargs,
+                kwargs_alias,
                 available_product_types,
                 product_type_configs,
                 product_type,

{eodag-3.10.0 → eodag-3.10.1}/eodag/api/product/_product.py

@@ -48,6 +48,7 @@ from eodag.api.product.metadata_mapping import (
 from eodag.utils import (
     DEFAULT_DOWNLOAD_TIMEOUT,
     DEFAULT_DOWNLOAD_WAIT,
+    DEFAULT_SHAPELY_GEOMETRY,
     DEFAULT_STREAM_REQUESTS_TIMEOUT,
     USER_AGENT,
     ProgressCallback,
@@ -67,12 +68,6 @@ if TYPE_CHECKING:
     from eodag.types.download_args import DownloadConf
     from eodag.utils import Unpack
 
-try:
-    from shapely.errors import GEOSException
-except ImportError:
-    # shapely < 2.0 compatibility
-    from shapely.errors import TopologicalError as GEOSException
-
 
 logger = logging.getLogger("eodag.product")
 
@@ -136,6 +131,7 @@ class EOProduct:
             if key != "geometry"
             and value != NOT_MAPPED
             and NOT_AVAILABLE not in str(value)
+            and value is not None
         }
         if "geometry" not in properties or (
             (
@@ -144,17 +140,17 @@ class EOProduct:
             )
             and "defaultGeometry" not in properties
         ):
-            raise MisconfiguredError(
-                f"No geometry available to build EOProduct(id={properties.get('id')}, provider={provider})"
-            )
+            product_geometry = DEFAULT_SHAPELY_GEOMETRY
         elif not properties["geometry"] or properties["geometry"] == NOT_AVAILABLE:
             product_geometry = properties.pop("defaultGeometry", DEFAULT_GEOMETRY)
         else:
             product_geometry = properties["geometry"]
 
-        self.geometry = self.search_intersection = get_geometry_from_various(
-            geometry=product_geometry
-        )
+        geometry_obj = get_geometry_from_various(geometry=product_geometry)
+        # whole world as default geometry
+        if geometry_obj is None:
+            geometry_obj = DEFAULT_SHAPELY_GEOMETRY
+        self.geometry = self.search_intersection = geometry_obj
 
         self.search_kwargs = kwargs
         if self.search_kwargs.get("geometry") is not None:
@@ -163,7 +159,7 @@ class EOProduct:
             )
             try:
                 self.search_intersection = self.geometry.intersection(searched_geom)
-            except (GEOSException, ShapelyError):
+            except ShapelyError:
                 logger.warning(
                     "Unable to intersect the requested extent: %s with the product "
                     "geometry: %s",

{eodag-3.10.0 → eodag-3.10.1}/eodag/api/product/metadata_mapping.py

@@ -42,6 +42,7 @@ from shapely.ops import transform
 from eodag.types.queryables import Queryables
 from eodag.utils import (
     DEFAULT_PROJ,
+    DEFAULT_SHAPELY_GEOMETRY,
     _deprecated,
     deepcopy,
     dict_items_recursive_apply,
@@ -340,14 +341,16 @@ def format_metadata(search_param: str, *args: Any, **kwargs: Any) -> str:
         @staticmethod
         def convert_to_bounds(input_geom_unformatted: Any) -> list[float]:
             input_geom = get_geometry_from_various(geometry=input_geom_unformatted)
+            if input_geom is None:
+                input_geom = DEFAULT_SHAPELY_GEOMETRY
             if isinstance(input_geom, MultiPolygon):
                 geoms = [geom for geom in input_geom.geoms]
                 # sort with larger one at first (stac-browser only plots first one)
                 geoms.sort(key=lambda x: x.area, reverse=True)
-                min_lon = 180
-                min_lat = 90
-                max_lon = -180
-                max_lat = -90
+                min_lon = 180.0
+                min_lat = 90.0
+                max_lon = -180.0
+                max_lat = -90.0
                 for geom in geoms:
                     min_lon = min(min_lon, geom.bounds[0])
                     min_lat = min(min_lat, geom.bounds[1])

{eodag-3.10.0 → eodag-3.10.1}/eodag/plugins/crunch/filter_latest_intersect.py

@@ -70,6 +70,7 @@ class FilterLatestIntersect(Crunch):
         # Warning: May crash if startTimeFromAscendingNode is not in the appropriate format
         products.sort(key=self.sort_product_by_start_date, reverse=True)
         filtered: list[EOProduct] = []
+        search_extent: BaseGeometry
         add_to_filtered = filtered.append
         footprint: Union[dict[str, Any], BaseGeometry, Any] = search_params.get(
             "geometry"

{eodag-3.10.0 → eodag-3.10.1}/eodag/plugins/crunch/filter_overlap.py

@@ -20,15 +20,11 @@ from __future__ import annotations
 import logging
 from typing import TYPE_CHECKING, Any
 
+from shapely.errors import ShapelyError
+
 from eodag.plugins.crunch.base import Crunch
 from eodag.utils import get_geometry_from_various
 
-try:
-    from shapely.errors import GEOSException
-except ImportError:
-    # shapely < 2.0 compatibility
-    from shapely.errors import TopologicalError as GEOSException
-
 if TYPE_CHECKING:
     from eodag.api.product import EOProduct
 
@@ -108,7 +104,7 @@ class FilterOverlap(Crunch):
                         product_geometry = product.geometry.buffer(0)
                         try:
                             intersection = search_geom.intersection(product_geometry)
-                        except GEOSException:
+                        except ShapelyError:
                             logger.debug(
                                 "Product geometry still invalid. Overlap test restricted to containment"
                             )

{eodag-3.10.0 → eodag-3.10.1}/eodag/plugins/download/aws.py

@@ -716,7 +716,7 @@ class AwsDownload(Download):
             ignore_assets,
             product,
         )
-        if auth and isinstance(auth, boto3.resources.base.ServiceResource):
+        if auth and isinstance(auth, boto3.resource("s3").__class__):
             s3_resource = auth
         else:
             s3_resource = boto3.resource(