Oh, actually one-row-per-point is a bad idea, because the size of lidar sets mitigates against that. Putting them into multipoint collections of 50 or 100 points is better. But that implies preprocessing things a bit to find good patches. In generally, there's a lot of tooling needed to do this well, I fear.
P On Thu, Jul 8, 2010 at 6:27 AM, Paul Ramsey <[email protected]> wrote: > There is no recommended way right now. It's a core development > activity I'd love to have funded... :) > > http://opengeo.org/products/coredevelopment/postgis/pointclouds/ > > In the meanwhile a approach might be to put the x/y/z into a postgis > geometry and stuff the rest of the data into an array of doubles in > another column. Your app would need to know which array element was > which kind of data, but you'd still have it all available. > > P. > > On Thu, Jul 8, 2010 at 2:53 AM, Biddy <[email protected]> wrote: >> Hi everyone, >> >> is there a recommended way of storing lidar data in postgis? >> >> In particular, I am interested in not just storing long, lat, alt but also >> keeping all the raw data (for example range, target number, reflectance, >> etc.) >> >> Regards, >> B. >> >> >> _______________________________________________ >> postgis-users mailing list >> [email protected] >> http://postgis.refractions.net/mailman/listinfo/postgis-users >> > _______________________________________________ postgis-users mailing list [email protected] http://postgis.refractions.net/mailman/listinfo/postgis-users
