[GRASS-dev] [SoC] GSoC 2017 Weekly Report 5 - SOS tools in GRASS GIS
Hi everyone! Here is the fifth report of my GSoC project - SOS tools in GRASS GIS. You can see my project at wiki at [1] What did you get done this week? v.in.sos * using vectors in pyGRASS instead of v.in.sos * support multiple offerings * layers are for offerings and observed properties, rows are for one feature * handle data input with no observations for * handle too big input with warnings and errors t.vect.in.sos * first version (just draft with some bugs, they are saved as issues and will be solved after my return) What do you plan on doing next week? As I declared in my timeline and proposal, I would like to apologize that from tomorrow morning to the fifteenth of July, I will be out of internet and electricity (due to my work at summer camp). So I won't be able to do anything connected with GSoC. Are you blocked on anything? * Will be blocked on the absence of internet and electricity Regards, Ondrej [1] https://trac.osgeo.org/grass/wiki/GSoC/2017/SOSInGRASS ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] [SoC] Week 05: Integration Of PDAL into GRASS GIS
Weekly Report for Paul Schrum for Week 5 (the week ending 6/30/2017) Project: Integration Of PDAL into GRASS GIS 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/ptschrum/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/IntegrationOfPDALintoGRASSGIS ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] Passed: GRASS-GIS/grass-ci#2214 (master - 4b63a4b)
Build Update for GRASS-GIS/grass-ci - Build: #2214 Status: Passed Duration: 5 minutes and 49 seconds Commit: 4b63a4b (master) Author: Maris Nartiss Message: To prevent parallel (really rare) compilation failures, data dir must be processed before qtree. git-svn-id: https://svn.osgeo.org/grass/grass/trunk@71236 15284696-431f-4ddb-bdfa-cd5b030d7da7 View the changeset: https://github.com/GRASS-GIS/grass-ci/compare/eb71f338b036...4b63a4b80c80 View the full build log and details: https://travis-ci.org/GRASS-GIS/grass-ci/builds/248739245?utm_source=email_medium=notification -- You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] Python grass script error
Works just fine here.
What is the output of os.getenv("GISBASE")? Are you trying to run this
code outside of GRASS GIS session (this could explain lack of GISBASE
environmental setting)?
Māris.
2017-06-29 18:00 GMT+03:00 Margherita Di Leo :
> Hi,
>
> I have GRASS 7.3.svn (r71212). In python , calling grass.script I get:
>
import grass.script as grass
> Traceback (most recent call last):
> File "", line 1, in
> File "/usr/local/grass-7.3.svn/etc/python/grass/script/__init__.py", line
> 5, in
> from .core import *
> File "/usr/local/grass-7.3.svn/etc/python/grass/script/core.py", line 35,
> in
> gettext.install('grasslibs', os.path.join(os.getenv("GISBASE"),
> 'locale'))
> File "/usr/lib64/python2.7/posixpath.py", line 70, in join
> elif path == '' or path.endswith('/'):
> AttributeError: 'NoneType' object has no attribute 'endswith'
>
> Anyone can reproduce this error?
>
> Thank you in advance
>
>
> --
> Margherita Di Leo
>
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev
