Hi,
I have been checking all data and my diary and I realised that all problems
started since I create the boundary shapefile of my tiles some weeks ago.
'I looked into the tiles folders to see if there was something unexpected
and I I found 3 files in each of the tiles folder, for which I can exp
Hi Dan,
Yes I have the spdlib 3.2.0. installed through conda, I created an
environment for spdlib with all needed packages.
I created the tiles in January with the previous version of spdlib. Also
back in January I run all commands from merging to metrics without trouble.
I can visualise these pr
Hi Ramiro,
It sounds like the problems it is quite specific to your files.
If you run spdinfo on all your input files and outputs from each stage of
processing or open them in SPDPointsViewer are the all OK?
Are any warnings being printed at any stage of the processing? If so can you
post them
Hi Dan,
thanks for you answer. I think I will go for gdal_edit.py
It is pretty simple and for 0.0005960464 m difference I do not think I
should worry much.
My biggest problem is that I cannot run any process on the tiles I created
time ago.
Apparently when I run spdtranslate on the merged t
Hi Ramiro,
You could edit the header values using the GDAL Python bindings so the pixel
sizes are exactly 0.4 m or you can use another method to stack the files which
doesn't require the pixel sizes to be exactly the same.
I would use gdalbuildvrt (http://www.gdal.org/gdalbuildvrt.html) to crea
Hi,
I have processed some data with spdlib setting an output resolution of 0.4
m (I set a bin size of 0.4) and kea format.
Now I am trying to stack the output data to imagery with 0.4 resolution
using the rsgislib.
The rsgislib raises an error because resolution are not the same.
I have checked
