[SoC] Week 05: Integration Of PDAL into GRASS GIS

[Helmut Kudrnovsky]

Thanks for taking care to solve this.

Kind regards
Helmut

Am 01.07.2017 3:58 nachm. schrieb "Paul Schrum" <paul.schrum at gmail.com>:

> Hi Helmut,
>
> I just verified my repo is public.  I was also able to reproduce the
> problem.  So it has to do with it being on NC State's Enterprise github.  I
> will have to contact them to find out what to do about this.  I may not be
> able to accomplish this until Wednesday.
>
> - Paul
>
>
> On Sat, Jul 1, 2017 at 1:32 AM, Helmut Kudrnovsky <hkmyricaria at gmail.com>
> wrote:
>
>> Dear Paul,
>>
>> thanks for your weekly report.
>>
>> If I follow your link to your repository, I get
>>
>> Sign in via LDAP
>> The GSoC repository should be publicly accessible; otherwise nobody of
>> the broader community is able to follow your coding progress.
>>
>> Kind regards
>> Helmut (on behalf of the OSGeo-GSOC-admin team)
>>
>>
>> Am 30.06.2017 10:43 nachm. schrieb "Paul Schrum" <ptschrum at ncsu.edu>:
>>
>> 1. What did you get done this week?
>>
>> Achieved my goal of getting basic functionality to work.  Specifically,
>> the code now takes an input file name and an output file name via GRASS
>> v.in.pdal and uses pdal to create the output file using a pipeline json
>> string (created in memory only).  At this point I have only tested this on
>> pdal’s test file, 100-points.las from their github page.  Further, I have
>> only run the conversion to .txt format.  But it is happening in GRASS
>> code.  Link to last commit: https://github.ncsu.edu/ptschr
>> um/v_in_pdal/commit/9f20105628decae639d5e4752235b68dbf86d02b
>>
>>
>>
>> 2. What do you plan on doing next week?
>>
>> a. I need to develop code and a memory-only pipeline which will consume
>> points from a .las file one point at a time so I can use them to build a
>> GRASS Vector Map.  In other words, get a basic, no-frills conversion from
>> .las to GRASS to work like basic .las to .txt is now working.
>>
>> b. Resolve the .o linking issue I am having with the added .cpp and .hpp
>> files (see Blocked, below).
>>
>> c. Get the process of testing/proving 2a into a unit test.  Vashek has
>> added a unit testing framework to GRASS under a previous GSoC project.  I
>> will be developing my tests under his established framework.
>>
>> d. Add some common options to the GRASS command line option so we can do
>> more than trivial conversions.
>>
>> 3. Are you blocked on anything?
>>
>> I have added a new .cpp file and .hpp file for generating pipelines from
>> GRASS inputs.  They compile, but I can’t get them to link.  I think I will
>> need help figuring this out.
>>
>> Repo: https://github.ncsu.edu/ptschrum/v_in_pdal
>>
>> Wiki: https://trac.osgeo.org/grass/wiki/GSoC/2017/IntegrationOfPDA
>> LintoGRASSGIS
>>
>> _______________________________________________
>> SoC mailing list
>> SoC at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/soc
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/soc/attachments/20170701/b1dfa216/attachment.html>