Re: [GRASS-dev] [GRASS GIS] #3815: compression: libzstd should be a default config and a requirement if ZSTD is default compression method

2019-04-19 Thread GRASS GIS 
#3815: compression: libzstd should be a default config and a requirement if ZSTD
is default compression method
--+---
  Reporter:  mlennert |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.6.2
 Component:  Raster   |Version:  svn-trunk
Resolution:   |   Keywords:  compression zstd zlib
   CPU:  Unspecified  |   Platform:  Unspecified
--+---

Comment (by mmetz):

 Replying to [comment:5 neteler]:
 > Replying to [comment:3 mmetz]:
 > > Replying to [comment:2 mlennert]:
 > > > +1 for backporting.
 > >
 > > Done in relbr76 r74398
 >
 > Just FYI:
 > This broke the manual-building cronjobs on the grass.osgeo.org server
 but I fixed it by now actively disabling zstd in the configure step
 (Debian Jessie doesn't have zstd yet and #3486 = compile in a docker
 container is still open).

 A good reason to not make zstd a compulsory requirement. Debian Jessie has
 long-term support until 30 June 2020, and GRASS 7.x should IMHO run on
 this system (with appropriate configure options).

-- 
Ticket URL: 
GRASS GIS 

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

[GRASS-dev] [GRASS GIS] #3822: Tests for r.basins.fill are broken

2019-04-19 Thread GRASS GIS 
#3822: Tests for r.basins.fill are broken
-+-
 Reporter:  pmav99   |  Owner:  grass-dev@…
 Type:  defect   | Status:  new
 Priority:  normal   |  Milestone:
Component:  Tests|Version:  svn-trunk
 Keywords:   |CPU:  Unspecified
 Platform:  Unspecified  |
-+-
 These tests are broken both for python 2 and python 3:
 - {{{raster/r.basins.fill/testsuite/testrbf.py}}}
 -
 
http://fatra.cnr.ncsu.edu/grassgistests/reports_for_date-2019-03-26-07-00/report_for_nc_spm_full_v2alpha_nc/raster/r.basins.fill/testrbf/index.html

 Moreover, the testsuite [https://github.com/GRASS-GIS/grass-
 
ci/blob/8161cae6d4df311d6560e305644673834c8f7f01/raster/r.basins.fill/testsuite/testrbf.py#L24-L25
 overwrites the "elevation" and "geology"] maps thus ruining the test
 dataset (at least on python 3):

 before running the tests:
 {{{
 ./exec_grass.sh r.univar elevation
 Starting GRASS GIS...
 Cleaning up temporary files...
 Executing  ...
  100%
 total null and non-null cells: 29535
 total null cells: 0

 Of the non-null cells:
 --
 n: 29535
 minimum: 89.6269
 maximum: 134.301
 range: 44.6739
 mean: 116.855
 mean of absolute values: 116.855
 standard deviation: 9.32828
 variance: 87.0169
 variation coefficient: 7.98278 %
 sum: 3451315.7405014
 Execution of  finished.
 Cleaning up default sqlite database ...
 Cleaning up temporary files...
 }}}
 after:
 {{{
 ./exec_grass.sh r.univar elevation
 Starting GRASS GIS...
 Cleaning up temporary files...
 Executing  ...
  100%
 total null and non-null cells: 29535
 total null cells: 29535

 Of the non-null cells:
 --
 n: 0
 minimum: -nan
 maximum: -nan
 range: -nan
 mean: -nan
 mean of absolute values: -nan
 standard deviation: -nan
 variance: -nan
 variation coefficient: -nan %
 sum: -nan
 Execution of  finished.
 Cleaning up default sqlite database ...
 Cleaning up temporary files...
 }}}

 Until someone finds the time to fix them, please add the following
 decorator on the Test class:
 {{{
 import unittest

 @unittest.skip("See #3822")
 class TestRasterbasin(TestCase):
 # ...
 }}}

-- 
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] #3821: Python3 + gunnitest.test_checkers

2019-04-19 Thread GRASS GIS 
#3821: Python3 + gunnitest.test_checkers
--+-
  Reporter:  pmav99   |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:
 Component:  Python   |Version:  svn-trunk
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by pmav99):

 * Attachment "test_checkers.patch" added.


-- 
Ticket URL: 
GRASS GIS 

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

[GRASS-dev] [GRASS GIS] #3821: Python3 + gunnitest.test_checkers

2019-04-19 Thread GRASS GIS 
#3821: Python3 + gunnitest.test_checkers
-+-
 Reporter:  pmav99   |  Owner:  grass-dev@…
 Type:  defect   | Status:  new
 Priority:  normal   |  Milestone:
Component:  Python   |Version:  svn-trunk
 Keywords:   |CPU:  Unspecified
 Platform:  Unspecified  |
-+-
 {{{lib/python/gunittest}}} needs the attached patch for python 3

-- 
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] #3820: Error i.pansharpen in grass76 relbranch

2019-04-19 Thread GRASS GIS 
#3820: Error i.pansharpen in grass76 relbranch
--+-
  Reporter:  veroandreo   |  Owner:  grass-dev@…
  Type:  defect   | Status:  closed
  Priority:  normal   |  Milestone:  7.6.2
 Component:  Imagery  |Version:  svn-releasebranch76
Resolution:  fixed|   Keywords:  i.pansharpen
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by cmbarton):

 Replying to [comment:1 veroandreo]:
 > It does work in trunk with no reported errors. However, if I run it in
 trunk compiled with python 3 in a virtualenv, I get:
 >
 > {{{
 > i.pansharpen red=lsat7_2002_30@PERMANENT   green=lsat7_2002_20
 blue=lsat7_2002_10 pan=lsat7_2002_80 method=ihs   output=lsat7_2002_ihs
 > Using 8bit image channels
 > Performing pan sharpening with hi res pan image: 14.25
 > Transforming to IHS color space...
 >  100%
 > Histogram matching...
 >  100%
 > Traceback (most recent call last):
 >   File "/home/veroandreo/software/grass7_trunk/dist.x86_64-pc-linux-
 gnu/scripts/i.pansharpen", line 632, in 
 > main()
 >   File "/home/veroandreo/software/grass7_trunk/dist.x86_64-pc-linux-
 gnu/scripts/i.pansharpen", line 259, in main
 > ihs(pan, ms1, ms2, ms3, out, pid, sproc)
 >   File "/home/veroandreo/software/grass7_trunk/dist.x86_64-pc-linux-
 gnu/scripts/i.pansharpen", line 380, in ihs
 > panmatch = matchhist(pan, target, outname)
 >   File "/home/veroandreo/software/grass7_trunk/dist.x86_64-pc-linux-
 gnu/scripts/i.pansharpen", line 552, in matchhist
 > stats = stats_out.communicate()[0].split('\n')[:-1]
 > TypeError: a bytes-like object is required, not 'str'
 > }}}

   So far, it is not designed to work in Python 3. I have not yet upgraded
 my computers so I can't yet test. A coming step will be to develop a new
 workflow to compile GRASS in Python 3.

-- 
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-user] Nice opportunity to show off GRASS functionality and topological vector format ?

2019-04-19 Thread Nikos Alexandris 

* Nikos Alexandris  [2019-04-19 13:46:18 +0200]:


* Markus Metz  [2019-04-18 18:38:28 +0200]:


On Tue, Apr 16, 2019 at 11:07 AM Moritz Lennert <
mlenn...@club.worldonline.be> wrote:


Hi,

If anyone has some time and wants to show off some GRASS GIS power:

https://www.ecmwf.int/en/learning/workshops/ecmwf-summer-weather-code-2019

"The Summer of Weather Code(ESoWC) programme by the European Centre for
Medium-Range Weather Forecasts (ECMWF) is a collabrative online
programme to promote the development of weather-related open-source
software."

More specificially:

https://github.com/esowc/challenges_2019

And even more, I think this challenge is a fairly low hanging fruit
using GRASS GIS tools:

https://github.com/esowc/challenges_2019/issues/3


I agree, this reads like a low-hanging fruit. I could submit an abstract
until Sunday 21 April with a fairly detailed workflow, but I will most
probably not have the time to write such a tool: apparently they would like
to have a custom QGIS plugin.


Panos literally implemented Nyal Dawson's excellent recommendation(s)
[0, 1, 2] and exposing a GRASS GIS module/add-on is easy. An example is
the QGIS plugin [3] for the `r.estimap.recreation` plugin [4].

[0] https://lists.osgeo.org/pipermail/qgis-developer/2019-February/056155.html
[1] https://lists.osgeo.org/pipermail/qgis-developer/2019-February/056285.html
[2] https://github.com/qgis/QGIS/pull/9202
[3] https://gitlab.com/natcapes/natcapes_qgis
[4] https://gitlab.com/natcapes/r.estimap.recreation

This makes the process as easy as never before, as far as I understand.
In my humble view, this should be further adopted and advertised.

On/Off-topic (Cc-ing also the qgis-developer mailing list):

I left from the `r.estimap.recreation` project leaving behind one
remaining issue-to-solve: https://issues.qgis.org/issues/21322.

This issue concerns only the interface and does not affect the
core work of exposing a GRASS GIS add-on inside QGIS' Processing
Framework. Nevertheless, in my humble view, this issue is important to
the GRASS GIS community and having an up-to-date documentation will save
our time from figuring out how the interface related api works.


And here an entry in gis.se:
https://gis.stackexchange.com/a/319333/5256.

Nikos



Markus M



APPLICATION DEADLINE: SUNDAY, 21 APRIL 23:59 GMT


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



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



--
Nikos Alexandris | Remote Sensing & Geomatics
GPG Key Fingerprint 6F9D4506F3CA28380974D31A9053534B693C4FB3 
___

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


--
Nikos Alexandris | Remote Sensing & Geomatics
GPG Key Fingerprint 6F9D4506F3CA28380974D31A9053534B693C4FB3 
___

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

Re: [GRASS-dev] [GRASS-user] Nice opportunity to show off GRASS functionality and topological vector format ?

2019-04-19 Thread Nikos Alexandris 

* Markus Metz  [2019-04-18 18:38:28 +0200]:


On Tue, Apr 16, 2019 at 11:07 AM Moritz Lennert <
mlenn...@club.worldonline.be> wrote:


Hi,

If anyone has some time and wants to show off some GRASS GIS power:

https://www.ecmwf.int/en/learning/workshops/ecmwf-summer-weather-code-2019

"The Summer of Weather Code(ESoWC) programme by the European Centre for
Medium-Range Weather Forecasts (ECMWF) is a collabrative online
programme to promote the development of weather-related open-source
software."

More specificially:

https://github.com/esowc/challenges_2019

And even more, I think this challenge is a fairly low hanging fruit
using GRASS GIS tools:

https://github.com/esowc/challenges_2019/issues/3


I agree, this reads like a low-hanging fruit. I could submit an abstract
until Sunday 21 April with a fairly detailed workflow, but I will most
probably not have the time to write such a tool: apparently they would like
to have a custom QGIS plugin.


Panos literally implemented Nyal Dawson's excellent recommendation(s)
[0, 1, 2] and exposing a GRASS GIS module/add-on is easy. An example is
the QGIS plugin [3] for the `r.estimap.recreation` plugin [4].

[0] https://lists.osgeo.org/pipermail/qgis-developer/2019-February/056155.html
[1] https://lists.osgeo.org/pipermail/qgis-developer/2019-February/056285.html
[2] https://github.com/qgis/QGIS/pull/9202
[3] https://gitlab.com/natcapes/natcapes_qgis
[4] https://gitlab.com/natcapes/r.estimap.recreation

This makes the process as easy as never before, as far as I understand.
In my humble view, this should be further adopted and advertised.

On/Off-topic (Cc-ing also the qgis-developer mailing list):

I left from the `r.estimap.recreation` project leaving behind one
remaining issue-to-solve: https://issues.qgis.org/issues/21322.

This issue concerns only the interface and does not affect the
core work of exposing a GRASS GIS add-on inside QGIS' Processing
Framework. Nevertheless, in my humble view, this issue is important to
the GRASS GIS community and having an up-to-date documentation will save
our time from figuring out how the interface related api works.

Nikos



Markus M



APPLICATION DEADLINE: SUNDAY, 21 APRIL 23:59 GMT


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



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



--
Nikos Alexandris | Remote Sensing & Geomatics
GPG Key Fingerprint 6F9D4506F3CA28380974D31A9053534B693C4FB3 
___

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

Re: [GRASS-dev] [GRASS GIS] #3820: Error i.pansharpen in grass76 relbranch

2019-04-19 Thread GRASS GIS 
#3820: Error i.pansharpen in grass76 relbranch
--+-
  Reporter:  veroandreo   |  Owner:  grass-dev@…
  Type:  defect   | Status:  closed
  Priority:  normal   |  Milestone:  7.6.2
 Component:  Imagery  |Version:  svn-releasebranch76
Resolution:  fixed|   Keywords:  i.pansharpen
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by cmbarton):

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


Comment:

 Should be fixed now in r74403.

-- 
Ticket URL: 
GRASS GIS 

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