[GRASS-dev] [SoC] Week 07: Integration Of PDAL into GRASS GIS

[Paul Schrum]

*1. What did you get done this week?*
a. Got v.in.pdal to work in its most basic task: Creating a GRASS VectorMap
from a .las file using a pdal filter (which is created in code).  Fulfills
Week 6 Item 2a.  Commit


d. Renamed the module on github from v_in_pdal to v.in.pdal and followed
through on updating links at the 2017 Accepted Page
 and
the Project
Wiki
.

c. Started working on r.in.pdal.  Fulfills Week 6 Item 2b (No commit ready
for this.)


*2. What do you plan on doing next week?*
a. Complete the basic functionality of r.in.pdal as a refactor from the
existing r.in.lidar source.

b. Set up and pass unit tests for v.in.pdal and r.in.pdal.  Carried over
from Week 6.

c. Begin work on r3.in.pdal.

*3. Are you blocked on anything?*
Yes.  After setting up r.in.pdal and adding the #include files for Pdal,
make can't find them.  I have a request in with my mentor to help me
troubleshoot this as soon as possible.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] move everything from /lib/init/grass.py to /lib/python/init

[Maris Nartiss]

2017-07-14 19:00 GMT+03:00 Vaclav Petras :
> Also I think one reason for having
> them there was that grass.py works without a he G Python lib found. Vaclav

This! Although having a module would be fine, we must take extra care
to put warnings in all files to not depend on any other GRASS GIS
functions that might not be available/useable before full
initialisation is done.

Māris.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev