Re: [GRASS-user] Python3 with grass.7.9.dev?

2020-12-10 Thread Markus Neteler
Rich,

Rich Shepard  schrieb am Fr., 11. Dez. 2020,
01:17:

> I believe that the only python2 application still installed here is grass.
> Will the 7.9.dev versions run on python3? I've python3-3.7.9 installed
> here.
> I'd like to clean out all the python2 packages when I can.
>


Just go ahead.
Python 3 is already supported since 7.8.0, see

https://trac.osgeo.org/grass/wiki/Grass7/NewFeatures78

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


[GRASS-user] Python3 with grass.7.9.dev?

2020-12-10 Thread Rich Shepard

I believe that the only python2 application still installed here is grass.
Will the 7.9.dev versions run on python3? I've python3-3.7.9 installed here.
I'd like to clean out all the python2 packages when I can.

Stay well all,

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


Re: [GRASS-user] r.futures not working

2020-12-10 Thread Helmut Kudrnovsky
Tom Hackbarth wrote
> Dear grass users,
> 
> I am trying to work my way through the r.futures workshop (
> https://grasswiki.osgeo.org/wiki/Workshop_on_urban_growth_modeling_with_FUTURES#Potential_submodel),
> but as soon as I get to the point of using the first r.futures module -
> r.futures-potential I come to a dead end.
> 
> This is the message I get:
> 
> ___
> 
> r.futures.potential input=sampling@practice1 output=potential.csv
> columns=devpressure_0_5_92,road_dens_perc,forest_1992_smooth_perc,dist_to_water_km,dist_to_protected_km
> developed_column=urban_change_clip subregions_column=counties
> Computing model...
> Traceback (most recent call last):
>   File "C:\Users\\AppData\Roaming\GRASS7\addons/scripts
> /r.futures.potential.py", line 221, in 
> 
> sys.exit(main())
>   File "C:\Users\\AppData\Roaming\GRASS7\addons/scripts
> /r.futures.potential.py", line 192, in main
> p = subprocess.Popen(cmd, stdout=subprocess.PIPE,
> stderr=subprocess.PIPE)
>   File "D:\Programme\apps\Python37\lib\subprocess.py", line
> 756, in __init__
> restore_signals, start_new_session)
>   File "D:\Programme\apps\Python37\lib\subprocess.py", line
> 1155, in _execute_child
> startupinfo)
> FileNotFoundError: [WinError 2] The system cannot find the file specified)
> 
> 
> _
> 
> There seems to be a problem with the Python code. I also tried to work it
> out on linux manjaro, but I get more or less the same error message in the
> End.
> 
> Is there anyone who can help me on this? I came not even close to
> repairing the error, so I am happy about any advice one can give me.
> 
> Thank you in advance.
> 
> Best regards
> 
> Tom
> 
> ___
> grass-user mailing list

> grass-user@.osgeo

> https://lists.osgeo.org/mailman/listinfo/grass-user


which winGRASS version are you using? standalone winGRASS? OSGeo4W winGRASS?
QGIS bundled winGRASS?

>D:\Programme\apps\Python37\

which python are you using? is it the phyton bundled with winGRASS?



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


[GRASS-user] How to add a new column based of polyline cat.

2020-12-10 Thread Kenneth Roy Cabrera Torres
Dear GRASS users:

Can you give any suggestions to solve this problem?

I have an ordered dataset of segments of river currents output from
r.stream.order command.
I will like to add a column to this dataset that identifies each current
according to Horton ordering.
I mean it actually identifies the Horton number. But what I want to do is
to separate each
Horton current from each order. For example, if I have, say 4 Horton
currents of order 5,
then I will like to have an additional column that identifies each Horton
current (5-1, 5-2, ..., 5-4).

I try with v.build.polyline and indeed it separates the individual currents
of the same
Horton order. But I don't know how to incorporate that new cat ID to the
current segments' dataset.

Thank you for your help.

-- 
Kenneth Roy Cabrera Torres
Cel 315 504 9339
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user


Re: [GRASS-user] r.futures not working

2020-12-10 Thread Anna Petrášová
Hi Tom,

On Thu, Dec 10, 2020 at 4:24 AM Tom Hackbarth  wrote:

> Hi Anna,
>
> thanks for your answer.
>
> I reinstalled it already multiple times. I get the same error message
> every time though. I will try it on a mac tomorrow, but that is the last
> idea I have. Has there ever been a problem like this using r.futures? It's
> such a shame because I really want to use it for my Master's Thesis as it
> is capable of all the things that I need to do for it, but I cannot get
> it to work.
>

I am not sure why reinstalling doesn't work and I am myself on Linux
so can't test now. You can try to paste a line like this:

set PATH=%PATH%;C:\Program Files\R\R-3.5.0\bin

in the GRASS terminal (the black one), you need to change the path to R
based on your R installation. Then try to run Rscript in the terminal, just
to see if the binary can now be found. If yes, try to run
r.futures.potential. This temporarily changes the PATH variable so that
your system can find R, once you close GRASS, you need to repeat this next
you need to run it. Let us know if at least this works.

Anna


>
> Best regards
>
> Tom
>
> Am Mi., 9. Dez. 2020 um 15:01 Uhr schrieb Anna Petrášová <
> kratocha...@gmail.com>:
>
>>
>>
>> On Wed, Dec 9, 2020 at 8:37 AM Tom Hackbarth 
>> wrote:
>>
>>> Dear grass users,
>>>
>>> I am trying to work my way through the r.futures workshop (
>>> https://grasswiki.osgeo.org/wiki/Workshop_on_urban_growth_modeling_with_FUTURES#Potential_submodel),
>>> but as soon as I get to the point of using the first r.futures module -
>>> r.futures-potential I come to a dead end.
>>>
>>> This is the message I get:
>>>
>>> ___
>>>
>>> r.futures.potential input=sampling@practice1 output=potential.csv
>>> columns=devpressure_0_5_92,road_dens_perc,forest_1992_smooth_perc,dist_to_water_km,dist_to_protected_km
>>> developed_column=urban_change_clip subregions_column=counties
>>> Computing model...
>>> Traceback (most recent call last):
>>>   File "C:\Users\\AppData\Roaming\GRASS7\addons/scripts
>>> /r.futures.potential.py", line 221, in 
>>> sys.exit(main())
>>>   File "C:\Users\\AppData\Roaming\GRASS7\addons/scripts
>>> /r.futures.potential.py", line 192, in main
>>> p = subprocess.Popen(cmd, stdout=subprocess.PIPE,
>>> stderr=subprocess.PIPE)
>>>   File "D:\Programme\apps\Python37\lib\subprocess.py", line
>>> 756, in __init__
>>> restore_signals, start_new_session)
>>>   File "D:\Programme\apps\Python37\lib\subprocess.py", line
>>> 1155, in _execute_child
>>> startupinfo)
>>> FileNotFoundError: [WinError 2] The system cannot find the file
>>> specified)
>>>
>>> _
>>>
>>> There seems to be a problem with the Python code. I also tried to work
>>> it out on linux manjaro, but I get more or less the same error message in
>>> the End.
>>>
>>> Is there anyone who can help me on this? I came not even close to
>>> repairing the error, so I am happy about any advice one can give me.
>>>
>>> Thank you in advance.
>>>
>>> Copying response from grass-web:
>>
>> r.futures.potential calls Rscript, so the error means it can't find the
>> Rscript binary. If R is installed, I would recommend reinstalling GRASS,
>> during installation it tries to automatically look for it, so there is a
>> chance it will work then. I would recommend subscribing to grass-user
>> mailing list and ask more questions there.
>>
>> Anna
>>
>>
>>> Best regards
>>>
>>> Tom
>>> ___
>>> grass-user mailing list
>>> grass-user@lists.osgeo.org
>>> https://lists.osgeo.org/mailman/listinfo/grass-user
>>>
>>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user


Re: [GRASS-user] Call for candidates for Chief Return Officer(s) to oversee election of new Project Steering Committee

2020-12-10 Thread Moritz Lennert

On 10/12/20 14:43, Rich Shepard wrote:

On Thu, 10 Dec 2020, Moritz Lennert wrote:


The first step in that procedure is the nomination of one (or several)
Chief Return Officer(s) (CRO) who will oversee the election process and
who should not be a member of the current PSC, nor aim at becoming a
member of the new PSC.


Moritz,

What does the position involve and require?


Basically the tasks are:

- Announce elections and election procedures
- Receive nominations and confirmation from candidates that they accept 
to be nominated

- Fill out the list of nominees on the wiki page [1]
- Collect some info from the candidates and put it on the wiki page (see 
at the very end of the page the suggestion, i.e. ask each candidate to 
respond to the question  "What should the community expect from your PSC 
membership?")
- organize the election (configure vote on 
https://vote.heliosvoting.org/, launch vote, launch reminder, tally votes)

- announce results
 - deal with any complaints (I doubt that there will be any)

Moritz

[1] https://trac.osgeo.org/grass/wiki/PSC/Election2020
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user


Re: [GRASS-user] Call for candidates for Chief Return Officer(s) to oversee election of new Project Steering Committee

2020-12-10 Thread Rich Shepard

On Thu, 10 Dec 2020, Moritz Lennert wrote:


The first step in that procedure is the nomination of one (or several)
Chief Return Officer(s) (CRO) who will oversee the election process and
who should not be a member of the current PSC, nor aim at becoming a
member of the new PSC.


Moritz,

What does the position involve and require?

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


[GRASS-user] Call for candidates for Chief Return Officer(s) to oversee election of new Project Steering Committee

2020-12-10 Thread Moritz Lennert

Dear all,

As part of the effort to guarantee a solid and sustainable governance of 
GRASS GIS development, and in accordance with OSGeo guidelines, we have 
a Project Steering Committee (PSC) [1]. Although most decisions are 
taken by consensus via the mailing lists or via discussions in github 
issues, some decisions go through this committee: annual budget, 
admission of new developers into the core development team, and some 
fundamental decisions (recent example: phasing out of a 32-bit version 
for MS Windows).


The last election for this committee was in 2016 and at the time we 
decided that the PSC should be renewed approximately every 3 years. We 
are already beyond this time frame and so a new election should happen, 
soon. The general outline of the procedure has been drafted [2].


The first step in that procedure is the nomination of one (or several) 
Chief Return Officer(s) (CRO) who will oversee the election process and 
who should not be a member of the current PSC, nor aim at becoming a 
member of the new PSC.


Is anyone willing to play this role ? You can just respond directly here 
on the list to display your interest.


In a second step, we will be looking for candidates for the new PSC. For 
an overview of the (fairly low-noise) activity of the PSC, you can 
browse through the archives of its public mailing list [3]. You will see 
that it is not a job that requires a lot of work, but it is an essential 
job nevertheless. Also: no need to be a developer to be part of the PSC, 
users should also be represented.


On behalf of the current PSC,
Moritz

[1] https://trac.osgeo.org/grass/wiki/PSC 



[2] https://trac.osgeo.org/grass/wiki/PSC/Election2020

[3] https://lists.osgeo.org/pipermail/grass-psc/
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user


Re: [GRASS-user] unstable results with r.param.scale ?

2020-12-10 Thread Maris Nartiss
Thank you Vincent & Vincent.
I managed to reproduce an issue with curvature tool – output result
differs significantly by each run.

You can track progress in GitHub issue tracker:
https://github.com/OSGeo/grass/issues/1168

In the mean time just disable OpenMP before running r.param.scale:
export OMP_NUM_THREADS=1

Māris.
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user