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