Re: [GRASS-dev] best practices for subject lines of PR

On Fri, May 8, 2020 at 1:04 PM Stefan Blumentrath < stefan.blumentr...@nina.no> wrote: > Hi, > > Yes, I would also be very interested in some guidance on this! > Here are guidelines I wrote for commit messages for Subversion. A lot of it should still apply for both commits and PRs.

Re: [GRASS-dev] New GUI startup discussion

On Thu, May 14, 2020 at 9:29 PM Robert Lagacé wrote: > Le 20-05-14 à 16 h 51, Vaclav Petras a écrit : > > > * A demo location with some minimal data should be part of the > installation and copied to some default palace for the first-time user. > > I like very much this o

Re: [GRASS-dev] New GUI startup discussion

at 1:22 PM Vaclav Petras wrote: > Dear all, > > We will meet to discuss ideas for the new startup of GRASS GIS > specifically using the GUI. The meeting will be a video call on Thursday > starting at 18:00 UTC. > > > https://www.timeanddate.com/worldclock/converter.html?iso=

Re: [GRASS-dev] New GUI startup discussion

The link to meeting today is below. We are starting in two hours at 18:00 UTC <https://www.timeanddate.com/worldclock/converter.html?iso=20200514T18=1440=204=195=51=207=671> . https://ncsu.zoom.us/j/94368491790?pwd=N21jNGlpelJiWEJ2dkoxTHBDT24ydz09 On Mon, May 11, 2020 at 1:22 PM

Re: [GRASS-dev] New GUI startup discussion

On Tue, May 12, 2020 at 12:03 AM Robert Lagacé wrote: > > It would nice to have the possibility to define a config file which > contain the basic (projection and datum reference data for the user area) > and we ask them to put it in some specific place in their dicrectory. When > Grass start

[GRASS-dev] New GUI startup discussion

Dear all, We will meet to discuss ideas for the new startup of GRASS GIS specifically using the GUI. The meeting will be a video call on Thursday starting at 18:00 UTC. https://www.timeanddate.com/worldclock/converter.html?iso=20200514T18=1440=204=195=51=207=671 This will be a great

Re: [GRASS-dev] Let's talk about releases - 7.8.3, 7.10, 8.0

On Thu, Apr 30, 2020 at 9:59 PM Vaclav Petras wrote: > Dear users and devs, > > I though it would be a good idea to video meet next week and talk about > what would be the best way of releasing GRASS GIS in the future. As always, > both contributors and users are invited

Re: [GRASS-dev] Let's talk about releases - 7.8.3, 7.10, 8.0

New URL (Zoom): https://ncsu.zoom.us/j/95921808290?pwd=UnVOa0VHN2gvbWJLbDExNEJ4TWU3Zz09 ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Let's talk about releases - 7.8.3, 7.10, 8.0

The link to meeting today is below. We are starting in two hours at 18:00 UTC . https://meet.jit.si/lets-talk-grass-releases ___ grass-dev mailing list

Re: [GRASS-dev] Let's talk about releases - 7.8.3, 7.10, 8.0

, Vaclav On Thu, Apr 30, 2020 at 9:59 PM Vaclav Petras wrote: > Dear users and devs, > > I though it would be a good idea to video meet next week and talk about > what would be the best way of releasing GRASS GIS in the future. As always, > both contributors and users are invited

[GRASS-dev] Let's talk about releases - 7.8.3, 7.10, 8.0

Dear users and devs, I though it would be a good idea to video meet next week and talk about what would be the best way of releasing GRASS GIS in the future. As always, both contributors and users are invited to share ideas and opinions. I'm thinking to meet for one hour. Here is a Doodle poll

Re: [GRASS-dev] Backport sync: merge mess

On Wed, Apr 8, 2020 at 5:13 PM Markus Neteler wrote: > Hi Vaclav, > > Thanks for your extensive explanations! Much appreciated. > > I think that I have probably found the missing part: I should have > deleted the *entire* directory. By just deleting my fork and re-adding > it as a "remote" I

Re: [GRASS-dev] Backport sync: merge mess

On Tue, Apr 7, 2020 at 5:06 PM Markus Neteler wrote: > > Thanks for your detailed reply, some comments inline: > > > On Tue, Apr 7, 2020 at 3:24 PM Vaclav Petras > wrote: > >> Fortunately, having Squash and merge saves the day here. Couple notes: > >>

Re: [GRASS-dev] Automatic/CI compilation on macOS

= sys.argv.index(batch_exec_param) > > ValueError: '--exec' is not in list > > > > During handling of the above exception, another exception occurred: > > > > Traceback (most recent call last): > > File "/usr/local/Cellar/osgeo-grass/7.8.2_3/libexec/bin/gras

Re: [GRASS-dev] [SOC] GSoC 2020 proposal

On Mon, Mar 30, 2020 at 7:36 AM Vishavdeep Singh wrote: > Dear GRASS community, > > I am Vishavdeep, a undergraduate student of Dr. BR. Ambedkar University, Agra > from India. I would like to work on a Seam integration of GRASS GIS and > jupyter notebook. It is a very important topic and I

Re: [GRASS-dev] grass on osgeo4w and spyder

On Tue, Mar 24, 2020 at 4:31 PM Helmut Kudrnovsky wrote: > pvanbosgeo wrote > > Hi devs, > > > > Has any of you experience in running Spyder (or any other Python IDE) > > from the GRASS command line (GRASS installed on Windows 10 with > > OSGeo4W)? Any tips for how to set this up? > > > > I can

Re: [GRASS-dev] Automatic/CI compilation on macOS

On Thu, Mar 5, 2020 at 1:52 PM Rainer M Krug wrote: > > > On 5 Mar 2020, at 17:53, Vaclav Petras wrote: > > > > On Thu, Mar 5, 2020 at 11:37 AM Rainer M Krug wrote: > >> OK - one step closer to success. Now I just have to know the location >> where the data

Re: [GRASS-dev] Automatic/CI compilation on macOS

able. You can try something along these lines. > > Rainer > > > > On 5 Mar 2020, at 16:28, Rainer M Krug wrote: > > > > On 5 Mar 2020, at 16:22, Rainer M Krug wrote: > > > > On 5 Mar 2020, at 14:52, Vaclav Petras wrote: > > > > On Thu, Mar 5

Re: [GRASS-dev] Automatic/CI compilation on macOS

On Thu, Mar 5, 2020 at 4:27 AM Rainer M Krug wrote: > OK - found the ci. > > The formula installs, but I get a warning at the end, which results in a > warning, which is than interpreted as an error. The warning (which I also > get locally) is the following: > > If it is the case that you can

Re: [GRASS-dev] silly question

t; Professor of Anthropology, School of Human Evolution & Social Change >> Head, Graduate Faculty in Complex Adaptive Systems Science >> Arizona State University >> >> voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC) >> fax: 480-965-7671 (SHESC), 480-727-

[GRASS-dev] Automatic/CI compilation on macOS

Dear all, I made some updates towards updating the conda recipe for GRASS GIS on macOS by Eric Hutton, but it is not working yet. You can find the WIP PR here: https://github.com/csdms-stack/grass-recipe/pull/1 You can see the current state in Travis linked from the PR or in GitHub Actions of

Re: [GRASS-dev] silly question

Thanks Anna for identifying this. Looks likely. Markus, Michael, I don't see the bad URL anywhere on Trac wiki, grasswiki, or in CONTRIBUTING.md file (as far as search works for URLs, it does at least for Trac). Michael, The CONTRIBUTING.md file has SSH URL for your fork and HTTPS for the OSGeo

[GRASS-dev] Adding path iconv library to ./configure

Dear all, In order to compile in a conda environment (where iconv is installed through conda, not in the system), I'm trying to add a path to icon into ./configure(.in). The issue is that although GRASS happens to configure properly, the compilation fails because libiconv.* is not found. I have

Re: [GRASS-dev] No module named grass.script

Hi Zoltan, On Sun, Feb 9, 2020 at 8:15 AM Zoltan Szecsei wrote: > > set > PYTHONPATH=%PYTHONPATH%;%OSGEO4W_ROOT%\apps\grass\grass78\etc\python\grass > The path needs to be just to ...\etc\python, grass is already the package name (you can examine the directory to see if there is __init__.py

Re: [GRASS-dev] local install addons on Windows

Hi Paulo, On Sun, Feb 2, 2020 at 8:58 AM Paulo van Breugel wrote: > > I am looking for a way to easily install addons on Windows that are > not in the official repository. This is currently not possible using > g.extension, because addons cannot be compiled on Windows. > > But what if I would

Re: [GRASS-dev] view trac tickets disabled?

Hi Markus, On Fri, Feb 7, 2020 at 3:40 PM Markus Metz wrote: > > now and then I want to view existing GRASS trac tickets, but going to > https://trac.osgeo.org/grass and clicking on "View Tickets" leads me to > https://github.com/OSGeo/grass/issues. Can this redirection be reverted, > please? I

Re: [GRASS-dev] Fwd: New Defects reported by Coverity Scan for grass

Hi Maris and Markus, On Tue, Feb 4, 2020 at 3:39 AM Maris Nartiss wrote: > Hello Markus, > as most of errors reported are legit, some of them are useless at the > current philosophy of GRASS GIS. We are OK with small memory leaks, as > modules are intended to be short running and then memory is

[GRASS-dev] Example project for a GRASS GIS module on GitHub

Dear users and contributors, I've created an example project (repository) on GitHub. It is a GRASS GIS module written in Python which simply adds two raster maps together. It uses GitHub Actions to build the module and publish its documentation as a website (using GitHub Pages).

Re: [GRASS-dev] communication of community sprint decisions

On Mon, Jan 13, 2020 at 3:00 PM Markus Neteler wrote: > On Mon, Jan 13, 2020 at 8:22 PM Vaclav Petras > wrote: > > On Sat, Jan 11, 2020 at 6:10 AM Markus Neteler > wrote: > >> Hi Prague-2019 sprinters, all, > >> > >> On Fri, Dec 20, 2019 at 8:52 AM Vac

Re: [GRASS-dev] communication of community sprint decisions

On Sat, Jan 11, 2020 at 6:10 AM Markus Neteler wrote: > Hi Prague-2019 sprinters, all, > > On Fri, Dec 20, 2019 at 8:52 AM Vaclav Petras > wrote: > > On Wed, Dec 18, 2019 at 9:44 AM Veronica Andreo > wrote: > >> > >> > >> I've been reading the d

Re: [GRASS-dev] Try GRASS GIS online: rollApp - rollapp.com

read-only mode? > There is a workaround: Change GRASS database directory to /tmp. Then, you can download a sample location and work with it. Perhaps a state GRASS could detect and switch to /tmp automatically. > Thanks, > Huidae > > On Fri, Dec 20, 2019 at 10:48 AM Vaclav Petras > wrot

[GRASS-dev] Try GRASS GIS online: rollApp - rollapp.com

Dear all, Following posts on Binder - mybinder.org [1] and CoCalc - cocalc.com [2, 3], I would like to introduce also rollApp - rollapp.com, another alternative for "Try online" link. It is a freemium service providing access to many (mostly) open source applications through a web browser (i.e.,

Re: [GRASS-dev] Try GRASS GIS online: CoCalc - cocalc.com

On Thu, Dec 19, 2019 at 7:14 AM Veronica Andreo wrote: > Hi > > El mié., 18 dic. 2019 19:06, Stefan Blumentrath < > stefan.blumentr...@nina.no> escribió: > >> Done. >> The CoCalc support team is on the issue. I also asked for a launcher >> button for GRASS GIS... >> >> Still, I have to mention,

Re: [GRASS-dev] communication of community sprint decisions

Hi Vero, On Wed, Dec 18, 2019 at 9:44 AM Veronica Andreo wrote: > > I've been reading the discussion page at: > https://grasswiki.osgeo.org/wiki/Talk:GRASS_GIS_Community_Sprint_Prague_2019 > and I see that we should open new bug reports or feature requests directly > in GitHub. When does this

[GRASS-dev] Keywords for r.null and in general

Hi all, I'm just seeking quick feedback on keywords for r.null module and adding some general questions for discussion if needed. I just added r.null.all to addons (do r.null for multiple maps) with keywords: raster map management null data no-data while MarkusN pointed out in the PR that

Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support

On Thu, Sep 5, 2019 at 7:18 AM Martin Landa wrote: > Hi, > > čt 5. 9. 2019 v 12:48 odesílatel Sebastiaan Couwenberg > napsal: > > > that's wrong, g.extension is using 'svn export' (for official repo). > > > > Using `svn export` for git repositories makes no sense/is a horrible > hack. > > I

Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support

On Thu, Sep 5, 2019 at 7:50 AM Sebastiaan Couwenberg wrote: > > On 9/5/19 12:54 PM, Markus Neteler wrote: > > Would shallow clone not clone the entire repo? But we only want a > > subdirectory out of it. > > `git clone --filter` may be an option, or restructure the repo with git > usage in mind

Re: [GRASS-dev] Unofficial GRASS test site down

On Sun, Aug 18, 2019, 12:41 PM Markus Neteler wrote: > Hi Vaclav, > > On Mon, Mar 11, 2019 at 6:21 PM Vaclav Petras > wrote: > > > > Hi Stefan, > > > > You just hit a (scheduled) power outage here. It is back online now. We > only missed two days

Re: [GRASS-dev] FOSS4G2019: State of GRASS GIS kind of presentation

On Mon, Aug 12, 2019 at 10:53 AM Markus Neteler wrote: > Hi, > > I am starting to prepare our talk > > "State of GRASS GIS Project: 35 years is nothing!" > https://talks.2019.foss4g.org/bucharest/talk/W3LWDV/ Hi Markus, I think in abstract you already list all things I presented in my two

[GRASS-dev] Try GRASS GIS online: CoCalc - cocalc.com

[was: Re: [GRASS-dev] Try GRASS GIS online: Binder - mybinder.org] On Thu, Aug 8, 2019 at 6:22 AM Stefan Blumentrath < stefan.blumentr...@nina.no> wrote: > > > For courses also: https://cocalc.com/ > > could be interesting. It does not (yet?) ship GRASS by default though. > The default

[GRASS-dev] Try GRASS GIS online: Binder - mybinder.org

Dear all, I would like GRASS GIS to have a page similar to these: https://jupyter.org/try "You can try Jupyter out right now, without installing anything." https://learngitbranching.js.org/ Learn by doing: Try Git commands right from your web browser. ( http://try.github.io/)

Re: [GRASS-dev] Docker image based on Alpine Linux with GRASS GIS 7.7.git and wxGUI

On Thu, Aug 1, 2019 at 1:22 PM Markus Neteler wrote: > Hi, > > On Thu, Aug 1, 2019 at 1:59 AM Vaclav Petras wrote: > > On Wed, Jul 31, 2019 at 11:41 AM Markus Neteler > wrote: > >> > >> In fact, $GISBASE/gui/wxpython/wxgui.py isn't present in the docker &g

Re: [GRASS-dev] Docker image based on Alpine Linux with GRASS GIS 7.7.git and wxGUI

On Wed, Jul 31, 2019 at 11:41 AM Markus Neteler wrote: > > In fact, $GISBASE/gui/wxpython/wxgui.py isn't present in the docker image. > > Do you have an idea what to look for (say, what does it (not) generate)? > Hi Markus, wxgui.py is a file copied from source to distribution by make, so the

Re: [GRASS-dev] extra verbosity in temporal commands

On Mon, Jul 29, 2019 at 7:45 PM Veronica Andreo wrote: > Hi devs, > > I have noticed since last week or so that every time I run a temporal > command, it clutters my terminal with "internal" stuff from the module. I > have not changed verbosity level. Could it be that some library change >

Re: [GRASS-dev] [GRASS-user] GRASS python + PyCharm

On Wed, Jun 12, 2019 at 5:09 PM Markus Neteler wrote: > On Wed, Jun 12, 2019 at 10:49 AM Helmut Kudrnovsky wrote: > > > > Hi, > > > > PyCharm is a nice python IDE. > > > > anyone some experiences to share how to integrate GRASS python (pygrass > and > > grass script) into the PyCharm IDE

Re: [GRASS-dev] instructions to update my local copy of trunk

On Sun, Jun 2, 2019 at 5:12 PM Markus Neteler wrote: > On Sun, Jun 2, 2019 at 10:52 PM Panagiotis Mavrogiorgos > wrote: > ... > > Markus wrote: > >> It there a way (magic flag?) to avoid this out-of-sync in the first > place? > >> E.g., for the cronjobs I do not want to go there weekly and "git

Re: [GRASS-dev] instructions to update my local copy of trunk

On Sun, Jun 2, 2019 at 9:01 PM Veronica Andreo wrote: > Ok, got it... the `git push origin` put my origin in sync with upstream. > So, for the way we have set remote/origin and remote/upstream, the update > goes from upstream to local and from local to origin, is that right? > Right. > Is

Re: [GRASS-dev] instructions to update my local copy of trunk

On Sun, Jun 2, 2019 at 4:11 PM Veronica Andreo wrote: > Hi Vaclav, > > El dom., 2 jun. 2019 a las 21:52, Vaclav Petras () > escribió: > >> >> >> On Sun, Jun 2, 2019 at 3:00 PM Veronica Andreo >> wrote: >> >>> Hi devs >>> >>

Re: [GRASS-dev] instructions to update my local copy of trunk

On Sun, Jun 2, 2019 at 3:00 PM Veronica Andreo wrote: > Hi devs > > Following instructions here: > https://trac.osgeo.org/grass/wiki/HowToGit#Keepyourlocalsourcecodeuptodate, > I get: > > [veroandreo@localhost grass7_trunk]$ git remote -v > origin g...@github.com:veroandreo/grass.git (fetch) >

Re: [GRASS-dev] black: Python code formatter (eg PEP8)

On Wed, May 29, 2019 at 4:07 AM Panagiotis Mavrogiorgos wrote: > > The main problem with adopting style checkers so late in a project's life > is that they usually introduce really vast changes. You practically end up > with a huge commit that touches each and every python file. Needless to say

Re: [GRASS-dev] Forestfrag WARNING: ZSTD compression error -14: Unsupported frame parameter

On Mon, May 27, 2019 at 3:25 PM Paulo van Breugel wrote: > Hi Václav / devs > > I am running r.forestfrag in Windows 10, grass 7.6.2 Computation with a > moving window size of 21 (but at another computer same happens at size 9) > gives met the following error: >

Re: [GRASS-dev] grass-addons on github

On Mon, May 27, 2019 at 3:12 AM Rainer M Krug wrote: > Disadvantage: From the GitHub blog: > > >- Managing dynamic, rapidly evolving or heavily co-dependent >repositories with submodules can quickly become frustrating. This post was >focused on simple, relatively static parent-child

Re: [GRASS-dev] grass-addons on github

On Fri, May 24, 2019 at 2:48 AM Paulo van Breugel wrote: > > Are we working with a central repository (OSGeo/grass-addons) and follow > the same protocol as for OSGEO/grass. If so, who will be responsible for > approving pull requests? An alternative more like the old situation is that > authors

Re: [GRASS-dev] git: how to avoid bogus merge commits

On Wed, May 22, 2019 at 3:31 PM Markus Metz wrote: > > Of course I could (should) do a "git pull" before a "git push", but I > think it is not uncommon that someone forgets the "git pull" before the > "git push". > It is not that executing push before pull causes problems. You simply need to do

Re: [GRASS-dev] git merge mess on master

ass/commit/2ff8d1e762d646dd8be82b8da483d12c2a772c26 [2] https://git-man-page-generator.lokaltog.net/ On Tue, May 21, 2019 at 1:12 PM Vaclav Petras wrote: > > > On Tue, May 21, 2019 at 7:48 AM Markus Neteler wrote: > >> On Tue, May 21, 2019 at 11:23 AM Bas Couwenberg >> wrote: >> >

Re: [GRASS-dev] black: Python code formatter (eg PEP8)

On Mon, May 20, 2019 at 8:31 AM Markus Neteler wrote: > > Back - Python code formatter (eg. PEP8) > https://github.com/python/black I like that, although I don't understand why they didn't decide for 4 spaces for first indent level and 1 tab for the second one ;-) But on a serious note: > Would

Re: [GRASS-dev] git merge mess on master

On Tue, May 21, 2019 at 7:48 AM Markus Neteler wrote: > On Tue, May 21, 2019 at 11:23 AM Bas Couwenberg > wrote: > > On 2019-05-21 11:22, Markus Neteler wrote: > > > How to revert that? Of course someone had to run into this at some > > > point, so seems I "volunteered" to be the first :(( > >

Re: [GRASS-dev] Segment library zero filling

On Mon, May 20, 2019 at 1:46 PM Markus Metz wrote: > > On Mon, May 20, 2019 at 7:18 PM Vaclav Petras > wrote: > > > > On Mon, May 20, 2019 at 11:57 AM Markus Metz < > markus.metz.gisw...@gmail.com> wrote: > >> > >> On Mon, May 20, 2019 at 5:39 PM

Re: [GRASS-dev] Segment library zero filling

On Mon, May 20, 2019 at 11:57 AM Markus Metz wrote: > > > On Mon, May 20, 2019 at 5:39 PM Vaclav Petras > wrote: > > > > Hi MarkusM and all, > > > > I'm trying to understand if the Segment_open() [1] function fills with > zeros or not. I don't think it do

[GRASS-dev] Segment library zero filling

Hi MarkusM and all, I'm trying to understand if the Segment_open() [1] function fills with zeros or not. I don't think it does since it is calling G_malloc (malloc) or Segment_format_nofill(). However, it is not completely clear to me what is supposed to be doing because documentation still says

Re: [GRASS-dev] wingrass builds down

On Sun, May 19, 2019 at 2:03 PM Martin Landa wrote: > > This opens long time planned question. Do we really need to provide > WinGRASS 32bit builds. Only 64bit builds would enough probably. Any > opinion? Ma Do we have download statistics for 32bit installers?

Re: [GRASS-dev] svn/trac -> git/github migration plan

On Sat, May 18, 2019 at 12:11 PM Markus Neteler wrote: > > On Sat, May 18, 2019 at 5:59 PM Panagiotis Mavrogiorgos > wrote: > > > > I would suggest that: > > > > - even core devs fork the main repo > > - "origin" is the personal remote GRASS repository (e.g. in my case >

Re: [GRASS-dev] grass-addons git repo clean-up

On Sun, May 19, 2019 at 8:50 AM Martin Landa wrote: > Hi, > > ne 19. 5. 2019 v 11:52 odesílatel Martin Landa > napsal: > > > * tools/ content could be moved to a new git repo, > > > `grass-maintenance-tools` (any idea for better name). > > another option is to keep tools in `grass-addons` repo,

Re: [GRASS-dev] svn/trac -> git/github migration plan

Hi Panos and all, On Fri, May 17, 2019 at 5:09 AM Panagiotis Mavrogiorgos wrote: > > I would argue that even core developers should not be using the main repo > as their > personal one and that, at least most of the time, they should instead be > using the same > procedure as every other

Re: [GRASS-dev] svn/trac -> git/github migration plan

On Thu, May 16, 2019 at 8:26 AM Bas Couwenberg wrote: > > On 2019-05-16 14:16, Markus Neteler wrote: > > External contributors > > # workflow for external contributors - they have to fork the repo in > > GitHub Web interface > > # create fork via github GUI > > git clone $my_for_url > > #

Re: [GRASS-dev] svn/trac -> git/github migration plan

On Thu, May 16, 2019 at 2:07 AM Martin Landa wrote: > Hi, > > st 15. 5. 2019 v 18:20 odesílatel Vaclav Petras > napsal: > > Another thing is the need for new contributing guidelines. Git is not > Subversion and committing to master won't work (please, let me know if you &

Re: [GRASS-dev] svn/trac -> git/github migration plan

On Wed, May 15, 2019 at 4:24 PM Markus Neteler wrote: > > On Wed, May 15, 2019 at 10:20 PM Luca Delucchi wrote: > > On Wed, 15 May 2019 at 21:40, Veronica Andreo wrote: > > >> Another thing is the need for new contributing guidelines. Git is not Subversion and committing to master won't work

Re: [GRASS-dev] svn/trac -> git/github migration plan

On Wed, May 15, 2019 at 12:47 PM Markus Neteler wrote: > > Later on, also commit claiming is possible and easy, so nothing is lost. > Sounds good. I didn't know. We just have to be very clear about the current state not capturing everyone. ___

Re: [GRASS-dev] svn/trac -> git/github migration plan

On Wed, May 15, 2019 at 9:14 AM Martin Landa wrote: > Hi, > > st 15. 5. 2019 v 9:51 odesílatel Martin Landa > napsal: > > Something strange happen with svn repo after r74441. I will publish > > testing repo for public review hopefully today. > > OK, finally a new fresh grass repo preview

Re: [GRASS-dev] Benchmark the overhead of calling GRASS modules

environment. Master’s thesis. Czech Technical University in Prague. http://geo.fsv.cvut.cz/proj/dp/2013/vaclav-petras-dp-2013.pdf On Wed, May 1, 2019 at 6:03 PM Markus Metz wrote: > Hi Panos, > > IMHO the overhead of calling GRASS modules is insignificant because it is > in the range of mil

Re: [GRASS-dev] GSoC Proposal: Python package for topology tools

Hello Facundo, Using the GRASS GIS algorithms in various settings is certainly something we are aiming for. However, as you probably understood from the conversation here, it is not clear what exactly you are trying to achieve considering the already available ways (APIs if you will). Also, to

Re: [GRASS-dev] Shell scripts for tests

Hi Panos, That sounds good, please see the details inline. On Fri, Mar 29, 2019 at 8:27 AM Panagiotis Mavrogiorgos wrote: > > The GRASS testsuite contains several tests that have been written as shell > scripts. If I am not mistaken, those can be identified by the "unknown" > percentages in

Re: [GRASS-dev] Unofficial GRASS test site down

Hi Stefan, You just hit a (scheduled) power outage here. It is back online now. We only missed two days of actual runs which is not a big deal (no running for the past states, next scheduled one is for tomorrow/this night). Glad to hear you find it useful! Vaclav On Mon, Mar 11, 2019 at 4:40 AM

Re: [GRASS-dev] Migration to git, use addons as test case?

On Thu, Jan 24, 2019 at 3:12 AM Luca Delucchi wrote: > > > On Tue, 22 Jan 2019 at 08:09, Stefan Blumentrath < > stefan.blumentr...@nina.no> wrote: > >> >> Just wondering, regarding migration to git, would it be helpful to use >> AddOns (and possibly sandbox) as a test case? >> >> > yes this

Re: [GRASS-dev] Testsuite: script for easier use of test framework

On Mon, Jan 21, 2019 at 5:34 PM Markus Neteler wrote: > On Mon, Jan 21, 2019 at 11:14 PM Vaclav Petras > wrote: > > On Mon, Jan 21, 2019 at 3:59 PM Markus Neteler > wrote: > >> On Mon, Jan 21, 2019 at 9:34 PM Vaclav Petras > wrote: > ... > >> > OK

Re: [GRASS-dev] Testsuite: script for easier use of test framework

On Mon, Jan 21, 2019 at 3:59 PM Markus Neteler wrote: > On Mon, Jan 21, 2019 at 9:34 PM Vaclav Petras > wrote: > > On Mon, Jan 21, 2019 at 3:08 PM Markus Neteler > wrote: > >> > >> On Mon, Jan 21, 2019 at 1:48 AM Vaclav Petras > wrote: > >>

Re: [GRASS-dev] Testsuite: script for easier use of test framework

On Mon, Jan 21, 2019 at 3:08 PM Markus Neteler wrote: > On Mon, Jan 21, 2019 at 1:48 AM Vaclav Petras > wrote: > ... > > Any reason for the file, i.e. can this be in the documentation? > > Not only because... > > > Or do you want a simpler example in doc

Re: [GRASS-dev] Testsuite: script for easier use of test framework

On Sun, Jan 20, 2019 at 12:02 PM Markus Neteler wrote: > On Fri, Jan 18, 2019 at 2:00 AM Vaclav Petras > wrote: > > On Thu, Jan 17, 2019 at 11:11 AM Markus Neteler > wrote: > ... > >> > I changed the location on fatra to full NC SPM and did the rename as >

Re: [GRASS-dev] [GRASS-SVN] r73973 - in grass/trunk/testsuite: . examples

On Fri, Jan 18, 2019 at 12:33 AM wrote: > Author: neteler > Date: 2019-01-17 21:33:12 -0800 (Thu, 17 Jan 2019) > New Revision: 73973 > > Added: >grass/trunk/testsuite/examples/ >grass/trunk/testsuite/examples/test_framework_GRASS_GIS_with_NC.sh > Removed: >

Re: [GRASS-dev] Testsuite: script for easier use of test framework

On Thu, Jan 17, 2019 at 11:11 AM Markus Neteler wrote: > On Wed, Jan 16, 2019 at 9:53 PM Vaclav Petras > wrote: > ... > (just quickly while being busy right now) > > > I changed the location on fatra to full NC SPM and did the rename as you > suggested. I don't know

Re: [GRASS-dev] Testsuite: script for easier use of test framework

On Wed, Jan 16, 2019 at 12:00 PM Markus Neteler wrote: > > @Vaclav Petras > Maybe a workaround for the online test system at > http://fatra.cnr.ncsu.edu/grassgistests/summary_report/ > ? > Hi Markus, the reason I didn't do that was I was hoping we either decide which one

Re: [GRASS-dev] On `svn propset`

On Sun, Jan 13, 2019 at 12:59 PM Nikos Alexandris wrote: > > The properties seem to be already set and there is no need to re-set them. > Perhaps, once set for a file, in an SVN repository, there is no need for > a re-set? Even if actually replacing a file (instead of updating it) > with a file

Re: [GRASS-dev] [release planning] GRASS GIS 7.4.4 - as a "friendship release" for QGIS

On Fri, Jan 11, 2019 at 9:32 AM Veronica Andreo wrote: > El vie., 11 ene. 2019 a las 14:47, Vaclav Petras () > escribió: > >> Hi, I'm kindly asking whoever with access to update the website. The >> release announcement contains the links to the 7.4.4 for Win binaries, bu

Re: [GRASS-dev] [release planning] GRASS GIS 7.4.4 - as a "friendship release" for QGIS

Hi, I'm kindly asking whoever with access to update the website. The release announcement contains the links to the 7.4.4 for Win binaries, but the Win download page is not updated for 7.4.4 (7.4.3 there). https://grass.osgeo.org/download/software/ms-windows/

Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support

On Wed, Jan 9, 2019 at 10:01 AM Maris Nartiss wrote: > > trešd., 2019. g. 9. janv., plkst. 14:18 — lietotājs Laurent C. > () rakstīja: > > > > I believe that only a major release could be allowed to break a previously working functionality. It would be very confusing to have a code that work on

Re: [GRASS-dev] Documentation glitch

On Fri, Nov 23, 2018 at 10:32 AM Luí­s Moreira de Sousa < luis.de.so...@protonmail.ch> wrote: > > I bumped over a glitch with the documentation for r.out.gdal. One of the > examples is: > r.out.gdal in=elevation output=elevation.tif type=Float64 \ > createopt="COMPRESS=DEFLATE" > > But

Re: [GRASS-dev] v.clip and latlon?

On Sun, Nov 25, 2018 at 6:16 PM Michael Barton wrote: > Can do. Wanted to check first so as not to duplicate anything (search in > Trak leaves much to be desired). > I agree, but mostly because there is this hard split between full text search and query. The is no "fuzz search" so when somebody

Re: [GRASS-dev] v.clip and latlon?

On Sun, Nov 25, 2018 at 12:12 PM Michael Barton wrote: > Does v.clip have a problem or not work with latlon regions? I've been > trying to clip the gshhs coastline vector with a region and an area > generated from a region. In all cases, after half hour of running it comes > up with an empty

Re: [GRASS-dev] [GRASS-SVN] r73692 - grass/trunk/lib/init

On Sat, Nov 24, 2018 at 9:58 PM Vaclav Petras wrote: > > On Sat, Nov 24, 2018 at 5:54 AM Markus Metz > wrote: > >> >> >> On Thu, Nov 22, 2018 at 11:33 PM Vaclav Petras >> wrote: >> >> > That's all correct. There would have to be m

Re: [GRASS-dev] [release planning] GRASS GIS 7.4.3

On Sat, Nov 24, 2018 at 5:27 AM Pedro Venâncio wrote: > Hi all, > > When do you think the new r.mapcalculator can be introduced in GRASS core? > > https://trac.osgeo.org/grass/ticket/3431 > > It would be great to be introduced in one of the 7.4.x release cicle, to > be used with QGIS 2.18.x. >

Re: [GRASS-dev] [GRASS-SVN] r73692 - grass/trunk/lib/init

On Sat, Nov 24, 2018 at 5:54 AM Markus Metz wrote: > > > On Thu, Nov 22, 2018 at 11:33 PM Vaclav Petras > wrote: > > > That's all correct. There would have to be more to make it the same > procedure as in grass.py, but eventually we need to do that. >

Re: [GRASS-dev] [GRASS-SVN] r73692 - grass/trunk/lib/init

On Thu, Nov 22, 2018 at 10:57 AM Markus Metz wrote: > > > On Thu, Nov 22, 2018 at 3:31 PM Vaclav Petras > wrote: > > > > > > > > On Wed, Nov 21, 2018 at 2:12 PM Martin Landa > wrote: > >> > >> Hi, > >> > >> st 21.

Re: [GRASS-dev] [GRASS-SVN] r73692 - grass/trunk/lib/init

On Wed, Nov 21, 2018 at 2:12 PM Martin Landa wrote: > Hi, > > st 21. 11. 2018 v 20:05 odesílatel napsal: > > +# clean the sqlite db > > +from grass.script import db as gdb > > +from grass.script import core as gcore > > +conn = gdb.db_connection() > > +if

Re: [GRASS-dev] GRASS 7.4.2 won't configure on Mac

configure, the change is in your system. > > > On Nov 12, 2018, at 9:04 PM, Vaclav Petras wrote: > > Since it's complaining about /lib/cpp, > > ./configure: line 5164: /lib/cpp: No such file or directory > > I would say the problem is not zlib, but missing C++ compiler (at l

Re: [GRASS-dev] GRASS 7.4.2 won't configure on Mac

Since it's complaining about /lib/cpp, ./configure: line 5164: /lib/cpp: No such file or directory I would say the problem is not zlib, but missing C++ compiler (at least on my machine, /lib/cpp eventually points to /usr/bin/cpp-5), although I don't know why ./configure would catch that problem

Re: [GRASS-dev] Issue with G76 in docker: creating a location fails in codecs.py

On Fri, Nov 9, 2018 at 6:39 PM Markus Neteler wrote: > Hi, > > while we meanwhile use GRASS GIS 7.6.svn in docker for months we ran > into this issue today: > > root@52e6935c3247:/grassdb# grass76 --text c 'EPSG:4326' > /actinia_core/grassdb/latlongtest > Cleaning up temporary files... >

Re: [GRASS-dev] [GRASS-user] Example project on GitLab

On Wed, Nov 7, 2018 at 8:47 AM Bernardo Santos < bernardo_brand...@yahoo.com.br> wrote: > > thanks for that, it'll be very useful. I think a similar approach can be > used to build repositories for addons within GitHub, right? > Yes, when you involve Travis CI. > Do you see clear advantages of

Re: [GRASS-dev] [GRASS-user] Example project on GitLab

On Mon, Nov 5, 2018 at 2:43 PM Ken Mankoff wrote: > I think I will find it useful in helping some of my custom scripts to > official plugins. > Glad to hear that! Thanks for sharing your code! > On Fri, Nov 2, 2018 at 7:08 PM Vaclav Petras wrote: > >> Dear users and dev

[GRASS-dev] Example project on GitLab

Dear users and devs, I've created an example project at GitLab. It is a GRASS GIS module written in Python. It uses GitLab CI to build the module and publish its documentation as a website. https://gitlab.com/vpetras/r.example.plus If you are familiar with GitHub, GitLab will feel familiar as

Re: [GRASS-dev] Wrong or broken doc package for Ubuntu?

On Wed, Oct 31, 2018 at 12:02 PM Bas Couwenberg wrote: > On 2018-10-31 16:51, Vaclav Petras wrote: > > Am I missing something? Is the package broken? Should I open a ticket > > and > > where? > > Doesn't look like the package is broken: > > $ wget -q > >

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