Re: [GRASS-dev] Debugging, parallelism, etc.

Am 09.10.2022 20:45 schrieb Brad ReDacted: Those variables would be...? Is this documented somewhere? If not, can we get it documented? https://grasswiki.osgeo.org/wiki/Working_with_GRASS_without_starting_it_explicitly OpenMP can do far more than just loop "unrolling", these days. Tasking

Re: [GRASS-dev] multiprocessing problem

Hi Luca, Just two brainstorming ideas: - From a rapid glance at the code it seems to me that you create a separate worker for each row in the raster. Correct ? AFAIR, spawning workers does create quite a bit of overhead. Depending on the row to column ratio of your raster, maybe you would be

Re: [GRASS-dev] Invitation: End of year toast :)

Hi everyone, Won't be able to join you tonight. I wish everyone a happy new year 2022 with many great releases of GRASS GIS ! Moritz Le 27 décembre 2021 13:46:10 GMT+01:00, Veronica Andreo a écrit : >Dear all, > >We'd like to invite you all to a virtual end of year toast on *Wednesday,

Re: [GRASS-dev] Release of 7.8.6 ?

Great news ! Thanks a lot for all your work, Martin ! Moritz Le 11 octobre 2021 13:14:45 GMT+02:00, Martin Landa a écrit : >Dear all, > >čt 7. 10. 2021 v 23:21 odesílatel Veronica Andreo >napsal: >>> > Let's release 7.8.6 as it is (with an already big delay). If there are >>> > no objections

Re: [GRASS-dev] Release of 7.8.6 ?

Martin, Vaclav, Where are we at concerning the 7.8.6 release ? Did you work on this during your code sprint ? (sorry I was busy with a code sprint of my own at work, so I couldn't join). Moritz Am 03.10.2021 10:13 schrieb Nicklas Larsson: Hi All! There are some fixes that are labeled for

Re: [GRASS-dev] Community sprint at FOSS4G 2021

Hi all, I wanted to at least pop by and say hi, but I don't see anyone on the map in the code sprint room. There are four different jitsi meeting rooms in that map, but only one is currently used. If we decide to use another Jiitsi link for GRASS GIS discussions, we are asked to include

[GRASS-dev] Release of 7.8.6 ?

Hi everyone, Colleagues of mine are being bitten by https://github.com/OSGeo/grass/issues/1793 while teaching. It seems that wxpython 4.1 is becoming more widespread and so more and more people seem victim to this. I was unaware of this bug. IMHO it probably should have warranted a quick

[GRASS-dev] Fwd: [GRASS-web] New GIS mirror in Rabat, Morocco

FYI I think this needs some configuration because to get to the web site you need to go to https://mirror.marwan.ma/grass/html, but then none of the internal links work. Does someone have more experience with mirroring than me and can give some hints here ? Moritz Forwarded

Re: [GRASS-dev] [SoC] GSoC 2021 - Final Report [Parallelization of raster modules for GRASS GIS]

, either by checking into the branch, or on your local machine, you can rebase the branch on top of the current main branch (I don't think there will be any conflicts) Let me know if there are any issues :) Warm regards, Aaron - FROM: Moritz Lennert SENT: Monday, 13

Re: [GRASS-dev] [SoC] GSoC 2021 - Final Report [Parallelization of raster modules for GRASS GIS]

Hi Aaron, I have a use case for which I would like to try the parallelized r.neighbors. Do I just have to apply PR 1724 to current main to be able to do this, or do I have to do something else ? Moritz Am 25.08.2021 15:59 schrieb Aaron Saw Min Sern: Hi all, Thanks Vero for spotting the

[GRASS-dev] GRASS GIS moves to Open Collective for collecting donations and thanks its many financial contributors

Dear all, In order to make money donations easier, the GRASS GIS project has decided to use the Open Collective platform with the Open Source Geospatial (OSGeo) Foundation as its fiscal host: https://opencollective.com/grass. You can donate money via credit card, PayPal, or bank transfer

Re: [GRASS-dev] GitHub Discussions is enabled

Am 03.09.2021 09:29 schrieb Nikos Alexandris: Dear all, GitHub Discussions is enabled (https://github.com/OSGeo/grass/discussions/1841) -- obviously and clearly _not_ replacing the mailing lists. Warm regards, Nikos Thanks, Nikos, for the dedication you are showing for this and for being

Re: [GRASS-dev] [release planning] GRASS GIS 8: create new release branch

Le 16 août 2021 18:20:42 GMT+02:00, Veronica Andreo a écrit : >Hi all, > >El vie, 6 ago 2021 a las 4:29, Vaclav Petras () >escribió: > >> Are we ready to create the 8.0 release branch? >> > >Seems we are!! > >Once we create it, we will need to backport (cherry-pick) updates from the >> master

Re: [GRASS-dev] [SoC] GSoC 2021 - Parallelization of raster modules for GRASS GIS

Hi Aaron, I haven't had the chance to test all this, yet, but it's great work ! One suggestion: Le 9 août 2021 14:44:43 GMT+02:00, Aaron Saw Min Sern a écrit : >Hi everyone, > >Week 9 has concluded and here's my report for this week. > >1) What did I get done this week? > >r.univar

Re: [GRASS-dev] [release planning] GRASS GIS 8: create new release branch

Le 29 mai 2021 08:58:59 GMT+00:00, Markus Neteler a écrit : >If there are no objections I'd merge PR 1597 in the next days. +1 I think at this stage it should just happen, especially if it's a throw-away branch. Moritz ___ grass-dev mailing list

Re: [GRASS-dev] [release planning] Enable Zenodo before 7.8.6 and 8.0.0

Clear +1 from me. Moritz Le 24 mai 2021 03:08:06 GMT+01:00, Vaclav Petras a écrit  : >Hi all, > >Let's enable the Zenodo link before 7.8.6 and 8.0(.0?) releases to get DOIs >and Zenodo records. > >Solving the whole DOI linking and Zenodo archiving for the old versions may >be complex [1], but

Re: [GRASS-dev] GSoC welcome

Welcome and congratulations to all three of you ! I'm looking forward to your three exciting projects. Moritz On 18/05/21 05:12, Anna Petrášová wrote: Hi GRASS devs and new (and old) GSoC students! Congrats to Linda, Caitlin and Aaron for being selected to participate in GSoC this year [1],

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

that is looking for info that it shouldn't look for. Moritz -Original Message- From: grass-dev On Behalf Of Moritz Lennert Sent: torsdag 6. mai 2021 08:10 To: grass-dev@lists.osgeo.org; Markus Neteler ; GRASS developers list Subject: Re: [GRASS-dev] [release planning] GRASS GIS 7.8.6 Am

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

Am 5. Mai 2021 23:03:04 MESZ schrieb Markus Neteler : >Hi devs, > >On Mon, Apr 12, 2021 at 7:33 PM Markus Neteler wrote: >> On Sun, Mar 21, 2021 at 9:21 AM Markus Neteler wrote: >> ... >> > What's still to be done for 7.8.6? See the 7.8.6 milestone, it is >> > showing the remaining open

Re: [GRASS-dev] Add-ons not building since January

On 16/03/21 14:45, Anna Petrášová wrote: On Tue, Mar 16, 2021 at 8:55 AM Moritz Lennert mailto:mlenn...@club.worldonline.be>> wrote: On 16/03/21 06:57, Luca Delucchi wrote: > On Tue, 16 Mar 2021 at 01:10, Veronica Andreo mailto:veroand...@gmail.com>> wrote:

Re: [GRASS-dev] Add-ons not building since January

On 16/03/21 06:57, Luca Delucchi wrote: On Tue, 16 Mar 2021 at 01:10, Veronica Andreo wrote: Hi devs, Hi Vero, I'm teaching a GRASS course and one of the students using windows told me that he didn't have i.landsat.qa. Checking the log, the last building date seems to be January 26th

Re: [GRASS-dev] [GRASS-PSC] Min. req. of programming language standard support, GRASS GIS 8

On 26/02/21 19:44, Veronica Andreo wrote: Dear Nicklas, Thanks much for such a clearly written RFC! I only made very minor cosmetic changes. Are there any other comments, objections or suggestions? Or further aspects to be discussed? If no, maybe we can vote on it soon-ish, no? No

Re: [GRASS-dev] Need a mentor for GSoC parallelization topic

Hi Huidae, Am 18. Februar 2021 06:05:09 MEZ schrieb Huidae Cho : >Thanks. I'm not familiar with the process. The deadline for mentoring >organization applications is approaching. Have we already applied with all >those project ideas in the wiki (one application per organization I guess, >not per

Re: [GRASS-dev] [GRASS-user] Code sprint is now (OGC-OSGeo-ASF 2021)

Am 17. Februar 2021 17:40:03 MEZ schrieb Luca Delucchi : >Hi all, > >On Wed, 17 Feb 2021 at 17:29, Vaclav Petras wrote: >> >> Code sprint is now! >> > >I'm trying to connect sometime, specially during Italian evening time > >> >> Post you plan here: >> >>

Re: [GRASS-dev] Min. req. of programming language standard support, GRASS GIS 8

gt; > > On Thursday, 11 February 2021, 12:54:30 CET, Moritz Lennert > wrote: > > On 10/02/21 13:16, Nicklas Larsson wrote: >> It would be most favourable for all contributors and the project if the >> community could come to an agreement on this topic. I see no

Re: [GRASS-dev] Min. req. of programming language standard support, GRASS GIS 8

On 10/02/21 13:16, Nicklas Larsson wrote: It would be most favourable for all contributors and the project if the community could come to an agreement on this topic. I see no reason to postpone a decision on this much longer. The final word on this need to be that of the PSC's. Whether

[GRASS-dev] Elections results and new GRASS GIS PSC

Landa (83) * Verónica Andreo (76) * Moritz Lennert (74) * Václav Petráš (68) * Michael Barton (58) * Huidae Cho (56) For completeness, all relevant candidacy communications, as well as details about the voting process, have been published at:https://trac.osgeo.org/grass/wiki/PSC/Election2020

Re: [GRASS-dev] Should we use GitHub Discussions?

On 9/02/21 10:00, Markus Neteler wrote: On Tue, Feb 9, 2021 at 5:40 AM Vaclav Petras wrote: On Tue, Feb 2, 2021 at 5:49 PM Luca Delucchi wrote: On Thu, 21 Jan 2021 at 08:49, massimo di stefano wrote: ‘’’ I think emails (and mailing lists) are awesome, but mailing lists are increasingly

Re: [GRASS-dev] Min. req. of programming language standard support, GRASS GIS 8

Am 7. Februar 2021 05:01:38 MEZ schrieb "Anna Petrášová" : >On Wed, Feb 3, 2021 at 2:47 PM Anna Petrášová wrote: > >> >> >> On Tue, Feb 2, 2021 at 11:20 AM Nicklas Larsson >> wrote: >> >>> >>> >>> >>> >>> >>> On Friday, 29 January 2021, 18:50:34 CET, Anna Petrášová < >>>

[GRASS-dev] Support GRASS GIS financially !

Dear all, We just received our very first sponsorship contribution of 2021 (thank you !) and we want to take this occasion to thank all those who sponsored us last year and remind you that the GRASS GIS project needs financial support in order to: - organize very valuable face-to-face

Re: [GRASS-dev] Min. req. of programming language standard support, GRASS GIS 8

Am 31. Januar 2021 22:15:53 MEZ schrieb Markus Metz : >On Fri, Jan 29, 2021 at 11:19 PM Moritz Lennert < >mlenn...@club.worldonline.be> wrote: >> >> >> >> Am 29. Januar 2021 20:54:06 GMT+00:00 schrieb Markus Metz < >markus.metz.gisw...@gmail.com>:

Re: [GRASS-dev] Min. req. of programming language standard support, GRASS GIS 8

Am 29. Januar 2021 20:54:06 GMT+00:00 schrieb Markus Metz : >Hi Huidae, > >On Thu, Jan 28, 2021 at 6:30 PM Huidae Cho wrote: >> >> Markus, >> >> I think we have to think about what benefits it would bring to us by >modernizing C code. Probably, not much at all. Personally, I would keep it >as

Re: [GRASS-dev] [GRASS GIS Elections 2020] Voting phase closed, presentation of results

Wiki. > > >Voting result (ranking, name, number of votes): > > 1. Markus Neteler 95 > 2. Anna Petrášová 88 > 3. Helena Mitasova 86 > 4. Martin Landa 83 > 5. Verónica Andreo76 > 6. Moritz Len

Re: [GRASS-dev] Should we use GitHub Discussions?

I hear your arguments, Vaclav, and understand that new generations have other approaches to communication on the net, and use other tools. I have been confronted with students to whom I suggested to ask their questions on a mailing list only to realize a bit later that they had no idea what a

Re: [GRASS-dev] Should we use GitHub Discussions?

Am 17. Januar 2021 06:31:22 MEZ schrieb Vaclav Petras : >Dear all, > >What about enabling GitHub Discussions [1] on grass repo? Enabling is easy >[2], so the question really is, do we want them? They are for open ended >discussions, questions, etc. Right, like mailing list, but on GitHub. We do

Re: [GRASS-dev] minor tweak to new website

Am 15. Januar 2021 17:35:43 MEZ schrieb Michael Barton : >On the new download pages, I just noticed that the dev versions are referenced >like this: > >GRASS GIS 7.9 devel (unstable) > >This implies that GRASS 7.9 is risky and perhaps minimally useable. The >reality is that it works very well

[GRASS-dev] Statement Moritz Lennert

Dear all, I thank those who nominated me for putting my name up once again. Most of you will have seen me around as I'm one of the old ones, active in the GRASS GIS community for over 20 years now. In the past I've have worked on many different parts of GRASS: documentation, the first

Re: [GRASS-dev] [GRASS GIS] #2895: Define dependencies for GRASS addons

Am 18. Dezember 2020 09:57:53 MEZ schrieb GRASS GIS : >#2895: Define dependencies for GRASS addons >--+- > Reporter: pmav99 | Owner: grass-dev@… > Type: enhancement | Status: new > Priority: normal | Milestone:

Re: [GRASS-dev] Call for candidates for Chief Return Officer(s) to oversee election of new Project Steering Committee

Dear all, Many thanks to Hernán De Angelis who has agreed to serve as CRO ! We will put things in place with him to launch the entire process as soon as possible. Moritz Am 10. Dezember 2020 09:14:55 MEZ schrieb Moritz Lennert : >Dear all, > >As part of the effort to guarante

[GRASS-dev] Call for candidates for Chief Return Officer(s) to oversee election of new Project Steering Committee

Dear all, As part of the effort to guarantee a solid and sustainable governance of GRASS GIS development, and in accordance with OSGeo guidelines, we have a Project Steering Committee (PSC) [1]. Although most decisions are taken by consensus via the mailing lists or via discussions in github

Re: [GRASS-dev] Read-access to data in a different location with same SRS

Am 19. November 2020 15:52:18 MEZ schrieb "Anna Petrášová" : >Hi, > >On Thu, Nov 19, 2020 at 8:02 AM Moritz Lennert >wrote: > >> Hi, >> >> It was great seeing some of you last night via jitsi ! >> > >indeed! > >> >> In t

[GRASS-dev] Read-access to data in a different location with same SRS

Hi, It was great seeing some of you last night via jitsi ! In the context of the discussion of "location" vs "project", several of us pointed to the fact that we organize our data into locations by reference system with mapsets as project directories. PERMANENT (and other mapsets) can then be

Re: [GRASS-dev] [GRASS-user] Fwd: [OSGeo-Discuss] Reminder: OSGeo Virtual Community Sprint 2020 (17-19 November 2020)

Hi everyone, As several of you know already I've left the university and started a new job (at https://bluesquarehub.com/ for those of you who are curious). Because of that I don't have as much time for GRASS GIS development currently. However, if there is a specific meetting planned during

Re: [GRASS-dev] Milestone management: 7.8.5 or 7.10 or 8.0.0?

On 11/10/20 19:15, Martin Landa wrote: Hi, so 10. 10. 2020 v 18:21 odesílatel Markus Neteler napsal: let's split obvious milestone from to-be-decided milestone. we need to decide about the next milestone: do we want - 7.8.5, or refers to releasebranch_7_8 branch. GRASS 7.8.4 has been

Re: [GRASS-dev] what use are the mysites and point maps in the demolocation ?

On 4/08/20 23:16, Markus Neteler wrote: On Tue, Aug 4, 2020 at 3:24 PM Moritz Lennert wrote: Hello, In the context of the complete revamping of the GRASS GIS GUI startup, the idea is to use the existing demolocation as a possible basis for a direct entry into GRASS GIS without going through

[GRASS-dev] what use are the mysites and point maps in the demolocation ?

Hello, In the context of the complete revamping of the GRASS GIS GUI startup, the idea is to use the existing demolocation as a possible basis for a direct entry into GRASS GIS without going through complicated location setup (which will then be offered through the data catalog). In that

Re: [GRASS-dev] packagers' guidance on inclusion of small dataset into the GRASS GIS installation

On 3/08/20 17:44, Sebastiaan Couwenberg wrote: On 8/3/20 4:59 PM, Moritz Lennert wrote: On 3/08/20 16:37, Sebastiaan Couwenberg wrote: On 8/3/20 4:16 PM, Moritz Lennert wrote: I have a small question concerning the best way to include a very small dataset into the distribution of GRASS

Re: [GRASS-dev] packagers' guidance on inclusion of small dataset into the GRASS GIS installation

On 3/08/20 16:37, Sebastiaan Couwenberg wrote: On 8/3/20 4:16 PM, Moritz Lennert wrote: I have a small question concerning the best way to include a very small dataset into the distribution of GRASS GIS. We are currently working on the revamping of the GRASS GIS GUI startup experience

[GRASS-dev] packagers' guidance on inclusion of small dataset into the GRASS GIS installation

Hi Bas, Hi any other packages who might want to weigh in, I have a small question concerning the best way to include a very small dataset into the distribution of GRASS GIS. We are currently working on the revamping of the GRASS GIS GUI startup experience, and have the currently proposed

Re: [GRASS-dev] Unable to install grass-core on debian 10 (buster)

On 18/05/20 14:48, Moritz Lennert wrote: On 18/05/20 14:26, aborruso wrote: Hi, I would like to run some grass processes via sh scripts. After running "sudo apt-get install grass-core", I have: "The following packages have unmet dependencies:   grass-core : Depends: libg

Re: [GRASS-dev] Unable to install grass-core on debian 10 (buster)

On 18/05/20 14:26, aborruso wrote: Hi, I would like to run some grass processes via sh scripts. After running "sudo apt-get install grass-core", I have: "The following packages have unmet dependencies: grass-core : Depends: libgdal26 (>= 2.2.0) but it is not going to be installed

Re: [GRASS-dev] New GUI startup discussion

On 16/05/20 18:08, Vaclav Petras wrote: On Sat, May 16, 2020 at 8:25 AM Moritz Lennert mailto:mlenn...@club.worldonline.be>> wrote: On 15/05/20 03:54, Vaclav Petras wrote: > > > On Thu, May 14, 2020 at 9:29 PM Robert Lagacé > mailto:robert.l

Re: [GRASS-dev] New GUI startup discussion

On 15/05/20 03:54, Vaclav Petras wrote: On Thu, May 14, 2020 at 9:29 PM Robert Lagacé mailto:robert.lagace...@gmail.com>> 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

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

On 16/05/20 03:32, Vaclav Petras wrote: On Fri, May 8, 2020 at 1:04 PM Stefan Blumentrath mailto: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

Re: [GRASS-dev] [GRASS-user] Calling all imagery (especially i.maxlik and i.smap) users

On 6/05/20 08:33, Maris Nartiss wrote: Hello lists (sorry for cross-posting), as GRASS 8 starts to look less Duke Nukem Forever (a.k.a. never), it is a chance to change some things in imagery part. Thus if you heavy relay on imagery part of GRASS GIS, please find some time to give small

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

Hi, A few days ago, we had a discussion about good labelling of PRs/commits in order to make it easier to create News pages for new releases. I just opened PR #601 [1] which changes the API of the v.distance module. Is there a specific label I should put into the subject line of this PR to

[GRASS-dev] Fwd: [mlennert/grass] Run failed: CI - master (6669a4d)

Am I right in my interpretation that below build failures are not linked to my PR ? IIUC, the errors are in Python scripts and linked to the flake8 changes ? Moritz Forwarded Message Subject:[mlennert/grass] Run failed: CI - master (6669a4d) Date: Fri, 08 May 2020

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

Am 6. Mai 2020 15:17:08 MESZ schrieb Vaclav Petras : >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, >>

Re: [GRASS-dev] staging.grass.osgeo.org - uptodate for review?

Hi, Am 4. April 2020 20:56:12 MESZ schrieb Helmut Kudrnovsky : >hi, > >is staging.grass.osgeo.org uptodate for a review? We are in a state of constant review for the moment and any additional eyes and opinions are always useful. > >I saw a lot of PRs to the website, though I lost a bit the

[GRASS-dev] Website: MD formatting vs html

Hi Nick, Using below message just as an illustration to my question: IIUC, Hugo is mainly markdown. Markdown provides it's own syntax, e.g. for lists it uses *. Many of the pages currently in the new website use Html syntax. Is there a specific reason to do so ? Might it be better to impose

[GRASS-dev] generic address to access the manuals of the current stable version ?

Hi, ISTR some discussion about this (but maybe I just dreamed it ;-)), but how difficult would it be to create some sort of symlink to be able to point https://grass.osgeo.org/grass/ or https://grass.osgeo.org/grass-stable/ to the current stable version, i.e. now

Re: [GRASS-dev] Let's work on the new GRASS website!

On 26/03/20 23:26, Helmut Kudrnovsky wrote: Hi Vero, Maybe you want to vote in the doodle. We have a tie between >sunday and monday evening Do you have the doodle link at hand? ;-D https://doodle.com/poll/884epdzezy9zphpe ___ grass-dev mailing

Re: [GRASS-dev] Let's work on the new GRASS website!

Hi Vero, On 26/03/20 22:18, Veronica Andreo wrote: Hi Helli, Maybe you want to vote in the doodle. We have a tie between sunday and monday evening There still seems to be a tie. As you are the one who took the initiative, I would propose that you play the role of tie breaker and just

Re: [GRASS-dev] db.copy gives error

Am 14. März 2020 23:38:58 MEZ schrieb Markus Metz : >On Sat, Mar 14, 2020 at 3:27 PM Paulo van Breugel > >wrote: >> >> Dear devs, >> >> I have a grassgis database with in the mapset 'Permanent' a table >> 'vegetation_lookup'. I want top copy this table to the current >mapset. >> The following

Re: [GRASS-dev] any special reason why choice of raster compression method is done via environmental variable ?

Coming back to this to continue the discussion: On 15/12/19 21:41, Markus Metz wrote: On Tue, Dec 10, 2019 at 6:47 AM Moritz Lennert mailto:mlenn...@club.worldonline.be>> wrote: > > On 9/12/19 22:50, Markus Metz wrote: > >   Hi Moritz, > > > > On Wed,

Re: [GRASS-dev] missing logs for Windows addons

On 6/01/20 13:29, Martin Landa wrote: Ahoj, po 6. 1. 2020 v 9:42 odesílatel Anna Petrášová napsal: Thanks for looking into this! Unfortunately, there is now a different problem, in 7.8 and 7.9, it looks like all c modules are not compiled, that's also the case of r.futures.pga (which is a c

[GRASS-dev] Fwd: [OSGeo-Discuss] Improving usability of INSPIRE data in FOSS4G client applications

As a heads up: Forwarded Message Subject: [OSGeo-Discuss] Improving usability of INSPIRE data in FOSS4G client applications Date: Thu, 12 Dec 2019 17:09:13 +0100 From: Marco Minghini To: disc...@lists.osgeo.org CC: marco.mingh...@ec.europa.eu Dear all, at

Re: [GRASS-dev] any special reason why choice of raster compression method is done via environmental variable ?

On 9/12/19 22:50, Markus Metz wrote:  Hi Moritz, On Wed, Dec 4, 2019 at 10:28 AM Moritz Lennert mailto:mlenn...@club.worldonline.be>> wrote: > > Hi Markus, > > In recent days, I've been confronted several times with the issue of > people trying to share data among

Re: [GRASS-dev] any special reason why choice of raster compression method is done via environmental variable ?

ASS environment variable instead of a shell variable might be an idea to make setting the default easier. Moritz > > trešd., 2019. g. 4. dec., plkst. 11:28 — lietotājs Moritz Lennert > () rakstīja: > > > > Hi Markus, > > > > In recent days, I've been con

[GRASS-dev] any special reason why choice of raster compression method is done via environmental variable ?

Hi Markus, In recent days, I've been confronted several times with the issue of people trying to share data among themselves, but using different versions of GRASS, and so raster data compressed in a more recent version of GRASS was not usable in an older version of GRASS. Now, I agree that

[GRASS-dev] Fwd: [Belgium] Fwd: [Dutch] CfP Geospatial Devroom at FOSDEM 2020

GRASS GIS contributions would be very welcome. I don't know, yet, if I will be in Brussels at the time. If yes, I can try to propose something. Moritz Forwarded Message Subject:[Belgium] Fwd: [Dutch] CfP Geospatial Devroom at FOSDEM 2020 Date: Mon, 28 Oct 2019

Re: [GRASS-dev] grass76 addons are taken from trac, but updates to addons happen on github

On 31/10/19 11:58, Markus Neteler wrote: Hi, On Thu, Oct 31, 2019 at 11:08 AM Martin Landa wrote: Hi, čt 31. 10. 2019 v 11:02 odesílatel Moritz Lennert napsal: I would assume that there are still quite a lot of GRASS 7.6.0 installations out there (it was released less than a year ago

Re: [GRASS-dev] grass76 addons are taken from trac, but updates to addons happen on github

On 31/10/19 11:08, Martin Landa wrote: Hi, čt 31. 10. 2019 v 11:02 odesílatel Moritz Lennert napsal: I would assume that there are still quite a lot of GRASS 7.6.0 installations out there (it was released less than a year ago). Would it we definitely need to release 7.6.2 (not sure if all

[GRASS-dev] grass76 addons are taken from trac, but updates to addons happen on github

Hi, After some intense doubts about my sanity, I noticed that I fell into a simple trap: I had fixed a bug in the i.segment.uspo addon quite a while ago, but the same bug kept on popping up, even though I have reinstalled the addon. Finally, I remembered that on the university's HPC it is

Re: [GRASS-dev] i.fusion.hpf addon: observing strong range change

On 29/10/19 19:11, Veronica Andreo wrote: On the other hand, i.pansharpen does include a re-scaling step, but whatever bit depth is passed as input it will be re-scaled to 8-bit. If the input data is >8-bit, it is a bit of a loss of radiometric resolution (if the resulting values can be used

Re: [GRASS-dev] i.fusion.hpf addon: observing strong range change

On 28/10/19 12:33, Markus Neteler wrote: On Mon, Oct 28, 2019 at 10:46 AM Moritz Lennert wrote: On 27/10/19 18:52, Markus Neteler wrote: Hi, I am using i.fusion.hpf on Worldview-2 data and see that the resulting range is completely different: # orig r.info -r

Re: [GRASS-dev] i.fusion.hpf addon: observing strong range change

On 27/10/19 18:52, Markus Neteler wrote: Hi, I am using i.fusion.hpf on Worldview-2 data and see that the resulting range is completely different: # orig r.info -r wv2_17OCT08182034_M2AS_058891334010_01_P001.5 min=0 max=1509 # HPF r.info -r wv2_17OCT08182034_M2AS_058891334010_01_P001.5.hpf

Re: [GRASS-dev] GRASS 7.8.1 ?

On 14/10/19 20:51, Helmut Kudrnovsky wrote: hi, as winGRASS is on the way to come back, see [1]. locally here is already winGRASS 7.8.0 running for testing. This is great news ! there are already a few reported issues for python3 and git related to winGRASS etc, e.g.

Re: [GRASS-dev] Python scripts: trigger cleanup function at keyboard interrupt (CTRL-C)

On 14/10/19 16:44, Anna Petrášová wrote: This is used in many scripts and should work: https://grasswiki.osgeo.org/wiki/GRASS_Python_Scripting_Library#Sophisticated_cleanup_procedure Not sure this works on a Ctrl-C. ISTR it doesn't, but this would have to be verified. Moritz On Mon, Oct

[GRASS-dev] issue with the compilation of several addons: ImportError: No module named lib.gis

Hi, Several addon modules are currently not compiled (imagery/i.cutlines, imagery/i.fusion.hpf, imagery/i.image.bathymetry, raster/r.cell.area, raster/r.gradient, raster/r.series.filter, etc). All show the same error message: "ImportError: No module named lib.gis". Any ideas where this

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

On 12/08/19 16:52, 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/ and would like to collect your ideas for that. Of course - Python 3 support - SVN to git migration - ... The

Re: [GRASS-dev] GRASS GIS at FOSS4G

On 23/07/19 15:17, Martin Landa wrote: Hi Moritz, po 15. 7. 2019 v 14:12 odesílatel Martin Landa napsal: - Have you all booked housing already ? If not, should we try to find some place (e.g. appartment) which could also be a place to work together, or should we ask whether a room

Re: [GRASS-dev] dealing with null values in rasters only within mask

Hi Markus, On 28/06/19 22:08, Markus Metz wrote: Hi Moritz, On Fri, Jun 28, 2019 at 11:56 AM Moritz Lennert mailto:mlenn...@club.worldonline.be>> wrote: > > On 28/06/19 11:10, Stefan Blumentrath wrote: > > Hi Moritz, > > > > Did you consider r.stats -

Re: [GRASS-dev] dealing with null values in rasters only within mask

On 28/06/19 11:10, Stefan Blumentrath wrote: Hi Moritz, Did you consider r.stats -N for checking for NULL values within the masked area, like: r.stats -N input=tile,MASK if there is *|1 in the output you have NULL cells in the tile... Nice trick, didn't actually know about the -N flag...

[GRASS-dev] dealing with null values in rasters only within mask

Hi to all, As a followup of some recent discussions concerning the handling of null values, I have a fundamental issue, and would like some feedback: I am working with irregular tiles of orthoimages. Each tile corresponds to the part of a large image mosaic that comes from a particular take.

[GRASS-dev] Port Dempster-Shafer module from grass6 to grass7

Hi, Colleagues of mine would be interested in the dst addon family of modules that currently exists for GRASS 6, but would need it for GRASS 7. Does anyone have ann idea how difficult it would be to port them to GRASS7 ? Moritz ___ grass-dev

Re: [GRASS-dev] error in v.overlay: Unable to write spatial index. Wrong node position

On 10/06/19 21:39, Markus Metz wrote: On Mon, Jun 10, 2019 at 6:12 PM Moritz Lennert mailto:mlenn...@club.worldonline.be>> wrote: > > Hi, > > I just came across this error: > > ** > ERROR: Unable to write spatial index. Wro

[GRASS-dev] error in v.overlay: Unable to write spatial index. Wrong node position

Hi, I just came across this error: ** ERROR: Unable to write spatial index. Wrong node position (950329504) in file (should be 950333637). ERROR: Clipping steps failed. Check above error messages and see following details: Module run None

Re: [GRASS-dev] GRASS GIS at FOSS4G

ping On 5/06/19 22:21, Moritz Lennert wrote: Hi everyone, It seems that we have one workshop accepted on TGRASS, plus the general "state of the project" presentation, plus several others where GRASS GIS is used in different forms. Sounds like a nice programme ! I will be in Buch

[GRASS-dev] GRASS GIS at FOSS4G

Hi everyone, It seems that we have one workshop accepted on TGRASS, plus the general "state of the project" presentation, plus several others where GRASS GIS is used in different forms. Sounds like a nice programme ! I will be in Bucharest from Sunday, Aug 25 afternoon, until Saturday, Aug 31,

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

On 12/05/19 18:19, Markus Neteler wrote: On Fri, May 10, 2019 at 5:06 PM Martin Landa wrote: Hi, út 7. 5. 2019 v 10:26 odesílatel Martin Landa napsal: commits can be referenced to github issues. Issue migration needs to be also done on private repository. This would require to set up empty

Re: [GRASS-dev] FYI: Season of the Docs

On 9/05/19 10:08, Panagiotis Mavrogiorgos wrote: Hello all, This year google launched a new project similar to Summer of Code whose scope is improving documentation. The deadline has passed but it might make sense to keep it in mind for next year:

Re: [GRASS-dev] v.to.db: next/prev line

On 8/05/19 11:44, Martin Landa wrote: Hi, st 8. 5. 2019 v 11:31 odesílatel Moritz Lennert napsal: I don't think we have a tool for this currently. However, I'm not sure that right and left are relevant terms for this case. Also: what do you do in the case when three lines meet at a node

Re: [GRASS-dev] v.to.db: next/prev line

Hi Martin, Am 8. Mai 2019 08:29:22 MESZ schrieb Martin Landa : >Hi, > >I wonder whether there is a tool in GRASS which enables writing to >attribute table information about next/previous lines. Basically info >about next_right_edge/next_left_edge. > >My idea is to extend `v.to.db` option `sides`

Re: [GRASS-dev] Motion: Migrate SVN and trac tickets to github under OSGeo organization

Am 25. April 2019 16:45:01 MESZ schrieb Martin Landa : >Dear PSC, > >po 22. 4. 2019 v 17:27 odesílatel Markus Neteler >napsal: >> Next steps of migration to Github: > >I will prepared detailed plan in the next days. Ma Kudos to you, Martin, for all the work you are doing on this ! Moritz

Re: [GRASS-dev] Addons manuals: logo and CSS file missing

On 25/04/19 07:56, Markus Metz wrote: On Thu, Apr 25, 2019 at 7:42 AM Martin Landa > wrote: > > Hi, > > st 24. 4. 2019 v 16:28 odesílatel Markus Neteler > napsal: > > Could you please verify? > > yes, the reason is that G76 is

Re: [GRASS-dev] which files are mandatory for raster maps

On 16/04/19 18:10, Markus Neteler wrote: Hi Moritz, On Tue, Apr 16, 2019 at 2:56 PM Moritz Lennert wrote: Hello, I'm working with a large batch of raster maps (4550 * 4 bands) and including all the auxiliary files this explodes my inode quota on our university's HPC system. Out

[GRASS-dev] which files are mandatory for raster maps

Hello, I'm working with a large batch of raster maps (4550 * 4 bands) and including all the auxiliary files this explodes my inode quota on our university's HPC system. While waiting to see if they can increase this, I was wondering which of the auxiliary files are absolutely mandatory. Can

[GRASS-dev] Nice opportunity to show off GRASS functionality and topological vector format ?

Hi, If anyone has some time and wants to show off some GRASS GIS power: https://www.ecmwf.int/en/learning/workshops/ecmwf-summer-weather-code-2019 "The Summer of Weather Code(ESoWC) programme by the European Centre for Medium-Range Weather Forecasts (ECMWF) is a collabrative online programme

Re: [GRASS-dev] include a 'nearest' option in r.walk ?

On 11/04/19 09:36, Markus Metz wrote: Hi Moritz, On Wed, Apr 10, 2019 at 4:16 PM Moritz Lennert mailto:mlenn...@club.worldonline.be>> wrote: > > Hi everyone, > > We are looking for a way to transform the r.walk output into a nearest > neighbor by cost map

  1   2   3   4   5   6   7   8   9   10   >