<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:m =
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.7600.16588"><!--[if !mso]>
<STYLE>v\:* {
BEHAVIOR: url(#default#VML)
}
o\:* {
BEHAVIOR: url(#default#VML)
}
w\:* {
BEHAVIOR: url(#default#VML)
}
.shape {
BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@font-face {
font-family: Consolas;
}
@page WordSection1 {size: 612.0pt 792.0pt; margin: 70.85pt 70.85pt 70.85pt 70.85pt; }
P.MsoNormal {
MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman","serif"; COLOR: black; FONT-SIZE: 12pt
}
LI.MsoNormal {
MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman","serif"; COLOR: black; FONT-SIZE: 12pt
}
DIV.MsoNormal {
MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman","serif"; COLOR: black; FONT-SIZE: 12pt
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
PRE {
MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Courier New"; COLOR: black; FONT-SIZE: 10pt; mso-style-priority: 99; mso-style-link: "HTML Preformatted Char"
}
SPAN.HTMLPreformattedChar {
FONT-FAMILY: Consolas; COLOR: black; mso-style-priority: 99; mso-style-link: "HTML Preformatted"; mso-style-name: "HTML Preformatted Char"
}
SPAN.EmailStyle19 {
FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d; mso-style-type: personal-reply
}
.MsoChpDefault {
FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.WordSection1 {
page: WordSection1
}
</STYLE>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=EN-US link=blue bgColor=white vLink=purple>
<DIV dir=ltr align=left><SPAN class=400334823-08072010><FONT color=#0000ff
size=2 face=Arial>Thanks guys. I think I understand better now the
issue. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=400334823-08072010><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=400334823-08072010><FONT color=#0000ff
size=2 face=Arial>So in some cases the resolution
loss is acceptable but in most cases it is not
correct?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=400334823-08072010><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=400334823-08072010><FONT color=#0000ff
size=2 face=Arial>I'm just curious aside from pulling aerial etc. out of Lidar
what use case people would use the MG4 Lidar to raster driver
for</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=400334823-08072010><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=400334823-08072010><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt"><A
href="http://trac.osgeo.org/gdal/ticket/3523">http://trac.osgeo.org/gdal/ticket/3523</A></SPAN></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=400334823-08072010><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt"></SPAN></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=400334823-08072010><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt">Sorry
for the endless Lidar newbie questions.</SPAN></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=400334823-08072010><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=400334823-08072010><FONT color=#0000ff
size=2 face=Arial>Thanks,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=400334823-08072010><FONT color=#0000ff
size=2 face=Arial>Regina</FONT></SPAN></DIV><BR>
<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>Pierre Racine<BR><B>Sent:</B> Thursday, July 08, 2010 12:38 PM<BR><B>To:</B>
PostGIS Users Discussion<BR><B>Subject:</B> Re: [postgis-users] lidar: what is
therecommended wayof storing/indexing<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=WordSection1>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Regina,
<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">there
is no real limits on the number of bands but I tend to agree with Paul: you can
convert a lidar coverage to a grid but this is a lossy operation like converting
a vector coverage to raster. The amount of information you lose is dependent on
the resolution of the target raster and there is no perfect resolution (only 0
which is impossible).<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Pierre<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<DIV
style="BORDER-BOTTOM: medium none; BORDER-LEFT: blue 1.5pt solid; PADDING-BOTTOM: 0cm; PADDING-LEFT: 4pt; PADDING-RIGHT: 0cm; BORDER-TOP: medium none; BORDER-RIGHT: medium none; PADDING-TOP: 0cm">
<DIV>
<DIV
style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<P class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; COLOR: windowtext; FONT-SIZE: 10pt">From:</SPAN></B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; COLOR: windowtext; FONT-SIZE: 10pt">
postgis-users-bounces@postgis.refractions.net
[mailto:postgis-users-bounces@postgis.refractions.net] <B>On Behalf Of
</B>Paragon Corporation<BR><B>Sent:</B> 8 juillet 2010 12:23<BR><B>To:</B>
'PostGIS Users Discussion'<BR><B>Subject:</B> Re: [postgis-users] lidar: what is
the recommended wayof storing/indexing<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt">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.</SPAN><o:p></o:p></P>
<P class=MsoNormal> <o:p></o:p></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt">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.</SPAN><o:p></o:p></P>
<P class=MsoNormal> <o:p></o:p></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt"><A
href="http://trac.osgeo.org/gdal/ticket/3523">http://trac.osgeo.org/gdal/ticket/3523</A></SPAN><o:p></o:p></P>
<P class=MsoNormal> <o:p></o:p></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt">So I'm
imaging your z, range, target number, reflectance you would store as
separate raster bands.</SPAN><o:p></o:p></P>
<P class=MsoNormal> <o:p></o:p></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt">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</SPAN><o:p></o:p></P>
<P class=MsoNormal> <o:p></o:p></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt"><A
href="http://www.postgis.org/documentation/manual-svn/RT_reference.html">http://www.postgis.org/documentation/manual-svn/RT_reference.html</A></SPAN><o:p></o:p></P>
<P class=MsoNormal> <o:p></o:p></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt">With
that you can do spatial intersects queries to pull out the different band values
with </SPAN><o:p></o:p></P>
<P class=MsoNormal> <o:p></o:p></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt"><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></SPAN><o:p></o:p></P>
<P class=MsoNormal> <o:p></o:p></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt">or
</SPAN><o:p></o:p></P>
<P class=MsoNormal> <o:p></o:p></P>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt"><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></SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt">The meta
data function would be useful for letting you know how many bands you have
etc.</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt"><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></SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt">Hope
that helps,</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt">Regina</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><o:p> </o:p></P></DIV>
<DIV style="TEXT-ALIGN: center" class=MsoNormal align=center>
<HR align=center SIZE=2 width="100%">
</DIV>
<P style="MARGIN-BOTTOM: 12pt" class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">
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</SPAN><o:p></o:p></P>
<P class=MsoNormal>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
href="http://www.rasdaman.org">www.rasdaman.org</A>.<BR><BR>-Peter<BR><BR><BR><BR><BR>Paul
Ramsey wrote: <o:p></o:p></P><PRE>Oh, actually one-row-per-point is a bad idea, because the size of<o:p></o:p></PRE><PRE>lidar sets mitigates against that. Putting them into multipoint<o:p></o:p></PRE><PRE>collections of 50 or 100 points is better. But that implies<o:p></o:p></PRE><PRE>preprocessing things a bit to find good patches. In generally, there's<o:p></o:p></PRE><PRE>a lot of tooling needed to do this well, I fear.<o:p></o:p></PRE><PRE><o:p> </o:p></PRE><PRE>P<o:p></o:p></PRE><PRE><o:p> </o:p></PRE><PRE>On Thu, Jul 8, 2010 at 6:27 AM, Paul Ramsey <A href="mailto:pramsey@opengeo.org"><pramsey@opengeo.org></A> wrote:<o:p></o:p></PRE><PRE> <o:p></o:p></PRE>
<BLOCKQUOTE style="MARGIN-TOP: 5pt; MARGIN-BOTTOM: 5pt"><PRE>There is no recommended way right now. It's a core development<o:p></o:p></PRE><PRE>activity I'd love to have funded... :)<o:p></o:p></PRE><PRE><o:p> </o:p></PRE><PRE><A href="http://opengeo.org/products/coredevelopment/postgis/pointclouds/">http://opengeo.org/products/coredevelopment/postgis/pointclouds/</A><o:p></o:p></PRE><PRE><o:p> </o:p></PRE><PRE>In the meanwhile a approach might be to put the x/y/z into a postgis<o:p></o:p></PRE><PRE>geometry and stuff the rest of the data into an array of doubles in<o:p></o:p></PRE><PRE>another column. Your app would need to know which array element was<o:p></o:p></PRE><PRE>which kind of data, but you'd still have it all available.<o:p></o:p></PRE><PRE><o:p> </o:p></PRE><PRE>P.<o:p></o:p></PRE><PRE><o:p> </o:p></PRE><PRE>On Thu, Jul 8, 2010 at 2:53 AM, Biddy <A href="mailto:newskatze@riomhphost.net"><newskatze@riomhphost.net></A> wrote:<o:p></o:p></PRE><PRE> <o:p></o:p></PRE>
<BLOCKQUOTE style="MARGIN-TOP: 5pt; MARGIN-BOTTOM: 5pt"><PRE>Hi everyone,<o:p></o:p></PRE><PRE><o:p> </o:p></PRE><PRE>is there a recommended way of storing lidar data in postgis?<o:p></o:p></PRE><PRE><o:p> </o:p></PRE><PRE>In particular, I am interested in not just storing long, lat, alt but also<o:p></o:p></PRE><PRE>keeping all the raw data (for example range, target number, reflectance,<o:p></o:p></PRE><PRE>etc.)<o:p></o:p></PRE><PRE><o:p> </o:p></PRE><PRE>Regards,<o:p></o:p></PRE><PRE>B.<o:p></o:p></PRE><PRE><o:p> </o:p></PRE><PRE><o:p> </o:p></PRE><PRE>_______________________________________________<o:p></o:p></PRE><PRE>postgis-users mailing list<o:p></o:p></PRE><PRE><A href="mailto:postgis-users@postgis.refractions.net">postgis-users@postgis.refractions.net</A><o:p></o:p></PRE><PRE><A href="http://postgis.refractions.net/mailman/listinfo/postgis-users">http://postgis.refractions.net/mailman/listinfo/postgis-users</A><o:p></o:p></PRE><PRE><o:p> </o:p></PRE><PRE> <o:p></o:p></PRE></BLOCKQUOTE></BLOCKQUOTE><PRE>_______________________________________________<o:p></o:p></PRE><PRE>postgis-users mailing list<o:p></o:p></PRE><PRE><A href="mailto:postgis-users@postgis.refractions.net">postgis-users@postgis.refractions.net</A><o:p></o:p></PRE><PRE><A href="http://postgis.refractions.net/mailman/listinfo/postgis-users">http://postgis.refractions.net/mailman/listinfo/postgis-users</A><o:p></o:p></PRE><PRE> <o:p></o:p></PRE>
<P class=MsoNormal><BR><BR><o:p></o:p></P><PRE>-- <o:p></o:p></PRE><PRE>Dr. Peter Baumann<o:p></o:p></PRE><PRE> - Professor of Computer Science, Jacobs University Bremen<o:p></o:p></PRE><PRE> <A href="http://www.faculty.jacobs-university.de/pbaumann">www.faculty.jacobs-university.de/pbaumann</A><o:p></o:p></PRE><PRE> mail: <A href="mailto:p.baumann@jacobs-university.de">p.baumann@jacobs-university.de</A><o:p></o:p></PRE><PRE> tel: +49-421-200-3178, fax: +49-421-200-493178<o:p></o:p></PRE><PRE> - Executive Director, rasdaman GmbH Bremen (HRB 147737)<o:p></o:p></PRE><PRE> <A href="http://www.rasdaman.com">www.rasdaman.com</A>, mail: <A href="mailto:baumann@rasdaman.com">baumann@rasdaman.com</A><o:p></o:p></PRE><PRE> tel: 0800-rasdaman, fax: 0800-rasdafax, mobile: +49-173-5837882<o:p></o:p></PRE><PRE>"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)<o:p></o:p></PRE><PRE><o:p> </o:p></PRE><PRE><o:p> </o:p></PRE></DIV></DIV></BODY></HTML>