<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'><div dir='ltr'>
Hi All,<BR> Thanks again to Leo, Regina and Paul for your help and suggestions. I will pursue this snap-to-grid approach for my next test set.<BR>As you may have guessed the amount of points we are working with are sourced from LiDAR.<BR>Mobile terrestrial in our case with a very high resolution. <BR>Various posts by Paul and others make various suggestions re efficiently storing these data within the current PostGIS system bounds but<BR> I was wondering if the LiDAR mention in the 2.0 TODO list is suggesting it will be in 2.0 or is it still on the waiting to be funded list.<BR> <BR>We have been working seriously on a PostGIS/LiDAR framework but within the PostGIS 1.5 constraints<BR>Thus we have implemented a one row per point process but realise that this probably is not best practice.<BR>However we need all the metadata per point such as range, reflectance, amplitude etc.<BR>So we don't see how clustering the points for efficient storage and indexing can be handled in PostGIS 1.5, <BR>and still maintain a full description of each points metadata.<BR> <BR>On this issue we have recently responded to this bolg on PostGIS and LiDAR data loading<BR> <BR><a href="http://ariasprado.name/2011/02/06/lidar-bulk-data-load.html">http://ariasprado.name/2011/02/06/lidar-bulk-data-load.html</a><BR> <BR>So far this is a ground up approach where our bulk loading approach has greatly improved our ability to work with LiDAR.<BR>This is because it is now spatially available through the DB instead of the standard LAS file approaches.<BR>We can now query, using PostGIS, in a multitude of spatial ways to retrieve bespoke LiDAR data sets for various<BR> feature extraction requirements we are working on.<BR> <BR>So, basically, is there a best practice yet re PostGIS and LiDAR until a dedicated LiDAR datatype is introduced.<BR> <BR>Once again thank you for your responses.<BR> <BR>Paul<BR> </div></body>
</html>