I write shell scripts to run modules for analyses, but have always used the
GUI to define locations and/or mapsets before importing data even with starting
grass with the -c option.
What I want to do now when importing project data is to have a script that
defines the location and mapset then imp
On Thu, 27 Apr 2023, Maris Nartiss wrote:
Peaking at the file list you provided, you are dealing with already
processed LiDAR data in raster (and shapefile) format. Thus r.in.gdal is
the way to go.
r.in.las (obsolete) and r.in.pdal (the new way to go) deal with raw
point clouds in LAS format. T
Peaking at the file list you provided, you are dealing with already
processed LiDAR data in raster (and shapefile) format. Thus r.in.gdal
is the way to go.
r.in.las (obsolete) and r.in.pdal (the new way to go) deal with raw
point clouds in LAS format. They perform point binning according to
chosen
On Thu, 27 Apr 2023, Rich Shepard wrote:
There are raster LiDAR modules (r.in.gdal, r.in.lidar, r.in.pdal) and the
latter two work with .las files, so I assume that my data use r.in.gdal.
It's been a long time since I've build LiDAR maps and I ask for the proper
command lines to 1) set the locat
There are raster LiDAR modules (r.in.gdal, r.in.lidar, r.in.pdal) and the
latter two work with .las files, so I assume that my data use r.in.gdal.
It's been a long time since I've build LiDAR maps and I ask for the proper
command lines to 1) set the location for import and 2) import the data. An
e
On Thu, 27 Apr 2023, Maris Nartiss wrote:
Do you mean `pdal info file.las`?
Maris,
That's helpful. Many thanks.
Regards,
Rich
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user
On Thu, 27 Apr 2023, Vincent Bain wrote:
https://github.com/LAStools/LAStools
Hope this helps !
Vincent,
Thank you.
Regards,
Rich
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user
