Re: [GRASS-dev] GRASS Teams on GitHub

Hi there, st 13. 3. 2024 v 1:36 odesílatel Vaclav Petras napsal: > On Fri, 8 Mar 2024 at 09:10, Ondřej Pešek wrote: >> @Vaclav: Do you have some more points against the master-children >> schema? It seems that the general agreement is *for* the restructuring >> into pare

Re: [GRASS-dev] GRASS Teams on GitHub

ainst when compared to the positive ones (although it's understandable that nobody wants to drop something that they have just created). Cheers from the discussion underworld, Ondrej čt 22. 2. 2024 v 9:35 odesílatel Ondřej Pešek napsal: > > Sweet devs, > > Looking at the GitHub

Re: [GRASS-dev] GRASS Teams on GitHub

omated dockerhub and homebrew >> builds > > > I don't know why we have that. It works for notifications, but I haven't seen > that used. Another potential candidate for disintegration then? >> On Thu, Feb 22, 2024 at 1:35 AM Ondřej Pešek via grass-dev >> wrote: >>&g

[GRASS-dev] GRASS Teams on GitHub

Sweet devs, Looking at the GitHub teams within the OSGeo organisation [1], it is impossible not to notice the fact that the GRASS people are very good in making themselves visible through visual weed infestation. On one side, it is nice to see GRASS all over the dance floor; on the other one, I

Re: [GRASS-dev] [EXTERNAL] [release planning] GRASS GIS 8.3.1

so 30. 9. 2023 v 16:12 odesílatel Markus Neteler via grass-dev napsal: > As far as I see the git on Windows issue has been solved as well as > many wxGUI bugs. > Still a few to go which are under review. Shall we wait for them? > Please let me know. Not only Windows wxGUI issues. It is

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

čt 23. 3. 2023 v 10:53 odesílatel Markus Neteler napsal: > - i.vi: support soil_line_slope for PVI #2561, pesekon2 Merged in #2561. A follow-up update of the manual [1] is waiting for a review and ready to be merged. [1] https://github.com/OSGeo/grass/pull/2903

Re: [GRASS-dev] GitHub backport label proposal

út 22. 11. 2022 v 14:24 odesílatel Markus Neteler napsal: > Our generic "backport" label seems to be mildly confusing (backport to > which branch?). > > My suggestion is to adopt the approach of GDAL: > > - backport release 7.8 > - backport release 8.2 > ... I like that. But maybe keeping just

Re: [GRASS-dev] new addon

út 1. 2. 2022 v 12:40 odesílatel Francesco Geri napsal: > *git clone g...@github.com:fra-lab/grass.git > * > > *Clone in 'grass' in corso...* > *The authenticity of host 'github.com (140.82.121.3)' > can't be established.* > *ECDSA key fingerprint is >

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

Ciao, st 29. 9. 2021 v 23:04 odesílatel Vaclav Petras napsal: > We are having a community sprint on Saturday, October 2nd, 2021. > Is anybody interested in working together during the European morning > instead of waiting for the conference day to start? > I wanted to make a quick visit in the

Re: [GRASS-dev] GRASS 8 addons

Hi Vaclav, po 6. 9. 2021 v 3:39 odesílatel Vaclav Petras napsal: > The plan is to create one. You can follow the progress here: > https://github.com/OSGeo/grass-addons/issues/528 > I guess that I should finally clean my glasses. I have tried to check the issues, but I have completely missed

[GRASS-dev] GRASS 8 addons

Hey you lovely devs, In some GRASS modules (e.g. v.db.select), there were certain changes altering their interface between GRASS GIS 7 and the messianic GRASS GIS 8. My question is - how to deal with that in the addons? Currently, there is no GRASS 8 branch in the addons repo. Is there a plan to

Re: [GRASS-dev] Website does not work with www for me

pá 14. 8. 2020 v 1:17 odesílatel Markus Neteler napsal: > Ondřej Pešek schrieb am Do., 13. Aug. 2020, > 23:50: > >> when I go to the GRASS website the lazy way without typing www ( >> grass.osgeo.org), I can load the page without a problem. However, when I >&

[GRASS-dev] Website does not work with www for me

Howdie, when I go to the GRASS website the lazy way without typing www ( grass.osgeo.org), I can load the page without a problem. However, when I want to try it with www (www.grass.osgeo.org), I get the "Page not found" error message. Is it just me? Is it normal? Is it internet mimicry? Is it

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

Hi Moritz, po 6. 1. 2020 v 16:56 odesílatel Moritz Lennert < mlenn...@club.worldonline.be> napsal: > I see that r.object.activelearning also fails with: > > "ModuleNotFoundError: No module named 'scipy'" > > Should this module be changed somehow to wrap the import in a way to > only make it fail

Re: [GRASS-dev] GRASS GIS at FOSS4G

Hi, st 5. 6. 2019 v 22:21 odesílatel Moritz Lennert < mlenn...@club.worldonline.be> 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 might be

Re: [GRASS-dev] GRASS GIS at FOSS4G

Hi Moritz, st 5. 6. 2019 v 22:21 odesílatel Moritz Lennert < mlenn...@club.worldonline.be> napsal: > - Who else will be in town at the beginning of the > week ? > Most probably me. I still haven't booked the flight, but I think I will book it either on Sunday or Monday. > - Should we organise

Re: [GRASS-dev] Fwd: [OSGeo-Discuss] FOSS4G 2019 Bucharest Call for Contributions Open

so 9. 2. 2019 v 5:49 odesílatel Moritz Lennert napsal: > On 8/02/19 18:03, Ondřej Pešek wrote: > > Fr 8. 2. 2019 15:27 Veronica Andreo > <mailto:veroand...@gmail.com>> wrote: > > > > Will you attend the conference, Ondrej? > > > > > &g

Re: [GRASS-dev] Fwd: [OSGeo-Discuss] FOSS4G 2019 Bucharest Call for Contributions Open

Fr 8. 2. 2019 15:27 Veronica Andreo wrote: > Will you attend the conference, Ondrej? > Yes. ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Python scripts in GRASS GIS: conditional loading of external libraries?

Hi, pá 19. 10. 2018 v 17:18 odesílatel Martin Landa napsal: > pá 19. 10. 2018 v 16:45 odesílatel Markus Neteler > napsal: > > we are currently writing a Python script which needs to import some > > heavy external libraries. > > if I understand well, a lazy import could help > > """ > def main:

Re: [GRASS-dev] Access to GRASS GIS addons

čt 11. 10. 2018 v 17:24 odesílatel Vaclav Petras napsal: > A 2016 GSoC project took different approach which could be reused in QGIS > independently from the current GRASS Plugin or Processing plugin > approaches. This is a good base for future work, perhaps even for > auto-generating the files

Re: [GRASS-dev] [SoC] GSoC 2017 Weekly Report 12 - SOS tools in GRASS GIS

Hi Madi, oh, I'm sorry. I have read that manual, but I have thought that the final report will be the next one. My fault. So here it is reelaborated. *Project Title:* SOS tools in GRASS GIS *Organization:* Google Summer of Code 2017 Open Source Geospatial Foundation (OSGeo) GRASS GIS

[GRASS-dev] [SoC] GSoC 2017 Weekly Report 12 - SOS tools in GRASS GIS

Hi everyone! Here is the twelfth report of my GSoC project - SOS tools in GRASS GIS. You can see my project at wiki at [1] What did you get done this week? all modules * made quiet, e.g. when creating temporal dataset with hundreds of maps, it doesn't show hundreds of builds main commits:

[GRASS-dev] [SoC] GSoC 2017 Weekly Report 11 - SOS tools in GRASS GIS

Hi everyone! Here is the eleventh report of my GSoC project - SOS tools in GRASS GIS. You can see my project at wiki at [1] What did you get done this week? v.in.sos * finally working the desired way even with more layers main commits: [2] [3] * uses yet existing columns for timestamps

[GRASS-dev] [SoC] GSoC 2017 Weekly Report 10 - SOS tools in GRASS GIS

Hi everyone! Here is the tenth report of my GSoC project - SOS tools in GRASS GIS. You can see my project at wiki at [1] What did you get done this week? r.in.sos * flag for deleting vector maps created as intermediates main commits: [2] * importing vectors and values in one step

[GRASS-dev] [SoC] GSoC 2017 Weekly Report 9 - SOS tools in GRASS GIS

Hi everyone! Here is the ninth report of my GSoC project - SOS tools in GRASS GIS. You can see my project at wiki at [1] What did you get done this week? * updated shell script style output to all modules main commits: [2] * handle import errors main commits: [3] * every flag

[GRASS-dev] [SoC] GSoC 2017 Weekly Report 8 - SOS tools in GRASS GIS

Hi everyone! Here is the eighth report of my GSoC project - SOS tools in GRASS GIS. You can see my project at wiki at [1] What did you get done this week? * t.vect.in.sos creates new vector for each offering and observed property main commits: [2], [3], [4] * implemented shell script

[GRASS-dev] [SoC] GSoC 2017 Weekly Report 7 - SOS tools in GRASS GIS

Hi everyone! Here is the seventh report of my GSoC project - SOS tools in GRASS GIS. You can see my project at wiki at [1] What did you get done this week? * As I declared in my timeline and proposal, I was out of internet and electricity during the last week. So I wasn't able to do anything

[GRASS-dev] [SoC] GSoC 2017 Weekly Report 6 - SOS tools in GRASS GIS

Hi everyone! Here is the sixth report of my GSoC project - SOS tools in GRASS GIS. You can see my project at wiki at [1] What did you get done this week? As I declared in my timeline and proposal, I was out of internet and electricity during the last week. So I wasn't able to do anything

[GRASS-dev] [SoC] GSoC 2017 Weekly Report 5 - SOS tools in GRASS GIS

Hi everyone! Here is the fifth report of my GSoC project - SOS tools in GRASS GIS. You can see my project at wiki at [1] What did you get done this week? v.in.sos * using vectors in pyGRASS instead of v.in.sos * support multiple offerings * layers are for offerings and observed properties, rows

[GRASS-dev] [SoC] GSoC 2017 Weekly Report 4 - SOS tools in GRASS GIS

Hi everyone! Here is the fourth report of my GSoC project - SOS tools in GRASS GIS. You can see my project at wiki at [1] What did you get done this week? v.in.sos * flags for printing timestamps of begin and end of observation * working with event_time (interval of observation is used in

[GRASS-dev] [SoC] GSoC 2017 Weekly Report 3 - SOS tools in GRASS GIS

Hi everyone! Here is the third report of my GSoC project - SOS tools in GRASS GIS. You can see my project at wiki at [1] What did you get done this week? This week was dedicated to the module v.in.sos: * Makefile and first html * UI * Prints informations about sensor offerings * Imports the

Re: [GRASS-dev] [SoC] GSoC 2017 Weekly Report 2 - SOS tools in GRASS GIS

Hi Maris, Luca, On 12 June 2017 at 08:11, Maris Nartiss wrote: > > > > I have no idea how much of XML parsing is needed, but implementing an > > own XML parser never sounds a good idea unless it is a quick hack. > > Working with XML in a correct way is PITA, unless your

[GRASS-dev] [SoC] GSoC 2017 Weekly Report 2 - SOS tools in GRASS GIS

Hi everyone! Here is the first report of my GSoC project - SOS tools in GRASS GIS. You can see my project at wiki at [1] What did you get done this week? * I had a problem with xml parser in OWSLib for SOS observations, because it works completely different way than we expected. After few

[GRASS-dev] [SoC] GSoC 2017 Weekly Report 1 - SOS tools in GRASS GIS

Hi everyone! Here is the first report of my GSoC project - SOS tools in GRASS GIS. You can see my project at wiki at [1] What did you get done this week? * I have studied OWSLib and its interaction with SOS. Especially with istSOS. I am also

Re: [GRASS-dev] GSoC 2017 - SOS tools

2017-03-31 0:33 GMT+02:00 Ondřej Pešek <pesej.ond...@gmail.com>: > Hi Massimo, > > 2017-03-30 14:50 GMT+02:00 massimo di stefano <massimodisa...@gmail.com>: > > Hi Ondrej, > > what about working on your gsoc 2016 idea? > > > > I guess we all want th

Re: [GRASS-dev] GSoC 2017 - SOS tools

Hi Massimo, 2017-03-30 14:50 GMT+02:00 massimo di stefano : > Hi Ondrej, > what about working on your gsoc 2016 idea? > > I guess we all want the GSOC be an “instrument” to involve students in the > project they chose and “hopefully” have them continuing what they

[GRASS-dev] GSoC 2017 - SOS tools

Hello everyone, I am Ondrej Pesek, a student at CTU in Prague (studying master studies in geomatics) and I would like to participate in GSoC 2017. I am most interested in the SOS topic [1]. I will work during summer in NINA where I should work with istSOS, So I'm thinking about istSOS also in

[GRASS-dev] GSoC 2016 - PyQt GRASS - Report 12

Hi all, here is my last week report. Wiki page: https://trac.osgeo.org/grass/wiki/GSoC/2016/PyQtGUI A link to my commits: https://github.com/pesekon2/GRASS-Qt-based-GUI/commits The goal of the project was to create new GUI for modules based on PyQt. The old one is based on wxPython. The reason

[GRASS-dev] GSoC 2016 - PyQt GRASS - Report 10

Hi all! Here is the tenth report of my GSoC project - PyQt based GUI of GRASS automatically generated from XML. For screenshots and other stuff see its wiki: https://trac.osgeo.org/grass/wiki/GSoC/2016/PyQtGUI What did you get done this week? * New widgets: Mapsets, locations and dbtable

[GRASS-dev] GSoC 2016 - PyQt GRASS - Report 9

Hi all! Here is the ninth report of my GSoC project - PyQt based GUI of GRASS automatically generated from XML. For screenshots and other stuff see its wiki: https://trac.osgeo.org/grass/wiki/GSoC/2016/PyQtGUI What did you get done this week? * New widget: dbtable * I had finally ordered tabs.

[GRASS-dev] GSoC 2016 - PyQt GRASS - Report 8

Hi all! Here is the eigth report of my GSoC project - PyQt based GUI of GRASS automatically generated from XML. For screenshots and other stuff see its wiki: https://trac.osgeo.org/grass/wiki/GSoC/2016/PyQtGUI What did you get done this week? * New widgets: layer, columns, multiple values with

[GRASS-dev] GSoC 2016 - PyQt GRASS - Report 7

Hi all! Here is the seventh report of my GSoC project - PyQt based GUI of GRASS automatically generated from XML. For screenshots and other stuff see its wiki: https://trac.osgeo.org/grass/wiki/GSoC/2016/PyQtGUI What did you get done this week? * New widgets: cats, multiple values, raster_3d *

[GRASS-dev] GSoC 2016 - PyQt GRASS - Report 6

Hi all! Here is the sixth report of my GSoC project - PyQt based GUI of GRASS automatically generated from XML. For screenshots and other stuff se its wiki: https://trac.osgeo.org/grass/wiki/GSoC/2016/PyQtGUI What did you get done this week? * The Run button works now also with flags. Also the

[GRASS-dev] GSoC 2016 - PyQt GRASS - Report 5

Hi all! Here is thefifth report of my GSoC project - PyQt based GUI of GRASS automatically generated from XML. For screenshots and other stuff se its wiki: https://trac.osgeo.org/grass/wiki/GSoC/2016/PyQtGUI What did you get done this week? * As I said, due to my exams, I didn't do anything.

[GRASS-dev] GSoC 2016 - PyQt GRASS - Report 4

Hi all! Here is the third report of my GSoC project - PyQt based GUI of GRASS automatically generated from XML. For screenshots and other stuff se its wiki: https://trac.osgeo.org/grass/wiki/GSoC/2016/PyQtGUI What did you get done this week? * The Run button really runs (but still not with

[GRASS-dev] GSoC 2016 - PyQt GRASS - Report 3

Hi all! Here is the third report of my GSoC project - PyQt based GUI of GRASS automatically generated from XML What did you get done this week? * I have upgraded GUI - now it works also with the string and integer types. (on the basic level) * I also have made some changes - SqlQuery is now

Re: [GRASS-dev] GSoC 2016 - PyQt GRASS - Report 2

Hi, it sounds good, thank you for opening new possibilities. To be honest, I didn't know about the g.parser rules. Now I'm just looking on that. It looks nice. In some latest version, I will try to implement it. Especially the mutually exclusive ones, it should be nice. Thanks 2016-06-08 9:30

Re: [GRASS-dev] GSoC 2016 - PyQt GRASS - Report 2

Hi, 2016-06-04 20:47 GMT+02:00 Vaclav Petras : > > the screenshots looks good. For the code, it might little bit too soon to > judge it, but just keep in mind the need for design we talked about > earlier. For some simple help, you can use pylint tool which will demand >

[GRASS-dev] GSoC 2016 - PyQt GRASS - Report 2

Hi all! Here is the second report of my GSoC project - PyQt based GUI of GRASS automatically generated from XML What did you get done this week? * Now the code is reading those types - float, range, sql_query, flags * It also writes their names or labels and types into GUI What do you plan on

Re: [GRASS-dev] GSoC 2016 - PyQt

9FDF2> 2016-05-30 9:14 GMT+02:00 Luca Delucchi <lucadel...@gmail.com>: > On 27 May 2016 at 23:27, Ondřej Pešek <pesej.ond...@gmail.com> wrote: > > > > Hi, > > > > Hi Ondrej, > > > here is report of what I have done during this week in my GRASS >

Re: [GRASS-dev] GSoC 2016 - PyQt

Hi, thanks for your response. 2016-05-25 17:26 GMT+02:00 Pietro : > > Perhaps, it could be useful to have a look at pygrass `Module` class [0], > that already parse the generated xml and instantiate `Parameter` class [1] > that validate the input from the user in the

[GRASS-dev] GSoC 2016 - PyQt

Hi everyone, the period of GSoC starts. I just want to present myself. My name is Ondrej Pesek and I'm from Czech Republic. I study geodesy, cartography and geomatics at Czech technical university in Prague. My project for GSoC 2016 is reimplementation of GUI generated from xml, wxpython -> PyQt.