POC MapProxy/Flow Checks

asafMasa commented 3 years ago

Vrt:

[x] Nodata / Alpha Channel difference - Using nodata
[x] Create vrt file from s3 stored tifs - gdalbuildvrt cannot locate tif files that are stored in s3

Gdal2Tiles:

[x] MapProxy render performance
[x] Mixed format support? PNG/JPEG - gdal2tiles supports only png format , theres some community forks to gdal2tiles.py with ability to choose jpeg format but not mixed
[x] Resampling method (average, near, bilinear, cubic, cubicspline, lanczos, antialias, mode, max, min, med, q1, q3)
[x] Type of PNG , Byte etc.. - RGB Color
[x] Examining the amount of work time at different levels: [x] 0-12: 10min [x] 13: 9min [x] 14: 12min [x] 15: 14min [x] 16: 18min [x] 17: 55mins [x] 18: 3hours

Zoom levels & Overviews:

[x] Generate max zoom level according to the resolution level of the layer - gdal2tiles service will contain some logic to compare resolution level to zoom level tiles requested.

MapProxy:

[x] Is there any limit of layers per mosaic
[x] Create 80 cache directories in minio from the original 'Tif' file and load it into mapproxy
[x] Check CPU performance
[x] Check if mapproxy creates any cache tiles for missing or upscaled/downscaled tiles

CL-SHLOMIKONCHA commented 3 years ago

gdalbuildvrt: gdalbuildvrt -vrtnodata 0 -a_srs EPSG:4326 -r bilinear fullpath/to/create/.vrt fullpath/to/stored/files/*.tif

gdal2tiles: gdal2tiles.py nodata.vrt -s EPSG:4326 -z 0-12 -p geodetic --tmscompatible

CL-SHLOMIKONCHA commented 3 years ago

result:

for every change detected in mapproxy config yaml file , mapproxy read it again, meanwhile the service is not available until its done. (the more layer published on yaml file - reads takes longer)
the more layers that mosaic contains - longer time per tiles request

MapColonies / GEEDocker