Re: [GRASS-dev] GSoC Ideas

[Luca Delucchi via grass-dev]

Hi Anna,

On Fri, 1 Mar 2024 at 17:30, Anna Petrášová  wrote:
>
> We have already students wanting to work on github issues linked as test of 
> skills. Martin and Luca, your ideas don't have a test of skills, please add 
> it there as soon as possible, otherwise we can't really use the idea, test of 
> skills is required by OSGeo.
>

Thanks for the reminder, I created this issue
https://github.com/OSGeo/grass-addons/issues/1033, is it doable or too
complicated?

> Thank you
>

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSoC Ideas

[Luca Delucchi via grass-dev]

On Mon, 12 Feb 2024 at 18:08, Markus Neteler  wrote:
>
> On Tue, Feb 6, 2024 at 12:11 AM Luca Delucchi via grass-dev
>  wrote:
> > On Mon, 5 Feb 2024 at 13:33, Veronica Andreo  wrote:
> > > That would be cool Luca! eodag allows you to download different EO 
> > > datasets.
> > >
> > > Do you think of a GSoC project idea to include eodag support for 
> > > i.sentinel.download, i.landsat.download and i.modis.download or as a new 
> > > module to download EO data in general? If you are willing to mentor, I 
> > > can be your second... mainly to test and make annoying questions :)
> > >
> >
> > Yes, the idea could be to add it to i.*.download, I was also thinking
> > of having a common library in grass python library as an interface to
> > eodag, but I'm not sure if it makes sense...
> >
> > However I tried to log to the wiki and I'm not able, and password
> > recover also didn't work
>
> Regina has updated the GRASS Wiki again and we have done a series of
> tests, fixing plugins and such.
>
> Please try again, now with your OSGeo-LDAP account.
>
> A "user merge" may come up. Let me know if it gets blocked so that I can 
> assist.
>

It worked properly now, I added the EODAG proposal, I didn't add any
test yet but I'll hope to do it ASAP

> Markus
>


ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSoC Ideas

[Luca Delucchi via grass-dev]

On Mon, 5 Feb 2024 at 13:33, Veronica Andreo  wrote:
>
> That would be cool Luca! eodag allows you to download different EO datasets.
>
> Do you think of a GSoC project idea to include eodag support for 
> i.sentinel.download, i.landsat.download and i.modis.download or as a new 
> module to download EO data in general? If you are willing to mentor, I can be 
> your second... mainly to test and make annoying questions :)
>

Yes, the idea could be to add it to i.*.download, I was also thinking
of having a common library in grass python library as an interface to
eodag, but I'm not sure if it makes sense...

However I tried to log to the wiki and I'm not able, and password
recover also didn't work

> Vero



-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSoC Ideas

[Luca Delucchi via grass-dev]

Il sab 3 feb 2024, 05:34 Anna Petrášová via grass-dev <
grass-dev@lists.osgeo.org> ha scritto:

> Hi,
>
> I created a GSoC Ideas 2024 page on grasswiki (as opposed to trac wiki,
> which I think we should be moving away from):
> https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024
>
> It's not updated yet, I plan to add more topics. If you want to mentor a
> topic, we can discuss it here.
>

Do you think an interface to eodag library, to download sentinel and
Landsat images for example, could be a topic for gsoc?

>
> Anna
>

Best
Luca
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Community meeting plans

[Luca Delucchi]

Il gio 6 apr 2023, 11:34 Micha Silver  ha scritto:

> Hello all:
>
Hi Micha

> I intend to participate in the upcoming community meeting in Prague. I
> hope to work on a GRASS addon to implement the OPTRAM model [1] for
> determining soil moisture from Sentinel 2 imagery. Has anyone done anything
> along this line? If you have an interest in such an addon, let me know.
>
> I could be interested but no idea about how much time I'll have during
code sprint

>
> Best regards,
>
> Micha
>
Best
Luca

>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] gunittest test temporal dataset

[Luca Delucchi]

Il lun 27 mar 2023, 13:21 Stefan Blumentrath  ha
scritto:

> Hi Luca,
>

Hi Stefan,

>
> Not that I am aware of. I use to parse output from t.list to check if a
> STDS exists...
>

Yes this was my idea too. Do you have an example?

>
> Cheers
> Stefan
>
>

Cheers
Luca

>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] gunittest test temporal dataset

[Luca Delucchi]

Hi devs,

is there a way to test if a temporal dataset exists or not?
something like assertRasterExists

in the case it doesn't exist it could be useful?

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Fwd: [Projects] OSGeo booth at FOSS4G 2022

[Luca Delucchi]

-- Forwarded message -
Da: Astrid Emde (OSGeo) 
Date: lun 15 ago 2022, 22:31
Subject: [Projects] OSGeo booth at FOSS4G 2022
To: OSGeo Projects 


Hello projects,

there will be an OSGeo booth at FOSS4G 2022 and also at SotM.

Hope to meet you there.

We will provide project flyer and sticker and information.

We plan to print some of the one pafe info flyer
https://github.com/OSGeo/osgeo/tree/master/marketing/print/one-page-info

If you have marketing material for your project you are welcome provide
it at the booth.

Please give feedback if you have material to astrid (dot) emde (at)
fossgis (dot) de

--
Best regards

Astrid Emde
-
Astrid Emde
OSGeo Secretary
Open Source Geospatial Foundation
https://www.osgeo.org/member/astrid-emde/
astrid (dot) emde (at) fossgis (dot) de

___
Projects mailing list
proje...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/projects
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] multiprocessing problem

[Luca Delucchi]

On Fri, 8 Apr 2022 at 16:33, Anna Petrášová  wrote:
>
> Hi Luca,
>

Hi Anna,

> I would say the biggest problem is the memory, I tried to run it and it 
> consumes way too much memory. Maybe you could process the differences from 
> each pixel (compute the sum) as they are computed, not collect it and do it 
> in the end. Otherwise you can significantly speed it up simply with one core 
> by using numpy in a better way:
>
> vals = np.array([np.abs(y - array.flat) for y in array.flat])
> ...
> out = np.sum(vals) / number2
>

yes, this work better then my solution, but increasing the number of
pixels I get the process killed. I have 16GB RAM and I was not able to
process 8 cells
I tried a few different solutions but the result is always the same.

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] multiprocessing problem

[Luca Delucchi]

On Fri, 8 Apr 2022 at 11:17, Stefan Blumentrath
 wrote:
>
> Ciao Luca,
>

Ciao Stefan

> Yes, you could also consider looping over e.g. rows (maybe in combination 
> with "np.apply_along_axis") so you could put results easier back together to 
> a map if needed at a later stage.
>
> In addition, since you use multiprocessing.Manager, you may try to use 
> multiprocessing.Array: 
> https://docs.python.org/3/library/multiprocessing.html#multiprocessing.Array
>
> E.g. here:
> https://github.com/lucadelu/grass-addons/blob/5ca56bdb8b3394ebeed23aa5b3240bf6690e51bf/src/raster/r.raoq.area/r.raoq.area.py#L81
>
> According to the post here: 
> https://medium.com/analytics-vidhya/using-numpy-efficiently-between-processes-1bee17dcb01
> multiprocessing.Array is needed to put the numpy array into shared memory and 
> avoid pickling.
>
> I have not tried or investigated myself, but maybe worth a try...
>

Yes I saw it but I didn't try before. I tried last days but I didn't
get any improvements, I will try in the coming days

> Cheers
> Stefan
>

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] multiprocessing problem

[Luca Delucchi]

On Fri, 8 Apr 2022 at 09:14, Moritz Lennert
 wrote:
>
> Hi Luca,
>

Hi Moritz,

> 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 better off sending larger chunks to workers ?
>

right now I creating a worker for each pixel to be checked against all
the other pixels, yes it could be and idea to send larger chunks, I
could split the array vertically according to the number of processor

> - Depending on the number of parallel jobs, disk access can quickly become 
> the bottleneck on non parallelized file systems. So it would be interesting 
> to see if using fewer processes might actually speed up things. Then it is a 
> question of finding the equilibrium.
>

ok, this make sense
thanks for your support

> Moritz
>

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] multiprocessing problem

[Luca Delucchi]

Hi devs,

I wrote an addons to calculate Rao's Q diversity index [0], I would
like to speed it up using multiprocessing but with multiprocessing it
took 2/3 times longer than a single process. Could someone look at the
code and explain to me what I'm doing wrong?
A colleague of mine suggested using cython with prange function [1]
but I would avoid it since I need to study it and how to compile it in
GRASS and I have no time to spend on it.

thanks a lot
Luca

[0] https://github.com/lucadelu/grass-addons/tree/raoq/src/raster/r.raoq.area
[1] https://cython.readthedocs.io/en/latest/src/userguide/parallelism.html

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Luca Delucchi]

On Mon, 2 Aug 2021 at 15:52, Aaron Saw Min Sern  wrote:
>
> Hi everyone,
>

Dear Aaron,
thanks a lot for your work, I didn't test yet any your pull request
but benchmark seems to be really promising

>
> 2) What do I plan on doing next week?
>
> Refactor r.univar
> Implement parallelization for r.series, r.patch

r.series is really important module for temporal analysis and I'm
really happy to see and test it in the next weeks

>
> 3) Am I blocked on anything?
> No major issues.
>
> Thanks,
> Aaron
>

regards

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Fwd: [OSGeo-Discuss] [FOSS4G] OSGeo Projects swag

[Luca Delucchi]

On Wed, 7 Jul 2021 at 09:02, Maris Nartiss  wrote:
>
>
> Tired of your lawn looking like a mess? Check out best gardening tips
> at https://grass.osgeo.org
>
> GRASS – taking care of lawns since 1982.
>
>
> Designing an advertisement around logo I leave to more skill full artists.
> Māris.

really cool idea, we could use the background image of our website
https://grass.osgeo.org//images/logos/banner.jpg

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Fwd: [OSGeo-Discuss] [FOSS4G] OSGeo Projects swag

[Luca Delucchi]

On Wed, 7 Jul 2021 at 16:19, Anna Petrášová  wrote:
>
> Hi,
>

Hi,

> what I think would be actually useful would be a GRASS cheatsheet, something 
> like this:
> https://pandas.pydata.org/Pandas_Cheat_Sheet.pdf
> That is obviously a lot of work, but maybe we could put together something 
> much simpler, at least for this occasion.
>

I like it, what do you think about a latex template?
I found this [0], it looks like a good starting point, better than
this [1] and this [2]

I try to find something in svg, scribus and libreoffice but I had not
result (maybe wrong query)

[0] http://tug.ctan.org/info/latex-refsheet/LaTeX_RefSheet.tex
 http://tug.ctan.org/info/latex-refsheet/LaTeX_RefSheet.pdf
[1] https://www.latextemplates.com/template/cheatsheet
[2]  http://wch.github.io/latexsheet/

> Anna
>

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Fwd: [OSGeo-Discuss] [FOSS4G] OSGeo Projects swag

[Luca Delucchi]

Hi devs,

Does anyone have any ideas?

-- Forwarded message -
From: María Arias de Reyna via Discuss 
Date: Mon, 5 Jul 2021 at 14:35
Subject: [OSGeo-Discuss] [FOSS4G] OSGeo Projects swag
To: OSGeo Discussions 


Hi everyone!

As this year we will not be able to give any kind of swag or
merchandise in person, we want to add a virtual "swag bag" for
attendees.

We were toying with the idea of offering things from the projects.
Like the instant classic joke of giving free QGIS licenses.

So I want to ask you, as part of FOSS4G projects, if you can send us
swags to offer. Members of projects will know better than us what each
project can offer and how to catch the eye of the attendees.

We would need:
 * An image
 * A catchy phrase
 * Longer description
 * Link, attached file or whatever we are offering. Could be a
download link of the software itself.

You can send me those in private if you don't want to spoil the surprise.

Just offering a free license of $project would be nice, but if you can
find something different or more experimental, we are here to
experiment!

Thank you so much,
María.
___
Discuss mailing list
disc...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/discuss


-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Luca Delucchi]

Il lun 14 giu 2021, 16:38 Veronica Andreo  ha scritto:

> Ciao Luca,
>

Ciao Vero,

>
>
> This is great news! It'd be great to have t.remove flags behaviour
> changed/fixed in grass 8.
> Shall we move the ticket in trac to an issue in github so we give it more
> visibility? If yes, I can do that.
>

For me it is not needed, if you like to move it I'm not against.

>
>
> cheers,
> Vero
>

Ciao
Luca

>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Luca Delucchi]

On Tue, 8 Jun 2021 at 16:10, Veronica Andreo  wrote:
>
> Hello devs,
>

Hi,

> As you all know, grass birthday is approaching... July 29th is just around 
> the corner. I'd love to celebrate GRASS' bday with a new release, with a big 
> release ;)
> Do you think that is doable? How much is missing for GRASS 8 release?
>

I would like to improve t.remove as reported
https://trac.osgeo.org/grass/ticket/3362#comment:1
I try to work on it next week

>
> Best,
> Vero
>


-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] GRASS on IRC

[Luca Delucchi]

Hi all,

there are problem with Freenode [0] where we have #grass channel.

What do you think to move to matrix.osgeo.org? It works with OSGeo account!


[0] https://diziet.dreamwidth.org/8514.html

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] ParallelModuleQueue freezes...

[Luca Delucchi]

On Thu, 27 May 2021 at 04:07, Anna Petrášová  wrote:
>
> Could you provide an example that is failing? The doctests are running for 
> me. I spent some time fixing it a couple months ago. I use Python 3.6, I 
> wonder if newer Python would cause some issues.
>

https://github.com/OSGeo/grass-addons/pull/523/files line 544, the
commented lines are not working for me..
If you want to try t.vi just comment line 543 and uncomment the
following lines..

> Anna
>

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] ParallelModuleQueue freezes...

[Luca Delucchi]

On Wed, 26 May 2021 at 15:13, Stefan Blumentrath
 wrote:
>
> Thanks, Markus.
>
> Seems that the ParallelModuleQueue itself works if it is fed with Module 
> objects, but not if MultiModule objects are put into the queue...
>
> So, I believe I am struggling with the same issue as Luca:
> https://github.com/OSGeo/grass-addons/pull/523#issue-629160914
>

probably yes

> Can it be that returns of the MuliModule should be different? If I understand 
> the source code [1]  correctly, Module returns "self" (a Module object) while 
> MultiModule returns "None". Can that be the root cause?
>

it seems to me that MultiModule returns "None" when it finish
otherwise return self.p (a Process instance)

> Any help is much appreciated...
>

same for my side :-)

> Cheers
> Stefan
>
> 1: 
> https://grass.osgeo.org/grass79/manuals/libpython/_modules/pygrass/modules/interface/module.html#MultiModule
>


-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Management of signature files

[Luca Delucchi]

On Wed, 28 Apr 2021 at 13:34, Maris Nartiss  wrote:
>
> Hello Luca,

Hi Maris,

> I would also love to hear your personal vote on an approach we should
> take with signature management tools in G8.
>

I think Vaclav's words are perfect and I quote entirely them.
Probably I like more a set of tools external from g.*


>
> I guess same applies to copy and remove too. At least i.signatures.*
> case is a bit better as these are specific tools for the task and thus
> an extra option of "signature type" can be added to distinguish sig
> from sigset.
>

yes

>
> Māris.

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] d.mon segfaulting on debian/ubuntu custom/docker

[Luca Delucchi]

Il mar 4 mag 2021, 20:30 Jachym Cepicky  ha
scritto:

> Hi,
>

Hi Jackym

>
> running
>
> d.mon start=cairo
> d.mon stop=cairo
>
> will lead to Segmentation fault.
>
> same for
>
> d.mon start=wx0
> or
>
> d.mon start=png
>
> I'm using GRASS 7.8.2, official packages from Ubuntu 20.04, nothing fancy.
>
> When tried docker image
>
> docker run --rm -ti -v $(pwd):/data/ -v $(pwd)/grassdata:/grassdata
> mundialis/grass-py3-pdal:stable-ubuntu
>
> it was segfaulting too! so was debian
>
> when trying -alpine , no problem (or did not seem to be)
>
> Any hint, what could be the reason?
>

No idea, just a silly question...
Did you try rendering any maps?
With cairo I usually set the output variable...

I'm using "d.mon start=cairo out=/path/to/file" daily and I have no
problem.

>
> Jachym
>

Ciao
Luca

>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Management of signature files

[Luca Delucchi]

Hi Maris,

On Wed, 28 Apr 2021 at 07:38, Maris Nartiss  wrote:
>
> These are only band-aids for current situation.
> i.signature.copy is dangerous to use – one has to be certain that
> raster map order in REF files of both groups match. If one group has
> different order, it still will copy over signature file without
> complaints (think – use data of green band to analyse content of red
> band).

I opened a ticket https://github.com/OSGeo/grass-addons/issues/517 if
you have any better idea please add it to the issue

> i.signature.list only lists signatures of type sig but ignores sigset
> – nothing to see here.
>
https://github.com/OSGeo/grass-addons/issues/518

>
> Māris.
>

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] problem compiling addons

[Luca Delucchi]

On Mon, 29 Mar 2021 at 14:45, Markus Neteler  wrote:
>
> Hi Luca,
>

Hi Markus,

> On Mon, Mar 29, 2021 at 8:47 AM Luca Delucchi  wrote:
> >
> > Hi devs,
> >
> > I'm trying to compile addons against my local GRASS installation. On
> > my machine Python2 doesn't exist so I don't have python command, so I
> > cannot compile because It cannot find python
> >
> > if [ "/home/lucadelu/installati/grass78/scripts/t.rast.what.aggr" !=
> ...
> > /home/lucadelu/installati/grass78/scripts/t.rast.what.aggr
> > --html-description < /dev/null | grep -v '\|' >
> > t.rast.what.aggr.tmp.html ; fi
> > /usr/bin/env: 'python': No such file or directory
>
> Did you try (Ubuntu/Debian/...):
>
> sudo update-alternatives --install /usr/bin/python python /usr/bin/python3 1
> ?
>

yes, nothing changed


> ...
> > If add create python command a symbol link of python3 I have another problem
> >
> > gmake78
> > if [ "/home/lucadelu/installati/grass78/scripts/t.rast.what.aggr" !=
> ...
> > GISBASE=/home/lucadelu/installati/grass78
> > PATH="/home/lucadelu/installati/grass78/bin:/home/lucadelu/installati/grass78/bin:/home/lucadelu/installati/grass78/scripts:$PATH"
> > PYTHONPATH="/home/lucadelu/installati/grass78/etc/python:/home/lucadelu/installati/grass78/gui/wxpython:$PYTHONPATH"
> > LD_LIBRARY_PATH="/home/lucadelu/installati/grass78/bin:/home/lucadelu/installati/grass78/bin:/home/lucadelu/installati/grass78/scripts:/home/lucadelu/installati/grass78/lib:/home/lucadelu/installati/grass78/lib:"
> > LC_ALL=C LANG=C LANGUAGE=C g.parser -t t.rast.what.aggr.py | sed
> > s/\"/\"/g | sed 's/.*/_("&")/' >
> > /home/lucadelu/installati/grass78/locale/scriptstrings/t.rast.what.aggr_to_translate.c
> > /bin/sh: 1: cannot create
> > /home/lucadelu/installati/grass78/locale/scriptstrings/t.rast.what.aggr_to_translate.c:
> > Directory nonexistent
>
> Confirmed, I had the same issue here.
>
> ...
> > I cannot understand what is doing,
>
> It is needed for gettext extraction.
>
> > the problem seems related to
> > `scriptstrings` directory doesn't exist in locale directory
>
> Yes, I had to create it, so it would be
>
> mkdir -p /home/lucadelu/installati/grass78/locale/scriptstrings/
>

ok, this is solving also for me

> Not sure why this happens occasionally. Perhaps you have configured
> the source code --without-nls? Maybe then the subdir is not generated
> but better to always have it present?
>

no, I double checked and I didn't set --without-nls
maybe it could be useful, at the end it is just a directory

> Markus



--
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] problem compiling addons

[Luca Delucchi]

Hi devs,

I'm trying to compile addons against my local GRASS installation. On
my machine Python2 doesn't exist so I don't have python command, so I
cannot compile because It cannot find python

if [ "/home/lucadelu/installati/grass78/scripts/t.rast.what.aggr" !=
"" ] ; then GISRC=/home/lucadelu/installati/grass78/demolocation/.grassrc78
GISBASE=/home/lucadelu/installati/grass78
PATH="/home/lucadelu/installati/grass78/bin:/home/lucadelu/installati/grass78/bin:/home/lucadelu/installati/grass78/scripts:$PATH"
PYTHONPATH="/home/lucadelu/installati/grass78/etc/python:/home/lucadelu/installati/grass78/gui/wxpython:$PYTHONPATH"
LD_LIBRARY_PATH="/home/lucadelu/installati/grass78/bin:/home/lucadelu/installati/grass78/bin:/home/lucadelu/installati/grass78/scripts:/home/lucadelu/installati/grass78/lib:/home/lucadelu/installati/grass78/lib:"
LC_ALL=C LANG=C LANGUAGE=C
/home/lucadelu/installati/grass78/scripts/t.rast.what.aggr
--html-description < /dev/null | grep -v '\|' >
t.rast.what.aggr.tmp.html ; fi
/usr/bin/env: 'python': No such file or directory
make: *** [/home/lucadelu/installati/grass78//include/Make/Html.make:14:
t.rast.what.aggr.tmp.html] Error 1
rm t.rast.what.aggr.tmp.html

If add create python command a symbol link of python3 I have another problem

gmake78
if [ "/home/lucadelu/installati/grass78/scripts/t.rast.what.aggr" !=
"" ] ; then GISRC=/home/lucadelu/installati/grass78/demolocation/.grassrc78
GISBASE=/home/lucadelu/installati/grass78
PATH="/home/lucadelu/installati/grass78/bin:/home/lucadelu/installati/grass78/bin:/home/lucadelu/installati/grass78/scripts:$PATH"
PYTHONPATH="/home/lucadelu/installati/grass78/etc/python:/home/lucadelu/installati/grass78/gui/wxpython:$PYTHONPATH"
LD_LIBRARY_PATH="/home/lucadelu/installati/grass78/bin:/home/lucadelu/installati/grass78/bin:/home/lucadelu/installati/grass78/scripts:/home/lucadelu/installati/grass78/lib:/home/lucadelu/installati/grass78/lib:"
LC_ALL=C LANG=C LANGUAGE=C
/home/lucadelu/installati/grass78/scripts/t.rast.what.aggr
--html-description < /dev/null | grep -v '\|' >
t.rast.what.aggr.tmp.html ; fi
VERSION_NUMBER=7.8.6dev VERSION_DATE=2021
MODULE_TOPDIR=/home/lucadelu/installati/grass78/ \
python3 /home/lucadelu/installati/grass78/tools/mkhtml.py
t.rast.what.aggr >
/home/lucadelu/installati/grass78/docs/html/t.rast.what.aggr.html
VERSION_NUMBER=7.8.6dev
/home/lucadelu/installati/grass78/tools/g.html2man.py
"/home/lucadelu/installati/grass78/docs/html/t.rast.what.aggr.html"
"/home/lucadelu/installati/grass78/docs/man/man1/t.rast.what.aggr.1"
GISRC=/home/lucadelu/installati/grass78/demolocation/.grassrc78
GISBASE=/home/lucadelu/installati/grass78
PATH="/home/lucadelu/installati/grass78/bin:/home/lucadelu/installati/grass78/bin:/home/lucadelu/installati/grass78/scripts:$PATH"
PYTHONPATH="/home/lucadelu/installati/grass78/etc/python:/home/lucadelu/installati/grass78/gui/wxpython:$PYTHONPATH"
LD_LIBRARY_PATH="/home/lucadelu/installati/grass78/bin:/home/lucadelu/installati/grass78/bin:/home/lucadelu/installati/grass78/scripts:/home/lucadelu/installati/grass78/lib:/home/lucadelu/installati/grass78/lib:"
LC_ALL=C LANG=C LANGUAGE=C g.parser -t t.rast.what.aggr.py | sed
s/\"/\"/g | sed 's/.*/_("&")/' >
/home/lucadelu/installati/grass78/locale/scriptstrings/t.rast.what.aggr_to_translate.c
/bin/sh: 1: cannot create
/home/lucadelu/installati/grass78/locale/scriptstrings/t.rast.what.aggr_to_translate.c:
Directory nonexistent
make: [/home/lucadelu/installati/grass78//include/Make/ScriptRules.make:28:
/home/lucadelu/installati/grass78/locale/scriptstrings/t.rast.what.aggr_to_translate.c]
Error 2 (ignored)
rm t.rast.what.aggr.tmp.html

I cannot understand what is doing, the problem seems related to
`scriptstrings` directory doesn't exist in locale directory

thanks

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Luca Delucchi]

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 [0]. 
> i.landsat.qa was added a couple of weeks later, hence not there.
>
> Is there a way to re trigger the building of add-ons for windows? Or an 
> alternative solution for windows users to install add-ons?
>

I'm not a windows user, so I could say something wrong, since it is a
python script could be enough to copy the python file into addons
folder and make it executable (on Unix it works)

> Thanks much!
> Vero
>


--
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Moving to Black for Python formatting

[Luca Delucchi]

On Fri, 26 Feb 2021 at 06:00, Vaclav Petras  wrote:
>
> Dear all,
>

Dear Vaclav,

> Black is now applied to all except for GUI code (that will change hopefully 
> soon). There are few exceptions in place, most notably ctypes. The compliance 
> is checked using Checks in each PR (aka GitHub Actions). The version used is 
> Black 20.8b1. It will be updated as new releases come with possibly small 
> changes to the formatting of the code.
>
> Use the same Black version locally, but if you don't, the worst thing which 
> will happen is that the check will fail and you will need to fix your PR. 
> There is a new file in the root of the repo called pyproject.toml which your 
> local Black and perhaps your editor should pick up currently with settings 
> only for Black. Obviously, the idea is that you just throw Black formatter at 
> your file and don't care about formatting things manually anymore.
>
> A lot happened with Flake8 compiace, but that's mostly irrelevant to Black 
> except that bulk of formatting issues are gone which are now all enabled 
> except line length check and one issue which conflicts with Black. This is 
> accompanied by supporting # % and not just #% in the option parser. Thanks to 
> this and recent Flake8-related fixes by Anna, it is possible to use Flake8 
> quite effectively to check for problems although a lot of issues still need 
> to be ignored which is configured separately in each major directory 
> containing Python code.
>
> Several non-whitespace changes were included in the Black formatting, namely 
> updates of remaining u-string literals to Python 3 and some trailing comma 
> syntax which now makes Python 3.6 the minimum.
>
> There is also a PR #1391 which will make it easy to ignore these (and other) 
> formatting commits when doing git blame in the command line. The GitHub web 
> interface offers an easy way to move over a revision.
>

thanks a lot for the explanation

> All this applies to core repo, not the grass-addons repo. Ideas and 
> volunteers are welcome.
>

Do you have any suggestions on how to proceed to grass-addons?
Did you just run blake inside a folder or did you do something more?

> Best,
> Vaclav
>

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[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:
>
> https://github.com/opengeospatial/joint-ogc-osgeo-asf-sprint-2021/issues/2
>

could make sense to start a v.in.ogc.features to import features from
OGC API Feature service using owslib library?

>
> Vaclav

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] ASF - OGC - OSGeo code sprint - Feb 17-19, 2021

[Luca Delucchi]

On Thu, 11 Feb 2021 at 16:28, Anna Petrášová  wrote:
>
> Hi Vero,
>
Hi all,

> we registered for this, we probably won't participate 100% of the time, but 
> hope to see other GRASS devs there.
>

I also registered myself!

> Anna & Vaclav
>

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSoC 2021 Project - Sunveer Singh

[Luca Delucchi]

On Wed, 3 Feb 2021 at 14:15, Sunveer Singh  wrote:

> Dear Team,
>
> Dear Devs,


> I am Sunveer Singh, I graduated from high school in 2021 and will start my
> undergraduate studies in Fall 2021 and have been accepted into a university
> so it makes me eligible to participate in GSoC this year.
>
> I was Google Code-in 2017 Grand Prize Winner, Google Code-in 2018
> Finalist, and Google Code-in 2019 Mentor with OSGeo. And I majorly worked
> on GRASS GIS unit testing tasks during that time. And I would like to work
> on a GSoC project with GRASS GIS related to it.
>

you can see his tests here
https://github.com/OSGeo/grass/search?q=Sunveer=code


> I found this following project and I would be happy to work on it this
> year:
> https://trac.osgeo.org/grass/wiki/GSoC/2017#Toolsforgeneratingunittestsfromexamplesinthemanual
>
>
> I see that this project was skipped after 2017 and no one had worked on
> it, so I would like to work on this as it is totally of my interest and my
> skills. Will the mentors written on the page will be the same i.e Vaclav
> Petras and Soeren Gebbert?
>
>
Sunveer showed a lot of dedication and interest in GRASS GIS project, I
think he would be a great candidate for GSOC

Thank You
> Sunveer
> https://sunveersingh.github.io/
>
> --
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Luca Delucchi]

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 seen as archaic and not accessible
> ‘’’
>
> What about migrating our mailing list to mailman3?
> The postorius interface looks modern and when integrated with hyper kitty, 
> allows an easy access to the list archives (including search and post 
> statistics).
>

I fully agree with this proposal, but this should be done at OSGeo
Level, Massimo do you want to investigate this solution with SAC?

>
> My 2cents.
>

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Fwd: [Board] Fwd: Scheduling of the Joint OGC OSGeo ASF Virtual Code Sprint

[Luca Delucchi]

-- Forwarded message -
From: Angelos Tzotsos 
Date: Wed, 20 Jan 2021 at 14:40
Subject: [Board] Fwd: Scheduling of the Joint OGC OSGeo ASF Virtual Code
Sprint
To: OSGeo Board , ,
proje...@lists.osgeo.org , OSGeo Discussions <
disc...@lists.osgeo.org>





 Forwarded Message 
Subject: Re: Scheduling of the Joint OGC OSGeo ASF Virtual Code Sprint
Date: Wed, 20 Jan 2021 12:48:37 +
From: Gobe Hobona  
To: oapi-styles@lists.opengeospatial.org,
edr-api@lists.opengeospatial.org,
ogcapi-records@lists.opengeospatial.org, OGC API Maps SWG

, OGC WFS-FES SWG

,
ogcapi-common@lists.opengeospatial.org,
ogcapi-processes@lists.opengeospatial.org,
coverages@lists.opengeospatial.org,
ogcapi-tiles@lists.opengeospatial.org,
routing@lists.opengeospatial.org
CC: Martin Desruisseaux 
, Angelos Tzotsos 


All,

The Joint Virtual Code Sprint will be held on the 17th, 18th and 19th of
February 2021 starting from 07:00am EST until 05:30pm EST each day.

Please reserve the dates in your calendars.

The formal announcement is being prepared and will include a link to the
Registration page.

Regards,

Gobe


On 12 Jan 2021, at 13:21, Gobe Hobona  
wrote:

All,

The Apache Software Foundation (ASF), Open Geospatial Consortium (OGC), and
Open Source Geospatial Foundation (OSGeo) are currently planning a joint
Virtual Code Sprint to be held during the second half of February 2021.

The code sprint will cover multiple ASF and OSGeo projects, and OGC
standards. The code sprint is open to all participants in ASF, OSGeo and
OGC, even if you are not active members or contributors to the efforts of
the organizers.

To help us schedule the sprint, please enter your availability for the
sprint into the Doodle poll at https://doodle.com/poll/3ptyzi9vwfuak5bq



The Doodle poll will close on Tuesday 19th January 2021 at 17:00 EST.

Please feel free to forward this message to any colleagues that may be
interested.

Regards.

Gobe
__

Gobe Hobona, PhD MRICS
Director of Product Management, Standards | Open Geospatial Consortium (OGC)
Tel: +44 744 409 6781
ghob...@ogc.org   | ogc.org
  | @opengeospatial



-- 
  

 ___
Board mailing list
bo...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/board


-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Luca Delucchi]

On Sun, 17 Jan 2021 at 15:27, Stefan Blumentrath
 wrote:
>
> Dear all,
>
Dear al,,

> In general, I do agree with Moritz on this.
>
> In addition to the risk of more fragmented communication, I do appreciate the 
> fact that ML-discussion is archived. Furthermore, GitHub discussion seems to 
> be a feature that locks us more into GitHub and would it make more 
> complicated if we should be forced to move to another platform (given the 
> proprietary nature of GitHub).
>
> I do also see that some discussion has moved to github issues/PRs, but that 
> is probably only natural, esp. when point of the discussion is specifics of 
> an implementation / change.
>
> However, to address both valid issues (demand for web-based forum and a 
> coherent communication), we could probably to three things:
> 1. Encourage all contributors to discuss/mention more significant changes on 
> the ML.
> 2. Promote nabble 
> [http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html] on our github 
> repository
> 3. Check whether it would be feasible to sign up to nabble / ML with 
> OAuth/github to make integration more seamless. I have no idea though if this 
> would be feasible at all. Maybe OSGeo admins know?...
>

I also agree with Mortiz and Stefan

> Cheers
> Stefan
>

ciao
Luca
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Fwd: [Projects] Fwd: Scheduling of the Joint OGC OSGeo ASF Virtual Code Sprint

[Luca Delucchi]

-- Forwarded message -
From: Angelos Tzotsos 
Date: Tue, 12 Jan 2021 at 15:21
Subject: [Projects] Fwd: Scheduling of the Joint OGC OSGeo ASF Virtual Code
Sprint
To: , proje...@lists.osgeo.org <
proje...@lists.osgeo.org>, OSGeo Board , OSGeo
Discussions 





 Forwarded Message 
Subject: Scheduling of the Joint OGC OSGeo ASF Virtual Code Sprint
Date: Tue, 12 Jan 2021 13:21:24 +
From: Gobe Hobona  
To: oapi-styles@lists.opengeospatial.org,
edr-api@lists.opengeospatial.org,
ogcapi-records@lists.opengeospatial.org, OGC API Maps SWG

, OGC WFS-FES SWG

,
ogcapi-common@lists.opengeospatial.org,
ogcapi-processes@lists.opengeospatial.org,
coverages@lists.opengeospatial.org,
ogcapi-tiles@lists.opengeospatial.org
CC: Martin Desruisseaux 
, Angelos Tzotsos 


All,

The Apache Software Foundation (ASF), Open Geospatial Consortium (OGC), and
Open Source Geospatial Foundation (OSGeo) are currently planning a joint
Virtual Code Sprint to be held during the second half of February 2021.

The code sprint will cover multiple ASF and OSGeo projects, and OGC
standards. The code sprint is open to all participants in ASF, OSGeo and
OGC, even if you are not active members or contributors to the efforts of
the organizers.

To help us schedule the sprint, please enter your availability for the
sprint into the Doodle poll at https://doodle.com/poll/3ptyzi9vwfuak5bq



The Doodle poll will close on Tuesday 19th January 2021 at 17:00 EST.

Please feel free to forward this message to any colleagues that may be
interested.

Regards.

Gobe
__

Gobe Hobona, PhD MRICS
Director of Product Management, Standards | Open Geospatial Consortium (OGC)
Tel: +44 744 409 6781
ghob...@ogc.org | ogc.org | @opengeospatial


-- 
  

 ___
Projects mailing list
proje...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/projects


-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [Projects] [Board] upcoming OSGeo/OGC/Apache code sprint

[Luca Delucchi]

On Fri, 8 Jan 2021 at 14:16, Angelos Tzotsos  wrote:
>
> Hi all and happy new year!
>

Hi Angelos,

> We will soon be able to announce dates for the code sprint.
> If projects are willing to participate (and be listed in the official
> announcement) please let us know.
>
GRASS GIS project is happy to join, thanks

> Best,
> Angelos
>

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Fwd: [Projects] [Board] upcoming OSGeo/OGC/Apache code sprint

[Luca Delucchi]

Are we interested to participate?

-- Forwarded message -
Da: Angelos Tzotsos 
Date: ven 8 gen 2021, 14:16
Subject: Re: [Projects] [Board] upcoming OSGeo/OGC/Apache code sprint
To: 
Cc: osgeo-board List 


Hi all and happy new year!

We will soon be able to announce dates for the code sprint.
If projects are willing to participate (and be listed in the official
announcement) please let us know.

Best,
Angelos

On 12/10/20 3:05 PM, Tom Kralidis wrote:
> Hi everyone: as part of our ongoing collaboration with OGC, and given
> the synergy of FOSS4G projects and OGC standards, we are working with
> OGC and the Apache Software Foundation to coordinate an OSGeo/OGC/ASF
> virtual code sprint in Q1 2021 (~February 2021).
>
> As with previous OSGeo presence at OGC Hackathons, we will document and
> report on OSGeo participation at the event.  This will provide
> value in terms of having a sense of FOSS4G projects involvement as part
> of our OGC collaboration.  This will also help coordinate involvement
> at future hackathons / code sprints at both OSGeo code sprints (i.e.
perhaps
> a dedicated interoperability theme), OGC Hackathons, or related ASF
events.
>
> We are working with OGC and ASF to coordinate dates for the events, as
well
> as a joint announcement to help advertise the event details in the coming
weeks.
>
> Given the synergy of FOSS4G projects and OGC standards, we kindly ask
> that projects
> consider participation in this important upcoming event.  This event with
also
> will be a first between OSGeo/OGC and ASF, and provides the opportunity
> for cross-pollination with ASF geospatial projects (see [1] as an example
of
> geospatial projects presented at ApacheCon 2020 as an example).
>
> Thanks
>
> ..Tom
>
> [1] https://apachecon.com/acah2020/tracks/geospatial.html
> ___
> Board mailing list
> bo...@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/board
> .


-- 
Angelos Tzotsos, PhD
President
Open Source Geospatial Foundation
http://users.ntua.gr/tzotsos

___
Projects mailing list
proje...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/projects
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Luca Delucchi]

On Thu, 19 Nov 2020 at 14:02, Moritz Lennert
 wrote:
>
> Hi,
>
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 used for data that is common to many projects and can thus be 
> accessed read-only from their respective mapsets. This helps avoiding data 
> duplication across projects.
>
> In the perspective where each location is a project we this would somehow get 
> lost, as this concept invites duplication into each project.
>
> However, Luca raised an interesting point in the chat which we didn't get to 
> discuss: it might be possible to define some mechanism to make data in one 
> location readable from another location as long as they are in the same SRS. 
> An easy and dirty way is obviously to just use symbolic links as Luca seemed 
> to suggest, but that means there is no control over the actual correspondence 
> of location definitions. Also I don't know how cross-platform this would be.
>
> But maybe we could take this idea and create a more sophisticated mechanism, 
> extending g.mapsets to allow creating a read-only access to mapsets even 
> outside the current location, as long as the reference systems are identical 
> (would just requiring the PROJ files to be identical be enough ? Too 
> restrictive ?).
>
> This would possibly allow to go further in the idea of organizing data by 
> projects instead of locations, while also keeping
> the idea of avoiding data duplication (people could create base data projects 
> with data common to many projects).
>
> How does that sound ?
>

I support any idea that could be useful for GRASS, and I think project
could bring more users, however I would like to continue to work as I
do today and I think this is the main idea of Vaclav, if I understood
correctly.
If we want switch to project I think we should remove all the
references to Location (in doc and code)

> Moritz
>

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] OSGeo virtual code sprint

[Luca Delucchi]

On Fri, 6 Nov 2020 at 12:42, Veronica Andreo  wrote:
>
> Hi devs,
>

Hi

> Now that the dates for the OSGeo virtual code sprint are set, is anyone 
> planning to participate? The table here [0] looks pretty empty so far... I'm 
> not sure I'll be able to commit full time, but we could arrange a meeting one 
> of those days to discuss our own agenda. What do you think?
>

I will participate, for the meeting depends on scheduled time

> Just an idea :)
>
> Cheers,
> Vero
>

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Make terminal window optional?

[Luca Delucchi]

On Sun, 6 Sep 2020 at 05:06, Vaclav Petras  wrote:
>
> Dear all,
>

Hi Vaclav,

>
> 2. Remove the terminal from desktop launchers so that GRASS GIS starts 
> without the terminal when started in the GUI way. When a user starts GRASS 
> GIS using a command from an existing terminal, there is no change from the 
> current behavior: a (sub-)shell is started and possibly GUI launches.
>

this is fine for me

> Best,
> Vaclav
>

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Fwd: [Projects] Promoting OSGeo projects on the MapScaping Podcast

[Luca Delucchi]

I think it could be a good way to increase GRASS visibility.. I cannot
help so much since my english is really poor :-/

-- Forwarded message -
From: Jody Garnett 
Date: Tue, 23 Jun 2020 at 17:46
Subject: [Projects] Promoting OSGeo projects on the MapScaping Podcast
To: proje...@lists.osgeo.org 


The Marketing Committee is exploring additional outreach ideas to
reach everyone who cannot join us for FOSS4G this year.

Our first experiment is to collaborate with the MapScaping Podcast
(which you may already know from recent presentations on PostGIS,
PostgreSQL, QGIS, Qfield and other technologies). We are looking for
volunteers to do a podcast episode on additional OSGeo projects.

Projects wishing to take part please contact the marketing committee
mailing list, we have allocated a budget for 4 projects to be
represented.

Here are some words from Daniel and the MapScaping podcast:

My name is Daniel O’Donohue, I am a big fan and user of open source
geospatial software. I am also the host of The MapScaping Podcast
which is a weekly podcast for the geospatial community.

I would like to work with you to increase the awareness of open source
geospatial software. I have published episodes about Postgres/
Postgis, QGIS, QField and Input, R, and geospatial python which my
audience has responded well to. I would really like to promote and
introduce people to other open-source geospatial tools but producing
and publishing podcasts is not free and finding qualified guests to
talk about things like GeoNode and Geoserver is not easy.

Here is what my process for producing a podcast episode looks like:

Pre-interview
This is a 30-40 minute informal call where we can meet each other and
discuss topics and questions that might lead to interesting and
informative conversation for the audience. I use a software called
calendly which takes care of all of the time zone issues. I will send
you a link, you choose I time that suits you and we can go from there.
All the pre-interviews and interviews are recorded remotely using
software called cleanfeed. There is nothing to install, I will send
you a link and as long as you have a good microphone and a quiet place
we should be fine. This is also an opportunity for me to test your
audio and explain the structure of the interview and what the
recording process looks. Great audio quality and the ability to speak
clearly is a must!

If the pre-interview goes well we will schedule a time to record a
podcast episode. I like to schedule an hour for each interview, the
published episode will be somewhere between 30-40 minutes but by
scheduling an hour we have time to fix any technical issues and repeat
questions and answers if needed. The episode will typically be
published somewhere 2 - 4 weeks after being recorded.

If you are interested in being involved it is a good idea to listen to
an episode or two so you get a feel for the style and structure of the
podcast. I am really looking forward to working with you on this!

--
Jody Garnett
___
Projects mailing list
proje...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/projects


-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] v.what.strds: timestamp column

[Luca Delucchi]

On Tue, 16 Jun 2020 at 00:08, Stefan Blumentrath
 wrote:
>
> Hei Martin,
>
Hi,

>
> What about:
>
> https://grass.osgeo.org/grass78/manuals/addons/v.what.strds.timestamp.html
>
> Written for the IRSAE course at Studenterhytta (Oslo, Norway), in order to 
> e.g. spatio-temporal match temperature timeseries and GPS-tracking data.
>

I used it successfully few months ago

>
> Cheers,
>
> Stefan
>

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Busy SQLITE db

[Luca Delucchi]

On Mon, 4 May 2020 at 11:18, Stefan Blumentrath
 wrote:
>
> Ciao Luca,
>

Ciao Stefan,

> If you have stale processes e.g. on cluster nodes that have the DB opened 
> this may occur.
>

first time it happen---

> Also the file system can have an impact (e.g. writing to an SQLite DB on a 
> CIFS file system from Linux is simply impossible). But that should give a 
> different error message.
>
> So I would look for hanging processes... And you could try to copy the 
> mapset, remove the old one and rename the copy back...
>
yes, I would avoid this, but it worked

> Cheers
> Stefan
>

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Busy SQLITE db

[Luca Delucchi]

Hi all,

I'm facing the problem with Busy SQLITE db using GRASS 7.8 in a HPC system.
Reading other problems like that I saw a Metz answer [0] and another
from Luis [1] but I'm not able to fix the problem. Now the mapset is
unusable with vector.

Do you have any idea how to solve the problem and where it come from?

g.remove type=vector name=nuts2_lst_2003_daily -f
Removing vector 
WARNING: Busy SQLITE db, already waiting for 10 seconds...
WARNING: Busy SQLITE db, already waiting for 20 seconds...

[0] http://osgeo-org.1560.x6.nabble.com/SQLITE-db-locking-problem-td5182180.html
[1] 
https://gis.stackexchange.com/questions/321986/grass-what-to-do-when-the-sqlite-database-becomes-busy

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Luca Delucchi]

On Fri, 27 Mar 2020 at 16:35, Veronica Andreo  wrote:
>
> Hello again
>
> Markus reminded me of the daylight saving time change over there happening 
> this weekend, so to avoid confusion, we meet at:
>
> https://www.timeanddate.com/worldclock/meetingdetails.html?year=2020=3=29=18=0=0=37=48=195=51=671=207
>
> here https://meet.jit.si/grass-website
>

ok, I will join as soon the children are sleeping (around 21:30)

> Cheers,
> Vero
>

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Luca Delucchi]

On Tue, 24 Mar 2020 at 18:40, Veronica Andreo  wrote:
>
> Hi Stefan :)

Hi all,

>>
>> If not, maybe a first step could be create a task list / issues based on:
>>
>> https://grasswiki.osgeo.org/wiki/Website_migration_plan_2019 (?)
>>
>> where people can sign up to certain tasks, so we work coordinated?
>
>
> We don't have it, but it is indeed a very good idea. Would you be willing to 
> draft something in the wiki and then we can add stuff there? Maybe organize 
> by pages/sections?

could we use the existing page
https://grasswiki.osgeo.org/wiki/Website_migration_plan_2019, if yes I
can update the wiki page with the jobs already done

>
> Yes, many might be in the same position. We could do a general kick-off call 
> and then each one works in their (self)assigned task(s)
>

+1

> Let's hear others' opinion
>
> Cheers,
> Vero
>

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] compiling failing in ctypes

[Luca Delucchi]

Hi devs,

I updated my OS to debian unstable (bullseye) and I'm not able anymore
to compile grass (7.8 releasebranch and master) because ctypes has
errors, I attach the error file.
I'm compiling it with python3 (3.7.7 version)

Any idea?

-- 
ciao
Luca

www.lucadelu.org


ctype.err
Description: Binary data
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Luca Delucchi]

On Sat, 14 Mar 2020 at 15:27, Paulo van Breugel  wrote:
>
> Dear devs,
>

Dear Paulo,

> 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 used to work I think, but now gives me some errors:
>
> db.copy from_driver=sqlite
> from_database=/media/grassdb/biodiv/PERMANENT/sqlite/sqlite.db
> from_table=vegetation_lookup to_driver=sqlite
> to_database=$GISDBASE/$LOCATION_NAME/$MAPSET/sqlite/sqlite.db
> to_table=vegetation_lookup
>
> ERROR: Unable to create directory '///sqlite' for sqlite database
> dbmi: Protocol error
> WARNING: Unable to open database  by driver 
>
> Any idea what I am doing wrong here?
>

try to protect the to_database string value like
'$GISDBASE/$LOCATION_NAME/$MAPSET/sqlite/sqlite.db' otherwise the
variable are replaced with empty value

> With kind regards,
>
> Paulo
>

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] silly question

[Luca Delucchi]

Hi Michael,

On Wed, 4 Mar 2020 at 19:49, Michael Barton  wrote:
>
> I want to do something that should be simple but it is not. I want to be able 
> to update my fork of GRASS source code from master. The wiki instructions say 
> I should be able to do this with:
>
> git fetch upstream
> git rebase upstream/master
>
> But when I do, I get:
>
> unable to access 'https://github.com:OSGeo/grass.git/': Port number ended 
> with 'O'
>

it seems wrong the url, it should be https://github.com/OSGeo/grass.git

> Any suggestions? I don't want to have to keep forking and cloning
>
> Michael
>


-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Workshop a FOSS4G 2020

[Luca Delucchi]

Hi everybody,

Is someone thinking to submit a workshop proposal for FOSS4G 2020?

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] r.in.wms not by default in winGRASS 7.8.1

[Luca Delucchi]

On Wed, 22 Jan 2020 at 08:57, Yann Chemin  wrote:
>
> Hi,
>

Hi Yann,

>
> is there a possibility to manually make it available somehow?

you could try wx.metada [0]

> Thank you
> Yann

[0] 
https://github.com/OSGeo/grass-addons/tree/master/grass7/gui/wxpython/wx.metadata
[1] https://grasswiki.osgeo.org/wiki/ISO/INSPIRE_Metadata_Support

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Luca Delucchi]

On Sat, 14 Dec 2019 at 13:57, Moritz Lennert
 wrote:
>
> As a heads up:
>

the code to run the tests is here

https://github.com/lucadelu/caniuse/tree/grass

it should be improved, but right now I have no time

>
>  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 the European Commission - Joint Research Centre (JRC) we have been
> working with our Contractors (WeTransform and Epsilon Italia) on a set
> of actions aimed at improving the usability of INSPIRE data sets. For
> those who are not familiar with INSPIRE [1], this is the European
> Spatial Data Infrastructure (SDI) built on top EU Member States
> infrastructures to support European environmental policies.
>
> The rationale behind these actions is that GML is the default encoding
> for INSPIRE data because INSPIRE xml schemas are generated automatically
> from the conceptual UML models. These schemas are complex and many
> existing (web, desktop and mobile) client applications are not able to
> fully consume or make use of data shared according to these schemas.
>
> Two actions have been completed over the last year in order to:
> 1) improve client support for INSPIRE data
> 2) develop an alternative encoding for INSPIRE data (GeoJSON)
>
> Within the first Action [2], we compiled a "can I use" matrix [3]
> describing which functionality associated with the consumption of
> INSPIRE data (both in GML and GeoJSON) is supported by which client. The
> clients tested are QGIS, GRASS GIS, hale studio, OpenLayers and
> LeafletJS as well as some proprietary solutions.
>
> This e-mail is first of all to inform you about this Action and to show
> that, as you can notice in [3], open source solutions are currently the
> most successful ones, but some improvement is still possible. In this
> regard, we have established communication with the software PSC and/or
> communities and discussed the prioritisation of functionalities that
> should be improved or developed for each software to best satisfy user
> needs.
>
> Whenever other encodings (e.g. GeoPackage) for INSPIRE data will become
> available, the same approach should be followed.
>
> In addition, since the Action is formally completed but the outcomes
> will still be very important for the INSPIRE community in the future, we
> are currently exploring how to ensure the sustainability of the tool. In
> particular, we would open an invitation to anyone (project developers,
> users or communities, or simply interested people) to contribute to keep
> the matrix up-to-date by testing new/future versions of specific OSGeo
> tools (in particular those mentioned above - QGIS, GRASS GIS, OpenLayers
> and LeafletJS - but also other tools). The tests, described at [4],
> consist of general GIS tasks and do not require INSPIRE-specific
> knowledge. Interested people can also submit content through issues or
> pull requests in the GitHub repository [5] or contact us.
>
> Thank you all for your attention.
> Best regards,
> Alex and Marco
>
>
> [1] https://inspire.ec.europa.eu
> [2]
> https://webgate.ec.europa.eu/fpfis/wikis/pages/viewpage.action?pageId=418580131
> [3] https://inspire-mif.github.io/caniuse/generator/out.html
> [4] https://github.com/INSPIRE-MIF/caniuse/tree/master/docs
> [5] https://github.com/INSPIRE-MIF/caniuse
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev



-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Fwd: [TOSprint] OSGeo Code Sprint 2020 in Athens: Pick the dates

[Luca Delucchi]

If you are interested in participating please choose you best dates

-- Forwarded message -
From: Angelos Tzotsos 
Date: Tue, 12 Nov 2019 at 16:27
Subject: [TOSprint] OSGeo Code Sprint 2020 in Athens: Pick the dates
To: 


Hi all,

We finally got available dates for the venue:
27/4 - 1/5
4/5 - 7/5
25/5 - 29/5

Here is a poll to figure out the dates:

https://doodle.com/poll/zrkp3ztzs764uifq

Cheers,
Angelos


--
Angelos Tzotsos, PhD
Charter Member
Open Source Geospatial Foundation
http://users.ntua.gr/tzotsos

___
TOSprint mailing list
tospr...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/tosprint


-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GRASS GIS at FOSS4G

[Luca Delucchi]

Il mer 5 giu 2019, 22:21 Moritz Lennert  ha
scritto:

> Hi everyone,
>

Hi,
I'm not sure yet to be in Bucharest, but

>
> I will be in Bucharest from Sunday, Aug 25 afternoon, until Saturday,
> Aug 31, mid-day.
>
> The TGRASS workshop is on August 27, 14:00 - 18:00.
>
> I was wondering:
>
> - Who else will be in town at the beginning of the
> week ?
>

I should arrive Wednesday

- Should we organise some form of small GRASS sprint on Monday and
>   Tuesday ?
>

If you want space I can ask to the organization...

- 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 available at the
>   FOSS4G premises ?
>

I didn't book anything yet but I should be hosted by a friend living in
Bucharest

>
> What do you think ?
>
> Moritz
>

Ciao
Luca

>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Early "warning": upcoming switch of SVN to readonly mode for planned GitHub migration

[Luca Delucchi]

On Fri, 17 May 2019 at 16:28, Martin Landa  wrote:
>
> Hi,
>

Hi,

> pá 17. 5. 2019 v 9:25 odesílatel Martin Landa  napsal:
> > > later tonight or tomorrow (Friday, May 17th, 2010) we'll switch the
> > > GRASS GIS svn server to readonly-mode, in order make the GitHub
> > > migration [1] possible.
> >
> > done, svn is in READ-ONLY mode. Please do not try to commit.
>
> migration done for core repo. Please REVIEW result at
>
> https://github.com/OSGeo/grass
>
> Thanks. Martin
>

thanks a lot!

> PS: Addons and Promo repo migration will be finished tomorrow afternoon (CET).
>


-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Luca Delucchi]

On Wed, 15 May 2019 at 21:40, Veronica Andreo  wrote:
>
> Hi,
>

Hi,


>> 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 
>> want me to show some examples).
>
>
> I am very interested in such examples, esp. how the workflow will be from now 
> on for example when making a small change in manuals.
>

Yes, it is important to know this. How to use branches and also how to
update local version from the master one. Should we use a private
clone and make pull request to the main repository o use the main
repository directly?

> I think it is very important that those of you more familiar with git and 
> GitHub develop or show example workflows of how to contribute, backport (if 
> that will be still called like that), and so on.
>

+1

> my 0.01 cent
> Vero
>

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Luca Delucchi]

On Thu, 9 May 2019 at 15:18, Moritz Lennert
 wrote:
>
>
> Generally all GSoC or similar events are handled centrally via OSGeo
> with individual projects providing ideas.
>
> This year, OSGeo has been accepted as organisation:
> https://wiki.osgeo.org/wiki/Season_Of_Docs_2019
>
> For GSoC, see:
> See https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2019
>
>
> Markus did transmit the info to the list:
>
> https://lists.osgeo.org/pipermail/grass-dev/2019-April/091819.html
>

If we want to partecipate we should write some ideas as Geonetwork o
QGIS [0], if someone would like to leads this action I can help..

>
> Moritz
>

[0] https://wiki.osgeo.org/wiki/Season_of_Docs_Ideas_2019


-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Luca Delucchi]

On Tue, 26 Mar 2019 at 03:11, Facundo Ferrin  wrote:
>
> Hi there!

Hi Facundo,
>
>
> My name is Facundo Ferrin. I am a nuclear engineer who is taking a master in 
> Computer Vision in Barcelona, and finally I found my opportunity to 
> contribute to OSGeo by applying two things that I really like: Python and 
> Backend development . I do not know exactly what I should write in this first 
> email, so I'll start by listing the projects I'm interested in.
>
> I'm working in a company that is developing a platform for precision 
> agriculture called Auravant (https://www.auravant.com/). I work as a backend 
> developer and data analyst and I use daily almost every tool that you post in 
> the ideas: GeoServer, PostGIS, QGis. I'm also porting a tool for polygon 
> simplification called topoJSON (https://github.com/fferrin/topojson).
>
> ---
> MY MAIN IDEA is to start porting GRASS tools into a python package that can 
> be used in other projects (beyond the client to use by command line). I don't 
> know if it's something you have in mind but for offline and automated 
> analysis it would be very useful. I particularly had problems when I tried to 
> simplify geometries since the geometry of polygons was not taken into account.
> ---

Your idea is not clear to me, there are already two Python library to
work with GRASS. you can find some ideas in the proposal page
https://trac.osgeo.org/grass/wiki/GSoC/2019 (for example
Neweasy-to-useCLIandAPIforGRASSGIS) and
https://trac.osgeo.org/grass/wiki/GSoC/2018 (Improve GRASS integration
in QGIS 3)

> Hope to hear from you soon!
>

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Introduction and Idea ( GSOC 2019 )

[Luca Delucchi]

On Sat, 2 Mar 2019 at 18:48, Soumya kanta Das
 wrote:
>
> Hello,

Hi,

> Myself Soumya Kanta Das, studying Geo-informatics. Currently i work on 
> automating geospatial workflow and Machine learning applications. I have 
> previously worked on automated identification of buildings in Satellite 
> imagery using Deep learning. I have language proficiency in python.
>
> I would like to develop a Deep learning module for grass using tensorflow 
> library and python 3. Which would be very helpful for end-users.
>

something already exists in GRASS GIS addons using tensorflow [0], you
can have look there..

> Thank you.
>

[0] https://grass.osgeo.org/grass74/manuals/addons/i.ann.maskrcnn.html

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] i.sentinel improvements

[Luca Delucchi]

On Wed, 13 Feb 2019 at 15:02, Roberta Fagandini  wrote:
>
> I took a look at the interface and I saw a new text form for the output 
> suffix name..if the -c flag is checked, does the module create two different 
> output (13 atmospherically corrected bands and 13 topographically corrected 
> bands)?

right now yes

> maybe only one output (i.e. 13 bands to which both corrections are applied) 
> would be better.
>

could make sense, probably a new flag to keep/remove atmospherically
corrected bands could be useful

>
> ciao
> Roberta
>


-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] i.sentinel improvements

[Luca Delucchi]

On Mon, 17 Dec 2018 at 10:38, Luca Delucchi  wrote:
>
> Hi all,
>

Hi devs,

> - i.sentinel.preproc add capability to compute topographic correction
> using the following prcedure
>

done in r74080, please test it

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] closing tickets as wontfix because of "No activity"

[Luca Delucchi]

On Sat, 9 Feb 2019 at 22:42, Markus Metz 
wrote:

> Hi Martin,
>

Hi,

>
> I don't think it is a good idea to close tickets as "wontfix" because of
> "No activity". The issues might still be relevant. I suggest to ping the
> appropriate maintainer(s) instead.
>
>
I had same feeling...


> "wontfix" should IMHO be used if a ticket can not be fixed for technical
> reasons.
>
> my2c
>
> Markus M
>
>
-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Luca Delucchi]

On Fri, 8 Feb 2019 at 15:27, Veronica Andreo  wrote:
>
> Hi everyone,
>
> I think we can manage to propose 2 workshops to show how great GRASS is, no? 
> And the 2 topics  on the table are pretty interesting so, why not?
>

Yes we can propose it but it is not sure that they will accept both.
One year, I don't remember which, only one per software was acepted
since there was to many submissions and not enough rooms

>
> Vero
>

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Luca Delucchi]

On Fri, 25 Jan 2019 at 11:49, Moritz Lennert
 wrote:
>
> Who else will come to Bucharest ? Anyone willing to (co-)organise a
> workshop ?
>

I will but I cannot choose the dates yet. I can help to co-organise...

> What topics would users find the most useful for a workshop ?
>

temporal series
remote sensing
classification

??

> Moritz
>


-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Fwd: [pdal] C API for PDAL now on GitHub

[Luca Delucchi]

Hi all,

Could this be useful for pdal integration?

Regards
Luca

-- Forwarded message -
From: Jaime Soto 
Date: ven 25 gen 2019, 16:28
Subject: [pdal] C API for PDAL now on GitHub
To: 


There is now a C API for PDAL available at https://github.com/PDAL/CAPI.
The API exposes PDAL's JSON pipeline functionality just like the Python and
Java bindings available at GitHub. Take a look at the tests for examples on
how to use the API.

A "pdal-c" package is also available for vcpkg and a conda-forge package is
on its way. I hope that this library serves as a useful FFI for other
language bindings. Please submit an issue or pull request at GitHub if you
have any suggestions. Your help will be much appreciated.

Thanks,

Jaime Soto | js...@simverge.com

___
pdal mailing list
p...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/pdal
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Luca Delucchi]

On Tue, 22 Jan 2019 at 08:09, Stefan Blumentrath 
wrote:

> Hei,
>

Hi,


>
> Just wondering, regarding migration to git, would it be helpful to use
> AddOns (and possibly sandbox) as a test case?
>
>
yes this could be a good idea, but first probably we have to choose which
git platform to use. There are many possible options right now


> Anyway, let me know if / how amateurs like me can contribute / help with
> the migration process...
>
>
same here


> Cheers
> Stefan
>
>
-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Luca Delucchi]

On Sun, 20 Jan 2019 at 23:11, Stefan Blumentrath
 wrote:
>
> Indeed, great job, Vero, Markus and Markus!
> Thanks for your effort!
>

Thanks a lot

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Release policy: towards an urgent GRASS GIS release with Python3 support

[Luca Delucchi]

Il giorno gio 27 dic 2018, 10:38 Markus Neteler  ha
scritto:

> Dear all,
>

Dears,


> We may discuss to make 7.6 LTS and 7.4 EOL but many distros won't
> allow to update to 7.6 nor a 7.6 LTS will motivate us to avoid
> backporting and focus on 7.8 :-)
>
> Opinions?
>


Are we sure that a so big change does not require a major release, moving
forward to 8.0?

I remember already some discussion about it but I don't remember if we
arrive to a conclusion.


> Markus
>

my2cents

Luca

>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Budget to request to OSGeo

[Luca Delucchi]

Hi all,

I saw few emails from other projects for the budget 2019 to ask to OSGeo, I
didn't see any email here, do we need funds?

Regards
Luca
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] i.sentinel improvements

[Luca Delucchi]

Hi all,

I would like to do some improvements in i.sentinel
Since I'm not the main author I would like to get approval before to
start to work on it.
- i.sentinel.download add capability to filter out scenes with small
percent (user could decide the percentage to keep) of area matching
the area of interest
- i.sentinel.import add capability to cut the scene on the footprint
to simplify scenes patch
- i.sentinel.preproc add capability to compute topographic correction
using the following prcedure

###
eval `r.sunmask -sg ele=DTM year=${dat:0:4} month=$(echo $dat:4:2 |
sed 's/^0*//') day=${dat:6:2} hour=${dat:9:2} minute=${dat:11:2}
second=${dat:13:2} timezone=0`
z=`echo "90 - $sunangleabovehorizon" | bc -l`
echo "${inpmap} $z $sunazimuth"
i.topo.corr -i basemap=DTM zenit=$z azimuth=$sunazimuth output=dtm_illu

for m in `g.list type=raster pattern=${inpmap}*_cor`; do g.region
raster=$m; r.mapcalc expr="${m}_d=double(${m})"; done

i.topo.corr basemap=dtm_illu input=`g.list type=raster sep=comma
pattern=${inpmap}*_cor_d` output=tcor zenith=$z method=c-factor

g.remove -f type=raster pattern=${inpmap}*_cor_d
###

let me know.

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] g.region "Illegal instruction (core dumped)"

[Luca Delucchi]

On Fri, 23 Nov 2018 at 12:46, Markus Metz  wrote:
>
>
> The reason is that the GRASS version you are running has been compiled for a 
> different CPU type/model. Try to recompile with the CFLAG "-march=x86-64", 
> this will produce generic 64 bit binaries.
>

thanks Markus, it fixed my problem.

> Markus M
>

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] g.region "Illegal instruction (core dumped)"

[Luca Delucchi]

Hi devs,

I installed GRASS 7.6 on a Singularity container [0] but I have
problems with some commands that return "Illegal instruction (core
dumped)", one of this is g.region.

GRASS 7.6.svn (eu_laea):~ > g.region -p
D1/5: G_set_program_name(): g.region
D2/5: G_file_name(): path = /fem4/pgis/grassdata/eu_laea/sentinel
D2/5: G_file_name(): path = /fem4/pgis/grassdata/eu_laea/PERMANENT/DEFAULT_WIND
D2/5: G_file_name(): path = /fem4/pgis/grassdata/eu_laea/PERMANENT/DEFAULT_WIND
D2/5: file open: read (mode = r)
D2/5: G__read_Cell_head
D2/5: G__read_Cell_head_array
Illegal instruction (core dumped)

I tried to debug [1] it with ldd but I don't see anything wrong

ldd `which g.region`
linux-vdso.so.1 (0x7ffe66981000)
libgrass_gproj.7.6.svn.so =>
/usr/local/grass-7.6.svn/lib/libgrass_gproj.7.6.svn.so
(0x2b1a49282000)
libgrass_vector.7.6.svn.so =>
/usr/local/grass-7.6.svn/lib/libgrass_vector.7.6.svn.so
(0x2b1a4928f000)
libgrass_dig2.7.6.svn.so =>
/usr/local/grass-7.6.svn/lib/libgrass_dig2.7.6.svn.so
(0x2b1a49306000)
libgrass_g3d.7.6.svn.so =>
/usr/local/grass-7.6.svn/lib/libgrass_g3d.7.6.svn.so
(0x2b1a49321000)
libgrass_raster.7.6.svn.so =>
/usr/local/grass-7.6.svn/lib/libgrass_raster.7.6.svn.so
(0x2b1a49343000)
libgrass_gis.7.6.svn.so =>
/usr/local/grass-7.6.svn/lib/libgrass_gis.7.6.svn.so
(0x2b1a4937)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x2b1a493d9000)
libproj.so.13 => /lib/x86_64-linux-gnu/libproj.so.13 (0x2b1a4956d000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x2b1a495e9000)
libgdal.so.20 => /lib/libgdal.so.20 (0x2b1a497a6000)
libgrass_dbmiclient.7.6.svn.so =>
/usr/local/grass-7.6.svn/lib/libgrass_dbmiclient.7.6.svn.so
(0x2b1a4a9c1000)
libgrass_dbmibase.7.6.svn.so =>
/usr/local/grass-7.6.svn/lib/libgrass_dbmibase.7.6.svn.so
(0x2b1a4a9ce000)
libgrass_dgl.7.6.svn.so =>
/usr/local/grass-7.6.svn/lib/libgrass_dgl.7.6.svn.so
(0x2b1a4a9e3000)
libgrass_linkm.7.6.svn.so =>
/usr/local/grass-7.6.svn/lib/libgrass_linkm.7.6.svn.so
(0x2b1a4a9fd000)
libgrass_rtree.7.6.svn.so =>
/usr/local/grass-7.6.svn/lib/libgrass_rtree.7.6.svn.so
(0x2b1a4aa02000)
libgeos_c.so.1 => /lib/x86_64-linux-gnu/libgeos_c.so.1 (0x2b1a4aa0e000)
libgrass_btree2.7.6.svn.so =>
/usr/local/grass-7.6.svn/lib/libgrass_btree2.7.6.svn.so
(0x2b1a4aa46000)
libpq.so.5 => /lib/x86_64-linux-gnu/libpq.so.5 (0x2b1a4aa4e000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x2b1a4aa9b000)
libgrass_datetime.7.6.svn.so =>
/usr/local/grass-7.6.svn/lib/libgrass_datetime.7.6.svn.so
(0x2b1a4aaa)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x2b1a4aaab000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 (0x2b1a4acc9000)
libzstd.so.1 => /lib/x86_64-linux-gnu/libzstd.so.1 (0x2b1a4acdc000)
/lib64/ld-linux-x86-64.so.2 (0x2b1a4924b000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x2b1a4ad77000)
libarmadillo.so.9 => /lib/libarmadillo.so.9 (0x2b1a4ad9a000)
libpoppler.so.80 => /lib/x86_64-linux-gnu/libpoppler.so.80
(0x2b1a4ada5000)
libjson-c.so.3 => /lib/x86_64-linux-gnu/libjson-c.so.3 (0x2b1a4b081000)
libfreexl.so.1 => /lib/x86_64-linux-gnu/libfreexl.so.1 (0x2b1a4b28c000)
libqhull.so.7 => /lib/x86_64-linux-gnu/libqhull.so.7 (0x2b1a4b297000)
libwebp.so.6 => /lib/x86_64-linux-gnu/libwebp.so.6 (0x2b1a4b4f5000)
libepsilon.so.1 => /lib/x86_64-linux-gnu/libepsilon.so.1
(0x2b1a4b76)
libodbc.so.2 => /lib/x86_64-linux-gnu/libodbc.so.2 (0x2b1a4b77a000)
libodbcinst.so.2 => /lib/x86_64-linux-gnu/libodbcinst.so.2
(0x2b1a4b9ea000)
libkmlbase.so.1 => /lib/x86_64-linux-gnu/libkmlbase.so.1
(0x2b1a4bc0)
libkmldom.so.1 => /lib/x86_64-linux-gnu/libkmldom.so.1 (0x2b1a4bc1e000)
libkmlengine.so.1 => /lib/x86_64-linux-gnu/libkmlengine.so.1
(0x2b1a4bcd8000)
libkmlxsd.so.1 => /lib/x86_64-linux-gnu/libkmlxsd.so.1 (0x2b1a4bd15000)
libkmlregionator.so.1 =>
/lib/x86_64-linux-gnu/libkmlregionator.so.1 (0x2b1a4bd2b000)
libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x2b1a4bd39000)
libxerces-c-3.2.so => /lib/x86_64-linux-gnu/libxerces-c-3.2.so
(0x2b1a4bd76000)
libopenjp2.so.7 => /lib/x86_64-linux-gnu/libopenjp2.so.7
(0x2b1a4c121000)
libnetcdf.so.13 => /lib/x86_64-linux-gnu/libnetcdf.so.13
(0x2b1a4c379000)
libhdf5_serial_hl.so.100 =>
/lib/x86_64-linux-gnu/libhdf5_serial_hl.so.100 (0x2b1a4c4bb000)
libsz.so.2 => /lib/x86_64-linux-gnu/libsz.so.2 (0x2b1a4c4e1000)
libhdf5_serial.so.100 =>
/lib/x86_64-linux-gnu/libhdf5_serial.so.100 (0x2b1a4c6e4000)
libmfhdfalt.so.0 => /lib/libmfhdfalt.so.0 (0x2b1a4ca42000)
libdfalt.so.0 => /lib/libdfalt.so.0 (0x2b1a4ca6c000)
libogdi.so.3.2 => /lib/libogdi.so.3.2 (0x2b1a4cb14000)
libgif.so.7 => /lib/x86_64-linux-gnu/libgif.so.7 

[GRASS-dev] r.pi addons on windows

[Luca Delucchi]

Hi devs,

it seems that there are problem in the compilation of r.pi addons on windows [0]
Could someone check to the problems?

[0] http://wingrass.fsv.cvut.cz/grass74/x86_64/addons/grass-7.4.2/logs/r.pi.log

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] PyGRASS: changing description and comments

[Luca Delucchi]

Il giorno sab 10 nov 2018, 17:46 Luí­s Moreira de Sousa <
luis.de.so...@protonmail.ch> ha scritto:

> Hi all,
>

Hi Luis,

>
> is there a way of modifying the contents of the description and comments
> fields associated with rasters? I could also use r.support, but it would be
> more elegant to use the API.
>

It seems that description and comments are not possible to be modified by
the API, other values instead are [0]

[0]
https://grass.osgeo.org/grass70/manuals/libpython/pygrass.raster.html#module-pygrass.raster.history


> Thank you.
> --
>

Ciao
Luca
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Compatibility of GPL v.2/3 and EUPL v1.2 licenses

[Luca Delucchi]

On Mon, 22 Oct 2018 at 16:39, Moritz Lennert
 wrote:
>
> On 22/10/18 16:33, Nikos Alexandris wrote:
> > * Nikos Alexandris  [2018-10-22 13:51:01 +0200]:
> >
> >> Is, effectively, the compilation of a GRASS GIS addon, using the above
> >> mentioned source code files, considered as "linking into GRASS"?
> >
> >
> > Here the section "Discussion on “Linking" from
> > https://joinup.ec.europa.eu/collection/eupl/eupl-compatible-open-source-licences#section-3
> >
> > (After an off-list communication with
> > https://twitter.com/luis_m_de_sousa, thank you)
> >
> > It would be nice to have an official answer. or text for these
> > questions.
>
> I don't know if anyone of us is a lawyer, so maybe this is something
> which should be put before the FSF ?
>

Also OSGeo could ask to a lawyer, this could be one of the reason
because OSGeo exists

> Moritz
>


-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] g.extension problem with old GRASS version

[Luca Delucchi]

Hi devs,

A colleague of mine has an old GRASS 7.2.1 version and he tried to use
g.extension and he got this error

Downloading precompiled GRASS Addons ...
Downloading source code for  from

which is identified as 'remote_zip' type of source...
ERROR: Extension  not found

the problem is related to the missing folder
http://wingrass.fsv.cvut.cz/grass72/x86_64/addons/grass-7.2.1/ only
7.2.2 and 7.2.3 versions

I would like to know how this repository is managed...

regards

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Corso GRASS-GIS

[Luca Delucchi]

Ciao a tutti,

volevo segnalarvi questo corso che si terrà in Norvegia fra due
settimane, di seguito la mail dell'organizzatore

---

Dear all,

There are some available places left at a 3-days intense workshop on
GIS in Applied Ecology (but techniques would be applicable to other
domains too) from 24.09.2018 to 27.09.2018 at Studenterhytta, Oslo.
With full board provided and no other distraction than beautiful
nature around, participants can fully focus on learning new
techniques, applying them to their ongoing projects and networking
with the others.

Topic of the course will be Advanced Geospatial Analysis with an
emphasis on handling of Earth Observation and Time Series data using
GRASS GIS and Python. The course is kindly supported by IRSAE
(https://irsae.no/).

Course fees are:
3900 NOK (~ 410 €) for participants from IRSAE institutions
4900 NOK (~ 515 €) for participants from non-IRSAE institution.

and cover as mentioned accommodation and food (breakfast, lunch and
dinner for the 3 nights at Studenterhytta).

Teachers will be Martin Landa and Luca Delucchi.

More information about the course can be found here:
http://training.gismentors.eu/grass-gis-irsae-winter-course-2018/

Registration here:
https://goo.gl/forms/yUyIEbUUoab4B04l1

Looking forward to an instructive course in a great surrounding.

Kind regards,

Stefan


-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Fwd: Patch for ctypesgen

[Luca Delucchi]

Hi all,

 I just get this mail, I don't know if it could be useful yet, I'm more or
less offline and I cannot check if we already fix the problem.

Regards
Luca

-- Forwarded message -
From: Alan Robertson 
Date: mer 5 set 2018, 05:05
Subject: Patch for ctypesgen
To: 


Hi Luca,

I think you're one of the people who was involved with a patch to the GRASS
software: https://trac.osgeo.org/grass/changeset/72361

If so, I found a related error that I suspect you folks might like to be
aware of:

https://github.com/davidjamesca/ctypesgen/issues/62

Patch is included in the issue - although it's not a PR. I also provided
your patches to the project as well.

Thanks for fixing those problems!

-- 
  Alan Robertson
  al...@unix.sh
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] i.sentinal addons

[Luca Delucchi]

On Mon, 27 Aug 2018 at 09:15, Roberta Fagandini  wrote:
>
> Hi,
>

Hi,

>
> Yes, thanks!
>

Done in r73191. With 73192 I added an error for previous directories.

> Roberta
>

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Regarding More Contributions

[Luca Delucchi]

On Thu, 23 Aug 2018 at 06:35, Sunveer Singh  wrote:
>
> Hi,
>

Hi,

> How was the GSoC this year? Hope you guys enjoyed mentoring new students!
>

GSoC was hard but pleasant time

> I would like to contribute more tests, On which modules should I write test?
>

there are a lot of them... but some are really difficult, I suggest
you to look at the manual a choose someone that seems simple to you

r.buffer
r.buffer.lowmem
r.buildvrt
r.carve
r.category
r.circle
r.clump
r.coin
r.colors.out
r.composite
r.compress
r.contour
r.covar
r.cross
r.describe
r.distance
r.example
r.external
r.external.out
r.fill.dir
r.flow
r.his
r.in.aster
r.in.bin
r.in.gridatb
r.in.mat
r.in.png
r.in.srtm
r.in.wms
r.in.wms
r.in.xyz
r.kappa
r.lake
r.latlong
r.li
r.li.cwed
r.li.daemon
r.li.dominance
r.li.edgedensity
r.li.mpa
r.li.mps
r.li.padcv
r.li.padrange
r.li.padsd
r.li.patchdensity
r.li.patchnum
r.li.pielou
r.li.renyi
r.li.richness
r.li.shannon
r.li.shape
r.li.simpson
r.mfilter
r.neighbors
r.null
r.out.ascii
r.out.bin
r.out.gdal
r.out.gridatb
r.out.mat
r.out.mpeg
r.out.png
r.out.pov
r.out.ppm
r.out.ppm3
r.out.vrml
r.out.vtk
r.param.scale
r.plus.example
r.proj
r.quant
r.quantile
r.random
r.random.surface
r.reclass.area
r.region
r.regression.line
r.regression.multi
r.relief
r.resamp.bspline
r.resamp.filter
r.resamp.interp
r.resamp.rst
r.resamp.stats
r.resample
r.rescale
r.rescale.eq
r.ros
r.sim.sediment
r.sim.water
r.solute.transport
r.spread
r.spreadpath
r.statistics
r.stats.quantile
r.stats.zonal
r.stream.extract
r.sunhours
r.sunmask
r.support
r.support.stats
r.surf.area
r.surf.contour
r.surf.fractal
r.surf.gauss
r.surf.idw
r.surf.random
r.terraflow
r.thin
r.tile
r.to.rast3elev
r.topidx
r.topmodel
r.transect
r.uslek
r.usler
r.volume
r.walk
r.water.outlet
r.watershed
r.what
r.what.color
r3.cross.rast
r3.gwflow
r3.in.ascii
r3.in.lidar
r3.in.v5d
r3.in.xyz
r3.info
r3.mask
r3.mkdspf
r3.out.ascii
r3.out.bin
r3.out.v5d
r3.out.vtk
r3.retile
r3.showdspf
r3.stats
r3.support
t.create
t.list
t.rast.colors
t.rast.list
t.rast.mapcalc
t.rast.out.vtk
t.rast3d.mapcalc
t.register
t.remove
t.rename
t.select
t.topology
t.vect.db.select
t.vect.export
t.vect.what.strds
v.buffer
v.build
v.build.all
v.build.polylines
v.class
v.cluster
v.colors
v.colors.out
v.db.connect
v.decimate
v.delaunay
v.drape
v.example
v.external
v.external.out
v.extrude
v.generalize
v.hull
v.import
v.in.db
v.in.dwg
v.in.dxf
v.in.e00
v.in.geonames
v.in.mapgen
v.in.ogr
v.in.region
v.in.wfs
v.kcv
v.kernel
v.label
v.label.sa
v.lidar.correction
v.lidar.edgedetection
v.lidar.growing
v.lrs
v.lrs.create
v.lrs.label
v.lrs.segment
v.lrs.where
v.mkgrid
v.neighbors
v.net.alloc
v.net.allpairs
v.net.bridge
v.net.centrality
v.net.components
v.net.connectivity
v.net.distance
v.net.flow
v.net.iso
v.net.path
v.net.salesman
v.net.spanningtree
v.net.steiner
v.net.timetable
v.net.visibility
v.normal
v.out.ascii
v.out.dxf
v.out.ogr
v.out.postgis
v.out.pov
v.out.svg
v.out.vtk
v.outlier
v.overlay
v.parallel
v.patch
v.perturb
v.proj
v.qcount
v.random
v.reclass
v.rectify
v.sample
v.segment
v.split
v.support
v.surf.idw
v.to.db
v.to.points
v.to.rast
v.to.rast3
v.transform
v.type
v.vol.rst
v.voronoi
v.what.rast


> Thank You
> Sunveer
> https://sunveersingh.github.io/
>


-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] i.sentinal addons

[Luca Delucchi]

On Tue, 21 Aug 2018 at 14:36, Roberta Fagandini  wrote:
>
> Hi all,

Hi,

> obviously, it's ok for me but is it possible to wait for the announcement of 
> GSoc results?

announcement is done, right?

> I added the links to the SVN repository to my final report and I'd like them 
> to work for a few more days.
>

could we move them?

> Thanks!
>
> Roberta
>

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS-user] Fwd: [Projects] OSGeo Annual General Meeting - projects please join and report (August 30 2018)

[Luca Delucchi]

On Thu, 23 Aug 2018 at 15:06, Markus Neteler  wrote:
>
> Does anyone volunteer to update accordingly
>
> https://docs.google.com/presentation/d/1imiG7x09ry7lGvmS15FCVq2Z7yaICY00fcpXBK27TXY/edit?usp=sharing
> ?
>

I asked edit access, I will do it in the next days if none will modify
it before...

> Markus
>
> /me at GeoSTAT 2018 at time



-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] i.sentinel.import problems

[Luca Delucchi]

On Tue, 21 Aug 2018 at 18:59, Martin Landa  wrote:
>
> Hi Luca,
>

Hi Markus,

>
> fixed in r73131. A new info message is printed.
>
> No clouds layer found in
> .
> Import skipped
>

also this works, thanks

> Ma
>

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] i.sentinel.import problems

[Luca Delucchi]

On Tue, 21 Aug 2018 at 18:34, Martin Landa  wrote:
>
> Hi Luca,
>

Hi Martin,

>
> please try
>
> i.sentinel.import -cr input=/tmp/ pattern='B(02|03|04|08|8A|11|12)'
>
> Fixed in r73130.
>

it works thanks!

> [...]
>
> Martin
>

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] i.sentinal addons

[Luca Delucchi]

Hi all,

could we move the new modules (i.sentinel.preproc and i.sentinel.mask)
into i.sentinel folder, so people installing i.sentinel they install
the 4 modules.

I can take care to fix the Makefiles

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] i.sentinel.import problems

[Luca Delucchi]

Hi Martin,

I'm trying i.sentinel.* module and I got problems with i.sentinel.import
I downloaded 3 scene with i.sentinel.download

i.sentinel.download -l settings=/tmp/settings_sentinel
start=2017-01-10 end=2017-01-13 order=desc clouds=0
3 Sentinel product(s) found
860d118d-c117-4472-8b51-654d6784a40a 2017-01-12T16:16:21Z  0% S2MSI1C
c2eaa8d0-eebe-4b4d-b18b-669a2172b02f 2017-01-12T16:16:21Z  0% S2MSI1C
a3d9b19c-2262-4f88-b107-07ee09e217d3 2017-01-12T16:16:21Z  0% S2MSI1C

and after I run

i.sentinel.import -cr input=/tmp/ pattern='B[02|03|04|08|8A|11|12]'

I got two problems:
- all bands are imported
g.list rast map=. pattern=*_B*
T17SLT_20170112T161621_B01
T17SLT_20170112T161621_B02
T17SLT_20170112T161621_B03
T17SLT_20170112T161621_B04
T17SLT_20170112T161621_B05
T17SLT_20170112T161621_B06
T17SLT_20170112T161621_B07
T17SLT_20170112T161621_B08
T17SLT_20170112T161621_B09
T17SLT_20170112T161621_B10
T17SLT_20170112T161621_B11
T17SLT_20170112T161621_B12
T17SLT_20170112T161621_B8A
T17SNT_20170112T161621_B01
T17SNT_20170112T161621_B02
T17SNT_20170112T161621_B03
T17SNT_20170112T161621_B04
T17SNT_20170112T161621_B05
T17SNT_20170112T161621_B06
T17SNT_20170112T161621_B07
T17SNT_20170112T161621_B08
T17SNT_20170112T161621_B09
T17SNT_20170112T161621_B10
T17SNT_20170112T161621_B11
T17SNT_20170112T161621_B12
T17SNT_20170112T161621_B8A
T17SNU_20170112T161621_B01
T17SNU_20170112T161621_B02
T17SNU_20170112T161621_B03
T17SNU_20170112T161621_B04
T17SNU_20170112T161621_B05
T17SNU_20170112T161621_B06
T17SNU_20170112T161621_B07
T17SNU_20170112T161621_B08
T17SNU_20170112T161621_B09
T17SNU_20170112T161621_B10
T17SNU_20170112T161621_B11
T17SNU_20170112T161621_B12
T17SNU_20170112T161621_B8A

- a problem with the cloud mask

Reprojecting ...
ERROR: No OGR layers available
ERROR: Unable to import
   

ERROR: No OGR layers available
ERROR: Unable to import
   

ERROR: No OGR layers available
ERROR: Unable to import
   

Exception OSError: OSError(2, 'No such file or directory') in > ignored

probably because the clouds are 0%

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Regarding More Contributions

[Luca Delucchi]

On Sat, 21 Jul 2018 at 17:52, Sunveer Singh  wrote:
>
> Hi!
>

Hi Sunveer,

> Sorry I was not active for a long. But from now I will be giving my whole to 
> contribute.
>

sorry for the delay in the answer, but this summer is really busy

> What can I do? I have already written some tests for modules and I can write 
> more.
>

yes you can write more test or improve translation of your mother
language [0] or look to some simple issue [1]

> And if there is more stuff I can do please let me know.
>
> Thank you
> Sunveer

[0] https://www.transifex.com/grass-gis/grass7/dashboard/
[1] https://trac.osgeo.org/grass/report/1

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Fwd: [Projects] OSGeo Annual General Meeting - projects please join and report (August 30 2018)

[Luca Delucchi]

On 3 August 2018 at 15:48, Markus Neteler  wrote:
> Hi devs, all,
>

Hi,

> for the upcoming FOSS4G conference we shall prepare a quick (2 minute)
> project update for GRASS GIS, like last year.
>
> Who will be in Dar and willing to present our updates there?
>

I will be there and available.

> Happy to help collecting the material. Also catchy screenshots are
> always welcome!
>

yes please,  I have few time to work on it...

> thanks
> Markus
>


-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] New dev team on github for initial tests

[Luca Delucchi]

On 13 June 2018 at 22:07, Markus Neteler  wrote:
>
> As I said: the OSGeo git services are IMHO under-staffed and would
> require  a dedicated budget. Could be a nice idea but the board needs
> to support that.
>

I don't think so, git on OSGeo server is working [0], and the board
also use it [1]. I don't see any problem, it is like trac or svn
I also used it for an OSGeo code [2]

> Markus
>

PS
Probably I will move most of my github repositories to OSGeo one and
gitlab according the code topic

[0] https://git.osgeo.org/gitea/
[1] https://git.osgeo.org/gitea/osgeo/todo/issues
[2] https://git.osgeo.org/gitea/lucadelu/gci_analyst

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] New dev team on github for initial tests

[Luca Delucchi]

Il mer 13 giu 2018, 04:13 Vaclav Petras  ha scritto:

>
> > gitea, gitlab is not working for me
>
>
> Luca, I think you need to be more specific.
>

I was speaking about the gitlab instance on OSGeo server [0],  it is not
working for me... Otherwise I like gitlab it self and I'm already using it.

Is it more clear now?

Best
Luca

[0] http://wiki.osgeo.org/wiki/SAC:Git_Service
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] New dev team on github for initial tests

[Luca Delucchi]

On 6 June 2018 at 07:23, Markus Neteler  wrote:
>
> Which of the two? Gitea or gitlab?
>

gitea, gitlab is not working for me

> Will they be stable and maintained installations with backup strategy for
> the years to come?
>

I think like svn and trac. However the backup for the git repository
is not needed since all the history is present in each copy of the
project, maybe could be useful for issue and PR

> Markus
>


-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GRASS and Anaconda

[Luca Delucchi]

Il gio 7 giu 2018, 20:58 Michael Barton  ha scritto:

> Along with helping me set up a new way to compile and package GRASS
> binaries for the Mac, Eric Hutton of the Community Surface Dynamics
> Modeling System (CSDMS – http//csdms.colorado.edu) has created a Conda
> recipe for building GRASS in the Anaconda environment. This is now deployed
> in the csdms stack at GitHub. Several versions of GRASS, for Linux and Mac
> are available. Details and instructions for building GRASS with Anaconda
> can be found at:
>
>
>
> https://github.com/csdms-stack/grass-recipe
>
>
>
> Many thanks to Eric and CSDMS
>
>
>
> Happy GRASSing!
>
> Michael
>
>
>
> __
>
> C. Michael Barton
>
> Director, Center for Social Dynamics & Complexity
>
> Professor of Anthropology, School of Human Evolution & Social Change
>
> Head, Graduate Faculty in Complex Adaptive Systems Science
>
> Arizona State University
>
> Tempe, AZ  85287-2402
>
> USA
>
>
>
> voice:480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
>
> fax:  480-965-7671(SHESC), 480-727-0709 (CSDC)
>
> www:  http://csdc.asu.edu, http://shesc.asu.edu
>
> http://www.public.asu.edu/~cmbarton
>
>
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] New dev team on github for initial tests

[Luca Delucchi]

On 5 June 2018 at 01:21, Huidae Cho  wrote:
> Yeah, that acquisition is bad news. Why can we just not use the OSGeo one?

This is my favourite choice

> Just curious.
>
> Huidae
>

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Regarding testing

[Luca Delucchi]

On 13 May 2018 at 08:12, Sanjeet <edu.sanj...@gmail.com> wrote:
> On Wed, May 9, 2018 at 3:30 AM, Luca Delucchi <lucadel...@gmail.com> wrote:
>> On 8 May 2018 at 07:39, Sanjeet <edu.sanj...@gmail.com> wrote:
>>> I made some minor changes in 'utils.py' in lib/python/script and
>>> 'test_utils.py' in its testsuite.
>>> https://github.com/sanjeetbhatti/FullSupportPython3/blob/master/patch.diff
>>>
>>> The Python 3's bytes cannot contain ASCII literal characters,
>>> therefore I can't seem to test it as such, I encoded it first before
>>> checking for an assertion, which I am not sure is a correct way to do
>>> so as we are ensuring that we do not pass any bytes with ASCII literal
>>> characters.
>>
>> could be this a problem with languages using strange accent mark?
>> We had and have problem with some languages in translations
>>
>>> Same thing is in test_start_command_functions.py.
>>> Moreover, I generalized the encode and decode functions by using
>>> string conversion for int and float values.
>>>
>>> Please let me know if this is the correct way to go about it.
>>>
>> It seems correct to me, but please Anna answer
>
> Hi Anna and Luca,
>

Hi Sanjeet

> I have been working with scripts and testing them with python3 and I
> made some changes in 2 different patches:
> 1. patch.diff -> has changes for unicode/bytes in utils and its
> test_utils.py along with test_start_command_functions.py (depending on
> the changes in utils)
> 2. raster.diff -> has changes for raster.py
>

What other devs think about the patches?

They seem ok for me, I tested and they work

> Please take a look here:
> https://github.com/sanjeetbhatti/FullSupportPython3
>
> For other tests, I have created a google sheet:
> https://docs.google.com/spreadsheets/d/1eAIJtegNWSbBscFChhQzMTl0vmbGPjmrW_013hSw9bI
>

A comment about results, for me the test_doctest.py is working fine
with Python 3.5.3

 100%
 100%
Loading floating point data with 8 bytes ... (6x4x3)
 100%
Loading floating point data with 8 bytes ... (6x4x3)
 100%
.
--
Ran 1 test in 0.785s
OK


> I'm working on few other testsuites and hoping to have a couple of
> patches submitted by tomorrow.
>
> Thanks
> --
> Sanjeet Bhatti



-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] remove raster map in C code

[Luca Delucchi]

On 11 May 2018 at 10:54, Markus Metz <markus.metz.gisw...@gmail.com> wrote:
> Hi Luca,
>

Hi Markus,

> On Fri, May 11, 2018 at 10:26 AM, Luca Delucchi <lucadel...@gmail.com>
> wrote:
>>
>> Hi devs,
>>
>> I would like to remove a raster map inside a C module, looking aroung
>> I found the M_do_remove function used in g.remove and r.reclass. So I
>> tried to use it but I get error in compilation
>>
>> OBJ.x86_64-pc-linux-gnu/main.o: In function `main':
>> main.c:(.text.startup+0x9eb): undefined reference to `M_get_element'
>> main.c:(.text.startup+0x9f5): undefined reference to `M_do_remove'
>> collect2: error: ld returned 1 exit status
>
> this is a problem of the linker: you need to link against the manage lib,
> see e.g. the Makefile for g.remove. Try
>
> LIBES = $(MANAGELIB) $(RASTERLIB) $(GISLIB)
> DEPENDENCIES = $(MANAGEDEP) $(RASTERDEP) $(GISDEP)
>
> in the Makefile of your module.
>

thanks, now it compile but I get "Segmentation fault", the module is
r.tile, I attached the diff, could someone have a look to it please?

> HTH,
>
> Markus M
>



-- 
ciao
Luca

www.lucadelu.org
Index: raster/r.tile/Makefile
===
--- raster/r.tile/Makefile	(revision 72704)
+++ raster/r.tile/Makefile	(working copy)
@@ -2,8 +2,8 @@
 
 PGM = r.tile
 
-LIBES = $(RASTERLIB) $(GISLIB)
-DEPENDENCIES = $(RASTERDEP) $(GISDEP)
+LIBES = $(MANAGELIB) $(RASTERLIB) $(GISLIB)
+DEPENDENCIES = $(MANAGEDEP) $(RASTERDEP) $(GISDEP)
 
 include $(MODULE_TOPDIR)/include/Make/Module.make
 
Index: raster/r.tile/main.c
===
--- raster/r.tile/main.c	(revision 72704)
+++ raster/r.tile/main.c	(working copy)
@@ -15,12 +15,15 @@
 #include 
 #include 
 #include 
+#include 
 #include 
+#include 
 
 static struct
 {
 struct Option *rastin, *rastout, *width, *height, *overlap;
 } parm;
+
 static struct Cell_head dst_w, src_w, ovl_w;
 static int xtiles, ytiles;
 static RASTER_MAP_TYPE map_type;
@@ -30,6 +33,9 @@
 int main(int argc, char *argv[])
 {
 struct GModule *module;
+struct Range int_range;
+struct FPRange fp_range;
+struct Flag *flag;
 int infile;
 const char *mapset;
 size_t cell_size;
@@ -75,6 +81,10 @@
 parm.overlap->multiple = NO;
 parm.overlap->description = _("Overlap of tiles");
 
+flag = G_define_flag();
+flag->key = 'n';
+flag->description = _("Does not create tiles having only NULL values");
+
 if (G_parser(argc, argv))
 	exit(EXIT_FAILURE);
 
@@ -149,8 +159,31 @@
 	}
 
 	for (xtile = 0; xtile < xtiles; xtile++) {
-	Rast_close(outfiles[xtile]);
-	write_support_files(xtile, ytile, overlap);
+Rast_close(outfiles[xtile]);
+write_support_files(xtile, ytile, overlap);
+if (flag->answer){
+char name[GNAME_MAX];
+sprintf(name, "%s-%03d-%03d", parm.rastout->answer, ytile, xtile);
+if (map_type == CELL_TYPE) {
+CELL min, max;
+Rast_read_range(name, G_mapset(), _range);
+min = int_range.min;
+max = int_range.max;
+if (IS_NULL_C() && IS_NULL_C()){
+M_do_remove(M_get_element("raster"), name);
+G_debug(0, "Removed empty tile %s", name);
+}
+} else {
+DCELL min, max;
+Rast_read_fp_range(name, mapset, _range);
+min = fp_range.min;
+max = fp_range.max;
+if (IS_NULL_D() && IS_NULL_D()){
+M_do_remove(M_get_element("raster"), name);
+G_debug(0, "Removed empty tile %s", name);
+}
+}
+}
 	}
 }
 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] remove raster map in C code

[Luca Delucchi]

Hi devs,

I would like to remove a raster map inside a C module, looking aroung
I found the M_do_remove function used in g.remove and r.reclass. So I
tried to use it but I get error in compilation

OBJ.x86_64-pc-linux-gnu/main.o: In function `main':
main.c:(.text.startup+0x9eb): undefined reference to `M_get_element'
main.c:(.text.startup+0x9f5): undefined reference to `M_do_remove'
collect2: error: ld returned 1 exit status

In the source code of the module I added #include 
that it seems the header containing the definition of M_do_remove.

Any idea?

Thanks in advance

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Regarding testing

[Luca Delucchi]

On 8 May 2018 at 07:39, Sanjeet  wrote:
>
> Hi Anna,
>

Hi,

> I made some minor changes in 'utils.py' in lib/python/script and
> 'test_utils.py' in its testsuite.
> https://github.com/sanjeetbhatti/FullSupportPython3/blob/master/patch.diff
>
> The Python 3's bytes cannot contain ASCII literal characters,
> therefore I can't seem to test it as such, I encoded it first before
> checking for an assertion, which I am not sure is a correct way to do
> so as we are ensuring that we do not pass any bytes with ASCII literal
> characters.

could be this a problem with languages using strange accent mark?
We had and have problem with some languages in translations

> Same thing is in test_start_command_functions.py.
> Moreover, I generalized the encode and decode functions by using
> string conversion for int and float values.
>
> Please let me know if this is the correct way to go about it.
>

It seems correct to me, but please Anna answer

> Thanks
> --
> Sanjeet Bhatti



-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS-SVN] r72686 - grass/trunk/raster/r.mode/testsuite

[Luca Delucchi]

On 5 May 2018 at 05:57, Anna Petrášová  wrote:
> Hi,
>

Hi,

> I just wanted to point out, that some of the newly added tests were
> actually not testing anything (see below) or failing because of
> whitespace, please be more careful what you commit.
>

sorry, but I  usually test them, maybe I skip some.
However some tests are failing because in the basic_north_carolina
doesn't contain some useful maps like landsat for i.* commands.

what do you think to use the full North Casolina dataset as default
one? If there consensus I could try to fix the failing tests


> Thank you,
>
> Anna
>

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] new website: draft roadmap and collection of ideas

[Luca Delucchi]

On 28 April 2018 at 14:54, Markus Neteler  wrote:
> Hi all,
>

Hi,

>
> Just as a reminder, please edit and add your suggestions.
>

It is fine for me, we should start to modify the website, I can help
moving the content but not with the style

> Best,
> Markus
>


-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSoC Introduction

[Luca Delucchi]

On 25 April 2018 at 05:40, Anna Petrášová  wrote:
> Hi Sanjeet,
>

Hi Sanjeet, Anna

>
> welcome! For start, please create a wiki page on trac wiki (you should
> already have access there), look at the examples from the past years,
> and follow similar structure:
> https://trac.osgeo.org/grass/wiki/GSoC
>

yes please create the page looking at previous year projects.

> We will need to decide how to manage your contributions, since you
> won't have access rights to the svn repository. We might need to do it
> similarly as we did with one student 2 years ago, he tracked the
> applied changesets in his github repository, which could be then
> submitted to Google in the end of the program. You could post your
> changes in tickets (created specifically for this GSoC) and they will
> be applied by me, Luca or other developers. I understand this is not
> ideal workflow, so if anybody has better idea, let me know.
>

I fully agree, I think small patches (for example a patch for each
file you modify) is better then bigger, so we can look it

> For the community bonding period there are couple things I suggest.
> * make sure you have all the development environment ready (you
> probably have that already)
> * have good idea about the code structure
> * make yourself familiar with the testing framework, I would like you
> to use it to update current tests of the libraries, adjust them to
> work with Python3 and write new tests:
>   https://grass.osgeo.org/grass74/manuals/libpython/gunittest_testing.html
>   http://fatra.cnr.ncsu.edu/grassgistests/summary_report/
> * specifically start looking at Python scripting library, it would be
> great if you could start working on it during the bonding period,
> specific challenges you may encounter there may help us get the
> discussion going.
>

yes, to start you can just launch GRASS and from the command line in
GRASS launch a Python3 console, it work.

Please use standard North Carolina dataset [0], the tests actually use
the "basic" version of the dataset

> I will let you know if I think of more things. Please send your
> questions/concerns either directly to me and Luca, or copy also the
> grass-dev mailing list, so that we can keep other developers in the
> loop.
>
> Thank you and looking forward to working with you,
>
> Anna
>


[0] http://grass.osgeo.org/download/sample-data/

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev