Re: [GRASS-user] Loading LPC data in GRASS

[Markus Neteler]

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 belongs to the GRASS GIS
*addon* r.in.pdal which is a Python script.
You can install it with

g.extension r.in.pdal

and it does not require any recompilation of GRASS GIS itself.

(and yes, it is less fancy and slower than the upcoming C
implementation by Maris which you downloaded via PR).


> ERROR: The input dataset has undefined projection

This is a data problem but can be handled.

> I have pdal installed locally and am not using a Docker container for it. 
> What should I be doing differently to load LPC data?

The local PDAL installation is fine for the r.in.pdal *addon*.

HTH,

Markus

-- 
Markus Neteler, PhD
https://www.mundialis.de - free data with free software
https://grass.osgeo.org
https://courses.neteler.org/blog
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Loading LPC data in GRASS

[Andreas Yankopolus]

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) error, but that’s it.

Cheers,

Andreas



___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Loading LPC data in GRASS

[Maris Nartiss]

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 flag to ignore this error. If coordinate system of
your location and LAS files does not match, specify it with input_srs
parameter.

Good luck,
Māris.


2021-03-24 22:23 GMT+02:00, Andreas Yankopolus :
> 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 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:
>
>   ERROR: The input dataset has undefined projection
>
> I have pdal installed locally and am not using a Docker container for it.
> What should I be doing differently to load LPC data?
>
> Thanks,
>
> Andreas
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Loading LPC data in GRASS

[Andreas Yankopolus]

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 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:

ERROR: The input dataset has undefined projection

I have pdal installed locally and am not using a Docker container for it. What 
should I be doing differently to load LPC data?

Thanks,

Andreas___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Loading LPC data in GRASS

[Maris Nartiss]

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, Andreas Yankopolus :
> 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 it appears that LPC support requires compiling your
> own binary, which I did from the GitHub repo following these instructions:
>
> https://grasswiki.osgeo.org/wiki/Compile_and_Install_Ubuntu
> 
>
> The resulting 7.9.dev binary has v.in.pdal but not r.in.pdal. Is there a way
> to get the latter working? All the tutorials I’m finding refer to
> r.in.lidar, which appears similar to r.in.pdal but relies on deprecated
> liblas instead of pdal.
>
> Looks like d.vect will get me from a vector layer to a raster layer but
> haven’t figured it out yet. Should I import using v.in.pdal then convert to
> raster with d.vect?
>
> Thanks,
>
> Andreas
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] Loading LPC data in GRASS

[Andreas Yankopolus]

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 it appears that LPC support requires compiling your 
own binary, which I did from the GitHub repo following these instructions:

https://grasswiki.osgeo.org/wiki/Compile_and_Install_Ubuntu 


The resulting 7.9.dev binary has v.in.pdal but not r.in.pdal. Is there a way to 
get the latter working? All the tutorials I’m finding refer to r.in.lidar, 
which appears similar to r.in.pdal but relies on deprecated liblas instead of 
pdal.

Looks like d.vect will get me from a vector layer to a raster layer but haven’t 
figured it out yet. Should I import using v.in.pdal then convert to raster with 
d.vect?

Thanks,

Andreas___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user