Re: [GRASS-dev] grass on osgeo4w and spyder

[Vaclav Petras]

On Tue, Mar 24, 2020 at 4:31 PM Helmut Kudrnovsky  wrote:

> pvanbosgeo wrote
> > Hi devs,
> >
> > Has any of you experience in running Spyder (or any other Python IDE)
> > from the GRASS command line (GRASS  installed on Windows 10 with
> > OSGeo4W)? Any tips for how to set this up?
> >
> > I can run R/Rstudio from the GRASS command line. Nothing to set up,
> > just typing in rstudio on the grass gis command line to fire up
> > rstudio.
> >
> > That does not work, however, with Spyder (installed with Anaconda). As
> > an alternative, I tried to install Spyder with pip on the osgeo4w
> > command line. Installation seems to work, but when typing in spyder3
> > on the command line, nothing happens.
>
> have a look at
>
> https://grasswiki.osgeo.org/wiki/Tools_for_Python_programming#PyCharm_IDE
>
> it's related to
>
> add python-grass.bat for Python initialization
> https://github.com/OSGeo/grass/pull/43
> 


Once you figure out that for Spyder, please consider updating Windows
instructions at:

https://grasswiki.osgeo.org/wiki/Tools_for_Python_programming#Spyder_editor

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

Re: [GRASS-dev] grass on osgeo4w and spyder

[Helmut Kudrnovsky]

>I can run R/Rstudio from the GRASS command line. Nothing to set up,
>just typing in rstudio on the grass gis command line to fire up
>rstudio. 

I've implemented this by integrating

https://github.com/OSGeo/grass/tree/master/mswindows/external/rbatch

and

by adding some lines to the startup environment

https://github.com/OSGeo/grass/blob/master/mswindows/env.bat#L18







-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] grass on osgeo4w and spyder

[Helmut Kudrnovsky]

pvanbosgeo wrote
> Hi devs,
> 
> Has any of you experience in running Spyder (or any other Python IDE)
> from the GRASS command line (GRASS  installed on Windows 10 with
> OSGeo4W)? Any tips for how to set this up?
> 
> I can run R/Rstudio from the GRASS command line. Nothing to set up,
> just typing in rstudio on the grass gis command line to fire up
> rstudio.
> 
> That does not work, however, with Spyder (installed with Anaconda). As
> an alternative, I tried to install Spyder with pip on the osgeo4w
> command line. Installation seems to work, but when typing in spyder3
> on the command line, nothing happens.

have a look at 

https://grasswiki.osgeo.org/wiki/Tools_for_Python_programming#PyCharm_IDE

it's related to 

add python-grass.bat for Python initialization
https://github.com/OSGeo/grass/pull/436






-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Markus Neteler]

Hi all,

On Tue, Mar 24, 2020 at 5:59 PM Stefan Blumentrath
 wrote:
> Is there a list of things that people could/should work on?
>
> 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?


Here you go:
https://github.com/OSGeo/grass-website/projects/1

:-)

Cheers

Markus
___
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

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

[Veronica Andreo]

Hi Stefan :)

El mar., 24 mar. 2020 a las 17:59, Stefan Blumentrath (<
stefan.blumentr...@nina.no>) escribió:

> Ciao Vero,
>
>
>
> Very good initiative.
>
>
>
> Is there a list of things that people could/should work on?
>
>
>
> 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?

>
>
> Personally, even if in quarantine / isolation, I can only work on this
> during spare time, meaning evenings, when kids are in bed… So if there is a
> “sprint kick-off video conference” I would be happy if it could be
> scheduled for an evening…
>

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)

Let's hear others' opinion

Cheers,
Vero


>
> Cheers
>
> Stefan
>
>
>
> *From:* grass-dev  *On Behalf Of *Veronica
> Andreo
> *Sent:* tirsdag 24. mars 2020 17:08
> *To:* grass-dev ; GRASS-web <
> grass-...@lists.osgeo.org>
> *Subject:* [GRASS-dev] Let's work on the new GRASS website!
>
>
>
> Hi everyone,
>
>
>
> I hope all of you are doing well and stay healthy :) Since many of us are
> working from home or in quarantine, Luca and I thought this could be a good
> opportunity to do a full day sprint and work on the new GRASS website,
> i.e., fix issues, migrate/re-structure content, etc.
>
>
>
> Here's a doodle to vote on dates:
>
>
>
> https://doodle.com/poll/884epdzezy9zphpe
>
>
>
> I have put those days that for now I'm obliged to stay at home here in
> Argentina, but please suggest others if you want. Note that I left some
> empty spaces for eating too :)
>
>
>
> Once we find a day with majority of votes, then we can agree on a video
> call or so (jitsi works nicely)
>
>
>
> Let's finish the website!
>
>
>
> Cheers,
>
> Vero
>
>
>
> [I apologize for some double-postings, dunno who is in which list]
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3008: Mac Cmd-C clears console window instead of copying contents

[GRASS GIS]

#3008: Mac Cmd-C clears console window instead of copying contents
--+-
  Reporter:  cmbarton |  Owner:  grass-dev@…
  Type:  defect   | Status:  closed
  Priority:  normal   |  Milestone:  7.4.5
 Component:  wxGUI|Version:  unspecified
Resolution:  fixed|   Keywords:  mac
   CPU:  Unspecified  |   Platform:  MacOSX
--+-
Changes (by annakrat):

 * status:  new => closed
 * resolution:   => fixed


-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [GRASS GIS] #3592: cmd-c (copy on Mac) closes dialog in r.import

[GRASS GIS]

#3592: cmd-c (copy on Mac) closes dialog in r.import
--+-
  Reporter:  cmbarton |  Owner:  grass-dev@…
  Type:  defect   | Status:  closed
  Priority:  normal   |  Milestone:  7.6.2
 Component:  wxGUI|Version:  7.2.2
Resolution:  fixed|   Keywords:  cmd-c
   CPU:  Unspecified  |   Platform:  MacOSX
--+-
Changes (by annakrat):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Thanks!

-- 
Ticket URL: 
GRASS GIS 

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

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

[Stefan Blumentrath]

Ciao Vero,

Very good initiative.

Is there a list of things that people could/should work on?

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?

Personally, even if in quarantine / isolation, I can only work on this during 
spare time, meaning evenings, when kids are in bed… So if there is a “sprint 
kick-off video conference” I would be happy if it could be scheduled for an 
evening…

Cheers
Stefan

From: grass-dev  On Behalf Of Veronica Andreo
Sent: tirsdag 24. mars 2020 17:08
To: grass-dev ; GRASS-web 
Subject: [GRASS-dev] Let's work on the new GRASS website!

Hi everyone,

I hope all of you are doing well and stay healthy :) Since many of us are 
working from home or in quarantine, Luca and I thought this could be a good 
opportunity to do a full day sprint and work on the new GRASS website, i.e., 
fix issues, migrate/re-structure content, etc.

Here's a doodle to vote on dates:

https://doodle.com/poll/884epdzezy9zphpe

I have put those days that for now I'm obliged to stay at home here in 
Argentina, but please suggest others if you want. Note that I left some empty 
spaces for eating too :)

Once we find a day with majority of votes, then we can agree on a video call or 
so (jitsi works nicely)

Let's finish the website!

Cheers,
Vero

[I apologize for some double-postings, dunno who is in which list]
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Veronica Andreo]

Hi everyone,

I hope all of you are doing well and stay healthy :) Since many of us are
working from home or in quarantine, Luca and I thought this could be a good
opportunity to do a full day sprint and work on the new GRASS website,
i.e., fix issues, migrate/re-structure content, etc.

Here's a doodle to vote on dates:

https://doodle.com/poll/884epdzezy9zphpe

I have put those days that for now I'm obliged to stay at home here in
Argentina, but please suggest others if you want. Note that I left some
empty spaces for eating too :)

Once we find a day with majority of votes, then we can agree on a video
call or so (jitsi works nicely)

Let's finish the website!

Cheers,
Vero

[I apologize for some double-postings, dunno who is in which list]
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3652: Map display exception when switching to vector digitizer mode

[GRASS GIS]

#3652: Map display exception when switching to vector digitizer mode
+-
  Reporter:  balagates  |  Owner:  grass-dev@…
  Type:  defect | Status:  new
  Priority:  minor  |  Milestone:  7.8.3
 Component:  wxGUI  |Version:  7.4.0
Resolution: |   Keywords:
   CPU:  OSX/Intel  |   Platform:  MacOSX
+-

Comment (by nila):

 A fix for this issue has been proposed with
 [https://github.com/OSGeo/grass/pull/456 ​PR456].

 See also #3487.

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [GRASS GIS] #3592: cmd-c (copy on Mac) closes dialog in r.import

[GRASS GIS]

#3592: cmd-c (copy on Mac) closes dialog in r.import
--+-
  Reporter:  cmbarton |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.6.2
 Component:  wxGUI|Version:  7.2.2
Resolution:   |   Keywords:  cmd-c
   CPU:  Unspecified  |   Platform:  MacOSX
--+-

Comment (by nila):

 Fixed with commit
 
​[https://github.com/OSGeo/grass/commit/69148c8c2adb85233af5d120b990748a2ac81121
 69148c8]. This issue may be closed.

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [GRASS GIS] #3472: g.gui.iclass crashes the GUI

[GRASS GIS]

#3472: g.gui.iclass crashes the GUI
--+-
  Reporter:  cmbarton |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.4.5
 Component:  wxGUI|Version:  7.2.2
Resolution:   |   Keywords:  I.classify
   CPU:  Unspecified  |   Platform:  MacOSX
--+-

Comment (by nila):

 The [https://github.com/OSGeo/grass/pull/456 PR456] will probably fix
 this.

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [GRASS GIS] #3008: Mac Cmd-C clears console window instead of copying contents

[GRASS GIS]

#3008: Mac Cmd-C clears console window instead of copying contents
--+-
  Reporter:  cmbarton |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.4.5
 Component:  wxGUI|Version:  unspecified
Resolution:   |   Keywords:  mac
   CPU:  Unspecified  |   Platform:  MacOSX
--+-

Comment (by nila):

 Fixed with commit
 [https://github.com/OSGeo/grass/commit/69148c8c2adb85233af5d120b990748a2ac81121
 69148c8].
 This issue may be closed.

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [GRASS GIS] #3487: vector digitizer unstable

[GRASS GIS]

#3487: vector digitizer unstable
+---
  Reporter:  cmbarton   |  Owner:  grass-dev@…
  Type:  defect | Status:  new
  Priority:  critical   |  Milestone:  7.8.3
 Component:  wxGUI  |Version:  7.2.2
Resolution: |   Keywords:  digitizer, ctypes
   CPU:  OSX/Intel  |   Platform:  MacOSX
+---

Comment (by nila):

 This was a very tricky issue, but with a really simple solution. The
 ctypesgen generated python files are rendered incomplete, in this case  in
 particular `include/vect/dig_structs.h` and the python mapping of
 Map_info.

 E.g. the following parts of `etc/python/grass/lib/vector.py` were missing:
 {{{
 struct_Map_info.__slots__ = [
 ...
 struct_Map_info._fields_ = [
 ..
 }}}

 This can be fixed with the addition of the compiler flag `-D_Nullable=`.

 A fix for this issue has been proposed with
 [https://github.com/OSGeo/grass/pull/456 PR456].

-- 
Ticket URL: 
GRASS GIS 

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

[GRASS-dev] grass on osgeo4w and spyder

[Paulo van Breugel]

Hi devs,

Has any of you experience in running Spyder (or any other Python IDE)
from the GRASS command line (GRASS  installed on Windows 10 with
OSGeo4W)? Any tips for how to set this up?

I can run R/Rstudio from the GRASS command line. Nothing to set up,
just typing in rstudio on the grass gis command line to fire up
rstudio.

That does not work, however, with Spyder (installed with Anaconda). As
an alternative, I tried to install Spyder with pip on the osgeo4w
command line. Installation seems to work, but when typing in spyder3
on the command line, nothing happens.

Best regards,

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

Re: [GRASS-dev] compiling failing in ctypes

[Sebastiaan Couwenberg]

On 3/24/20 11:20 AM, Luca Delucchi wrote:
> 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)

python3 on Debian unstable now defaults to 3.8.2.

python3-defaults is not yet in testing (bullseye) due to many
autopkgtest failures, see:

 https://tracker.debian.org/pkg/python3-defaults

And the transition bugreport and tracker:

 https://bugs.debian.org/949187
 https://release.debian.org/transitions/html/python3.8-default.html

GRASS 7.8.2 built fine with python3.8 as part of the transition to PROJ 7.

 
https://buildd.debian.org/status/fetch.php?pkg=grass=amd64=7.8.2-1%2Bb4=1584544544=0

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Paulo van Breugel]

On Tue, Mar 24, 2020 at 10:24 AM Luca Delucchi  wrote:
>
> 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

OK, will try that, thanks.

>
> > 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

[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] db.copy gives error

[Moritz Lennert]

Am 14. März 2020 23:38:58 MEZ schrieb Markus Metz 
:
>On Sat, Mar 14, 2020 at 3:27 PM Paulo van Breugel
>
>wrote:
>>
>> Dear devs,
>>
>> 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
>
>Looking at the code of db.copy, it is not possible that this ever
>worked,
>you need to replace the variables with their actual values.

Well, it should work if you run 

eval $(g.gisenv -s) before, no ?

Moritz

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

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

[Paulo van Breugel]

On Sat, Mar 14, 2020 at 11:39 PM Markus Metz
 wrote:
>
>
>
> On Sat, Mar 14, 2020 at 3:27 PM Paulo van Breugel  
> wrote:
> >
> > Dear devs,
> >
> > 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
>
> Looking at the code of db.copy, it is not possible that this ever worked, you 
> need to replace the variables with their actual values.

Yes, I did work with the actual values, which gave me the error below.
Then I tried the above, but that as you rightly noted, shouldn't, and
didn't work either. In the meantime I recreated the database and did a
fresh install of grass, and now my script works again. I am not sure
which of the two made it work again (should have done this more
systematically), but in any case, thanks for the feedback Markus.

>
> Markus M
> >
> > 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?
> >
> > With kind regards,
> >
> > Paulo
> > ___
> > 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