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

[Vaclav Petras]

Thanks everyone for the support.

I was able to identify some potential issues. Namely, the auto-generated
metadata on Zenodo does not seem to be that great and that includes basic
things like title and license. How an author list will look is hard to say
without trying, but it is promised to be sensible. It seems that a lot of
projects just solve this using a .zenodo.json configuration file which
includes this info, e.g. a full author list.

Although these metadata issues are certainly visible, a DOI will be
generated and usable by itself in any case. Additionally, metadata can be
edited manually after the publishing/release. Finally, having .zenodo.json
is doable (probably through CITATION.cff which would be good to have
anyway). Thus, I don't see this as a blocker, just as something to resolve
on the way.

On Mon, May 24, 2021 at 1:27 PM Stefan Blumentrath <
stefan.blumentr...@nina.no> wrote:


> There is already a GRASS GIS community on Zenodo, managed by Pietro.
>
> There are way more GRASS related records in zenodo than registered in that
> community. Wound probably be useful to register relevant entries in a GRASS
> community...
>

There seems to be exactly n-1 GRASS-related records not in the community
(where n is all the GRASS-related records). Are we looking at the same one?

https://zenodo.org/communities/grass/


>
> Would it be an option to develop the community in that direction, Pietro?
> If others too think that's useful ...
>
> Cheers
> Stefan
> --
> *From:* grass-dev  on behalf of
> Veronica Andreo 
> *Sent:* Monday, May 24, 2021 1:48:21 PM
> *To:* Moritz Lennert 
> *Cc:* grass-dev ; Peter Löwe <
> peter.lo...@gmx.de>
> *Subject:* Re: [GRASS-dev] [release planning] Enable Zenodo before 7.8.6
> and 8.0.0
>
> +1 from my side too
>
> El lun., 24 may. 2021 03:23, Moritz Lennert 
> escribió:
>
> Clear +1 from me.
>
> Moritz
>
> Le 24 mai 2021 03:08:06 GMT+01:00, Vaclav Petras  a
> écrit :
>
> Hi all,
>
> Let's enable the Zenodo link before 7.8.6 and 8.0(.0?) releases to get
> DOIs and Zenodo records.
>
> Solving the whole DOI linking and Zenodo archiving for the old versions
> may be complex [1], but enabling the link between GitHub and Zenodo is
> trivial (one click) and every newly created GitHub release (we do those)
> will be automatically registered and receive DOI.
>
> Zenodo uses a system of DOI versions and a main DOI (Concept DOI). Whether
> it is an ideal system, that's a question, but it is currently the expected
> one since it is the same for everything on Zenodo. It is used automatically
> when using the GitHub-Zenodo integration.
>
> It seems I have the permissions to enable it for GRASS GIS. The one who
> enables that becomes a maintainer of it. I'm fine with that, but I won't be
> uploading any older versions. The maintainer can be changed later by
> contacting Zenodo support [2].
>
> Although there are things to figure out in terms of next steps, I don't
> see much risk in enabling it. There are no choices available in the setup
> or in terms of alternatives. DOI and some kind of registration are expected
> more and more.
>
> Thoughts?
>
> Vaclav
>
> [1] https://grasswiki.osgeo.org/wiki/GitHub-Zenodo_linkage
> 
> [2] https://github.com/zenodo/zenodo/issues/826
> 
>
> ___
> 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
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] strange problem using v.out.ogr

[Michael Barton]

Using a very recently compiled GRASS 7.9

I imported a gpkg vector area. This went fine AFAICT. It imported into the 
correct location. (ETRS89 Zone 30)

I want to export it to shapefile format.

When I try to export it to *any* format, I get the following error:

ERROR 10: Pointer 'hSRS' is NULL in 'OSRImportFromWkt'.
ERROR: Unable to create OGR spatial reference

I've checked the projection info and it seems fine and does not raise any error 
or warning. I tried exporting a map from the NC demo data and it exported fine.

Any idea what is wrong?

Michael
_
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Director, Network for Computational Modeling in Social & Ecological Sciences
Associate Director, School of Complex Adaptive Systems
Professor, School of Human Evolution & Social Change
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://shesc.asu.edu, https://complexity.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] GSoC Introduction: GRASS and Jupyter Notebooks

[Caitlin Haedrich]

Hello everyone,

My name is Caitlin Haedrich and I'm one of the OSgeo Google Summer of Code
participants. I'm a first year PhD student in Geospatial Analytics at North
Carolina State University in Raleigh, NC. You can read more about my
background and interests on my website [1].

This summer, I'll be working on improving the integration of GRASS GIS and
Jupyter Notebooks. I'm proposing a new python library, 'grass.jupyter',
that will contain functions for:
* initiating GRASS sessions in Jupyter
* displaying maps in a more intuitive way (wrapping 'd.erase' and other
required modules into one function)
* displaying interactive maps with folium

You can read more about the project in my proposal [2] and follow my
progress on the project wiki page [3].  I'd love to hear any ideas or
feedback you have for the project.

Lastly, I'd like to thank OSGeo and Google for giving me this opportunity.
I'm really looking forward to working with you all this summer and being
part of the OSGeo community.

Best,
Caitlin

[1] https://chaedri.github.io/
[2]
https://docs.google.com/document/d/1ZT0cZobd87YCb3Ogis7RzWPj02XZkCpAHbC3VBGh7gc/edit?usp=sharing
[3] https://trac.osgeo.org/grass/wiki/GSoC/2021/JupyterAndGRASS
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Michael Barton]

Thanks Vaclav,

This is really good.

+1

Michael
_
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Director, Network for Computational Modeling in Social & Ecological Sciences
Associate Director, School of Complex Adaptive Systems
Professor, School of Human Evolution & Social Change
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://shesc.asu.edu, https://complexity.asu.edu, 
http://www.public.asu.edu/~cmbarton

On May 24, 2021, at 10:27 AM, 
grass-dev-requ...@lists.osgeo.org 
wrote:

Date: Sun, 23 May 2021 22:08:06 -0400
From: Vaclav Petras mailto:wenzesl...@gmail.com>>
To: "grass-dev@lists.osgeo.org" 
mailto:grass-dev@lists.osgeo.org>>
Cc: Peter L?we mailto:peter.lo...@gmx.de>>
Subject: [GRASS-dev] [release planning] Enable Zenodo before 7.8.6 and
8.0.0
Message-ID:
mailto:CABo5uVuEtzzG4LTLg1JT0m64-2bZ1b-3TrfEmBFTLHaTp=b...@mail.gmail.com>>
Content-Type: text/plain; charset="utf-8"

Hi all,

Let's enable the Zenodo link before 7.8.6 and 8.0(.0?) releases to get DOIs
and Zenodo records.

Solving the whole DOI linking and Zenodo archiving for the old versions may
be complex [1], but enabling the link between GitHub and Zenodo is trivial
(one click) and every newly created GitHub release (we do those) will be
automatically registered and receive DOI.

Zenodo uses a system of DOI versions and a main DOI (Concept DOI). Whether
it is an ideal system, that's a question, but it is currently the expected
one since it is the same for everything on Zenodo. It is used automatically
when using the GitHub-Zenodo integration.

It seems I have the permissions to enable it for GRASS GIS. The one who
enables that becomes a maintainer of it. I'm fine with that, but I won't be
uploading any older versions. The maintainer can be changed later by
contacting Zenodo support [2].

Although there are things to figure out in terms of next steps, I don't see
much risk in enabling it. There are no choices available in the setup or in
terms of alternatives. DOI and some kind of registration are expected more
and more.

Thoughts?

Vaclav

[1] 
https://urldefense.com/v3/__https://grasswiki.osgeo.org/wiki/GitHub-Zenodo_linkage__;!!IKRxdwAv5BmarQ!K52Klqmq-tT_br3V2AsSeRGAToybyhL_vSfv1d-Fm4010Vq5iXdwZWttyJw2S6e9phs$
[2] 
https://urldefense.com/v3/__https://github.com/zenodo/zenodo/issues/826__;!!IKRxdwAv5BmarQ!K52Klqmq-tT_br3V2AsSeRGAToybyhL_vSfv1d-Fm4010Vq5iXdwZWttyJw2I-SDLvs$
-- next part --
An HTML attachment was scrubbed...
URL: 


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

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

[Stefan Blumentrath]

Sonds like a very good plan. Appreciate the effort.

There is already a GRASS GIS community on Zenodo, managed by Pietro.

There are way more GRASS related records in zenodo than registered in that 
community. Wound probably be useful to register relevant entries in a GRASS 
community...

Would it be an option to develop the community in that direction, Pietro? If 
others too think that's useful ...

Cheers
Stefan

From: grass-dev  on behalf of Veronica 
Andreo 
Sent: Monday, May 24, 2021 1:48:21 PM
To: Moritz Lennert 
Cc: grass-dev ; Peter Löwe 
Subject: Re: [GRASS-dev] [release planning] Enable Zenodo before 7.8.6 and 8.0.0

+1 from my side too

El lun., 24 may. 2021 03:23, Moritz Lennert 
mailto:mlenn...@club.worldonline.be>> escribió:
Clear +1 from me.

Moritz

Le 24 mai 2021 03:08:06 GMT+01:00, Vaclav Petras 
mailto:wenzesl...@gmail.com>> a écrit :
Hi all,

Let's enable the Zenodo link before 7.8.6 and 8.0(.0?) releases to get DOIs and 
Zenodo records.

Solving the whole DOI linking and Zenodo archiving for the old versions may be 
complex [1], but enabling the link between GitHub and Zenodo is trivial (one 
click) and every newly created GitHub release (we do those) will be 
automatically registered and receive DOI.

Zenodo uses a system of DOI versions and a main DOI (Concept DOI). Whether it 
is an ideal system, that's a question, but it is currently the expected one 
since it is the same for everything on Zenodo. It is used automatically when 
using the GitHub-Zenodo integration.

It seems I have the permissions to enable it for GRASS GIS. The one who enables 
that becomes a maintainer of it. I'm fine with that, but I won't be uploading 
any older versions. The maintainer can be changed later by contacting Zenodo 
support [2].

Although there are things to figure out in terms of next steps, I don't see 
much risk in enabling it. There are no choices available in the setup or in 
terms of alternatives. DOI and some kind of registration are expected more and 
more.

Thoughts?

Vaclav

[1] 
https://grasswiki.osgeo.org/wiki/GitHub-Zenodo_linkage
[2] 
https://github.com/zenodo/zenodo/issues/826
___
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] [release planning] Enable Zenodo before 7.8.6 and 8.0.0

[Veronica Andreo]

+1 from my side too

El lun., 24 may. 2021 03:23, Moritz Lennert 
escribió:

> Clear +1 from me.
>
> Moritz
>
> Le 24 mai 2021 03:08:06 GMT+01:00, Vaclav Petras  a
> écrit :
>>
>> Hi all,
>>
>> Let's enable the Zenodo link before 7.8.6 and 8.0(.0?) releases to get
>> DOIs and Zenodo records.
>>
>> Solving the whole DOI linking and Zenodo archiving for the old versions
>> may be complex [1], but enabling the link between GitHub and Zenodo is
>> trivial (one click) and every newly created GitHub release (we do those)
>> will be automatically registered and receive DOI.
>>
>> Zenodo uses a system of DOI versions and a main DOI (Concept DOI).
>> Whether it is an ideal system, that's a question, but it is currently the
>> expected one since it is the same for everything on Zenodo. It is used
>> automatically when using the GitHub-Zenodo integration.
>>
>> It seems I have the permissions to enable it for GRASS GIS. The one who
>> enables that becomes a maintainer of it. I'm fine with that, but I won't be
>> uploading any older versions. The maintainer can be changed later by
>> contacting Zenodo support [2].
>>
>> Although there are things to figure out in terms of next steps, I don't
>> see much risk in enabling it. There are no choices available in the setup
>> or in terms of alternatives. DOI and some kind of registration are expected
>> more and more.
>>
>> Thoughts?
>>
>> Vaclav
>>
>> [1] https://grasswiki.osgeo.org/wiki/GitHub-Zenodo_linkage
>> [2] https://github.com/zenodo/zenodo/issues/826
>>
> ___
> 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] GRASS GIS 7.8.6RC1 released

[Martin Landa]

Hi,

st 19. 5. 2021 v 23:50 odesílatel Markus Neteler  napsal:

wingrass binaries uploaded for testing:

* standalone: https://grass.osgeo.org/grass78/binary/mswindows/native/x86_64/
* osgeo4w network installer `grass` package from experimental area

Martin

-- 
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Moritz Lennert]

Clear +1 from me. 

Moritz

Le 24 mai 2021 03:08:06 GMT+01:00, Vaclav Petras  a écrit 
:
>Hi all,
>
>Let's enable the Zenodo link before 7.8.6 and 8.0(.0?) releases to get DOIs
>and Zenodo records.
>
>Solving the whole DOI linking and Zenodo archiving for the old versions may
>be complex [1], but enabling the link between GitHub and Zenodo is trivial
>(one click) and every newly created GitHub release (we do those) will be
>automatically registered and receive DOI.
>
>Zenodo uses a system of DOI versions and a main DOI (Concept DOI). Whether
>it is an ideal system, that's a question, but it is currently the expected
>one since it is the same for everything on Zenodo. It is used automatically
>when using the GitHub-Zenodo integration.
>
>It seems I have the permissions to enable it for GRASS GIS. The one who
>enables that becomes a maintainer of it. I'm fine with that, but I won't be
>uploading any older versions. The maintainer can be changed later by
>contacting Zenodo support [2].
>
>Although there are things to figure out in terms of next steps, I don't see
>much risk in enabling it. There are no choices available in the setup or in
>terms of alternatives. DOI and some kind of registration are expected more
>and more.
>
>Thoughts?
>
>Vaclav
>
>[1] https://grasswiki.osgeo.org/wiki/GitHub-Zenodo_linkage
>[2] https://github.com/zenodo/zenodo/issues/826
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev