*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 <https://github.com/PaulSchrum/v.in.pdal/commit/1baefcd51f2e9a0f6e80d9eb0e63caa238e4a398>
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 <https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2017_Accepted> and the Project Wiki <https://trac.osgeo.org/grass/wiki/GSoC/2017/IntegrationOfPDALintoGRASSGIS>. 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 [email protected] https://lists.osgeo.org/mailman/listinfo/grass-dev
