Re: [GRASS-user] grass-user Digest, Vol 180, Issue 4

[Markus Neteler]

Hi Tim,

On Sun, Apr 11, 2021 at 10:42 AM Timothy Glyn Southern via grass-user
 wrote:
>
> Thanks Anna, I believe you are correct with your ideas, unfortunately the 
> only fix given is way beyond my level of understanding and coding

AFAIK the needed upstream fix on wyPython was this:
https://github.com/wxWidgets/Phoenix/pull/1849/files
merged into their master on Nov 18, 2020. I have no idea in which
wxPython release this will be/has been included.

https://archlinux.org/packages/community/x86_64/python-wxpython/
--> python-wxpython 4.0.7.2-5, Build Date: 2020-11-12
  ==> too old.

https://github.com/wxWidgets/Phoenix/releases
on Nov 25, 2020: wxPython-4.1.1
  ==> not yet packaged.

(Note that I am only guessing around here.)

Since I use Fedora (33) and didn't want to wait I contacted the
maintainer in Nov 2020.
They patched the package accordingly, added the aforementioned fix:
https://src.fedoraproject.org/rpms/python-wxpython4/c/f5471fb86aaae46a686b85c654fcbb98516355e6?branch=rawhide
and shipped the updated 4.0.7-13 RPM package right away, end of Nov 2020.

Maybe you could request to apply the fix also in the Manjaro package?

> Is there likely to be an updated version loaded to repository before too long 
> that corrects the problem?

The packagers need to be aware of it...

Best,
Markus
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] grass-user Digest, Vol 180, Issue 4

[Timothy Glyn Southern via grass-user]

Thanks Anna, I believe you are correct with your ideas, unfortunately the only 
fix given is way beyond my level of understanding and coding and from what I 
gather uses a non svn version python 4.1. There was a mention in that link to a 
newer version of python 4.0.8 but it seems it has not either been implemented 
or if it has uploaded to the repository.

Evidently the bug is in both python 3.9 and the 4.0 version currently used in 
the repository.

Is there likely to be an updated version loaded to repository before too long 
that corrects the problem?

Kind regards

Tim
Dr Timothy Glyn Southern





> On 11 Apr 2021, at 04:55, Anna Petrášová  wrote:
> 
> Hello,
> 
> On Sat, Apr 10, 2021 at 12:51 PM Timothy Glyn Southern via grass-user 
> mailto:grass-user@lists.osgeo.org>> wrote:
> Problem with wxpython guy in Manjaro with grass 7.8.5
> 
> Dear colleagues,
> 
> Following a period of low use due to health issues I am once again trying to 
> use GRASS to visualise and analyse archaeological data.
> 
> I am running Manjaro and the latest download of GRASS from AUR.
> 
> It starts fine and shows both display windows for the GUI and then the 
> windows crash. It is repeatable.
> 
> I have tried removing GRASS and reinstalling but that has not fixed the 
> issue. As well I have tried changing the flags on the GUI. None make any 
> difference, as soon as the mouse is apparently moved the windows crash.
> 
> Is this a known problem and is there a work around?
> 
> based on your description it sounds like a bug in wxPython with Python 3.9:
> https://github.com/OSGeo/grass/issues/1123 
> 
> 
> Hope that helps,
> Anna
> 
> 
> Thanks
> 
> Tim Southern
> Dr Timothy Glyn Southern
> 0155 941 8432
> 0791 076 6814
> 
> 
> 
> 
> 
>> On 4 Apr 2021, at 20:00, grass-user-requ...@lists.osgeo.org 
>>  wrote:
>> 
>> Send grass-user mailing list submissions to
>>  grass-user@lists.osgeo.org 
>> 
>> To subscribe or unsubscribe via the World Wide Web, visit
>>  https://lists.osgeo.org/mailman/listinfo/grass-user 
>> 
>> or, via email, send a message with subject or body 'help' to
>>  grass-user-requ...@lists.osgeo.org 
>> 
>> 
>> You can reach the person managing the list at
>>  grass-user-ow...@lists.osgeo.org 
>> 
>> 
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of grass-user digest..."
>> 
>> 
>> Today's Topics:
>> 
>>   1. Re: r.watershed identify inland watershed (ming han)
>> 
>> 
>> --
>> 
>> Message: 1
>> Date: Sat, 3 Apr 2021 16:23:26 -0400
>> From: ming han mailto:dustm...@gmail.com>>
>> To: Micha Silver mailto:tsvi...@gmail.com>>
>> Cc: GRASS user list > >
>> Subject: Re: [GRASS-user] r.watershed identify inland watershed
>> Message-ID:
>>  > >
>> Content-Type: text/plain; charset="utf-8"
>> 
>> Hi Micha
>> 
>>I understand what you mean. But it requires another step to
>> manually identify depressions from these pre-conditioned DEM.
>> 
>> Cheers
>> Ming
>> 
>> 
>> Micha Silver mailto:tsvi...@gmail.com>> ?2021?4?3??? 
>> ??12:43???
>> 
>>> 
>>> On 4/2/21 5:37 PM, ming han wrote:
 Maybe I am the only one who has this demand. Following is just a
 recommendation to GRASS r.watershed function.
 Maybe it is worth having an option to avoid r.watershed overcome
 depressions.
 The reasons are 1) there are many hydrologically pre condition DEM
 data available globally, such as:HydroSHEDS, MERIT
2) the depression in these DEM are real
 depressions, overcome these depressions will make the entire drainage
 system
>>> 
>>> 
>>> Regarding Hydrosheds, the documentation[1] in section 3.4 explains how
>>> they overcame the problem of sinks. They performed a regular "fill
>>> sinks" operation on areas that were SRTM artifacts. True natural
>>> depressions were identified manually, then another manual procedure of
>>> carving rivers was done to force flow thru these depressions and produce
>>> hydrologically correct streams and basins. So pre-conditioning to
>>> overcome depressions is not a magic bullet...
>>> 
>>> 
>>> In my opinion, the best results are obtained when true depressions
>>> (pits, salt playas or karst regions) are identified, and set to NULL in
>>> the elevation raster. That will allow r.watershed to stop routing at
>>> those locations, and produce correct stream and basin layers.
>>> 
>>> 
>>> [1]https://hydrosheds.org/images/inpages/HydroSHEDS_TechDoc_v1_2.pdf 
>>> 
>>> 
>>> 
 

Re: [GRASS-user] grass-user Digest, Vol 180, Issue 4

[Anna Petrášová]

Hello,

On Sat, Apr 10, 2021 at 12:51 PM Timothy Glyn Southern via grass-user <
grass-user@lists.osgeo.org> wrote:

> Problem with wxpython guy in Manjaro with grass 7.8.5
>
> Dear colleagues,
>
> Following a period of low use due to health issues I am once again trying
> to use GRASS to visualise and analyse archaeological data.
>
> I am running Manjaro and the latest download of GRASS from AUR.
>
> It starts fine and shows both display windows for the GUI and then the
> windows crash. It is repeatable.
>
> I have tried removing GRASS and reinstalling but that has not fixed the
> issue. As well I have tried changing the flags on the GUI. None make any
> difference, as soon as the mouse is apparently moved the windows crash.
>
> Is this a known problem and is there a work around?
>

based on your description it sounds like a bug in wxPython with Python 3.9:
https://github.com/OSGeo/grass/issues/1123

Hope that helps,
Anna


> Thanks
>
> Tim Southern
> Dr Timothy Glyn Southern
> 0155 941 8432
> 0791 076 6814
>
>
>
>
>
> On 4 Apr 2021, at 20:00, grass-user-requ...@lists.osgeo.org wrote:
>
> Send grass-user mailing list submissions to
> grass-user@lists.osgeo.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.osgeo.org/mailman/listinfo/grass-user
> or, via email, send a message with subject or body 'help' to
> grass-user-requ...@lists.osgeo.org
>
> You can reach the person managing the list at
> grass-user-ow...@lists.osgeo.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of grass-user digest..."
>
>
> Today's Topics:
>
>   1. Re: r.watershed identify inland watershed (ming han)
>
>
> --
>
> Message: 1
> Date: Sat, 3 Apr 2021 16:23:26 -0400
> From: ming han 
> To: Micha Silver 
> Cc: GRASS user list 
> Subject: Re: [GRASS-user] r.watershed identify inland watershed
> Message-ID:
> 
> Content-Type: text/plain; charset="utf-8"
>
> Hi Micha
>
>I understand what you mean. But it requires another step to
> manually identify depressions from these pre-conditioned DEM.
>
> Cheers
> Ming
>
>
> Micha Silver  ?2021?4?3??? ??12:43???
>
>
> On 4/2/21 5:37 PM, ming han wrote:
>
> Maybe I am the only one who has this demand. Following is just a
> recommendation to GRASS r.watershed function.
> Maybe it is worth having an option to avoid r.watershed overcome
> depressions.
> The reasons are 1) there are many hydrologically pre condition DEM
> data available globally, such as:HydroSHEDS, MERIT
>2) the depression in these DEM are real
> depressions, overcome these depressions will make the entire drainage
> system
>
>
>
> Regarding Hydrosheds, the documentation[1] in section 3.4 explains how
> they overcame the problem of sinks. They performed a regular "fill
> sinks" operation on areas that were SRTM artifacts. True natural
> depressions were identified manually, then another manual procedure of
> carving rivers was done to force flow thru these depressions and produce
> hydrologically correct streams and basins. So pre-conditioning to
> overcome depressions is not a magic bullet...
>
>
> In my opinion, the best results are obtained when true depressions
> (pits, salt playas or karst regions) are identified, and set to NULL in
> the elevation raster. That will allow r.watershed to stop routing at
> those locations, and produce correct stream and basin layers.
>
>
> [1]https://hydrosheds.org/images/inpages/HydroSHEDS_TechDoc_v1_2.pdf
>
>
> incorrectly.
>
> I understand GRASS has other functions to solve this problem, but just
> a user recommendation. I use GRASS a lot.
>
> Thanks
> Ming
>
> ming han mailto:dustm...@gmail.com>>
> ?2021?3?30??? ??8:06???
>
>Got it, thanks everyone~
>Ming
>
>Micha Silver mailto:tsvi...@gmail.com>>
>?2021?3?29??? ??2:40???
>
>Hello:
>
>You might try `r.param.scale`, or even better `r.geomorphons`
>modules to
>identify geomorphology features, then filter out all pixels
>identified
>as pits.
>
>
>r.watershed is purposely designed to overcome depressions, and
>find flow
>routing thru these spots. So I don't think you can use that
>module to
>identify depressions.
>
>
>On 3/27/21 8:49 PM, ming han wrote:
>
> Hi  Everyone
>
> When I do watershed delineation using r.watershed for
>
>great salt
>
> lake watershed. I found r.watershed always tried to assign
>
>an outlet
>
> for a great salt lake, which does actually not exist because
>
>it is an
>
> inland lake and the great salt lake has no watershed outlet
>
>at all.
>
>
>  I noticed that there is a depression option. But is
>
>there any
>
> way that  r.watershed can automatically identify depressions
>
>while
>
> defining flow accumulation and stream network?
>
> Thanks
> Ming
>
> 

Re: [GRASS-user] grass-user Digest, Vol 180, Issue 4

[Timothy Glyn Southern via grass-user]

The problem I have just posted appears to be the same as ticket 1123 and 1261 
yet they were supposedly resolved in January. The issue appears to be that the 
promised wxPython 4.0.8 is still not used in the build but the problematic 
4.0.7.

Is there any news on when either wxPython 4.0.8 will be available?

Thanks

Tim Southern
Dr Timothy Glyn Southern
0155 941 8432
0791 076 6814





> On 10 Apr 2021, at 17:43, Timothy Glyn Southern  
> wrote:
> 
> Problem with wxpython guy in Manjaro with grass 7.8.5
> 
> Dear colleagues,
> 
> Following a period of low use due to health issues I am once again trying to 
> use GRASS to visualise and analyse archaeological data.
> 
> I am running Manjaro and the latest download of GRASS from AUR.
> 
> It starts fine and shows both display windows for the GUI and then the 
> windows crash. It is repeatable.
> 
> I have tried removing GRASS and reinstalling but that has not fixed the 
> issue. As well I have tried changing the flags on the GUI. None make any 
> difference, as soon as the mouse is apparently moved the windows crash.
> 
> Is this a known problem and is there a work around?
> 
> Thanks
> 
> Tim Southern
> Dr Timothy Glyn Southern
> 0155 941 8432
> 0791 076 6814
> 
> 
> 
> 
> 
>> On 4 Apr 2021, at 20:00, grass-user-requ...@lists.osgeo.org 
>>  wrote:
>> 
>> Send grass-user mailing list submissions to
>>  grass-user@lists.osgeo.org 
>> 
>> To subscribe or unsubscribe via the World Wide Web, visit
>>  https://lists.osgeo.org/mailman/listinfo/grass-user
>> or, via email, send a message with subject or body 'help' to
>>  grass-user-requ...@lists.osgeo.org
>> 
>> You can reach the person managing the list at
>>  grass-user-ow...@lists.osgeo.org
>> 
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of grass-user digest..."
>> 
>> 
>> Today's Topics:
>> 
>>   1. Re: r.watershed identify inland watershed (ming han)
>> 
>> 
>> --
>> 
>> Message: 1
>> Date: Sat, 3 Apr 2021 16:23:26 -0400
>> From: ming han 
>> To: Micha Silver 
>> Cc: GRASS user list 
>> Subject: Re: [GRASS-user] r.watershed identify inland watershed
>> Message-ID:
>>  
>> Content-Type: text/plain; charset="utf-8"
>> 
>> Hi Micha
>> 
>>I understand what you mean. But it requires another step to
>> manually identify depressions from these pre-conditioned DEM.
>> 
>> Cheers
>> Ming
>> 
>> 
>> Micha Silver  ?2021?4?3??? ??12:43???
>> 
>>> 
>>> On 4/2/21 5:37 PM, ming han wrote:
 Maybe I am the only one who has this demand. Following is just a
 recommendation to GRASS r.watershed function.
 Maybe it is worth having an option to avoid r.watershed overcome
 depressions.
 The reasons are 1) there are many hydrologically pre condition DEM
 data available globally, such as:HydroSHEDS, MERIT
2) the depression in these DEM are real
 depressions, overcome these depressions will make the entire drainage
 system
>>> 
>>> 
>>> Regarding Hydrosheds, the documentation[1] in section 3.4 explains how
>>> they overcame the problem of sinks. They performed a regular "fill
>>> sinks" operation on areas that were SRTM artifacts. True natural
>>> depressions were identified manually, then another manual procedure of
>>> carving rivers was done to force flow thru these depressions and produce
>>> hydrologically correct streams and basins. So pre-conditioning to
>>> overcome depressions is not a magic bullet...
>>> 
>>> 
>>> In my opinion, the best results are obtained when true depressions
>>> (pits, salt playas or karst regions) are identified, and set to NULL in
>>> the elevation raster. That will allow r.watershed to stop routing at
>>> those locations, and produce correct stream and basin layers.
>>> 
>>> 
>>> [1]https://hydrosheds.org/images/inpages/HydroSHEDS_TechDoc_v1_2.pdf
>>> 
>>> 
 incorrectly.
 
 I understand GRASS has other functions to solve this problem, but just
 a user recommendation. I use GRASS a lot.
 
 Thanks
 Ming
 
 ming han mailto:dustm...@gmail.com>>
 ?2021?3?30??? ??8:06???
 
Got it, thanks everyone~
Ming
 
Micha Silver mailto:tsvi...@gmail.com>>
?2021?3?29??? ??2:40???
 
Hello:
 
You might try `r.param.scale`, or even better `r.geomorphons`
modules to
identify geomorphology features, then filter out all pixels
identified
as pits.
 
 
r.watershed is purposely designed to overcome depressions, and
find flow
routing thru these spots. So I don't think you can use that
module to
identify depressions.
 
 
On 3/27/21 8:49 PM, ming han wrote:
> Hi  Everyone
> 
> When I do 

Re: [GRASS-user] grass-user Digest, Vol 180, Issue 4

[Timothy Glyn Southern via grass-user]

Problem with wxpython guy in Manjaro with grass 7.8.5

Dear colleagues,

Following a period of low use due to health issues I am once again trying to 
use GRASS to visualise and analyse archaeological data.

I am running Manjaro and the latest download of GRASS from AUR.

It starts fine and shows both display windows for the GUI and then the windows 
crash. It is repeatable.

I have tried removing GRASS and reinstalling but that has not fixed the issue. 
As well I have tried changing the flags on the GUI. None make any difference, 
as soon as the mouse is apparently moved the windows crash.

Is this a known problem and is there a work around?

Thanks

Tim Southern
Dr Timothy Glyn Southern
0155 941 8432
0791 076 6814





> On 4 Apr 2021, at 20:00, grass-user-requ...@lists.osgeo.org wrote:
> 
> Send grass-user mailing list submissions to
>   grass-user@lists.osgeo.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>   https://lists.osgeo.org/mailman/listinfo/grass-user
> or, via email, send a message with subject or body 'help' to
>   grass-user-requ...@lists.osgeo.org
> 
> You can reach the person managing the list at
>   grass-user-ow...@lists.osgeo.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of grass-user digest..."
> 
> 
> Today's Topics:
> 
>   1. Re: r.watershed identify inland watershed (ming han)
> 
> 
> --
> 
> Message: 1
> Date: Sat, 3 Apr 2021 16:23:26 -0400
> From: ming han 
> To: Micha Silver 
> Cc: GRASS user list 
> Subject: Re: [GRASS-user] r.watershed identify inland watershed
> Message-ID:
>   
> Content-Type: text/plain; charset="utf-8"
> 
> Hi Micha
> 
>I understand what you mean. But it requires another step to
> manually identify depressions from these pre-conditioned DEM.
> 
> Cheers
> Ming
> 
> 
> Micha Silver  ?2021?4?3??? ??12:43???
> 
>> 
>> On 4/2/21 5:37 PM, ming han wrote:
>>> Maybe I am the only one who has this demand. Following is just a
>>> recommendation to GRASS r.watershed function.
>>> Maybe it is worth having an option to avoid r.watershed overcome
>>> depressions.
>>> The reasons are 1) there are many hydrologically pre condition DEM
>>> data available globally, such as:HydroSHEDS, MERIT
>>>2) the depression in these DEM are real
>>> depressions, overcome these depressions will make the entire drainage
>>> system
>> 
>> 
>> Regarding Hydrosheds, the documentation[1] in section 3.4 explains how
>> they overcame the problem of sinks. They performed a regular "fill
>> sinks" operation on areas that were SRTM artifacts. True natural
>> depressions were identified manually, then another manual procedure of
>> carving rivers was done to force flow thru these depressions and produce
>> hydrologically correct streams and basins. So pre-conditioning to
>> overcome depressions is not a magic bullet...
>> 
>> 
>> In my opinion, the best results are obtained when true depressions
>> (pits, salt playas or karst regions) are identified, and set to NULL in
>> the elevation raster. That will allow r.watershed to stop routing at
>> those locations, and produce correct stream and basin layers.
>> 
>> 
>> [1]https://hydrosheds.org/images/inpages/HydroSHEDS_TechDoc_v1_2.pdf
>> 
>> 
>>> incorrectly.
>>> 
>>> I understand GRASS has other functions to solve this problem, but just
>>> a user recommendation. I use GRASS a lot.
>>> 
>>> Thanks
>>> Ming
>>> 
>>> ming han mailto:dustm...@gmail.com>>
>>> ?2021?3?30??? ??8:06???
>>> 
>>>Got it, thanks everyone~
>>>Ming
>>> 
>>>Micha Silver mailto:tsvi...@gmail.com>>
>>>?2021?3?29??? ??2:40???
>>> 
>>>Hello:
>>> 
>>>You might try `r.param.scale`, or even better `r.geomorphons`
>>>modules to
>>>identify geomorphology features, then filter out all pixels
>>>identified
>>>as pits.
>>> 
>>> 
>>>r.watershed is purposely designed to overcome depressions, and
>>>find flow
>>>routing thru these spots. So I don't think you can use that
>>>module to
>>>identify depressions.
>>> 
>>> 
>>>On 3/27/21 8:49 PM, ming han wrote:
 Hi  Everyone
 
 When I do watershed delineation using r.watershed for
>>>great salt
 lake watershed. I found r.watershed always tried to assign
>>>an outlet
 for a great salt lake, which does actually not exist because
>>>it is an
 inland lake and the great salt lake has no watershed outlet
>>>at all.
 
  I noticed that there is a depression option. But is
>>>there any
 way that  r.watershed can automatically identify depressions
>>>while
 defining flow accumulation and stream network?
 
 Thanks
 Ming
 
 ___
 grass-user mailing list
 grass-user@lists.osgeo.org