[GRASS-user] Large vector files

Michael Perdue michael_perdue at yahoo.ca
Tue Oct 10 02:48:39 EDT 2006

Really? Does this apply to the input ascii data set, the output  
raster or both? The sample data set I've been working with is roughly  
92 million points and is 2.5GB in size. I don't recall r.in.xyz  
complaining when I feed it the file. The output raster was  
considerably smaller though (around 10 million cells).


On 8-Oct-06, at 6:26 AM, 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.
> -- 
> Glynn Clements <glynn at gclements.plus.com>
> _______________________________________________
> grassuser mailing list
> grassuser at grass.itc.it
> http://grass.itc.it/mailman/listinfo/grassuser

Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 

More information about the grass-user mailing list