Hi Roberto,
The reason should be printed to the console, I have just checked the code and I
can't see any which I'd missed. It will be the line before it prints the
message saying the files are incompatible.
OK, so I think I know what the error you are getting might be. SPDMerge outputs
a UPD file (i.e., an SPD file without the spatial index; unsorted pulse data)
so you will need to use the spdtranslate command to build an appropriate index
before you can run the other commands.
The indexes are not kept as I assume the files are not on exactly the same grid
as spdtranslate just uses the TL pulse in the dataset for the TL of the file,
unless someone uses the options provided in spdtranslate to define the TL
themselves. I have been meaning to write a command which would do this but I
haven't got around to it yet, it would be useful for merging SPDLib generated
tiles for example.
Best wishes,
Pete
****************************************************
* Dr Pete Bunting
* Senior Lecturer in Remote Sensing
* Institute of Geography and Earth Sciences
* Aberystwyth University
* Aberystwyth
* Ceredigion
* SY23 3DB
* UK
*
* Ph: +44 (0) 1970 622615
* Mob: +44 (0) 7917 842743
* NZ Ph: +64 (0) 4 280 7430
* Email: [email protected]
****************************************************
On 22 Aug 2013, at 16:57, Roberto Antolín <[email protected]> wrote:
> Hi Pete and all,
>
> On Thu, Aug 22, 2013 at 03:05:33PM +0100, Pete Bunting wrote:
>
>> Hi Roberto,
>>
>> With the merging there is a switch --ignorechecks which I use when I know
>> files are 'the same'. These checks try to make sure that everything in the
>> headers of the SPD files are the same and very small rounding errors can
>> disrupt this, which is why I added the ignore switch.
>
> Yes, I was awared of this switch but I prefered to understand why the error
> arises. Would it be possible to know the reason?
>
>> As an aside, there is a python script (spdbuildmergecmd.py) which you can use
>> automatically build you spdmerge commands.
>
> I saw this python script browsing the source but I did not really understand
> it
> that much, not even with the manual. I will give it another chance.
>
>> With the other errors I don't know, I would need to have a look at the files
>> and try to reproduce the error and debug the code. Following the merge what
>> bin size are you translating your files to?
>
> Good point!
>
> I used the bin size by default to translate from las to spd, in fact
> spdinfo says the files Bin Sizes are:
> Gridding [xSize,ySize] Bin Size: [501,501] 1
>
> Surprisingly, the header of the merged file is:
> Gridding [xSize,ySize] Bin Size: [0,0] 0
>
> I guess that is why spdinterp and spdpmfgrd do not work properly. The question
> now is to know why Bin Size is 0.
>
>> If you are processing large datasets you might find it quicker and easier to
>> use the tiling commands which splits the scene into tiles (with an optional
>> overlap between tiles) which you can then process independently
>
> Yes, I know that. As a matter of fact, my las files are actually tiles. I was
> just... testing ;)
>
> Cheers,
> Roberto
>
> --
> Roberto Antolín
> http://twitter.com/#!/tolanss
------------------------------------------------------------------------------
Introducing Performance Central, a new site from SourceForge and
AppDynamics. Performance Central is your source for news, insights,
analysis and resources for efficient Application Performance Management.
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
_______________________________________________
spdlib-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/spdlib-develop
