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 explain
its origin : Rows21Cols11.prj, Cols11/Rows21Cols11.dbf, Rows21Cols11.cpg.
I copied some tiles to a new folder and there I removed these 3 files from
the tile folder and now everything runs.
So, that seems to be source of my troubles. I guess the files where created
when running the spdtiling for the boundary file.
I am running now the entire script on a file and so far doesnt not give me
any trouble.
Thank you very much for you help.
Ramiro
2015-03-01 17:33 GMT+01:00 Ramiro Silveyra González <[email protected]>:
> 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 previous spd files I created. Also inspect them with
> spdinfo.
>
> Now, on the same tiles (same files) I can only run spdmerge to merge the
> files of a single files into one.
> The next step spdtranslate returns this warning.
>
> *Error: H5Dread failed*
>
> For a tile and its files I can read the info with spdinfo. Below you find
> the information of one of the files of tile 25_11, and the merged tile.
>
> I guess I could go back to the beginning, and create all tiles again. If
> my tiles are somehow corrupted or damage, the new tiles should not give me
> the error.
> I will try that and let you know if works.
>
> Thank you,
>
> Ramiro
>
> *--one file of the tile*
> File Path: ./Tiles/mp00260_row25col11.spd
> File Type:
> File Format Version: 2.1
> Point Version: 2
> Pulse Version: 2
> Generating Software: SPDLIB
> File Signature: SPDFILE
> Spatial Reference: PROJCS["DHDN / Gauss-Kruger zone
> 4",GEOGCS["DHDN",DATUM["D_Deutsches_Hauptdreiecksnetz",SPHEROID["Bessel_1841",6377397.155,299.1528128]],PRIMEM["Greenwich",0],UNIT["Degree",0.017453292519943295]],PROJECTION["Transverse_Mercator"],PARAMETER["latitude_of_origin",0],PARAMETER["central_meridian",12],PARAMETER["scale_factor",1],PARAMETER["false_easting",4500000],PARAMETER["false_northing",0],UNIT["Meter",1]]
> Creation Time (YYYY:MM:DD HH:MM:SS): 2015:1:21:1:49:13
> Capture Time (YYYY:MM:DD HH:MM:SS): 0:0:0:0:0:0
> Index Type: No Index
> The file contains:
> Contains discrete returns
> Number of Points = 46165
> Number of Pulses = 25163
> BBOX [xmin, ymin, xmax, ymax]:
> [4595427.646,5438073.732,4596527.646,5439173.732]
> BBOX [Azimuth Min, Zenith Min, Azimuth Max, Zenith Max]: [0,0,0,0]
> Z : [0,871.195983887]
> Range: [0,0]
> Scanline: [0,0]
> Scanline Idx: [0,0]
> Gridding [xSize,ySize] Bin Size: [0,0] 0
> Wavelengths:
> 0
> Bandwidths:
> 0
> Pulse Repetition Freq: 0
> Beam Divergance: 0
> Sensor Height: 0
> Footprint: 0
> Max. Scan Angle: 0
> Waveform Bin Resolution: 32
> Temporal Waveform Bin Spacing: 0
> Sensor Speed: 0
> Sensor Scanrate: 0
> Pulse Density: 0
> Point Density: 0
> Pulse cross track spacing: 0
> Pulse along track spacing: 0
> Pulse angular spacing azimuth: 0
> Pulse angular spacing zenith: 0
> Sensor Aperture Size: 0
> Pulse Energy: 0
> Field of view: 0
> User Meta Data:
>
> *--merged tile*
> File Path: ./als_dr_opt3_row25col11_2014_DHDNGK4.spd
> File Type:
> File Format Version: 2.1
> Point Version: 2
> Pulse Version: 2
> Generating Software: SPDLIB
> File Signature: SPDFILE
> Spatial Reference: PROJCS["DHDN / Gauss-Kruger zone
> 4",GEOGCS["DHDN",DATUM["D_Deutsches_Hauptdreiecksnetz",SPHEROID["Bessel_1841",6377397.155,299.1528128]],PRIMEM["Greenwich",0],UNIT["Degree",0.017453292519943295]],PROJECTION["Transverse_Mercator"],PARAMETER["latitude_of_origin",0],PARAMETER["central_meridian",12],PARAMETER["scale_factor",1],PARAMETER["false_easting",4500000],PARAMETER["false_northing",0],UNIT["Meter",1]]
> Creation Time (YYYY:MM:DD HH:MM:SS): 2015:3:1:16:37:31
> Capture Time (YYYY:MM:DD HH:MM:SS): 0:0:0:0:0:0
> Index Type: No Index
> The file contains:
> Contains discrete returns
> Number of Points = 37034735
> Number of Pulses = 18553481
> BBOX [xmin, ymin, xmax, ymax]:
> [4595418.795,5438064.581,4596534.686,5439186.713]
> BBOX [Azimuth Min, Zenith Min, Azimuth Max, Zenith Max]: [0,0,0,0]
> Z : [0,1124.22998047]
> Range: [0,0]
> Scanline: [0,0]
> Scanline Idx: [0,0]
> Gridding [xSize,ySize] Bin Size: [0,0] 0
> Wavelengths:
> 0
> Bandwidths:
> 0
> Pulse Repetition Freq: 0
> Beam Divergance: 0
> Sensor Height: 0
> Footprint: 0
> Max. Scan Angle: 0
> Waveform Bin Resolution: 32
> Temporal Waveform Bin Spacing: 0
> Sensor Speed: 0
> Sensor Scanrate: 0
> Pulse Density: 0
> Point Density: 0
> Pulse cross track spacing: 0
> Pulse along track spacing: 0
> Pulse angular spacing azimuth: 0
> Pulse angular spacing zenith: 0
> Sensor Aperture Size: 0
> Pulse Energy: 0
> Field of view: 0
> User Meta Data:
>
> spdinfo - end
>
>
>
>
>
> 2015-03-01 12:55 GMT+01:00 Daniel Clewley <[email protected]>:
>
>> 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 as here.
>>
>> Are you running the latest version of SPDLib, if you've installed through
>> conda this is 3.2.0 (build 3).
>>
>> Thanks,
>>
>> Dan
>>
>> On 27 Feb 2015, at 17:17, Ramiro Silveyra González <[email protected]>
>> wrote:
>>
>> Hi Dan,
>>
>> thanks for you answer. I think I will go for gdal_edit.py
>> It is pretty simple and for 0.00000005960464 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 tiles something goes
>> wrong with header information of the spd file,
>> because the next command I am applying fails to read the spd file and
>> returns the following errors:
>>
>> Error: H5Dread failed
>> Error: The SPD major version header value was not provided.
>>
>> I cannot figure out what goes wrong. Script, files and spdlib version are
>> fine.
>> Whatever the problem is, happens when translating the merged file.
>>
>>
>> Thanks,
>>
>> Ramiro
>>
>> 2015-02-26 14:13 GMT+01:00 Daniel Clewley <[email protected]>:
>>
>>> 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
>>> create a virtual raster stack and then gdal_translate to convert to KEA.
>>>
>>> Hope this helps,
>>>
>>> Dan
>>>
>>> On 23 Feb 2015, at 22:30, Ramiro Silveyra González <[email protected]>
>>> wrote:
>>>
>>> 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 the resolution of spdlib processed data and instead of
>>> 0.4, it is
>>> *0.400000005960464.*
>>>
>>> Is there a way to keep the resolution to 0.4 with SPDlib?
>>>
>>> Thanks,
>>>
>>> Ramiro
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
>>> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
>>> with Interactivity, Sharing, Native Excel Exports, App Integration & more
>>> Get technology previously reserved for billion-dollar corporations, FREE
>>>
>>> http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
>>>
>>> _______________________________________________
>>> spdlib-develop mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/spdlib-develop
>>>
>>>
>>
>>
>
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
spdlib-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/spdlib-develop
