Hi Mattias,
Yes, that might be an option for some files, I haven't tried it though. I will
add it to the list of things to do as would probably be a useful addition to
spdlib.
In most cases I think the points are probably just noise removed by the
operator but this results in the point numbering being incorrect. However, if
that is the case then the SPDLib behaviour of warning the user and building a
pulse from the points available is probably the correct behaviour?
Cheers, Pete
On 14 Aug 2013, at 14:04, Mattias Nyström <[email protected]> wrote:
> Hi Pete,
>
> If I have a LAS-file with messed up order, wouldn’t it be possible to sort
> the LAS-file by GPS-time and then do the pulse-rebuild?
>
> Cheers,
> Mattias
>
> From: Pete Bunting [mailto:[email protected]]
> Sent: den 14 augusti 2013 13:09
> To: Roberto Antolín
> Cc: [email protected]
> Subject: Re: [spdlib-develop] spdtranslate WARNING: Pulse was written as
> incompleted pulse
>
> Hi Roberto,
>
> This was a feature I added in May. It is about rebuilding pulses from the LAS
> file. The assumption is that a LAS file is in time order and/or at least that
> if a point states that it is point 1 or 3 then then next three will be 2 or 3
> and 3 of 3 etc. Basically, I ran into problems as I got delivered a file
> where this had been broken and when SPDLib was building pulses it was getting
> some crazy results as it just read point 1 of 3 and then read the next 3
> points and build a pulse rather than checking the numberings of the those
> pulses.
>
> Therefore, I introduce an extra 2 LAS readers. Where the LAS reader is
> specified the behaviour is largely the same as before but where it finds a
> pulse which doesn't make sense then it outputs the warning you are seeing but
> still writes the pulse to the output SPD file - fixing the pulse so it is
> consistent SPD Pulse in the process. LASNP does not try to build pulses and
> just stores each point within a separate pulse - which is an overhead but
> will always work however messed up a LAS file is. LASSTRICT will fail if one
> of these errors is encountered and print out some debug info about the error
> such as what is was expecting etc.
>
> Under normal circumstances you should just use the LAS reader and just keep
> an eye on how many warnings you are getting. If you are getting a significant
> number then it might be worth looking at the data in more detail to check for
> issues there is a command spdlastest which can help with that or change to
> the LASNP reader. I have tended to find I get a small number of these
> warnings on almost every file but I don't know why these seems to occur to
> regularly.
>
> I hope that helps explain the warnings you are seeing.
>
> Cheers, 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 14 Aug 2013, at 11:45, Roberto Antolín <[email protected]> wrote:
>
>
> Hi all,
> I would like to translate a bunch of LAS files into a SPD format, so I
> tried this command:
> spdtranslate --if LAS --of SPD -o outputFile.spd -i inputFile.las -x
> FIRST_RETURN --temppath /tmp/
>
> I use older versions of spdtranslate and I had no problem. Some weeks
> ago I downloaded spdlib form the bitbucket repos and now spdtranslate
> throws me this annoying warning:
>
> Start Pulse (Num Returns = 2): p.GetReturnNumber() = 1
> In Pulse (Num Returns = 1): pt.GetReturnNumber() = 1
> The return number was: 1
> The next return number should have been: 2
> WARNING: Pulse was written as incompleted pulse.
>
> Any hint on what this warning means and on how to get rid of it?
>
> Thanks,
> Roberto
>
> --
> Roberto
>
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> _______________________________________________
> spdlib-develop mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/spdlib-develop
>
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk_______________________________________________
> spdlib-develop mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/spdlib-develop
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
spdlib-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/spdlib-develop
