Re: [GRASS-user] Installation Issues on CentOS8

2020-12-16 Thread Markus Neteler
On Wed, Dec 16, 2020 at 6:05 PM mdwxman  wrote:
>
> Thank you Markus.  I’m glad I stuck with GRASS long enough to find a 
> solution.  I’m very fortunate to discover this user group, too.  As I looked 
> through the archive for the last two years I found lots of interesting and 
> helpful messages.

Great, and yes, the GRASS GIS mailing lists a very useful resource
(btw: started in 1991!).

How can we advertise them better?

> One additional and brief question: in attempting to debug the script I’m 
> curious regarding any software suggestions you might have for that task.  Of 
> course, experience & knowledge play a crucial role but any debugging software 
> might be helpful.  Any suggestions?

You can find a collection of debugging suggestions here:
https://grasswiki.osgeo.org/wiki/GRASS_Debugging

Here your other question:

On Wed, Dec 16, 2020 at 6:10 PM mdwxman  wrote:
>
> I noticed the issues with both the GDAL and PROJ packages.  I’ve noticed that 
> it can be difficult and sometimes impossible to find necessary packages on 
> several Fedora repos.

I suppose you refer to the Centos repos? That I also found annoying.
So much that I reformatted our server :p, switching to a different
distro.

However, the Fedora (not the same thing!) geo-related repos are
sufficiently well maintained.

> It makes things difficult and frustrating to install packages when even Conda 
> can’t find necessary libraries.

Yes. Feel free to contact me personally if you still lack packages on
Centos, maybe I have an idea.

Cheers
Markus

-- 
Markus Neteler, PhD
https://www.mundialis.de - free data with free software
https://grass.osgeo.org
https://courses.neteler.org/blog
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user


Re: [GRASS-user] How to find elevation drop for all cells in a basin

2020-12-16 Thread Ken Mankoff

I agree this would work. Given that I have 65036 basins, I was trying to avoid 
a loop. But if it's fast, who cares... I will try this method.

Thanks,

  -k.

On 2020-12-16 at 08:29 -08, Thomas Adams  wrote...
> Hi Ken!
>
> So, presumably, you know the locations of all the basin outlets
> (lat-long, e.g.). Using *v.what.rast*, query the elevation map to get
> the elevation at the basin outlet (locations) that the vector points
> identify. This associates the basin outlet elevation with its
> location. Assuming you have a single elevation map, you'll need to
> mask the elevation map to use the method I suggested. You can get the
> basin boundary -- if these are not already identified -- to create a
> mask using *r.water.outlet*. For each basin, set the MASK and do the
> r.mapcalc calculation I proposed, because you know the outlet
> elevation and the elevation at all cells within the MASKed basin area.
> r.mapcalc will create a new map 'diff' comprised of the elevation
> differences between the elevation at the basin outlet and all other
> cells in the basin. The elevation difference at the basin outlet will
> be ZERO.
>
> The whole process is easily scriptable. I have done this kind of thing
> a fair amount, FWIW...
>
> Later, after all the diff maps have been created, you could (if you
> wanted/needed to) patch them together or do statistics on them, etc. I
> hope all this makes sense...
>
> Best, Tom
>
> On Tue, Dec 15, 2020 at 3:52 PM Ken Mankoff  wrote:
>
>>
>> On 2020-12-15 at 12:28 -08, Thomas Adams  wrote...
>> > So, if I understand, that seems pretty simple and could be done
>> > with r.mapcalc:
>> >
>> > diff = elev - outlet_elev
>> >
>> > where elev is a raster map of elevations and outlet_elev is the
>> > elevation at the basin outlet. Using a basin mask the calculation
>> > could be confined to any basin of interest. But, I am probably
>> > missing something, I think…
>>
>> One of us is missing something, but I'm happy to assume it is me :).
>>
>> If outlet_elev is only defined at the outlets, diff is only defined
>> at the outlets. I want it defined for every inland cell in every
>> basin. I have 1,000s of basins.
>>
>> How do I define outlet_elev everywhere? I can do it now using
>> r.stream.distance but prior to Anna suggesting that, I didn't know
>> how to do it. Is there some trick like for each basin I set the
>> category to the elevation of the outlet, and then use mapcalc @math
>> function to create the outlet_elev raster?
>>
>>   -k.
>>

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


Re: [GRASS-user] Installation Issues on CentOS8

2020-12-16 Thread mdwxman via grass-user
I noticed the issues with both the GDAL and PROJ packages. I’ve noticed that it 
can be difficult and sometimes impossible to find necessary packages on several 
Fedora repos. It makes things difficult and frustrating to install packages 
when even Conda can’t find necessary libraries.

Michael Allen
Industrial Weather
763-777-1263

On Wed, Dec 16, 2020 at 8:27 AM, Markus Neteler  wrote:

> Michael,
>
> On Wed, Dec 16, 2020 at 4:36 AM mdwxman via grass-user
>  wrote:
>>
>> I don't often compile software on CentOS but even this one has me confused. 
>> I'm attempting to install some version of GRASS 7.8 on a CentOS 8 box and 
>> I've been attempting to do so, on off for the last 6 months.
>
> I did the same and it was a bumpy ride. Reason: a lot of packages were
> missing. I even had to become package maintainer in Fedora to push
> PROJ and GDAL packages...
>
>> There have been several different errors and I've attempted to use conda, 
>> conda with a local environment using Python 3.6., yum, and DNF. There are 
>> two types of errors: one is the failure to find the gui (g.gui).
>
> The GUI issue was there till the end of November. Reason: wxpython4
> package missing, see here:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1765573
>
> It has finally been provided.
>
>> The other involves a complete stop.
>>
>> This time I've used the grass-7.8.0.tar.gz files from the GRASS geo site.
>
> Please use at least 7.8.4, soon 7.8.5 for relevant bugfixes:
>
> https://trac.osgeo.org/grass/wiki/Release/7.8.5-News
>
>> The lastest attempt results in a stop in the ./configure line at:
>>
>> include/Make/Vars.make:1: included/Make/Platform.make: No such file or 
>> directory
>>
>> Since it stopped I attempted to use:
>>
>> make: *** No rule to make target 'include/Make/'. Stop.
>>
>> I've installed all required libraries and other applications (I think).
>
> Please see here:
>
> https://grasswiki.osgeo.org/wiki/Compile_and_Install#CentOS
> --> Centos8
>
>> I am a newbie with compilers but does anyone have some help for this.
>>
>> The machine is a Centos 8 machine with 7 Tb disk storage and running a 
>> 16-core Ryzen CPU at 4125 MHz.
>
> THat should be perfectly fine.
>
>> Thanks. I hope someone can help.
>
> Hope the Wiki instructions help - if not, let us know.
>
> Markus
>
> --
> Markus Neteler, PhD
> https://www.mundialis.de - free data with free software
> https://grass.osgeo.org
> https://courses.neteler.org/blog___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user


Re: [GRASS-user] Installation Issues on CentOS8

2020-12-16 Thread mdwxman via grass-user
Thank you Markus. I’m glad I stuck with GRASS long enough to find a solution. 
I’m very fortunate to discover this user group, too. As I looked through the 
archive for the last two years I found lots of interesting and helpful messages.

One additional and brief question: in attempting to debug the script I’m 
curious regarding any software suggestions you might have for that task. Of 
course, experience & knowledge play a crucial role but any debugging software 
might be helpful. Any suggestions?

Thanks again. Your answers uniformly provide the reasons for the errors. Many 
thanks.

Michael Allen
Industrial Weather
763-777-1263

On Wed, Dec 16, 2020 at 8:27 AM, Markus Neteler  wrote:

> Michael,
>
> On Wed, Dec 16, 2020 at 4:36 AM mdwxman via grass-user
>  wrote:
>>
>> I don't often compile software on CentOS but even this one has me confused. 
>> I'm attempting to install some version of GRASS 7.8 on a CentOS 8 box and 
>> I've been attempting to do so, on off for the last 6 months.
>
> I did the same and it was a bumpy ride. Reason: a lot of packages were
> missing. I even had to become package maintainer in Fedora to push
> PROJ and GDAL packages...
>
>> There have been several different errors and I've attempted to use conda, 
>> conda with a local environment using Python 3.6., yum, and DNF. There are 
>> two types of errors: one is the failure to find the gui (g.gui).
>
> The GUI issue was there till the end of November. Reason: wxpython4
> package missing, see here:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1765573
>
> It has finally been provided.
>
>> The other involves a complete stop.
>>
>> This time I've used the grass-7.8.0.tar.gz files from the GRASS geo site.
>
> Please use at least 7.8.4, soon 7.8.5 for relevant bugfixes:
>
> https://trac.osgeo.org/grass/wiki/Release/7.8.5-News
>
>> The lastest attempt results in a stop in the ./configure line at:
>>
>> include/Make/Vars.make:1: included/Make/Platform.make: No such file or 
>> directory
>>
>> Since it stopped I attempted to use:
>>
>> make: *** No rule to make target 'include/Make/'. Stop.
>>
>> I've installed all required libraries and other applications (I think).
>
> Please see here:
>
> https://grasswiki.osgeo.org/wiki/Compile_and_Install#CentOS
> --> Centos8
>
>> I am a newbie with compilers but does anyone have some help for this.
>>
>> The machine is a Centos 8 machine with 7 Tb disk storage and running a 
>> 16-core Ryzen CPU at 4125 MHz.
>
> THat should be perfectly fine.
>
>> Thanks. I hope someone can help.
>
> Hope the Wiki instructions help - if not, let us know.
>
> Markus
>
> --
> Markus Neteler, PhD
> https://www.mundialis.de - free data with free software
> https://grass.osgeo.org
> https://courses.neteler.org/blog___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user


Re: [GRASS-user] How to find elevation drop for all cells in a basin

2020-12-16 Thread Thomas Adams
Hi Ken!

So, presumably, you know the locations of all the basin outlets (lat-long,
e.g.). Using  *v.what.rast*, query the elevation map to get the elevation
at the basin outlet (locations) that the vector points identify. This
associates the basin outlet elevation with its location. Assuming you have
a single elevation map, you'll need to mask the elevation map to use the
method I suggested. You can get the basin boundary -- if these are not
already identified -- to create a mask using *r.water.outlet*. For each
basin, set the MASK and do the r.mapcalc calculation I proposed, because
you know the outlet elevation and the elevation at all cells within the
MASKed basin area. r.mapcalc will create a new map 'diff' comprised of the
elevation differences between the elevation at the basin outlet and all
other cells in the basin. The elevation difference at the basin outlet will
be ZERO.

The whole process is easily scriptable. I have done this kind of thing a
fair amount, FWIW...

Later, after all the diff maps have been created, you could (if you
wanted/needed to) patch them together or do statistics on them, etc. I hope
all this makes sense...

Best,
Tom

On Tue, Dec 15, 2020 at 3:52 PM Ken Mankoff  wrote:

>
> On 2020-12-15 at 12:28 -08, Thomas Adams  wrote...
> > So, if I understand, that seems pretty simple and could be done with
> > r.mapcalc:
> >
> > diff = elev - outlet_elev
> >
> > where elev is a raster map of elevations and outlet_elev is the elevation
> > at the basin outlet. Using a basin mask the calculation could be confined
> > to any basin of interest. But, I am probably missing something, I think…
>
> One of us is missing something, but I'm happy to assume it is me :).
>
> If outlet_elev is only defined at the outlets, diff is only defined at the
> outlets. I want it defined for every inland cell in every basin. I have
> 1,000s of basins.
>
> How do I define outlet_elev everywhere? I can do it now using
> r.stream.distance but prior to Anna suggesting that, I didn't know how to
> do it. Is there some trick like for each basin I set the category to the
> elevation of the outlet, and then use mapcalc @math function to create the
> outlet_elev raster?
>
>   -k.
>


-- 
Thomas E Adams, III
1724 Sage Lane
Blacksburg, VA 24060
tea...@gmail.com (personal)
t...@terrapredictions.org (work)

1 (513) 739-9512 (cell)
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user


Re: [GRASS-user] Installation Issues on CentOS8

2020-12-16 Thread Markus Neteler
Michael,

On Wed, Dec 16, 2020 at 4:36 AM mdwxman via grass-user
 wrote:
>
> I don't often compile software on CentOS but even this one has me confused. 
> I'm attempting to install some version of GRASS 7.8 on a CentOS 8 box and 
> I've been attempting to do so, on off for the last 6 months.

I did the same and it was a bumpy ride. Reason: a lot of packages were
missing. I even had to become package maintainer in Fedora to push
PROJ and GDAL packages...

> There have been several different errors and I've attempted to use conda, 
> conda with a local environment using Python 3.6., yum, and DNF. There are two 
> types of errors: one is the failure to find the gui (g.gui).

The GUI issue was there till the end of November. Reason: wxpython4
package missing, see here:

https://bugzilla.redhat.com/show_bug.cgi?id=1765573

It has finally been provided.

> The other involves a complete stop.
>
> This time I've used the grass-7.8.0.tar.gz files from the GRASS geo site.

Please use at least 7.8.4, soon 7.8.5 for relevant bugfixes:

https://trac.osgeo.org/grass/wiki/Release/7.8.5-News

> The lastest attempt results in a stop in the ./configure line at:
>
> include/Make/Vars.make:1: included/Make/Platform.make: No such file or 
> directory
>
> Since it stopped I attempted to use:
>
> make: *** No rule to make target 'include/Make/'. Stop.
>
> I've installed all required libraries and other applications (I think).

Please see here:

https://grasswiki.osgeo.org/wiki/Compile_and_Install#CentOS
--> Centos8

> I am a newbie with compilers but does anyone have some help for this.
>
> The machine is a Centos 8 machine with 7 Tb disk storage and running a 
> 16-core Ryzen CPU at 4125 MHz.

THat should be perfectly fine.

> Thanks. I hope someone can help.

Hope the Wiki instructions help - if not, let us know.

Markus

-- 
Markus Neteler, PhD
https://www.mundialis.de - free data with free software
https://grass.osgeo.org
https://courses.neteler.org/blog
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user