I’m trying to calculate the NDVI using the snappy_ndvi.py example buyt the processing is extremely slow, maybe more than one day to process 30978 lines. However, the time employed when I use the destock application is around 20 minuts.
Maybe the example is not well suited for a product with multiple resolutions. For a MERIS RR product with a size of 1121x14993 it just takes a few seconds.
With S2 I notice that it even starts slower and then further slows down. Probably the reader is not as fast as the one for Envisat. This is very likely caused by the data format.
After I made some changes to the script I can process almost one line per second.
When I resample the product before and store it in BEAM-DIMAP format the processing is as fast as for MERIS.
I’ve attached the updated script updated. snappy_s2_ndvi.py (2.0 KB)
I tried with the new version and the first 1024 lines was processed fast but after that it became slow again. Are there any possible to subset just band 4 and 8 whitout lossing resolution?, in order to test the script with a small scene.
Really thanks for the quick replay. It is really kind of you and I am appreciating it so much.
I have another question about subset. Is it possible just subset band B4 and B8? Both bands present a 10m resolution so a resampling method is not necessary, is not?
Anyone got any solutions on this issue with slow computing? I’m trying to calculate a normalized index and after 1 minute it just stops but not on all Sentinel 3 files, just some of them. I set up the memory in the config files too. Anyone got better ideas?