Re: [GRASS-dev] [GRASS-user] How to get the area of a polygon in a layer

[Nikos Alexandris]

Dear list,

is the
https://grass.osgeo.org/uploads/grass/sampledata/firedemo_grass7.sh
script available. This link is broken.

Thank you, Nikos


signature.asc
Description: PGP signature
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] tygrass, working with GRASS GIS under Terminology

[Yann Chemin]

Nice Nik!



> On 23 Oct 2018, at 12:13, Markus Neteler  wrote:
> 
> On Tue, Oct 23, 2018 at 7:38 AM Nikos Alexandris
>  wrote:
>> 
>> Maybe of your interest,
>> 
>> an approach on rendering maps directly in the Terminology terminal while
>> working interactively or even while running a script:
>> https://gitlab.com/NikosAlexandris/tygrass
>> 
>> an experimental addon:
>> https://gitlab.com/NikosAlexandris/d.tyraster
>> 
>> a series of screencasts:
>> https://archive.org/details/GrassGisUnderTerminology [*]
> 
> Wow, that's fancy!!!
> 
> I just tried on my Fedora box (`dnf install terminology`), works perfectly 
> fine.
> 
> Congrats,
> 
> Markus
> 
>> Nikos
>> 
>> [*] replay is slow, to do: maybe some quality downgrade
>> ___
>> grass-dev mailing list
>> grass-dev@lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/grass-dev
> 
> 
> 
> -- 
> Markus Neteler, PhD
> http://www.mundialis.de - free data with free software
> http://grass.osgeo.org
> http://courses.neteler.org/blog
> ___
> 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] Compatibility of GPL v.2/3 and EUPL v1.2 licenses

[Luí­s Moreira de Sousa]

Dear all,

you may consider the services of Malcolm Bain, who was an invited speaker at 
FOSS4G Europe:
http://www.id-lawpartners.com/en

I agree with Luca that OSGeo has a role to play in this.

Cheers.

Luís

Sent from ProtonMail mobile

 Original Message 
On 23 Oct 2018, 12:11, Luca Delucchi wrote:

> On Mon, 22 Oct [2018](tel: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

Re: [GRASS-dev] Python script dependencies

[Michel Wortmann]

Great, thanks Stefan!
I find those standard Makefiles deserve a mention in the GRASS and Python 
documentation somewhere.

Michel

> On 23 Oct 2018, at 11:25, Stefan Blumentrath  
> wrote:
> 
> Hi Michael,
>  
> Have a look at 
> e.g.https://github.com/pesekon2/GRASS-GIS-SOS-tools/tree/master/sos 
>  or
> https://trac.osgeo.org/grass/browser/grass-addons/grass7?order=name#gui/wxpython/wx.metadata
>  
> 
> for inspiration regarding addon-libraries (in Python).
>  
> Kind regards,
> Stefan
>  
> From: grass-dev  On Behalf Of Michel 
> Wortmann
> Sent: tirsdag 23. oktober 2018 11:20
> To: grass-dev 
> Subject: [GRASS-dev] Python script dependencies
>  
> Hi team,
>  
> I have some python modules developed in a toolbox and install them all using 
> g.extension with the SUBDIRS Makefile variable. I frequently feel like I need 
> to share code between those modules, i.e. I would like to create a utility 
> module that can be imported by all other modules in the toolbox. I managed to 
> install the module in the .grass7/addons/script directory, but the 
> installation of the other modules fails because they cant import the 
> utilities yet. Installing it like any other module seems to bring all sorts 
> of problems including the requirement to include the toolbox name that has 
> dots in them preventing a python import.
>  
> How would I best go about this?
>  
> Thanks a lot,
> Michel
> 
> -
> * Michel Wortmann
> * Post-doc
> * Potsdam Institute for Climate Impact Research (PIK)
> * Telegrafenberg  A62,  14473 Potsdam, Germany
> * Tel.:  0049 (0)331 288 2546
> * E-mail: wortm...@pik-potsdam.de 
> * Internet: www.pik-potsdam.de/members/wortmann 
> 
> -

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

Re: [GRASS-dev] tygrass, working with GRASS GIS under Terminology

[Markus Neteler]

On Tue, Oct 23, 2018 at 7:38 AM Nikos Alexandris
 wrote:
>
> Maybe of your interest,
>
> an approach on rendering maps directly in the Terminology terminal while
> working interactively or even while running a script:
> https://gitlab.com/NikosAlexandris/tygrass
>
> an experimental addon:
> https://gitlab.com/NikosAlexandris/d.tyraster
>
> a series of screencasts:
> https://archive.org/details/GrassGisUnderTerminology [*]

Wow, that's fancy!!!

I just tried on my Fedora box (`dnf install terminology`), works perfectly fine.

Congrats,

Markus

> Nikos
>
> [*] replay is slow, to do: maybe some quality downgrade
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev



-- 
Markus Neteler, PhD
http://www.mundialis.de - free data with free software
http://grass.osgeo.org
http://courses.neteler.org/blog
___
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

Re: [GRASS-dev] Python script dependencies

[Stefan Blumentrath]

Hi Michael,

Have a look at e.g. 
https://github.com/pesekon2/GRASS-GIS-SOS-tools/tree/master/sos or
https://trac.osgeo.org/grass/browser/grass-addons/grass7?order=name#gui/wxpython/wx.metadata
for inspiration regarding addon-libraries (in Python).

Kind regards,
Stefan

From: grass-dev  On Behalf Of Michel Wortmann
Sent: tirsdag 23. oktober 2018 11:20
To: grass-dev 
Subject: [GRASS-dev] Python script dependencies

Hi team,

I have some python modules developed in a toolbox and install them all using 
g.extension with the SUBDIRS Makefile variable. I frequently feel like I need 
to share code between those modules, i.e. I would like to create a utility 
module that can be imported by all other modules in the toolbox. I managed to 
install the module in the .grass7/addons/script directory, but the installation 
of the other modules fails because they cant import the utilities yet. 
Installing it like any other module seems to bring all sorts of problems 
including the requirement to include the toolbox name that has dots in them 
preventing a python import.

How would I best go about this?

Thanks a lot,
Michel

-
* Michel Wortmann
* Post-doc
* Potsdam Institute for Climate Impact Research (PIK)
* Telegrafenberg  A62,  14473 Potsdam, Germany
* Tel.:  0049 (0)331 288 2546
* E-mail: wortm...@pik-potsdam.de
* Internet: 
www.pik-potsdam.de/members/wortmann
-

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

[GRASS-dev] Python script dependencies

[Michel Wortmann]

Hi team,

I have some python modules developed in a toolbox and install them all using 
g.extension with the SUBDIRS Makefile variable. I frequently feel like I need 
to share code between those modules, i.e. I would like to create a utility 
module that can be imported by all other modules in the toolbox. I managed to 
install the module in the .grass7/addons/script directory, but the installation 
of the other modules fails because they cant import the utilities yet. 
Installing it like any other module seems to bring all sorts of problems 
including the requirement to include the toolbox name that has dots in them 
preventing a python import.

How would I best go about this?

Thanks a lot,
Michel

-
* Michel Wortmann
* Post-doc
* Potsdam Institute for Climate Impact Research (PIK)
* Telegrafenberg  A62,  14473 Potsdam, Germany
* Tel.:  0049 (0)331 288 2546
* E-mail: wortm...@pik-potsdam.de
* Internet: www.pik-potsdam.de/members/wortmann
-

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