[pgpointcloud] Full waveform data

[Rémi Cura]

Hey Kevin,
So far pgpointcloud can store fixed-size point type
(aka, the point type amount of requiered bit is fully fixed).
The issue is that fullwaveform may have a non fixed number of samples per
waveform (at least for our hardware, according to my colleague Dr. Clément
Mallet)

I think it's possible to use pgpointcloud with full waveform.
I see 2 solutions



 - (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).


Cheers,
Rémi-C

2017-01-06 18:56 GMT+01:00 Kevin Beam <kevin.beam at nsidc.org>:

> Has there been any discussion about, or has anyone tried, using
> pgpointcloud with full waveform data?
>
> We recently successfully prototyped using pgpointcloud with IceBridge
> ATM L1B data. We've wondered whether it would be possible to use or
> extend pgpointcloud with, for example, IceBridge LVIS L1B full waveform
> data (http://nsidc.org/data/docs/daac/icebridge/ilvis1b/v1/index.html
> and http://nsidc.org/data/docs/daac/icebridge/ilvis1b/). That data has
> 120 transmit waveform samples and 528 receive waveform samples.
>
> The main use case we have at this point is spatial and temporal
> subsetting of this data. There are some other methods we may pursue if
> pgpointcloud  is not an option.
>
> I wonder if it could be as simple as storing the point data in
> patch/point tables and augmenting the results with the waveform data
> after the spatial/temporal query (from waveform data in other tables).
>
> Kevin
>
> --
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pgpointcloud/attachments/20170110/6c74bab9/attachment.html>