@gfenoy or maybe, as an alternative, use the one provided with the default binary image in /var/www/html/data?

@gfenoy or maybe, as an alternative, use the one provided with the default binary image in /var/www/html/data?

Indeed, the examples repository already contains the required files. But, as we are now using a volume for /usr/com/zoo-project the file are only available in /var/www/html/data even if they are copied in the right location in the Dockerfile on line 336.

I am wondering if it would be better to use symbolic links from /usr/com/zoo-project to /var/www/html/data for both topofr.tif and station1.gml. This way we don't need to download twice the same files.

git + symlinks + Windows is a horrible mix
I don't know how is the binary image generated? Or maybe simply configure the GDAL service to use /var/www/html/data

@gfenoy I think that the best solution is to make Docker prepoluate this directory:
https://docs.docker.com/storage/volumes/#populate-a-volume-using-a-container

Where does this file come from? It is not in the git repository, yet it is in the official image?

git + symlinks + Windows is a horrible mix

Agreed.

I don't know how is the binary image generated? Or maybe simply configure the GDAL service to use /var/www/html/data

The binary image is generated using a dedicated GitHub Action.

@gfenoy I think that the best solution is to make Docker prepoluate this directory: https://docs.docker.com/storage/volumes/#populate-a-volume-using-a-container

Where does this file come from? It is not in the git repository, yet it is in the official image?

The files required by the examples are stored in another dedicated GitHub repository: https://github.com/ZOO-Project/examples

This repo is cloned from the Dockerfile used by the GitHub Action: https://github.com/ZOO-Project/ZOO-Project/blob/main/.github/workflows/docker-image.yml responsible for building and pushing the official image

Populating the directory looks perfect to me

Superseded by #25