Indeed, a column store for arrays is usually quite ;-) inefficient.
Let me point you to the rasdaman array DBMS which plugs into PostgreSQL
and offers an optimized array query language on top. See www.rasdaman.org.
-Peter
Paul Ramsey wrote:
Oh, actually one-row-per-point is a bad idea, bec
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 wel
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 doub
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.
___
