Hi all. When I want to process image from 1C to 2A using sen2cor L2A_Process, and when I am configure L2A_GIPP.xml to use DEM to dem/srtm folder I get this:
The download of srtm images is good, and when L2A_process start, I get new images for scene that I process:
I get the same error. Process stop and no messages are printed in the terminal.
When processing using NO DEM the correction is performed without errors.
Hi both. It looks as if multiple instances of the gdal warp are executed in parallel and that this apparently blocks the generation of the DEMs. Can you confirm that you are doing a parallel processing? And if yes, how many processes in parallel?
Can you try with only one processing? Before you do this, remove the temporary files in the dem/srtm directory (these are the ones with the long names). Leave only the images with the name srtm_xx_yy.tif. In the next days I will try to reproduce your problem.
OK, I will have a check, but I need some more info in ahead: please give me the ID of the product you are working with. I need this because I need to check whether there is something wrong with the generation of the DEMs for this product in special. Does it always occurr or does it randomly occurr, and how many tiles do you process? Thanks for your info.
I can’t find ID of product. Name of scene is:
S2A_OPER_PRD_MSIL1C_PDMC_20151223T032753_R036_V20151222T094850_20151222T094850.SAFE
I am processing entire scene, all granules.
You can see which srtm dem scenes I have, and what L2A_Process created, and than nothing happens:
what is completely strange is the mix of the two progress meters of GDAL (the dotted numbers: the should normally go from 0 - 100 - it looks like in your case two gdal processes are started at the same time and they seem to interfere. I never observed this before …
I’m experiencing a similar problem running sen2cor from the command line in Debian testing: everything works fine without the DEM but the process stops with no error if the DEM folder is specified (inside the sen2cor installation folder or not didn’t change anything…). By the way, I don’t see the strange behavior reported by Milutinke that made umwilm think to a conflict between several parallel processes.
I’m processing entire images and it happens every time with images from different locations in Europe, this is what happens