<div dir="auto">Thanks for taking care to solve this. <div dir="auto"><br></div><div dir="auto">Kind regards </div><div dir="auto">Helmut </div></div><div class="gmail_extra"><br><div class="gmail_quote">Am 01.07.2017 3:58 nachm. schrieb "Paul Schrum" <<a href="mailto:paul.schrum@gmail.com">paul.schrum@gmail.com</a>>:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi Helmut,<br><br></div><div>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.<br></div><div><br></div>- Paul<br><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Jul 1, 2017 at 1:32 AM, Helmut Kudrnovsky <span dir="ltr"><<a href="mailto:hkmyricaria@gmail.com" target="_blank">hkmyricaria@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">Dear Paul, <div dir="auto"><br></div><div dir="auto">thanks for your weekly report. </div><div dir="auto"><br></div><div dir="auto">If I follow your link to your repository, I get </div><div dir="auto"><br></div><h3 style="padding:10px 15px;margin:0px;font-size:14px;color:rgb(255,255,255);border-bottom:1px solid rgb(221,221,221);background-color:rgb(88,104,115);font-family:-apple-system,blinkmacsystemfont,"segoe ui",helvetica,arial,sans-serif,"apple color emoji","segoe ui emoji","segoe ui symbol"">Sign in via LDAP</h3><br><div class="gmail_extra" dir="auto">The GSoC repository should be publicly accessible; otherwise nobody of the broader community is able to follow your coding progress. </div><div class="gmail_extra" dir="auto"><br></div><div class="gmail_extra" dir="auto">Kind regards </div><div class="gmail_extra" dir="auto">Helmut (on behalf of the OSGeo-GSOC-admin team) </div><div class="gmail_extra" dir="auto"><br></div><div class="gmail_extra" dir="auto"><br><div class="gmail_quote"><div><div class="m_-4523083767623340500h5">Am 30.06.2017 10:43 nachm. schrieb "Paul Schrum" <<a href="mailto:ptschrum@ncsu.edu" target="_blank">ptschrum@ncsu.edu</a>>:<br type="attribution"></div></div><blockquote class="m_-4523083767623340500m_-7478522214744524411quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="m_-4523083767623340500h5"><div dir="ltr"><div>1. What did you get done this week?</div><div><br></div><div>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: <a href="https://github.ncsu.edu/ptschrum/v_in_pdal/commit/9f20105628decae639d5e4752235b68dbf86d02b" target="_blank">https://github.ncsu.edu/ptschr<wbr>um/v_in_pdal/commit/9f20105628<wbr>decae639d5e4752235b68dbf86d02b</a></div><div><br></div><div> </div><div><br></div><div>2. What do you plan on doing next week?</div><div><br></div><div>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.</div><div><br></div><div>b. Resolve the .o linking issue I am having with the added .cpp and .hpp files (see Blocked, below).</div><div><br></div><div>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.</div><div><br></div><div>d. Add some common options to the GRASS command line option so we can do more than trivial conversions.</div><div><br></div><div>3. Are you blocked on anything?</div><div><br></div><div>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.</div><div> <br></div><div>Repo: <a href="https://github.ncsu.edu/ptschrum/v_in_pdal" target="_blank">https://github.ncsu.edu/ptschr<wbr>um/v_in_pdal</a><br></div><div><br></div><div>Wiki: <a href="https://trac.osgeo.org/grass/wiki/GSoC/2017/IntegrationOfPDALintoGRASSGIS" target="_blank">https://trac.osgeo.org/grass/w<wbr>iki/GSoC/2017/IntegrationOfPDA<wbr>LintoGRASSGIS</a></div></div>
<br></div></div>______________________________<wbr>_________________<br>
SoC mailing list<br>
<a href="mailto:SoC@lists.osgeo.org" target="_blank">SoC@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/soc" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailma<wbr>n/listinfo/soc</a><br></blockquote></div><br></div></div>
</blockquote></div><br></div>
</blockquote></div></div>