[GRASS-dev] Re: [STATSGRASS] r.in.xyz: New module for loading and binning massive x, y, z datasets (LIDAR, Swath bathymetry)

Patton, Eric epatton at nrcan.gc.ca
Mon Jun 12 12:11:23 EDT 2006


Hamish, 

Thanks for this script! It's MUCH better than the hack I was using (i.e.,
xyz --> GMT's xyz2grd --> r.in.bin). I can confirm the program worked
perfectly with a 980MB swath multibeam bathymetry dataset.

--
Eric Patton 
epatton at nrcan.gc.ca

-----Original Message-----
From: grass-dev-bounces at grass.itc.it [mailto:grass-dev-bounces at grass.itc.it]

Sent: Monday, June 12, 2006 12:48 PM
To: Hamish
Cc: grassuser at grass.itc.it; statsgrass at grass.itc.it; grass-dev at grass.itc.it
Subject: [GRASS-dev] Re: [STATSGRASS] r.in.xyz: New module for loading and
binning massive x, y, z datasets (LIDAR, Swath bathymetry)

Hamish,

I think this is a wonderful and much needed addition. Thank you very much!

Regards,
Tom


Hamish wrote:
> Hi,
>
> In blatant violation of any sort of feature freeze for the next 
> release of GRASS GIS I have added a new (long missing) module to GRASS
6.1:
>   r.in.xyz
>
> This is a replacement for s.in.ascii+ s.cellstats+ s.to.rast in GRASS 5.
>
>
> The r.in.xyz module will load and bin ungridded x,y,z ASCII data into 
> a new raster map. The user may choose from a variety of statistical 
> methods in creating the new raster.
>
> r.in.xyz is designed for processing massive point cloud datasets, for 
> example raw LIDAR or sidescan sonar swath data.
>
> And it's fast. Very fast.
>
>
> idea:
>   http://grass.itc.it/pipermail/grass-dev/2006-May/023376.html
>
> help page:
>   http://grass.ibiblio.org/grass61/manuals/html61_user/r.in.xyz.html
>
> screenshots:
>   http://hamish.bowman.googlepages.com/grassfiles#xyz
>
>
>
> The r.to.vect module has been given a "-b" flag to skip building 
> vector topology (same as v.in.ascii) and the v.surf.rst interpolation 
> module has been modified to not require topology from input points. 
> This gets around the approx 3 million point memory limit of the vector 
> engine due to topology overhead. [i.e. you can fill holes with 
> regularized splines]
>
>
> question for stats experts: Should it be using population or sample 
> variance? n is generally low so it makes a difference here. In 
> r.univar it is usually so large not to matter (there we use population 
> variance for vague reasons).
>
>
> Thanks to Helena Mitasova for testing and helping me work out the last 
> few bugs. I would be interested to hear how things go with Large input 
> files (LFS, bigger than 2gb).
>
>
> enjoy,
> Hamish
>
> _______________________________________________
> statsgrass mailing list
> statsgrass at grass.itc.it
> http://grass.itc.it/mailman/listinfo/statsgrass
>   


--
Thomas E Adams
National Weather Service
Ohio River Forecast Center
1901 South State Route 134
Wilmington, OH 45177

EMAIL:	thomas.adams at noaa.gov

VOICE:	937-383-0528
FAX:	937-383-0033

_______________________________________________
grass-dev mailing list
grass-dev at grass.itc.it
http://grass.itc.it/mailman/listinfo/grass-dev




More information about the grass-dev mailing list