Frequently Asked Questions¶

Contents:

Q: How can I fix “proj_create_from_database: ellipsoid not found” messages?
Q: Why do I get a log error when running several jobs?
Q: How can I overcome timeouts when searching for online products?
Q: How can I ask another question?

Q: How can I fix “proj_create_from_database: ellipsoid not found” messages?¶

A: Just ignore the error. As far as we known, it has no incidence.

This message is produced by current version of GDAL (used by OTB 7.3 and 7.4) on Sentinel-1 products with an “unnamed ellipsoid”. If you execute gdalinfo on these Sentinel-1 products you will also observe the error, independently of S1Tiling or OTB.

Example:

$> gdalinfo s1a-iw-grd-vv-20200108t044150-20200108t044215-030704-038506-001.tiff
ERROR 1: PROJ: proj_create_from_database: ellipsoid not found
proj_create_from_database: ellipsoid not found
Driver: GTiff/GeoTIFF
Files: s1a-iw-grd-vv-20200108t044150-20200108t044215-030704-038506-001.tiff
Size is 25345, 16817
GCP Projection =
GEOGCRS["WGS 84",
    DATUM["World Geodetic System 1984",
        ELLIPSOID["unnamed",6378137,298.25722356049,
...

It’s likely related to GDAL issue #2321, and tracked in S1Tiling issue #46.

Q: Why do I get a log error when running several jobs?¶

A: When running S1Tiling in several jobs that can be executed simultaneously, DO NOT execute S1Tiling in the same directory. Also, DO NOT use the same global directory to generate temporary files. Indeed, parallel instances of S1Tiling will write in the same files and corrupt them. Make sure to work in different spaces.

In other words,

execute S1Tiling from, for instance, ${PBS_O_WORKDIR}/${PBS_JOBID}, – indeed, unlike ${TMPDIR}/, ${PBS_O_WORKDIR}/${PBS_JOBID} will persist job execution on PBS.
and set [PATHS].tmp to ${TMPDIR}/whatever-${PBS_JOBID}.

This Q/A is tracked in S1Tiling issue #70.

Q: How can I overcome timeouts when searching for online products?¶

Some data providers like PEPS may fail to obtain in time the list of products matching our criteria.

Since EODAG v2.11.0, we can override the default timeout value thanks to:

the $EODAG__{PROVIDER}__SEARCH__TIMEOUT environment variable,
or the configuration option {provider}.search.timeout.

In case you have to cope with an earlier version of EODAG, you can still run S1Processor with --nb_max_search_retries.

Q: How can I ask another question?¶

You can contact us and ask any question related to S1Tiling on S1Tiling discourse forum.

If you think your issue is a bug, please follow the procedure described in the contributing guide.