<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Ok, 88 million points and running 64bit Linux. Since 3D points<br>
and no additional data columns columns I think it will default<br>
to not creating a database, so you don't have to worry about the<br>
-t flag or the memory needed for that, just the finite amount of<br>
RAM per point for topology. Maybe 64GB RAM will be enough for 88M,<br>
perhaps more, but it will need a lot to build topology for all those<br>
points.<br></blockquote><div><br></div><div>Ok<br></div><div> </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
May I ask what process you'd like to do with the data?</blockquote><div><br></div><div>I am processing point clouds from photogrammetry (here an engraved megalith, 6.5 m²) and LIDAR data in forested areas (archaeology at another scale).<br>
</div><div>For this i am working on a script that perform all classical processes (for achaeologist, including qualimetry, animations, PDF maps etc.) for all *.csv file in a given directory. It's a work in progress, shellscript, but i hope to do this in C and/ or in a contribution to grass if it worth it.<br>
</div><div> </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> Perhaps<br>
r.in.xyz + r.to.vect helps reduce the number of points to something<br>
more manageable.</blockquote><div><br></div><div>I will try this.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> The v.in.ascii '-r' flag can be helpful for importing<br>
only those points within the current computational region of interest,<br>
and if importing without building topology (the '-b' flag you tried<br>
before) many of the LiDAR modules and v.surf.rst have been modified<br>
to work without needing it.<br></blockquote><div><br></div><div>ok, i will looke at that too.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
If it is some other vector module maybe we can modify it to load data<br>
without topology too.<br></blockquote><div><br></div><div>i use also v.neighbors<br></div><div> </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Is it sparse x,y data or gridded?<br></blockquote><div> </div><div>It's sparse data.<br>
</div><br></div><div class="gmail_quote">Thanks à lot !!!<br><br></div><div class="gmail_quote">yann<br></div><br><br clear="all"><br>
</div></div>