<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.7600.16588"></HEAD>
<BODY bgColor=#ffffff text=#000000>
<DIV dir=ltr align=left><SPAN class=996301016-08072010><FONT color=#0000ff
size=2 face=Arial>Okay since everyone is providing their suggestions, let me
provide my less than educated suggestion based on my fuzzy assumption of how
Lidar is structured.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=996301016-08072010><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=996301016-08072010><FONT color=#0000ff
size=2 face=Arial>Why don't you just use the new WKT Raster (PostGIS raster
storage)? It allows you to store multiple bands per pixel. I think
you might even be able to use GDAL to load the Lidar data right in ot the
PostGIS raster storage format given this bug fix.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=996301016-08072010><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=996301016-08072010><FONT color=#0000ff
size=2 face=Arial><A
href="http://trac.osgeo.org/gdal/ticket/3523">http://trac.osgeo.org/gdal/ticket/3523</A></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=996301016-08072010><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=996301016-08072010><FONT color=#0000ff
size=2 face=Arial>So I'm imaging your z, range, target number, reflectance
you would store as separate raster bands.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=996301016-08072010><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=996301016-08072010><FONT color=#0000ff
size=2 face=Arial>Pierre and Jorge can correct me, but I don't think there is a
limit on the number of raster bands you can store per raster
tile</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=996301016-08072010></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=996301016-08072010></SPAN><SPAN
class=996301016-08072010><FONT color=#0000ff size=2 face=Arial><A
href="http://www.postgis.org/documentation/manual-svn/RT_reference.html">http://www.postgis.org/documentation/manual-svn/RT_reference.html</A></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=996301016-08072010><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=996301016-08072010><FONT color=#0000ff
size=2 face=Arial>With that you can do spatial intersects queries to pull out
the different band values with </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=996301016-08072010><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=996301016-08072010><FONT color=#0000ff
size=2 face=Arial><A
href="http://www.postgis.org/documentation/manual-svn/RT_ST_Intersection.html">http://www.postgis.org/documentation/manual-svn/RT_ST_Intersection.html</A></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=996301016-08072010><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=996301016-08072010><FONT color=#0000ff
size=2 face=Arial>or </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=996301016-08072010><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV><FONT color=#0000ff size=2 face=Arial></FONT><FONT color=#0000ff size=2
face=Arial><A
href="http://www.postgis.org/documentation/manual-svn/RT_ST_Value.html">http://www.postgis.org/documentation/manual-svn/RT_ST_Value.html</A></FONT></DIV>
<DIV><FONT color=#0000ff size=2 face=Arial></FONT> </DIV>
<DIV><SPAN class=996301016-08072010><FONT color=#0000ff size=2 face=Arial>The
meta data function would be useful for letting you know how many bands you have
etc.</FONT></SPAN></DIV>
<DIV><SPAN class=996301016-08072010><FONT color=#0000ff size=2
face=Arial></FONT></SPAN> </DIV>
<DIV><SPAN class=996301016-08072010><FONT color=#0000ff size=2 face=Arial><A
href="http://www.postgis.org/documentation/manual-svn/RT_ST_MetaData.html">http://www.postgis.org/documentation/manual-svn/RT_ST_MetaData.html</A></FONT></SPAN></DIV>
<DIV><SPAN class=996301016-08072010><FONT color=#0000ff size=2
face=Arial></FONT></SPAN> </DIV>
<DIV><SPAN class=996301016-08072010><FONT color=#0000ff size=2 face=Arial>Hope
that helps,</FONT></SPAN></DIV>
<DIV><SPAN class=996301016-08072010><FONT color=#0000ff size=2
face=Arial>Regina</FONT></SPAN></DIV>
<DIV><BR></DIV>
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B>
postgis-users-bounces@postgis.refractions.net
[mailto:postgis-users-bounces@postgis.refractions.net] <B>On Behalf Of </B>Peter
Baumann<BR><B>Sent:</B> Thursday, July 08, 2010 9:32 AM<BR><B>To:</B> PostGIS
Users Discussion<BR><B>Subject:</B> Re: [postgis-users] lidar: what is the
recommended wayof storing/indexing<BR></FONT><BR></DIV>
<DIV></DIV>Indeed, a column store for arrays is usually quite ;-)
inefficient.<BR>Let me point you to the rasdaman array DBMS which plugs into
PostgreSQL and offers an optimized array query language on top. See <A
class=moz-txt-link-abbreviated
href="http://www.rasdaman.org">www.rasdaman.org</A>.<BR><BR>-Peter<BR><BR><BR><BR><BR>Paul
Ramsey wrote:
<BLOCKQUOTE
cite=mid:AANLkTilgFs1vR5ZCkKy3ECu9pDE9tokfqX7Aks9YQadV@mail.gmail.com
type="cite"><PRE wrap="">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 <A class=moz-txt-link-rfc2396E href="mailto:pramsey@opengeo.org"><pramsey@opengeo.org></A> wrote:
</PRE>
<BLOCKQUOTE type="cite"><PRE wrap="">There is no recommended way right now. It's a core development
activity I'd love to have funded... :)
<A class=moz-txt-link-freetext href="http://opengeo.org/products/coredevelopment/postgis/pointclouds/">http://opengeo.org/products/coredevelopment/postgis/pointclouds/</A>
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 <A class=moz-txt-link-rfc2396E href="mailto:newskatze@riomhphost.net"><newskatze@riomhphost.net></A> wrote:
</PRE>
<BLOCKQUOTE type="cite"><PRE wrap="">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
<A class=moz-txt-link-abbreviated href="mailto:postgis-users@postgis.refractions.net">postgis-users@postgis.refractions.net</A>
<A class=moz-txt-link-freetext href="http://postgis.refractions.net/mailman/listinfo/postgis-users">http://postgis.refractions.net/mailman/listinfo/postgis-users</A>
</PRE></BLOCKQUOTE></BLOCKQUOTE><PRE wrap=""><!---->_______________________________________________
postgis-users mailing list
<A class=moz-txt-link-abbreviated href="mailto:postgis-users@postgis.refractions.net">postgis-users@postgis.refractions.net</A>
<A class=moz-txt-link-freetext href="http://postgis.refractions.net/mailman/listinfo/postgis-users">http://postgis.refractions.net/mailman/listinfo/postgis-users</A>
</PRE></BLOCKQUOTE><BR><PRE class=moz-signature cols="80">--
Dr. Peter Baumann
- Professor of Computer Science, Jacobs University Bremen
<A class=moz-txt-link-abbreviated href="http://www.faculty.jacobs-university.de/pbaumann">www.faculty.jacobs-university.de/pbaumann</A>
mail: <A class=moz-txt-link-abbreviated href="mailto:p.baumann@jacobs-university.de">p.baumann@jacobs-university.de</A>
tel: +49-421-200-3178, fax: +49-421-200-493178
- Executive Director, rasdaman GmbH Bremen (HRB 147737)
<A class=moz-txt-link-abbreviated href="http://www.rasdaman.com">www.rasdaman.com</A>, mail: <A class=moz-txt-link-abbreviated href="mailto:baumann@rasdaman.com">baumann@rasdaman.com</A>
tel: 0800-rasdaman, fax: 0800-rasdafax, mobile: +49-173-5837882
"Si forte in alienas manus oberraverit hec peregrina epistola incertis ventis dimissa, sed Deo commendata, precamur ut ei reddatur cui soli destinata, nec preripiat quisquam non sibi parata." (mail disclaimer, AD 10xx)
</PRE></BODY></HTML>