feat!: add option to avoid creating footprints TDE-1159

[l0b0]

Motivation

Give the user control of whether we create footprints for tiles. This is a workaround for some footprints resulting in unusably complex capture areas.

Modification

Add flag to control whether footprints (and therefore capture areas) are created.

We had to use a mandatory flag to workaround not finding how to conditionally pass arguments with Argo Workflows.

Checklist

• Tests updated
• Docs updated
• Issue linked in Title

[l0b0]

Manually tested:

docker run -v ${HOME}/tmp/:/tmp/:rw topo-imagery python standardise_validate.py --preset webp --from-file ./tests/data/aerial.json --collection-id 123 --start-datetime 2023-01-01 --end-datetime 2023-01-01 --target /tmp/ --source-epsg 2193 --target-epsg 2193 --gsd 10m --create-footprints=false
# Did not create a footprint
$ docker run -v ${HOME}/tmp/:/tmp/:rw topo-imagery python standardise_validate.py --preset webp --from-file ./tests/data/aerial.json --collection-id 123 --start-datetime 2023-01-01 --end-datetime 2023-01-01 --target /tmp/ --source-epsg 2193 --target-epsg 2193 --gsd 10m --create-footprints=true
# Created a footprint

Only the specified values are accepted:

❯ docker run -v ${HOME}/tmp/:/tmp/:rw topo-imagery python standardise_validate.py --preset webp --from-file ./tests/data/aerial.json --collection-id 123 --start-datetime 2023-01-01 --end-datetime 2023-01-01 --target /tmp/ --source-epsg 2193 --target-epsg 2193 --gsd 10m --create-footprints=True
usage: standardise_validate.py [-h] --preset PRESET --from-file FROM_FILE
                               --source-epsg SOURCE_EPSG --target-epsg
                               TARGET_EPSG --gsd GSD --create-footprints
                               CREATE_FOOTPRINTS [--cutline [CUTLINE]]
                               --collection-id COLLECTION_ID --start-datetime
                               START_DATETIME --end-datetime END_DATETIME
                               --target TARGET
standardise_validate.py: error: argument --create-footprints: Invalid boolean (must be exactly 'true' or 'false'): True

[paulfouquet]

We had to use a mandatory flag to workaround not finding how to conditionally pass arguments with Argo Workflows