[GRASS-user] Large vector files

Brad Douglas rez at touchofmadness.com
Sun Oct 8 14:45:53 EDT 2006

On Sun, 2006-10-08 at 13:26 +0100, Glynn Clements wrote:
> Hamish wrote:
> > > I would _highly_recommend trying r.in.xyz if you have not already done
> > > so. Especially with LIDAR and other forms of remotely-sensed data.
> > > I've had good success with it. Note there is also a parameter in
> > > r.in.xyz to control how much of the input map to keep in memory,
> > > allowing you to run the data import in multiple passes.  
> > 
> > note the r.in.xyz memory parameter is to help with massive RASTER
> > regions, nothing directly to do with the size of the input file.
> > The input file is not kept in memory! The output raster grid is.
> > 
> > I am always looking for feedback on how r.in.xyz goes with massive input
> > data. (>2gb? >4gb?)
> r.in.xyz doesn't use LFS, so it will be limited to 2Gb on 32-bit
> systems (any system where "long" is 32 bits). As it uses ANSI stdio
> functions (including ftell/fseek), extending it to support large files
> would be non-trivial.

Attached is a quick patch to enable LFS.  It's "poorly" implemented with
fseeko/ftello, so I'm not sure if I should commit it.

Brad Douglas <rez touchofmadness com>                      KB8UYR
Address: 37.493,-121.924 / WGS84    National Map Corps #TNMC-3785
-------------- next part --------------
A non-text attachment was scrubbed...
Name: r.in.xyz.pat
Type: text/x-patch
Size: 2375 bytes
Desc: not available
Url : http://lists.osgeo.org/pipermail/grass-user/attachments/20061008/a982a013/r.in.xyz.bin

More information about the grass-user mailing list