[GRASS-dev] grass.jupyter Mini Project: Week 4 Recap

2022-02-14 Thread Caitlin Haedrich 
Hi all,

Here's an update on what I've been working on over the last two weeks for
my Mini Project on improving grass.jupyter. Per usual, you can find more
details about the project and a copy of this report at [1].

*1) What did I accomplish over the past two weeks?*

   -
   - Took a week off to catch up on other work
   - Made minor edits, cleaned-up and wrote docstrings for TimeSeries
   visualizations [2]
   - Addressed visualizations issues with datasets that have varying time
   steps [2]
   - Started improving GRASS-folium integration for interactive mapping by
   restructuring interact_display.py and adding classes that can be passed to
   folium [3]

You can test it out the TimeSeries visualizations (animate and time_slider)
in Binder [4]


*2) What do I plan to do next week?*

   - Work on cleaning up temporary files created by grass.jupyter
   - Region handling for InteractiveMap (as you can see in the Binder link
   [4], the map is no longer automatically zoomed to the computation region)
   - Docstrings, comments, cleanup interact_display.py
   - Update grass_jupyter Notebook to include GRASS-folium example
   - Begin functions for viewing vector attributes in Pandas


*3) Am I blocked on anything?*

   - No, I'm not currently blocked on anything.

Feedback, thoughts and comments welcome!

Have a great week,
Caitlin

[1]
https://trac.osgeo.org/grass/wiki/GSoC/2021/JupyterAndGRASS/MiniGrant2022
[2] https://github.com/OSGeo/grass/pull/2010
[3] https://github.com/OSGeo/grass/pull/2208
[4]
https://mybinder.org/v2/gh/chaedri/grass/Jupyter-Timeseries?urlpath=lab%2Ftree%2Fdoc%2Fnotebooks%2FTemporal.ipynb
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS-PSC] difficult to get GRASS source code package

2022-02-14 Thread Nicklas Larsson via grass-dev 
Just to clarify, on the newly proposed link:

https://github.com/OSGeo/grass/tags

both *.zip AND *.tar.gz files are available.









On Monday, 14 February 2022, 21:27:41 CET, Huidae Cho  
wrote: 





+1 for ZIP links.

Huidae

On Mon, Feb 14, 2022 at 3:24 PM Jeff McKenna  
wrote:
> On 2022-02-14 4:01 p.m., Veronica Andreo wrote:
>> 
>> El lun, 14 feb 2022 a las 20:29, Vaclav Petras (> >) escribió:
>> 
>> 
>>     On Mon, 14 Feb 2022 at 14:22, Veronica Andreo >     > wrote:
>> 
>> 
>>         Currently, there's a link to releases  in the first entry of
>>         https://grass.osgeo.org/download/
>>          that points to
>>         https://github.com/OSGeo/grass/releases
>>         . I agree that esp for
>>         8.0.0 the link to the tarball means a lot of browsing down.
>> 
>> 
>>     Or instead of the releases page to that tags page I linked above.
>>     The links (both .tar.gz and .zip) are more readily available there.
>>     The target audience is technical anyway, so perhaps this is a
>>     preferred view at this point in the workflow.
>> 
>>     https://github.com/OSGeo/grass/tags
>>     
>> 
>> 
>> Here's the PR: https://github.com/OSGeo/grass-website/pull/284 
>> 
>> 
>> 
> 
> +1 to that change.
> 
> By the way, one of my last interactions with Martin Isenburg (may his 
> soul rest in peace) he gave me a strong lecture when I tried to send him 
> a tarball "jeff it is 2021 please send me something useful like a ZIP". 
>   He is totally right of course, and we should all remember to post 
> links to zip as well as .tar.gz etc on our main download pages.
> 
> -jeff
> 
> 
> 
> 
> 
> -- 
> Jeff McKenna
> GatewayGeo: Developers of MS4W, MapServer Consulting and Training
> co-founder of FOSS4G
> http://gatewaygeo.com/
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
> 


-- 

Huidae Cho, Ph.D., GISP, /hidɛ t͡ɕo/, 조희대, 曺喜大
GRASS GIS Developer
https://idea.isnew.info/

___
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-PSC] difficult to get GRASS source code package

2022-02-14 Thread Huidae Cho 
+1 for ZIP links.

Huidae

On Mon, Feb 14, 2022 at 3:24 PM Jeff McKenna 
wrote:

> On 2022-02-14 4:01 p.m., Veronica Andreo wrote:
> >
> > El lun, 14 feb 2022 a las 20:29, Vaclav Petras ( > >) escribió:
> >
> >
> > On Mon, 14 Feb 2022 at 14:22, Veronica Andreo  > > wrote:
> >
> >
> > Currently, there's a link to releases  in the first entry of
> > https://grass.osgeo.org/download/
> >  that points to
> > https://github.com/OSGeo/grass/releases
> > . I agree that esp for
> > 8.0.0 the link to the tarball means a lot of browsing down.
> >
> >
> > Or instead of the releases page to that tags page I linked above.
> > The links (both .tar.gz and .zip) are more readily available there.
> > The target audience is technical anyway, so perhaps this is a
> > preferred view at this point in the workflow.
> >
> > https://github.com/OSGeo/grass/tags
> > 
> >
> >
> > Here's the PR: https://github.com/OSGeo/grass-website/pull/284
> > 
> >
> >
>
> +1 to that change.
>
> By the way, one of my last interactions with Martin Isenburg (may his
> soul rest in peace) he gave me a strong lecture when I tried to send him
> a tarball "jeff it is 2021 please send me something useful like a ZIP".
>   He is totally right of course, and we should all remember to post
> links to zip as well as .tar.gz etc on our main download pages.
>
> -jeff
>
>
>
>
>
> --
> Jeff McKenna
> GatewayGeo: Developers of MS4W, MapServer Consulting and Training
> co-founder of FOSS4G
> http://gatewaygeo.com/
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
>


-- 
Huidae Cho, Ph.D., GISP, /hidɛ 
t͡ɕo/, 조희대, 曺喜大
GRASS GIS Developer
https://idea.isnew.info/
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS-PSC] difficult to get GRASS source code package

2022-02-14 Thread Jeff McKenna 

On 2022-02-14 4:01 p.m., Veronica Andreo wrote:


El lun, 14 feb 2022 a las 20:29, Vaclav Petras (>) escribió:



On Mon, 14 Feb 2022 at 14:22, Veronica Andreo mailto:veroand...@gmail.com>> wrote:


Currently, there's a link to releases  in the first entry of
https://grass.osgeo.org/download/
 that points to
https://github.com/OSGeo/grass/releases
. I agree that esp for
8.0.0 the link to the tarball means a lot of browsing down.


Or instead of the releases page to that tags page I linked above.
The links (both .tar.gz and .zip) are more readily available there.
The target audience is technical anyway, so perhaps this is a
preferred view at this point in the workflow.

https://github.com/OSGeo/grass/tags



Here's the PR: https://github.com/OSGeo/grass-website/pull/284 






+1 to that change.

By the way, one of my last interactions with Martin Isenburg (may his 
soul rest in peace) he gave me a strong lecture when I tried to send him 
a tarball "jeff it is 2021 please send me something useful like a ZIP". 
 He is totally right of course, and we should all remember to post 
links to zip as well as .tar.gz etc on our main download pages.


-jeff





--
Jeff McKenna
GatewayGeo: Developers of MS4W, MapServer Consulting and Training
co-founder of FOSS4G
http://gatewaygeo.com/
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS-PSC] difficult to get GRASS source code package

2022-02-14 Thread Veronica Andreo 
El lun, 14 feb 2022 a las 20:29, Vaclav Petras ()
escribió:

>
> On Mon, 14 Feb 2022 at 14:22, Veronica Andreo 
> wrote:
>
>>
>> Currently, there's a link to releases  in the first entry of
>> https://grass.osgeo.org/download/ that points to
>> https://github.com/OSGeo/grass/releases. I agree that esp for 8.0.0 the
>> link to the tarball means a lot of browsing down.
>>
>
> Or instead of the releases page to that tags page I linked above. The
> links (both .tar.gz and .zip) are more readily available there. The target
> audience is technical anyway, so perhaps this is a preferred view at this
> point in the workflow.
>
> https://github.com/OSGeo/grass/tags
>

Here's the PR: https://github.com/OSGeo/grass-website/pull/284
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS-PSC] difficult to get GRASS source code package

2022-02-14 Thread Vaclav Petras 
On Mon, 14 Feb 2022 at 14:22, Veronica Andreo  wrote:

>
> Currently, there's a link to releases  in the first entry of
> https://grass.osgeo.org/download/ that points to
> https://github.com/OSGeo/grass/releases. I agree that esp for 8.0.0 the
> link to the tarball means a lot of browsing down.
>

Or instead of the releases page to that tags page I linked above. The links
(both .tar.gz and .zip) are more readily available there. The target
audience is technical anyway, so perhaps this is a preferred view at this
point in the workflow.

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

Re: [GRASS-dev] [GRASS-PSC] difficult to get GRASS source code package

2022-02-14 Thread Veronica Andreo 
Hi all,

El lun, 14 feb 2022 a las 18:47, Markus Neteler ()
escribió:

> On Mon, Feb 14, 2022 at 5:08 PM Michael Barton 
> wrote:
> >
> > This sounds a bit weird, but with some recent changes to the GRASS
> website, it has become more difficult to find and download a current stable
> release.
> >
> > I went to find a tar/zip package of GRASS 8.0.0 source code to build and
> could not find one from the web site. The links all lead only to the GitHub
> repository.
>
> I agree that it is missing from
> https://grass.osgeo.org/download/



> In my view (I expressed that also in the past) we should link a zip
> file/tarball directly on that page. Just pointing to GH isn't enough
> and we even have the tarballs on the server:
>
> https://grass.osgeo.org/grass80/source/


Currently, there's a link to releases  in the first entry of
https://grass.osgeo.org/download/ that points to
https://github.com/OSGeo/grass/releases. I agree that esp for 8.0.0 the
link to the tarball means a lot of browsing down.
How would you like to include the tarball directly in the website? Would
you mind creating an issue in the website repo?

[image: image.png]

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

Re: [GRASS-dev] [GRASS-PSC] difficult to get GRASS source code package

2022-02-14 Thread Vaclav Petras 
Hi Michael,

This looks more like a grass-dev topic, than grass-psc. I'm adding
grass-dev, please remove grass-psc when (if) you reply.

I'll let others comment on the tarball and website and comment on the Git
and GitHub part. +1 for Nickals' answer.

Git is definitely a valid way of getting source code for a build and
perhaps a preferred one since there is all the extra metadata for files.
Maybe we should work on clarifying whether that's really the preferred way.

When using Git locally, you need to be careful if you are using your fork
or the upstream, OSGeo repo. If you do a new clone from GitHub, it should
be pretty clear what you used.

Clone by default gets the default branch which is main, so you need to
switch to another branch (`git switch` in modern Git, `git checkout` in old
Git):

git switch releasebranch_8_0
git switch --detach 8.0.0

git checkout releasebranch_8_0
git checkout 8.0.0

When we one does repetitive clones (e.g., in CI), you can do a shallow
clone with --branch (which works for tags too) to get just one given state
of the repo:

git clone --depth 1 --branch releasebranch_8_0
git clone --depth 1 --branch 8.0.0

When using GitHub, the link Download ZIP which is under the green Clone
button respects the current branch which you set using the combo-box at the
right side or using the "8 branches" link. You can get, e.g.,

https://github.com/OSGeo/grass/archive/refs/heads/releasebranch_8_0.zip

On top of what Nicklas said about the release, you can also use the "124
tags" link which takes you to an overview page with links for all tags
(==releases in our case).

https://github.com/OSGeo/grass/tags

Best,
Vaclav

On Mon, 14 Feb 2022 at 11:16, Michael Barton  wrote:

> I stand corrected. I am not sure that I have the current 8.0 stable
> release. Cloning gives me the main repository, not 8.0.0 stable. I can
> check out a branch but need to make sure that I've got the stable release
> 8.0.0. The reason is that I'm trying to package this in sync with other
> platforms. It looks like the 8.0.0 branch was updated recently. So it is
> not the fixed stable release of 17 days ago.
>
> Michael
> _
>
> C. Michael Barton
> Associate Director, School of Complex Adaptive Systems (
> https://scas.asu.edu)
> Professor, School of Human Evolution & Social Change (
> https://shesc.asu.edu)
> Director, Center for Social Dynamics & Complexity (
> https://complexity.asu.edu)
> Arizona State University
> Tempe, AZ 85287-2701
> USA
>
> Executive Director, Open Modeling Foundation (
> https://openmodelingfoundation.github.io)
> Director, Network for Computational Modeling in Social & Ecological
> Sciences (https://comses.net)
>
> personal website: http://www.public.asu.edu/~cmbarton
>
>
> On Feb 14, 2022, at 9:08 AM, Michael Barton 
> wrote:
>
> This sounds a bit weird, but with some recent changes to the GRASS
> website, it has become more difficult to find and download a current stable
> release.
>
> I went to find a tar/zip package of GRASS 8.0.0 source code to build and
> could not find one from the web site. The links all lead only to the GitHub
> repository. This is fine for people who want dev versions. But I would
> think that some people just want the package. I eventually cloned one from
> GitHub, but even there, it is not transparent how to get the stable release
> vs. an updated version. Even on GitHub, the clone/download button seemed to
> be missing.
>
> While I could get the software, it seems like we should put back in a link
> to the source code packages somewhere.
>
> Michael
> _
>
> C. Michael Barton
> Associate Director, School of Complex Adaptive Systems (
> https://scas.asu.edu)
> Professor, School of Human Evolution & Social Change (
> https://shesc.asu.edu)
> Director, Center for Social Dynamics & Complexity (
> https://complexity.asu.edu)
> Arizona State University
> Tempe, AZ 85287-2701
> USA
>
> Executive Director, Open Modeling Foundation (
> https://openmodelingfoundation.github.io)
> Director, Network for Computational Modeling in Social & Ecological
> Sciences (https://comses.net)
>
> personal website: http://www.public.asu.edu/~cmbarton
>
>
>
> ___
> grass-psc mailing list
> grass-...@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-psc
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev