[pgpointcloud] Full waveform data

[Adam Steer]

Thanks Rémi, Kevin - this question is really interesting to us also.

Rémi’s second suggestion was what sprung immediately mind for me - the first requires more knowledge than I have on how to index things well.

Regards

Adam


> On 11 Jan 2017, at 8:44 am, Kevin Beam <kevin.beam at nsidc.org> wrote:
> 
> Thank you Rémi-C. You described those solutions very well. At this point
> we are only trying to determine the feasibility of full waveform data
> using pgpointcloud and won't be implementing it yet. But if we do, I
> think the two solutions you've outlined below are where we will start.
> 
> As an aside, we *very much* appreciated your paper with Perret and
> Paparoditis earlier this year in ISPRS Journal of Photogrammetry and
> Remote Sensing. It was very helpful to us in our prototype.
> 
> Cheers,
> Kevin
> 
> On 01/10/2017 06:44 AM, Rémi Cura wrote:
>> - (super simple) use pgpointcloud as-is to store bounds of samples
>> position/time per waveform . The samples are stored elsewhere (blob, or
>> simply array of char), and the waveform geometric information (geometry of
>> the laser ray) is stored in base.
>> This allows you to use pgpointcloud with fast index to find the relevant
>> samples, then when you want to use the ful waveform, you get the
>> appropriate data and use your custom solutions.
>> 
>> - (need some work) add a new type of point dimension to pgpointcloud to
>> directly store the full waveframe samples in pgpointcloud, (the waveform
>> samples are all stored in one dimension of the point), and some utilitary
>> functions may be able to generate the samples as 3D points (with each
>> sample being a point with intensity).
> 
> -- 
> Kevin Beam
> kbeam at nsidc.org
> Software Engineer
> National Snow and Ice Data Center (NSIDC)
> University of Colorado Boulder
> 
> _______________________________________________
> pgpointcloud mailing list
> pgpointcloud at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/pgpointcloud