Re: [GRASS-dev] Adding hexagonal rasters to GRASS

Dear Luís, On Sun, Jul 23, 2017 at 11:50 AM, Luí­s Moreira de Sousa < luis.de.so...@protonmail.ch> wrote: > > I presented hex-utils at the GISTAM conference in April, here is the video: > https://www.youtube.com/watch?v=uLO4HDCVBp0 > > thank you, this is very informative and exiting! > > But

Re: [GRASS-dev] git repo for new Web site created

On Sat, Jul 22, 2017 at 2:04 PM, Markus Neteler wrote: > > Then we can enable you for the repo. > Please add me. My account is wenzeslaus https://git.osgeo.org/gogs/wenzeslaus ___ grass-dev mailing list grass-dev@lists.osgeo.org

Re: [GRASS-dev] Fwd: [mapserver-users] new official twitter account

Hi Luca, On Sat, Jul 22, 2017 at 5:24 AM, Luca Delucchi wrote: > > For social people do we want/have a twitter channel too? > years ago, Jorge Cornejo (CC'ed) created and used this account. However, recently the automatic settings associated with the account was only

Re: [GRASS-dev] New attempt to update GRASS for Mac

On Thu, Jul 20, 2017 at 3:34 AM, Rainer Krug <rainer_k...@icloud.com> wrote: > On 19 Jul 2017, at 21:54, Vaclav Petras <wenzesl...@gmail.com> wrote: > > On Wed, Jul 19, 2017 at 12:42 PM, Michael Barton <michael.bar...@asu.edu> > wrote: > >> >>

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

On Wed, Jul 19, 2017 at 1:42 AM, Pietro <peter.z...@gmail.com> wrote: > On Mon, Jul 17, 2017 at 5:36 PM, Vaclav Petras <wenzesl...@gmail.com> > wrote: > >> >> On Mon, Jul 17, 2017 at 12:36 AM, Pietro <peter.z...@gmail.com> wrote: >> >>> >&

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

eaders) as C which results in header `list` not being found (line 37 -> #include -> list: No such file or directory). Rename main.c to main.cpp. > > - Paul > > > On Sun, Jul 16, 2017 at 5:31 PM, Vaclav Petras <wenzesl...@gmail.com> > wrote: > >> >

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

On Mon, Jul 17, 2017 at 12:36 AM, Pietro <peter.z...@gmail.com> wrote: > > On Fri, Jul 14, 2017 at 6:00 PM, Vaclav Petras <wenzesl...@gmail.com> > wrote: > >> This is exactly what I had in my mind when doing the last major changes >> in the grass.py file.

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

On Sat, Jul 15, 2017 at 3:47 PM, Paul Schrum wrote: > > *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

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

Hi, Pietro. Just a short answer for now. This is exactly what I had in my mind when doing the last major changes in the grass.py file. I generally like the layout you suggested. It seems to me that choosing a good name for the whole module will be a bit tricky. Also I think one reason for having

Re: [GRASS-dev] GRASS GIS 7.2 talk at FOSS4G-E next week: highlights wanted

Hi Markus, On Thu, Jul 13, 2017 at 4:47 PM, Markus Neteler wrote: > > I'd be glad to receive some suggestions and ideas what to highlight > there beyond contents from > You can have a look at slides 43-56 from my presentation at NCGIS 2017. Cloud, superpixels, command line

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

Hi Paul, On Fri, Jun 30, 2017 at 4:42 PM, Paul Schrum wrote: > > > > 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

Re: [GRASS-dev] [SoC] Week 01 Report - Integration Of PDAL into GRASS GIS

This is actually a question for PDAL ML, not grass-dev, and Paul was discussing it there, hence Adam's email. But anyway, I told Paul not to worry about it for now, because the issue (linking LAZ libraries to PDAL) is more or less orthogonal to Paul's project (using PDAL in GRASS). Thanks all

[GRASS-dev] Talks and tutorials at ICC2017, Washington, DC, July

Dear users and developers, I would like to inform you about couple of talks and tutorials related to GRASS GIS which will happen at the International Cartographic Conference 2017 in Washington, DC, July 1 to 7, 2017. Here are the details: https://grasswiki.osgeo.org/wiki/GRASS_GIS_at_ICC_2017

Re: [GRASS-dev] r.colors.matplotlib

Hi Steve, On Tue, May 30, 2017 at 3:10 PM, Steven Pawley wrote: > > Thanks for writing the r.colors.matplotlib tools because I use the > matplotlib colorramps very frequently both in GRASS and in python more > generally. > Glad to hear that. > > I seem to be having

Re: [GRASS-dev] G7 helptext: replace Fig. 1: GRASS GIS 7 location structure with new figure

On Thu, May 25, 2017 at 1:15 AM, Markus Neteler wrote: > IMHO "Fig. 1: GRASS GIS 7 location structure" in > https://grass.osgeo.org/grass72/manuals/help_loc_struct.png > https://grass.osgeo.org/grass72/manuals/helptext.html > > (master: doc/help_loc_structure.odg) > > often

[GRASS-dev] Fwd: [OSGeo-Discuss] FOSS4G 2017 Boston Code Sprint

[forwarded from osgeo-discuss] Code Sprint in Boston, August 19th: https://wiki.osgeo.org/wiki/FOSS4G_2017_Code_Sprint Add yourself and topics if you are coming. Best, Vaclav -- Forwarded message -- From: Regina Obe Date: Sun, May 21, 2017 at 3:23 AM Subject:

Re: [GRASS-dev] Having trouble building GRASS from source and asking for help

On Mon, May 15, 2017 at 4:14 PM, Paul Schrum wrote: > I should get this to succeed before moving on to other steps. You don't actually need to do the "install" step to run it. Just run it using ./bin.../grass73. Generally speaking, it would be good to get this

Re: [GRASS-dev] Introduction for GSoC 2017

On Fri, May 12, 2017 at 9:51 AM, Martin Landa wrote: > since the tools is experimental we should not include in G7.4 I would > say. > Or just say they are experimental. > If you agree we have two options: > > * move it to Addons > * after creating relbr_74 to remove

Re: [GRASS-dev] Broken: GRASS-GIS/grass-ci#2145 (master - d37fa7c)

On Sun, May 7, 2017 at 8:00 AM, Markus Neteler <nete...@osgeo.org> wrote: > > On May 7, 2017 12:36 AM, "Vaclav Petras" <wenzesl...@gmail.com> wrote: > > > > On Fri, May 5, 2017 at 6:36 AM, Travis CI <bui...@travis-ci.org> wrote: > > >

Re: [GRASS-dev] Still Failing: GRASS-GIS/grass-ci#2150 (master - 6f1ff0c)

Please follow the discussion started from the first failed commit for updates: [GRASS-dev] Broken: GRASS-GIS/grass-ci#2145 (master - d37fa7c) http://lists.osgeo.org/pipermail/grass-dev/2017-May/084921.html http://lists.osgeo.org/pipermail/grass-dev/2017-May/084932.html

Re: [GRASS-dev] Broken: GRASS-GIS/grass-ci#2145 (master - d37fa7c)

On Fri, May 5, 2017 at 6:36 AM, Travis CI wrote: > > GRASS-GIS / grass-ci (master) > Build #2145 was broken. > ... > git-svn-id: https://svn.osgeo.org/grass/grass/trunk@71024 15284696-431f-4ddb-bdfa-cd5b030d7da7 > ... > > We have updated our sudo-enabled Precise images! Read

Re: [GRASS-dev] [GRASS-user] r.to.vect stats

On Fri, May 5, 2017 at 3:43 AM, Moritz Lennert wrote: > Markus is probably right: working with an intermediate file solves all > this and I don't think it would imply a serious speed decrease. > I have tested r.vect.stats (with pipe) and compared it with pipe in

Re: [GRASS-dev] [GRASS-user] r.to.vect stats

On Fri, May 5, 2017 at 3:55 AM, Martin Landa wrote: > BTW, meanwhile I changed in r71022 default > method from 'mean' (module was calculating mean value of categories) > to 'n' (number of points in cell). > Before it gave expected result for points with Z, e.g. in full

Re: [GRASS-dev] [GRASS-user] r.to.vect stats

On Wed, May 3, 2017 at 5:34 AM, Moritz Lennert <mlenn...@club.worldonline.be> wrote: > > On 02/05/17 15:53, Vaclav Petras wrote: >> I'm using pipe_command() which is just convenience function setting >> stdout=PIPE. Similarly feed_command() is just setting stdin=PIPE which

Re: [GRASS-dev] r.binning

On Wed, May 3, 2017 at 6:57 AM, Markus Neteler wrote: > > The module name r.binning is rather non-descriptive. I would suggest > > r.vect.stats because it can be regarded as the inverse of v.rast.stats, > and > > because it is similar to r.resamp.stats. All do statistical

Re: [GRASS-dev] [GRASS-SVN] r70999 - grass-addons/grass7/raster/r.learn.ml

On Tue, May 2, 2017 at 12:45 PM, wrote: > Author: spawley > Date: 2017-05-02 09:45:12 -0700 (Tue, 02 May 2017) > New Revision: 70999 > > Modified: >grass-addons/grass7/raster/r.learn.ml/r.learn.ml.py >grass-addons/grass7/raster/r.learn.ml/r_learn_utils.py > Log: >

Re: [GRASS-dev] [GRASS-SVN] r70814 - grass-addons/grass7/raster/r.vif

On Fri, Mar 31, 2017 at 8:56 AM, wrote: > Author: pvanbosgeo > Date: 2017-03-31 05:56:38 -0700 (Fri, 31 Mar 2017) > New Revision: 70814 > > Modified: >grass-addons/grass7/raster/r.vif/r.vif.html >grass-addons/grass7/raster/r.vif/r.vif.py > Log: > r.vif addon:

Re: [GRASS-dev] [GRASS-user] r.to.vect stats

On Tue, May 2, 2017 at 3:24 AM, Moritz Lennert wrote: > But I'm not against a wrapper. I added a prototype with limited >> functionality to addons [1]. However, I'm not sure how to account for >> large data - that's what discouraged me from creating a wrapper. The

Re: [GRASS-dev] r.binning

On Tue, May 2, 2017 at 5:31 AM, Paulo van Breugel wrote: > Just had a look at r.binning, very useful. > Thanks. But is is not complete yet. > > There is a small error in the code, you are importing grass.script as gs, > so on line 33 it should be > > options, flags =

Re: [GRASS-dev] [GRASS-user] r.to.vect stats

[Switching from grass-user to grass-dev.] On Mon, May 1, 2017 at 5:11 PM, Markus Metz wrote: > > > Is it different from the binning code in r.in.xyz ? > > > > > > Not really. r.in.lidar was based on r.in.xyz, now they are different > but of course the idea is to

Re: [GRASS-dev] wxGUI unusual high CPU usage debugging

On Tue, Apr 25, 2017 at 6:38 AM, Markus Neteler wrote: > If you can > > figure out the actual python program that it runs, that would be > helpful. > It runs wxgui.py [1], so you can use something like: cd grass/src python gui/wxpython/wxgui.py or: python

Re: [GRASS-dev] r.fill.gaps porting

On Mon, Apr 17, 2017 at 2:58 PM, Benjamin Ducke wrote: > > I've added a figure which shows the r.slope.aspect products from the > > surface without and with -p. You can see that the smoothing gives > > significantly different results and probably better ones. I had the same

Re: [GRASS-dev] r.fill.gaps porting

On Sat, Apr 15, 2017 at 8:32 AM, Benjamin Ducke wrote: > The thing is: I originally developed this module for > gradiometer data. That data is very noisy and has > high local variation. Interpolating that type of > data while preserving original measurements will > usually

Re: [GRASS-dev] r.fill.gaps porting

On Sat, Apr 15, 2017 at 8:57 AM, Markus Neteler wrote: > > These are 250x232, > > Would it be possible to have larger pics here? I guess they come from > Benjamin? > There are two next to each other, so the combined width is 500 which is almost our max for display (600).

Re: [GRASS-dev] r.fill.gaps porting

On Sat, Apr 15, 2017 at 7:51 AM, Maris Nartiss wrote: > As you added an example with LiDAR data - it is too large. Reduce its > size as default module help tab is much more narrow. > Maris, we agreed with Markus that the problem is in wxPython GUI versus submitting

Re: [GRASS-dev] r.fill.gaps porting

On Sat, Apr 15, 2017 at 8:03 AM, Markus Neteler wrote: > > > it is nice to see porting of old addons. > > As you added an example with LiDAR data - it is too large. Reduce its > > size as default module help tab is much more narrow. > > The HTML code currently is this: > >

[GRASS-dev] Workshops at FOSS4G 2017 in Boston and voting for presentations

Dear users and developers, I'm pleased to announce these two following GRASS GIS workshops which will happen at FOSS4G 2017 in Boston: * From GRASS GIS novice to power user * Processing lidar and UAV point clouds in GRASS GIS See the full descriptions here:

[GRASS-dev] Temporal tests failing: t.rast.aggregate

There are new tests for t.rast.aggregate which are failing. The change happened between these revisions: 2017-03-04 03:01:30 (SVN revision 70724 ) 2017-03-05 03:01:30 (SVN revision 70728

Re: [GRASS-dev] GRASS GIS and GSoC

Zeke, you should try to fix some tickets (as suggested on the GSoC wiki page you linked); see the lists below. Alternatively, for your project, it may be appropriate to implement a small tool for some dataset which is easy to handle for you (e.g. something you used before). Look at the r.modis

[GRASS-dev] GRASS wiki: uploading figures efficiently

Hi, I wonder if there is a better way of uploading and managing images on the GRASS (user) wiki (MediaWiki). I always go to a separate page to upload an image, then I go to get a code snipped somewhere to add it to a page the way I want. I can't exactly say what workflow I'm looking for, but

Re: [GRASS-dev] Introduction for GSoC 2017

On Sat, Mar 18, 2017 at 3:30 AM, Blumentrath, Stefan < stefan.blumentr...@nina.no> wrote: > Could also porting (competition) of the i.ortho.photo modules (and here > especially the missing GUI modules around it) to GRASS 7 become scope of > this GSoC idea? > See also:

Re: [GRASS-dev] Introduction for GSoC 2017

On Wed, Mar 15, 2017 at 3:00 AM, Moritz Lennert < mlenn...@club.worldonline.be> wrote: > > > > >> - A tool to attribute class values to raster objects. This is much > >> simpler and "just" a combination of GUI + r.what + form to add a > >> value + writing everything to a text file. In other

[GRASS-dev] Helping beginners and GSoC students find simple problems to tackle

Dear all, we suggest specific tickets to GSoC often tailored to a specific GSoC idea they are interested in. However, in general it is hard to find a right topic for a person who wants to start contributing to GRASS GIS (as opposed to writing additional modules with some specific functionality).

Re: [GRASS-dev] Introduction for GSoC '17

On Wed, Mar 15, 2017 at 7:55 AM, Anisha Godha wrote: > I am a fourth year student in Geological Technology at Indian Institute of > Technology Roorkee. This January, I built an ArcGIS plug-in in Python that > automates the Laminar Flow Model method to give a glacier's

Re: [GRASS-dev] Introduction for GSoC 2017

Dear Moritz and students, here are some of my ideas for these ideas. This is a good start. I think we need enhancement ticket with use cases for each item. On Tue, Mar 14, 2017 at 6:25 AM, Moritz Lennert < mlenn...@club.worldonline.be> wrote: > - A general vector interactive attribute table

Re: [GRASS-dev] To contribute in GRASS GIS

On Thu, Mar 9, 2017 at 2:11 PM, Anna Petrášová wrote: > > Hi Sushil, > > here are some general enhancements you could look at, all in C: > https://trac.osgeo.org/grass/ticket/1852 > https://trac.osgeo.org/grass/ticket/3217 > https://trac.osgeo.org/grass/ticket/2123 >

Re: [GRASS-dev] RGB colored and Transparent areas in one vector map

On Tue, Mar 7, 2017 at 4:10 AM, Nikos Alexandris wrote: > I would like to use a hexagon symbol (we don't > have one I think) > We actually do: https://trac.osgeo.org/grass/changeset/70136 I though it might be useful, e.g. for legend of v.mkgrid -h. Did you open the

Re: [GRASS-dev] GSoC 2017 - Generalized GUI code for Qt-based GUI

On Wed, Mar 8, 2017 at 2:21 AM, Ondrej Svoboda wrote: > A topic I am most interested in is Generalized GUI code for Qt-based GUI > [1]. > It would be good if you fork & clone the repo from last year [3] and make it work on your computer. It should be easy to find few things

Re: [GRASS-dev] GSOC

Hi Shreyan, sounds good! On Tue, Mar 7, 2017 at 7:49 AM, Shreyan Mehta wrote: > Integration of PDAL into GRASS GIS The best way to start on your application for this topic is compiling v.in.pdal module (vector/v.in.pdal directory) with latest PDAL, see #3243

Re: [GRASS-dev] RGB colored and Transparent areas in one vector map

On Mon, Mar 6, 2017 at 11:20 AM, Nikos Alexandris <n...@nikosalexandris.net> wrote: > > Vaclav Petras: > >> Try setting the column value to "none" (usually implemented for parameters, >> I'm not sure here). > > > Does not work, already tried that b

Re: [GRASS-dev] RGB colored and Transparent areas in one vector map

On Mon, Mar 6, 2017 at 6:44 AM, Nikos Alexandris wrote: > I have an rgb_column with RGBs for a vector map. For some areas, I would > like to have no color, as in trasparent. > > If I am not wrong, we can't do that, ie define "nv" as we can do in > color rules for a

Re: [GRASS-dev] Working with TGIS without starting GRASS explicitly

Older, but the general ideas still apply: On Thu, Sep 22, 2016 at 12:01 PM, Laurent C. wrote: > > My software is not really a GRASS module, it is more independent and > use only GRASS as a back-end. It is fully written in Python and using > --exec or GRASS_BATCH_JOB does not

Re: [GRASS-dev] Next events workshop

On Wed, Jan 25, 2017 at 3:49 AM, Luca Delucchi wrote: > is someone thinking to submit any workshop for FOSS4G 2017 in Boston > and FOSS4G EU 2017 in Paris? > The deadline for FOSS4G 2017 Boston is Monday, March 13. If anybody else plans to submit a workshop or is willing

Re: [GRASS-dev] GRASS working under Mac El Capitan with SIP/rootless?

On Wed, Sep 14, 2016 at 11:14 AM, Michael Barton wrote: > Oddly, the only things I've run into that don't work so far are 3D mode, > vector digitizer, and raster digitizer. The only errors are the following > in the terminal at startup: > > Launching GUI in the

[GRASS-dev] What long-term support means for GRASS GIS?

Hi, I know we've already touched on that, but I'm still unclear about what "long-term support" means for us. The release announcement for 7.2 says: As a stable release series, 7.2.x enjoys long-term support. which is more or less the same what 7.0 announcement says: As a stable release 7.0

Re: [GRASS-dev] github / travis sync - push file to grass-gis/homebrew-grass-dev repo when grass-gis is synsed to svn?

On Thu, Feb 9, 2017 at 4:25 PM, Rainer M Krug wrote: > Would it be possible to push a file containing e.g. the time to > grass-gis/homebrew-grass-dev? > > The content of the file does not matter, but e.g. the time would be > fine. > That would be a big workaround IMO. I think

Re: [GRASS-dev] new addon module: i.superpixels.slic - image segmentation using the SLIC segmentation method

Congratulations to the authors of i.superpixels.slic to a great achievement! I've noticed lot of promising commits. I've a suggestion to rename the one of the option called `k`. I think we were recently changing a lot of options in modules from a letter to a more descriptive name (num, number,

Re: [GRASS-dev] Still Failing: GRASS-GIS/grass-ci#1898 (master - 7fa0125)

On Mon, Feb 6, 2017 at 8:50 AM, Markus Neteler wrote: > > Otherwise, there is no problem at all with using the git repo. > > Perhaps yes if that brings back the Mac tests at lowest cost Assuming that the Homebrew repo will be tested separately, the question is if we want to

Re: [GRASS-dev] Still Failing: GRASS-GIS/grass-ci#1898 (master - 7fa0125)

On Mon, Feb 6, 2017 at 8:52 AM, Markus Neteler wrote: > On Mon, Feb 6, 2017 at 8:52 AM, Rainer M Krug wrote: > > Markus Neteler writes: > > How do you mean? The script is in the folder .travis (hidden to be > > in line with the naming of

Re: [GRASS-dev] Still Failing: GRASS-GIS/grass-ci#1909 (master - 05df514)

On Sat, Feb 4, 2017 at 8:48 AM, Yann wrote: > > Is Travis doing OK ? Sorry for the noise. The Mac compilation had 3rd party dependencies and other issues, see e.g. https://trac.osgeo.org/grass/ticket/3250 I committed https://trac.osgeo.org/grass/changeset/70483

Re: [GRASS-dev] GSoC proposal "Higher level API for C and C++" : need for discussion

On Wed, Feb 1, 2017 at 3:24 PM, Moritz Lennert wrote: > >please take a look at GAL project from 2008 [1]. Ma > > I didn't really work out the differences to GAL project but this GSoC project should be less ambitious, much more limited, cover smaller part of the

Re: [GRASS-dev] GSoC proposal "Higher level API for C and C++" : need for discussion

I did not include many details in the idea so here they are. On Wed, Feb 1, 2017 at 11:59 AM, Moritz Lennert < mlenn...@club.worldonline.be> wrote: > I just the GSoC proposal for a "Higher level API for C and C++". > It it should not remove the existing API but build on to of it. > I _think_

Re: [GRASS-dev] Still Failing: GRASS-GIS/grass-ci#1898 (master - 7fa0125)

On Sun, Jan 29, 2017 at 9:48 AM, Moritz Lennert < mlenn...@club.worldonline.be> wrote: > (R)eject, accept (t)emporarily or accept (p)ermanently? svn: E175002: > Unable to connect to a repository at URL > 'https://svn.osgeo.org/grass/grass/trunk' > > svn: E175002: OPTIONS of

Re: [GRASS-dev] Reviewing GSoC 2017 page

On Wed, Jan 25, 2017 at 6:35 PM, Blumentrath, Stefan < stefan.blumentr...@nina.no> wrote: > I took the liberty to add one on “tools for generating unit tests from > examples in module manuals”. Not sure if that is feasible or out of scope. > Please feel free to remove it if you don`t find it

Re: [GRASS-dev] Next events workshop

On Thu, Jan 26, 2017 at 4:51 AM, Luca Delucchi wrote: > > Please, let me know if you want to collaborate on this or other workshop > or > > you have some topics you would like to see covered. > > > > maybe we could also submit a Intro course, I could do that > Sure, my

Re: [GRASS-dev] Reviewing GSoC 2017 page

Worked. Thanks for tuning the spam filter, Markus. I just put all the new things at the beginning. On Wed, Jan 25, 2017 at 10:01 AM, Vaclav Petras <wenzesl...@gmail.com> wrote: > Can somebody reorder the ideas so that the fresh ideas are at the top? > When I try it, I get &qu

[GRASS-dev] Reviewing GSoC 2017 page

Can somebody reorder the ideas so that the fresh ideas are at the top? When I try it, I get "Too many links" or "Page not modified". Thanks, Vaclav ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Next events workshop

I plan to submit a workshop for FOSS4G 2017 in Boston. GRASS and lidar related. Please, let me know if you want to collaborate on this or other workshop or you have some topics you would like to see covered. Vaclav On Wed, Jan 25, 2017 at 3:49 AM, Luca Delucchi wrote: >

[GRASS-dev] GIScRG & QMRG - Call for Contribution to GIS / statistical open source software

All, I'm forwarding the following this general call relevant also to GRASS GIS contributors current and new. Deadline Feb 17. Link: http://bit.ly/2j9Igjt Description: GIScRG & QMRG - Call for Contribution to GIS / statistical open source software The GIScRG (Geographic Information Science

Re: [GRASS-dev] keyword for modules operating on level 1

On Tue, Jan 17, 2017 at 8:41 AM, Martin Landa wrote: > 2017-01-14 17:15 GMT+01:00 Martin Landa : > > I just not sure what name to choose for such keyword - 'level1' or > > 'level 1' seems to be too much cryptic for some users. Keywords like > > 'no

Re: [GRASS-dev] Fwd: [OSGeo] #1816: upgrade Trac to 1.2 release

On Tue, Jan 10, 2017 at 11:43 AM, Markus Neteler wrote: > From the OSGeo ticket: Alternatives ( to review for supporting Trac 1.2 ) : > - https://trac-hacks.org/wiki/TracStatsPlugin > Looks good. May be useful. Seems very comprehensive. Last commit on GitHub from Dec 2016.

Re: [GRASS-dev] Fwd: [OSGeo] #1816: upgrade Trac to 1.2 release

On Tue, Jan 10, 2017 at 10:53 AM, Markus Neteler wrote: > Hi devs, > > are we really using TracMetrixPlugin? See below... > > I don't know what part of Trac it is. It is this one? https://trac.osgeo.org/grass/pdashboard Nice overview, I used it several times just because it

Re: [GRASS-dev] Still Failing: GRASS-GIS/grass-ci#1837 (master - 542a054)

On Sat, Jan 7, 2017 at 5:24 PM, Anna Petrášová wrote: > it's failing on Mac only, but I don't see a log, so I can't fix it. Why is Mac build using brew? I would expect it to use the source code from the repo directly. ___

Re: [GRASS-dev] d.linegraph indentation mess

On Sun, Dec 18, 2016 at 4:29 PM, Vaclav Petras <wenzesl...@gmail.com> wrote: > I'll just reindent all Done. It was just the indent. https://trac.osgeo.org/grass/changeset/70130 and do the classic int -> size_t replacements. Not done. A lot of code would be to be changed includin

Re: [GRASS-dev] [GRASS-SVN] r70106 - grass/trunk/mswindows

On Tue, Dec 20, 2016 at 5:03 PM, wrote: > > Author: martinl > Date: 2016-12-20 14:03:52 -0800 (Tue, 20 Dec 2016) > New Revision: 70106 > > Modified: >grass/trunk/mswindows/GRASS-Installer.nsi.tmpl > Log: > wingrass: attempt to fix standalone installer to download and

Re: [GRASS-dev] v.select features without category skipped

On Tue, Dec 20, 2016 at 10:36 AM, Moritz Lennert < mlenn...@club.worldonline.be> wrote: > On 20/12/16 16:18, Luca Delucchi wrote: > >> On 20 December 2016 at 16:08, Moritz Lennert >> wrote: >> >> >>> You can go ahead and commit to trunk, unless someone objects. At

Re: [GRASS-dev] r.randomforest built status

On Sun, Dec 18, 2016 at 3:40 PM, Helmut Kudrnovsky wrote: > > > > Is there any "best practice" example available? > > > I've done it in this way : > > https://trac.osgeo.org/grass/browser/grass-addons/grass7/ >

Re: [GRASS-dev] d.linegraph indentation mess

On Sat, Dec 17, 2016 at 7:15 AM, Markus Neteler wrote: > > Indeed, the if() statement in 735 has some issues: braces missing or > indentation wrong. > > Any idea how to fix that correctly? > I need to look at these two if more closely, but otherwise I think I'll just

Re: [GRASS-dev] GRASS 7.2RC2 problem

Hi Michael, On Thu, Dec 15, 2016 at 3:35 PM, Michael Barton wrote: > > from my compiling environment shell and from within a functioning grass > environment. > When the log shows ``` Details: [Errno 2] No such file or directory g.gui.dbmgr: Unable to fetch interface

Re: [GRASS-dev] [release planning] 7.2.0

On Sun, Dec 11, 2016 at 2:43 PM, Martin Landa wrote: > > 2016-12-11 20:39 GMT+01:00 Markus Neteler : > > Sorry to bother: this does not sound like a GRASS GIS 7.2 problem to > > me but a winGRASS packaging issue? > > yes, it seems to be a WinGRASS

Re: [GRASS-dev] [release planning] 7.2.0

On Sat, Dec 10, 2016 at 1:04 PM, Martin Landa wrote: > 2016-12-10 17:52 GMT+01:00 Helena Mitasova : > > Regarding the release there is also a major issue with v.in.lidar - > Vasek is this still a problem in 7.2? > > do you mean Windows issue reported on

Re: [GRASS-dev] [release planning] 7.2.0

On Sat, Dec 10, 2016 at 10:57 AM, Martin Landa wrote: > 2016-12-10 16:51 GMT+01:00 Markus Neteler : > > On Dec 7, 2016 10:02 PM, "Markus Neteler" wrote: > >> Now the current showstopper is MacOSX it seems... > > > > Is this really a

Re: [GRASS-dev] GRASS 7.2RC2 problem

The issue is solved in Python 2.7.12 from 2016-06-25. https://hg.python.org/cpython/raw-file/v2.7.12/Misc/NEWS On Wed, Dec 7, 2016 at 6:59 PM, Michael Barton wrote: > We need to do something other than update Python. There is not that much which can be done on the

Re: [GRASS-dev] GRASS 7.2RC2 problem

On Wed, Dec 7, 2016 at 7:00 PM, Michael Barton wrote: > Also, why did this appear in GRASS 7.2 since mid-September? If we can > answer that, perhaps we can avoid this issue. Perhaps certain version of Python (the "patch" one, not just minor) or change in Mac OS API.

Re: [GRASS-dev] GRASS 7.2RC2 problem

On Wed, Dec 7, 2016 at 2:23 PM, Anna Petrášová wrote: > Looks like this: > http://bugs.python.org/issue26083 > Then it seems that the issue is unrelated to GRASS source code. Maybe an update of system Python would help. Many GRASS modules written in Python won't work with

Re: [GRASS-dev] GRASS 7.2RC2 problem

On Tue, Dec 6, 2016 at 7:03 PM, Michael Barton wrote: > Here is what I had to do before. > What happens when you do it now? Or you already did that now? > > Compile normally (my steps 1-5) > > 5.1. Do NOT create binary distribution yet (do not run make bindist) > 5.2.

Re: [GRASS-dev] GRASS 7.2RC2 problem

In the log there is: /Applications/Xcode.app/Contents/Developer/usr/bin/make xml/menudata.xml GISRC=... LC_ALL=C python core/toolboxes.py > xml/menudata.xml /Applications/Xcode.app/Contents/Developer/usr/bin/make xml/module_tree_menudata.xml GISRC=... LC_ALL=C python core/toolboxes.py

Re: [GRASS-dev] GRASS 7.2RC2 problem

I don't know what to think about the log. There should be no "up to date" massages after `make distclean`. make[4]: `/Users/cmbarton/grass_source/grass-7.2.0RC2/dist.x86_64- apple-darwin15.6.0/docs/man/man1/d.rhumbline.1' is up to date. On Tue, Dec 6, 2016 at 5:56 PM, Michael Barton

Re: [GRASS-dev] t.rast.out.xyz not exporting all cells in the computational region

On Tue, Dec 6, 2016 at 12:34 PM, Moritz Lennert < mlenn...@club.worldonline.be> wrote: > Le 6 décembre 2016 17:53:48 GMT+01:00, Martin Landa < > landa.mar...@gmail.com> a écrit : > >Hi, > > > >2016-12-06 17:45 GMT+01:00 Markus Neteler : > >> Big question: add to 7.2.0 or not? I

Re: [GRASS-dev] Passing computational region to individual commands

On Wed, Nov 23, 2016 at 3:41 PM, Markus Neteler wrote: > GRASS_REGION does not affect the stored computational region (i.e. the > WIND file) but appears to be only used by the following module call. Yes. A module reads the region from the env var. The behavior is the same if

Re: [GRASS-dev] man error on compilation

On Tue, Nov 22, 2016 at 1:01 PM, Yann Chemin wrote: > the error came when I would not flush all containers from previous build. > If I build with --no-cache, the issue does not come. > > Yes, cache seems tricky. I checkout and compile in one step. Longer and network

Re: [GRASS-dev] man error on compilation

On Tue, Nov 22, 2016 at 11:12 AM, Yann Chemin wrote: > I am compiling from SVN inside a docker (Debian testing) > > I'm just doing it with Ubuntu in Docker and I have no issue with r68881 (docker run ... grass --config revision). > for some reason inside man/ the

[GRASS-dev] Passing computational region to individual commands

[was: Adding an expert mode to the parser] On Sun, Sep 25, 2016 at 10:16 PM, Vaclav Petras <wenzesl...@gmail.com> wrote: > On Sun, Sep 25, 2016 at 5:40 PM, Sören Gebbert < > soerengebb...@googlemail.com> wrote: > >> >r.mapclac --raster-region= --north=

Re: [GRASS-dev] Standard option identifiers

On Mon, Oct 31, 2016 at 11:38 PM, Helmut Kudrnovsky wrote: > G_OPT_R_INPUTS > type : string > Once there is G_OPT_R_INPUTS, you don't need to provide `type: string` that's provided automatically. Typically you change key or description/label.

Re: [GRASS-dev] [GRASS-user] Fwd: Geospatial devroom at FOSDEM 2017 on Sunday 5/2/2017 in Brussels

On Mon, Oct 24, 2016 at 8:12 AM, Margherita Di Leo wrote: > On Thu, Oct 20, 2016 at 4:00 PM, Moritz Lennert < > mlenn...@club.worldonline.be> wrote: > >> After our latest discussions I think it might be interesting if someone >> could present the GRASS GIS testing framework.

[GRASS-dev] GRASS GIS meetup in Raleigh, North Carolina, Nov 5

at 2 PM. Join any time during the afternoon; we will be there at least till 6 PM, but there is an option to stay longer. Contact Vaclav Petras (Vashek) if you have any questions: wenzeslaus gmail com See this page for details: https://grasswiki.osgeo.org/wiki/GRASS_GIS_Raleigh_meetups_2016

[GRASS-dev] Color tables/rules now use standardized color parsing

Dear all, in r69708, I've changed the implementation of parsing color rules to use the G_str_to_color() function instead of a custom mechanism. This, in connection with r69683, adds the possibility to use HTML (CSS) style of hexadecimal colors with leading hash. So, now you can do: r.colors

Re: [GRASS-dev] v.wedge

On Tue, Oct 18, 2016 at 5:58 PM, Vincent Bain wrote: > > Hoping it can be useful I attach the bash script, don't know if it's > worth making it an addon, I guess it would be better to write new addons > in python... perhaps someone can turn it into something more "trendy"? >

Re: [GRASS-dev] Delete r.le.* now?

On Thu, Sep 1, 2016 at 4:13 AM, Moritz Lennert wrote: >>> I suggest identifying what is missing in r.li from r.le and opening tickets >>> for it. Then it seems that it is time to remove r.le.* from addons, so it is >>> clear that they don't need to be maintained.

[GRASS-dev] Specify color as #RRGGBB

Dear all, in r69683 I've added few lines to support colors hexadecimal numbers for colors when prefixed by hash. That's the syntax often used in HTML (CSS) and by other programs and formats. Now instead of d.vect map=hospitals color=80:170:255 you can do this: d.vect map=hospitals

<    1   2   3   4   5   6   7   8   9   10   >