Hi Andreas,
On Wed, Mar 24, 2021 at 9:23 PM Andreas Yankopolus wrote:
...
> Trying the tutorial in
> https://grass.osgeo.org/grass78/manuals/addons/r.in.pdal.html, I get the
> following error message when trying to read a .laz file with r.in.pdal:
Please note that the tutorial you cite
Maris,
> The r.in.pdal from the PR is totally different beast than one located in
> add-ons.
Thanks for your help. I’ve given up on this route, though. The tutorials seem
woefully out of date. I’ve managed to get a mist of black dots to appear on the
screen after a lot of trial and (mostly)
The r.in.pdal from the PR is totally different beast than one located
in add-ons.
It is quite common for LAS files to lack coordinate system
information. In a such case it is your responsibility to handle its
correctness. If your location is in the same coordinate system as LAS
files, just use -o
Maris,
> r.in.pdal still lacks metadata printing functionality and thus has not been
> merged into the main branch yet. You can get the code from this PR:
> https://github.com/OSGeo/grass/pull/1200
I switched to that PR with "git-pr 1200”, and the resulting binary has
r.in.pdal.
Trying the
Hello Andreas,
r.in.pdal still lacks metadata printing functionality and thus has not
been merged into the main branch yet. You can get the code from this
PR: https://github.com/OSGeo/grass/pull/1200
Let us know if there are any problems with r.in.pdal.
Best,
Māris.
2021-03-24 0:11 GMT+02:00,
I’m starting to work with LiDAR point cloud (LPC) data with the goal of
creating multi-band rasters that list terrain height, surface height, and
surface type. GRASS looks like the ticket for visualizing LPC data and
processing it into GeoTIFFs using Python scripting.
I’m on Ubuntu 20.04, and