[GRASS-dev] GSOC 2018 Proposal

2018-03-22 Thread Sanjeet
Hi,

This is my GSOC proposal for the idea: 'Full support of Python 3 in
GRASS GIS'. Please suggest any improvements, or share any other
feedback.

https://docs.google.com/document/d/18kD6I7adTKmtXpGOKr4A8hf1pBcf0LNU7jiiRoi9wJ8

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

[GRASS-dev] Python Unit-test On "r.basins.fill"

2018-03-22 Thread Sunveer Singh
Hello all,

Luca, I am so sorry, for the very very big delay was having my finals, and
today I finally completed writing test on r.basins.fill.

All, I am Sunveer Singh, 15 years old from India, Google Code-in 2017
Winner with OSGeo, I completed 16 tasks for GRASS GIS, within Google
Code-in, and contributed *test for r.info , i.vi
, v.extract, v.univar, v.select, r.report, r.texture,
v.vect.stats, r.recode, r.in.ascii and r.to.vect.* And created a video on

*How to create a location: Link to Video.
*
Due to my finals, I was unable to contribute to GRASS, but know I will
start Contributing again.

I have attached my test written in python for r.basins.fill. If any
improvement is needed in the test, please let me know.

Thank You for Your Precious Time.


Thank You
Sunveer
https://sunveersingh.github.io/
"""
Name:   r.basins.fill
Purpose:Tests r.basins.fill and its flags/options.
	
Author: Sunveer Singh
Copyright:  (C) 2017 by Sunveer Singh and the GRASS Development Team
Licence:This program is free software under the GNU General Public
	License (>=v2). Read the file COPYING that comes with GRASS
	for details.
"""
from grass.gunittest.case import TestCase

extract="""2  summit
3  ridge
4  shoulder
"""


class TestRasterbasin(TestCase):
cnetwork='elevation'
tnetwork='facility'
output='basinsoutput'
input="basin_50K"

@classmethod
def setUpClass(cls):
seed = 500
cls.use_temp_region()
cls.runModule('g.region', raster=cls.tnetwork, flags='p')
cls.runModule('r.watershed', elevation='elevation', stream=cls.cnetwork, threshold='5', overwrite=True)
cls.runModule('r.geomorphon', elevation=cls.cnetwork, forms=cls.tnetwork, overwrite=True)
cls.runModule('r.mapcalc', seed=seed, expression='rand_cell = rand(1, 200)', overwrite=True)
cls.runModule('r.thin', input=cls.input, output=cls.output)


@classmethod
def tearDownClass(cls):
cls.del_temp_region()

def tearDown(cls):
cls.runModule('g.remove', flags='f', type='raster', name=cls.output)

def test_no1(self):
lakes='lakes'
self.assertModule('r.basins.fill', cnetwork=self.cnetwork, tnetwork=self.tnetwork, output=self.output, number='1', overwrite=True)
self.assertRasterMinMax(map=lakes, refmin=34300, refmax=43600,
	msg="lakes in degrees must be between 34300 and 43600")

def test_no2(self):
soilsID='soilsID'
self.assertModule('r.basins.fill', cnetwork=self.cnetwork, tnetwork=self.tnetwork, output=self.output, number='3')
self.assertRasterMinMax(map=soilsID, refmin=18683, refmax=46555,
	msg="soilsID in degrees must be between 18683 and 46555")

def test_no3(self):
roadsmajor='roadsmajor'
self.assertModule('r.basins.fill', cnetwork=self.cnetwork, tnetwork=self.tnetwork, output=self.output, number='4')
self.assertRasterMinMax(map=roadsmajor, refmin=1, refmax=1,
	msg="roadsmajor in degrees must be between 1 and 1")

def test_no4(self):
slope='slope'
self.assertModule('r.basins.fill', cnetwork=self.cnetwork, tnetwork=self.tnetwork, output=self.output, number='5')
self.assertRasterMinMax(map=slope, refmin=0, refmax=38.68939,
	msg="slope in degrees must be between 0 and 38.68939")

if __name__ == '__main__':
from grass.gunittest.main import test
test()
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3211: Pygrass crash when trying to drop DB table

2018-03-22 Thread GRASS GIS
#3211: Pygrass crash when trying to drop DB table
--+-
  Reporter:  lrntct   |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.2.3
 Component:  PyGRASS  |Version:  svn-releasebranch72
Resolution:   |   Keywords:
   CPU:  x86-64   |   Platform:  Linux
--+-

Comment (by lucadelu):

 I tested the example and it is quite strange because inside the pyGRASS
 code is returning error, but if I run the problematic command just after
 there is no error...


 {{{
 ## -- End pasted text --
 WARNING: Vector map  already exists and will be
  overwritten
 > /home/lucadelu/compilati/grass_trunk/dist.x86_64-pc-linux-
 gnu/etc/python/grass/script/vector.py(49)vector_db()
 -> s = read_command('v.db.connect', quiet=True, flags='g', map=map,
 sep=';',
 (Pdb) c
 WARNING: Coor file of vector map  is larger than it
  should be (18 bytes excess)
 Building topology for vector map ...
 Registering primitives...
 ---
 CalledModuleError Traceback (most recent call
 last)
  in ()
  12   table=vect_map.name + 'junc', key='cat')
  13 t_junc = l_junc.table()
 ---> 14 t_junc.create(cols_j, overwrite=True)

 /home/lucadelu/compilati/grass_trunk/dist.x86_64-pc-linux-
 gnu/etc/python/grass/pygrass/vector/table.pyc in create(self, cols, name,
 overwrite, cursor)
1162 except OperationalError:  # OperationalError
1163 if overwrite:
 -> 1164 self.drop(force=True)
1165 cur.execute(sql.CREATE_TAB.format(tname=newname,
1166   coldef=coldef))

 /home/lucadelu/compilati/grass_trunk/dist.x86_64-pc-linux-
 gnu/etc/python/grass/pygrass/vector/table.pyc in drop(self, cursor, force)
1029 cur = cursor if cursor else self.conn.cursor()
1030 if self.exist(cursor=cur):
 -> 1031 used = db_table_in_vector(self.name)
1032 if used is not None and len(used) > 0 and not force:
1033 print(_("Deleting table <%s> which is attached"

 /home/lucadelu/compilati/grass_trunk/dist.x86_64-pc-linux-
 gnu/etc/python/grass/script/db.pyc in db_table_in_vector(table, mapset)
 192 vects = list_strings('vect', mapset=mapset)
 193 for vect in vects:
 --> 194 for f in vector_db(vect, stderr=nuldev).values():
 195 if not f:
 196 continue

 /home/lucadelu/compilati/grass_trunk/dist.x86_64-pc-linux-
 gnu/etc/python/grass/script/vector.pyc in vector_db(map, **args)
  47 """
  48 import pdb; pdb.set_trace()
 ---> 49 s = read_command('v.db.connect', quiet=True, flags='g',
 map=map, sep=';',
  50  **args)
  51 pdb.set_trace()

 /home/lucadelu/compilati/grass_trunk/dist.x86_64-pc-linux-
 gnu/etc/python/grass/script/core.pyc in read_command(*args, **kwargs)
 474 if _capture_stderr and returncode:
 475 sys.stderr.write(stderr)
 --> 476 return handle_errors(returncode, stdout, args, kwargs)
 477
 478

 /home/lucadelu/compilati/grass_trunk/dist.x86_64-pc-linux-
 gnu/etc/python/grass/script/core.pyc in handle_errors(returncode, result,
 args, kwargs)
 330 args = make_command(*args, **kwargs)
 331 raise CalledModuleError(module=None, code=repr(args),
 --> 332 returncode=returncode)
 333
 334 def start_command(prog, flags=b"", overwrite=False, quiet=False,

 CalledModuleError: Module run None ['v.db.connect', '--q', '-g',
 'map=drop_table_test@user1', 'sep=;'] ended with error
 Process ended with non-zero return code 1. See errors in the (error)
 output.

 In [2]: from grass.script import read_command

 In [3]: s = read_command('v.db.connect', quiet=True, flags='g',
 map='drop_table_test@
...: user1', sep=';')
 WARNING: Coor file of vector map  is larger than it
  should be (18 bytes excess)

 In [4]: s
 Out[4]:
 
'1/drop_table_test;drop_table_test;cat;/home/lucadelu/grassdata/nc_spm_08_grass7/user1/sqlite/sqlite.db;sqlite\n'
 }}}

-- 
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] #774: i.rgb.his, i.his.rgb, d.his support for >8 bit

2018-03-22 Thread GRASS GIS
#774: i.rgb.his, i.his.rgb, d.his support for >8 bit
--+-
  Reporter:  hamish   |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:  7.4.1
 Component:  Raster   |Version:  svn-trunk
Resolution:   |   Keywords:  i.rgb.his, i.his.rgb, d.his
   CPU:  All  |   Platform:  All
--+-

Comment (by Nikos Alexandris):

 A `gunittest` is available at:
 
https://github.com/NikosAlexandris/test_color_space_conversions/blob/master/test_color_space_roundtrips.py

 The tests compare the input R, G and B images (Landsat imagery from the
 `nc_spm_08_grass7` test data set)  from 6- up to 16-bit (by rescaling the
 original inputs) with the output R, G and B after a roundtrip from RGB to
 HIS and back to RGB color spaces.

 They confirm, as far as I understand, that the suggested modules

  * https://trac.osgeo.org/grass/browser/sandbox/alexandris/i.rgb.his/
  * https://trac.osgeo.org/grass/browser/sandbox/alexandris/i.his.rgb/

 work with precision levels 0.1 and 0.01. Setting the precision to 0.001,
 will cause the the test fail for `bits=` >= 15.

 HIS values are also tested for being inside the expected ranges.

 A review of the script would be much appreciated in order to confirm its
 functionality.

 Some points:

 * The script tests both the `i.rgb.his` and `i.his.rgb` modules. So, where
 should it be placed?

 * `r.rescale` smartly picks up the max value among any two values given in
 the `to=` parameter. This is a bit confusing and the tests will fail for
 bitnesses < 6. I think it is meaningful to test for bitnesses all the way
 down to 2-bit images.

 * Currently, the test counts 4 tests. Maybe it would make more sense to
 count as many as the different precision levels requested, and in addition
 as many as the different bitnesses tested.

 * Would be it better to create dynamically synthetic images instead of
 using "external" imagery?

 Can someone move the test to trunk as suggested by Vaclav?

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [SoC] Just in time: Seeking mentors for development of a Deep Learning model applied to Remote Sensing Data

2018-03-22 Thread Margherita Di Leo
Evandro,

On Thu, Mar 22, 2018 at 6:59 PM, Evandro Carrijo 
wrote:

> Hi Margherita,
>
> I really appreciate for your feedback! I'm not much familiar with GRASS
> GIS as I had only developed standalone codes in Python using directly
> libraries like GDAL and RIOS  and used QGIS for
> layers visualization. But, as I observed here
>  and here
> , Python scripts can
> easily be integrated within GRASS GIS and I could seamlessly adapt my
> programming skills to work with that. That way, I could compromise myself
> in integrating my already done codes (and new ones) into GRASS GIS
> software/libraries.
>

That's really good for you to familiarize with writing code in GRASS, as
that would give your idea more chances.

>
> Also, if allowed, I could edit the Ideas' wiki page to contemplate my own
> idea,
>

No, that is not necessary


> so that it could be visible to a broader audience. If I get a mentor in
> time, I will make a detailed proposal for the mentors/community be able to
> understand better the idea.
>

Actually it works the other way around, you're supposed to write and submit
your proposal at this stage, so that potential mentors can comment on it
and give you feedback, and decide whether it's feasible and if they want to
mentor it. Please, follow the guidelines I linked to you to submit a
proposal, and share it publicly also in GRASS mailing list for developers
to comment.

Good luck!

>
> Thank you very much,
>
> Evandro Carrijo Taquary
> Federal University of Goiás
>

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

Re: [GRASS-dev] [GRASS GIS] #3171: Python script fails on windows if parameter contains non-latin letters

2018-03-22 Thread GRASS GIS
#3171: Python script fails on windows if parameter contains non-latin letters
--+-
  Reporter:  marisn   |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.2.3
 Component:  Python   |Version:  svn-releasebranch72
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  MSWindows 8
--+-

Comment (by lucadelu):

 Could this ticket be closed?

-- 
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] #3246: r.in.srtm: patch to support SRTM water bodies import (SWBD)

2018-03-22 Thread GRASS GIS
#3246: r.in.srtm: patch to support SRTM water bodies import (SWBD)
--+-
  Reporter:  stjo |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:  7.4.1
 Component:  Python   |Version:  svn-releasebranch72
Resolution:   |   Keywords:  r.in.srtm
   CPU:  Unspecified  |   Platform:  All
--+-

Comment (by lucadelu):

 Replying to [comment:2 stjo]:
 > I'm really sorry for the wrong link.
 >
 > If you still want to test my changes, the correct link is:
 > https://e4ftl01.cr.usgs.gov/SRTM/SRTMSWBD.003/2000.02.11/

 Sorry I cannot access again to this link. It seems it requires special
 permission, I already authorized LP DAAC on my account.

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [SoC] Just in time: Seeking mentors for development of a Deep Learning model applied to Remote Sensing Data

2018-03-22 Thread Evandro Carrijo
Hi Margherita,

I really appreciate for your feedback! I'm not much familiar with GRASS GIS
as I had only developed standalone codes in Python using directly libraries
like GDAL and RIOS  and used QGIS for layers
visualization. But, as I observed here
 and here
, Python scripts can
easily be integrated within GRASS GIS and I could seamlessly adapt my
programming skills to work with that. That way, I could compromise myself
in integrating my already done codes (and new ones) into GRASS GIS
software/libraries.

Also, if allowed, I could edit the Ideas' wiki page to contemplate my own
idea, so that it could be visible to a broader audience. If I get a mentor
in time, I will make a detailed proposal for the mentors/community be able
to understand better the idea.

Thank you very much,

Evandro Carrijo Taquary
Federal University of Goiás

2018-03-22 14:08 GMT-03:00 Margherita Di Leo :

> Hi Evandro,
>
> thank you for your proposal, I put in cc also the GRASS GIS dev mailing
> list, as it might be a suitable project candidate if anyone is available
> for mentoring it. It is usually a bit more difficult to find mentors when
> the proposal comes from a student and it is not listed in our ideas page,
> however not impossible, and your idea sounds very interesting. Are you
> familiar with GRASS GIS?
> I'd like to point you out our recommendations for students at
> https://wiki.osgeo.org/index.php?title=Google_Summer_
> of_Code_Recommendations_for_Students , particularly our guidelines on how
> to submit a proposal.
>
> Thanks,
>
> On Thu, Mar 22, 2018 at 5:49 PM, Evandro Carrijo <
> evandro.taqu...@gmail.com> wrote:
>
>> Hello there!
>>
>> I'm a Computer Science Master's Degree student whose research if focused
>> on Deep Learning algorithms applied to Remote Sensing. Currently working at
>> the Laboratory of Image Processing and Geoprocessing
>>  settled at Federal University of Goiás -
>> Brazil. I'm also member of the High Performance Computing group of the same
>> university (more information here
>> ).
>>
>> Below I present an idea to explain how I can contribute to OSGeo
>> community and I'm seeking for mentors interested in assist my development.
>> Please, feel free to argue me any matter about the project idea.
>>
>> I would also appreciate a lot if you guys indicate a potential interested
>> mentor to my project idea or a OSGeo Project suitable to it.
>>
>> Hope there's some Interested ones out there!
>>
>> Idea
>>
>> The increasing number of sensors orbiting the earth is systematically
>> producing larger volumes of data, with better spatiotemporal resolutions.
>> To deal with that, better accurate machine learning approaches, such as
>> Deep Learning (DL), are needed to transform raw data into applicable
>> Information. Several DL architectures (e.g. CNN, semantic segmentation)
>> rely only at spatial dimension to perform, for example, land-cover/land-use
>> (LCLU) maps, disregarding the temporal dependencies between pixels
>> observations over the time. Also, high-res remote sensing data (e.g.
>> Planet, Sentinel) may provide more consistent time-series, that can be use
>> in the identification of important LCLU classes, like crop, pastureland and
>> grasslands.
>>
>> This potential can be explored using Recurrent Neural Networks (RNN), a
>> specific family of DL approaches which can take into account time
>> dimension. A promising project idea would be implement a RNN approach (e.g.
>> LSTM) to classify a Sentinel time-series, that will organize and preprocess
>> an input data set (e.g. labeled time-series), calibrate and evaluate a RNN
>> model, and finally classify an entire region (i.e. 2 or 3 scenes) to
>> produce a map for one or more LCLU class. It will be great evaluate the
>> accuracy and the spatial consistent of a map produced with a RNN approach.
>>
>> A simple example on classifying LCLU with two classes (pastureland and
>> non-pastureland):
>>
>> [image: itapirapua]
>> 
>> *Target region (input)*
>>
>> [image: itapirapua_ref]
>> 
>> *Generated LCLU map (output)*
>> Best,
>>
>> Evandro Carrijo Taquary
>> Federal University of Goiás
>>
>> ___
>> SoC mailing list
>> s...@lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/soc
>>
>
>
>
> --
> Margherita Di Leo
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #2790: Output of t.rast.list with method=comma and columns=name does not differ from output with columns=id

2018-03-22 Thread GRASS GIS
#2790: Output of t.rast.list with method=comma and columns=name does not differ
from output with columns=id
-+--
  Reporter:  veroandreo  |  Owner:  grass-dev@…
  Type:  defect  | Status:  closed
  Priority:  normal  |  Milestone:  7.4.1
 Component:  Temporal|Version:  svn-trunk
Resolution:  fixed   |   Keywords:  t.rast.list, t.vect.list
   CPU:  x86-64  |   Platform:  Linux
-+--
Changes (by lucadelu):

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


Comment:

 backported in r72502 and r72503

-- 
Ticket URL: 
GRASS GIS 

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

[GRASS-dev] GRASS GSoC 2018 proposal

2018-03-22 Thread Roberta Fagandini
Hi all!
I have already submitted a draft proposal (title: GRASS GIS module for
Sentinel-2 cloud and shadow detection) in response to the idea about cloud
masking published on the GRASS Google Summer of Code 2018 wiki page.
I'd like to share the propose with you [1].
Obviously, any hint/suggestion/feedback is welcome!

Roberta

[1] https://docs.google.com/document/d/1mQyouqbHGHugn5DjEDZI3hc1eU_
bT_b0qLJPPwkt_hk/edit?usp=sharing
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [SoC] Just in time: Seeking mentors for development of a Deep Learning model applied to Remote Sensing Data

2018-03-22 Thread Margherita Di Leo
Hi Evandro,

thank you for your proposal, I put in cc also the GRASS GIS dev mailing
list, as it might be a suitable project candidate if anyone is available
for mentoring it. It is usually a bit more difficult to find mentors when
the proposal comes from a student and it is not listed in our ideas page,
however not impossible, and your idea sounds very interesting. Are you
familiar with GRASS GIS?
I'd like to point you out our recommendations for students at
https://wiki.osgeo.org/index.php?title=Google_Summer_of_Code_Recommendations_for_Students
, particularly our guidelines on how to submit a proposal.

Thanks,

On Thu, Mar 22, 2018 at 5:49 PM, Evandro Carrijo 
wrote:

> Hello there!
>
> I'm a Computer Science Master's Degree student whose research if focused
> on Deep Learning algorithms applied to Remote Sensing. Currently working at
> the Laboratory of Image Processing and Geoprocessing
>  settled at Federal University of Goiás -
> Brazil. I'm also member of the High Performance Computing group of the same
> university (more information here
> ).
>
> Below I present an idea to explain how I can contribute to OSGeo
> community and I'm seeking for mentors interested in assist my development.
> Please, feel free to argue me any matter about the project idea.
>
> I would also appreciate a lot if you guys indicate a potential interested
> mentor to my project idea or a OSGeo Project suitable to it.
>
> Hope there's some Interested ones out there!
>
> Idea
>
> The increasing number of sensors orbiting the earth is systematically
> producing larger volumes of data, with better spatiotemporal resolutions.
> To deal with that, better accurate machine learning approaches, such as
> Deep Learning (DL), are needed to transform raw data into applicable
> Information. Several DL architectures (e.g. CNN, semantic segmentation)
> rely only at spatial dimension to perform, for example, land-cover/land-use
> (LCLU) maps, disregarding the temporal dependencies between pixels
> observations over the time. Also, high-res remote sensing data (e.g.
> Planet, Sentinel) may provide more consistent time-series, that can be use
> in the identification of important LCLU classes, like crop, pastureland and
> grasslands.
>
> This potential can be explored using Recurrent Neural Networks (RNN), a
> specific family of DL approaches which can take into account time
> dimension. A promising project idea would be implement a RNN approach (e.g.
> LSTM) to classify a Sentinel time-series, that will organize and preprocess
> an input data set (e.g. labeled time-series), calibrate and evaluate a RNN
> model, and finally classify an entire region (i.e. 2 or 3 scenes) to
> produce a map for one or more LCLU class. It will be great evaluate the
> accuracy and the spatial consistent of a map produced with a RNN approach.
>
> A simple example on classifying LCLU with two classes (pastureland and
> non-pastureland):
>
> [image: itapirapua]
> 
> *Target region (input)*
>
> [image: itapirapua_ref]
> 
> *Generated LCLU map (output)*
> Best,
>
> Evandro Carrijo Taquary
> Federal University of Goiás
>
> ___
> SoC mailing list
> s...@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/soc
>



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

Re: [GRASS-dev] [GRASS GIS] #3492: r.texture overwrites without --o flag and without any warning when map exists

2018-03-22 Thread GRASS GIS
#3492: r.texture overwrites without --o flag and without any warning when map
exists
--+-
  Reporter:  veroandreo   |  Owner:  grass-dev@…
  Type:  defect   | Status:  closed
  Priority:  normal   |  Milestone:  7.4.1
 Component:  Raster   |Version:  unspecified
Resolution:  fixed|   Keywords:  r.texture
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by mlennert):

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


Comment:

 Replying to [comment:3 mlennert]:
 > I committed a version with slightly modified wording to trunk in r72380.
 Candidate for backport to 7.4 ?

 Backported to 7.4 (r72500) and 7.2 (r72501).

 Closing the ticket.

-- 
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] #3223: r.info displays wrong timestamp after t.rast.series with a where clause

2018-03-22 Thread GRASS GIS
#3223: r.info displays wrong timestamp after t.rast.series with a where clause
--+-
  Reporter:  veroandreo   |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.4.1
 Component:  Default  |Version:  svn-trunk
Resolution:   |   Keywords:  r.info
   CPU:  Unspecified  |   Platform:  Linux
--+-

Comment (by veroandreo):

 Replying to [comment:2 huhabla]:
 > Fixed in grass trunk revision r72479. Please test.
 After testing, I backported to release branch 74 in r72493 and to release
 branch 72 in r72499 (this last one without test_t.sereis_bug_3223.sh)

 Thanks!

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] PROJ 5 support in trunk

2018-03-22 Thread Markus Metz
On Thu, Mar 22, 2018 at 7:16 AM, Markus Neteler  wrote:
>
> On Tue, Mar 20, 2018 at 8:04 PM, Markus Metz
>  wrote:
> > Hi all,
> >
> > I have added support for the new PROJ 5+ API in trunk, finished with
r72433.
>
> That's really great! First OSGeo project :-)
>
> It was a lot of work for you, thanks.

The work is not yet finished. The current implementation works but is ugly
and code in modules became less readable because of lots of ifdefs for
PROJ4 or PROJ5. I am now testing a new GRASS API as interface to PROJ4/5
that would allow to remove these ifdefs in modules. The old GRASS API as
well as the standard PROJ4 API will still be supported. The main difference
is that GRASS now uses for PROJ5 the new pipeline syntax which allows to
define more complex transformations. Forward/backward transformation will
also become easier by simply defining the direction. m.proj still needs to
be updated to support this new pipeline syntax with any number of steps as
input for proj_in.

>
> > This means, trunk is now using exclusively the new PROJ 5+ API if
available.
> >
> > This new PROJ 5 API is available e.g. in Debian testing.
> >
> > Please test!
> >
> > During testing, I discovered some dangerous naming conflicts in GRASS
and
> > PROJ4/PROJ5: internal functions start both in GRASS and PROJ with pj_
which
> > can lead to cryptic errors. Within GRASS, some but not all
> > projection-related functions start with GPJ_, this should be adopted for
> > those starting with pj_. Also the GRASS structure struct pj_info should
be
> > renamed to struct gpj_info.
>
> BTW: Also GDAL now comes with support for PROJ 5, see
> https://lists.osgeo.org/pipermail/gdal-dev/2018-March/048278.html

Nice!

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

Re: [GRASS-dev] [GRASS GIS] #3524: v.random restrict wrong categories assigned

2018-03-22 Thread GRASS GIS
#3524: v.random restrict wrong categories assigned
--+--
  Reporter:  martinl  |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.0.7
 Component:  Vector   |Version:  svn-trunk
Resolution:   |   Keywords:  v.random, restrict, cats
   CPU:  Unspecified  |   Platform:  Unspecified
--+--

Comment (by martinl):

 Fixed in all affected branches (trunk, g74, g72, g70).

-- 
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] #3524: v.random restrict wrong categories assigned

2018-03-22 Thread GRASS GIS
#3524: v.random restrict wrong categories assigned
--+--
  Reporter:  martinl  |  Owner:  grass-dev@…
  Type:  defect   | Status:  closed
  Priority:  normal   |  Milestone:  7.0.7
 Component:  Vector   |Version:  svn-trunk
Resolution:  fixed|   Keywords:  v.random, restrict, cats
   CPU:  Unspecified  |   Platform:  Unspecified
--+--
Changes (by martinl):

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


-- 
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] #3524: v.random restrict wrong categories assigned

2018-03-22 Thread GRASS GIS
#3524: v.random restrict wrong categories assigned
--+--
  Reporter:  martinl  |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.0.7
 Component:  Vector   |Version:  svn-trunk
Resolution:   |   Keywords:  v.random, restrict, cats
   CPU:  Unspecified  |   Platform:  Unspecified
--+--
Changes (by martinl):

 * milestone:  7.2.3 => 7.0.7


-- 
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] #3524: v.random restrict wrong categories assigned

2018-03-22 Thread GRASS GIS
#3524: v.random restrict wrong categories assigned
--+--
  Reporter:  martinl  |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.2.3
 Component:  Vector   |Version:  svn-trunk
Resolution:   |   Keywords:  v.random, restrict, cats
   CPU:  Unspecified  |   Platform:  Unspecified
--+--

Comment (by martinl):

 In [changeset:"72497" 72497]:
 {{{
 #!CommitTicketReference repository="" revision="72497"
 v.random restrict wrong categories assigned, see #3524 (g70: merge r72416
 + r72421 from trunk)
 }}}

-- 
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] #3223: r.info displays wrong timestamp after t.rast.series with a where clause

2018-03-22 Thread GRASS GIS
#3223: r.info displays wrong timestamp after t.rast.series with a where clause
--+-
  Reporter:  veroandreo   |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.4.1
 Component:  Default  |Version:  svn-trunk
Resolution:   |   Keywords:  r.info
   CPU:  Unspecified  |   Platform:  Linux
--+-

Comment (by neteler):

 Replying to [comment:2 huhabla]:
 > Fixed in grass trunk revision r72479. Please test.

 Quick question: should test_t.sereis_bug_3223.sh  be in trunk and be
 backported?

-- 
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] #3524: v.random restrict wrong categories assigned

2018-03-22 Thread GRASS GIS
#3524: v.random restrict wrong categories assigned
--+--
  Reporter:  martinl  |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.2.3
 Component:  Vector   |Version:  svn-trunk
Resolution:   |   Keywords:  v.random, restrict, cats
   CPU:  Unspecified  |   Platform:  Unspecified
--+--

Comment (by martinl):

 In [changeset:"72496" 72496]:
 {{{
 #!CommitTicketReference repository="" revision="72496"
 v.random restrict wrong categories assigned, see #3524 (merge r72416 +
 r72421 from trunk)
 }}}

-- 
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] #3524: v.random restrict wrong categories assigned

2018-03-22 Thread GRASS GIS
#3524: v.random restrict wrong categories assigned
--+--
  Reporter:  martinl  |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.2.3
 Component:  Vector   |Version:  svn-trunk
Resolution:   |   Keywords:  v.random, restrict, cats
   CPU:  Unspecified  |   Platform:  Unspecified
--+--

Comment (by martinl):

 In [changeset:"72495" 72495]:
 {{{
 #!CommitTicketReference repository="" revision="72495"
 v.random restrict wrong categories assigned, see #3524
 }}}

-- 
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] #3514: Read EPSG codes with PROJ v.5 fails

2018-03-22 Thread GRASS GIS
#3514: Read EPSG codes with PROJ v.5 fails
--+---
  Reporter:  nila |  Owner:  martinl
  Type:  defect   | Status:  closed
  Priority:  major|  Milestone:  7.4.1
 Component:  Startup  |Version:  unspecified
Resolution:  fixed|   Keywords:  PROJ_v.5 epsg startup
   CPU:  Unspecified  |   Platform:  All
--+---
Changes (by martinl):

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


Comment:

 In [changeset:"72494" 72494]:
 {{{
 #!CommitTicketReference repository="" revision="72494"
 Read EPSG codes with PROJ v.5 fails, fix #3514
 }}}

-- 
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] #3514: Read EPSG codes with PROJ v.5 fails

2018-03-22 Thread GRASS GIS
#3514: Read EPSG codes with PROJ v.5 fails
--+---
  Reporter:  nila |  Owner:  martinl
  Type:  defect   | Status:  assigned
  Priority:  major|  Milestone:  7.4.1
 Component:  Startup  |Version:  unspecified
Resolution:   |   Keywords:  PROJ_v.5 epsg startup
   CPU:  Unspecified  |   Platform:  All
--+---
Changes (by martinl):

 * milestone:  7.0.7 => 7.4.1


-- 
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] #2736: t.rast.algebra output naming sheme

2018-03-22 Thread GRASS GIS
#2736: t.rast.algebra output naming sheme
--+
  Reporter:  leohardtke   |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  closed
  Priority:  normal   |  Milestone:  7.6.0
 Component:  Default  |Version:  svn-trunk
Resolution:  fixed|   Keywords:  t.rast.algebra
   CPU:  Unspecified  |   Platform:  Unspecified
--+
Changes (by neteler):

 * keywords:   => t.rast.algebra
 * milestone:   => 7.6.0


-- 
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] #3302: t.rast.algebra: add support for suffix option in output map names

2018-03-22 Thread GRASS GIS
#3302: t.rast.algebra: add support for suffix option in output map names
-+-
  Reporter:  veroandreo  |  Owner:  grass-dev@…
  Type:  | Status:  closed
  enhancement|
  Priority:  normal  |  Milestone:  7.6.0
 Component:  Temporal|Version:  svn-trunk
Resolution:  fixed   |   Keywords:  t.rast.algebra, t.rast.mapcalc,
   CPU:  |  suffix
  Unspecified|   Platform:  Unspecified
-+-
Changes (by veroandreo):

 * status:  new => closed
 * resolution:   => fixed
 * milestone:  7.4.1 => 7.6.0


-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] Use 'from=' parameter in python script

2018-03-22 Thread Vaclav Petras
On Thu, Mar 22, 2018 at 5:36 AM, Nikos Alexandris 
wrote:

>
> rescale_output = g.read_command('r.rescale', overwrite=True, verbose=True,
>input=band, output=output_map_name, to=to_range)
> print rescale_output
>
> cls.runModule('r.rescale', overwrite=True, verbose=True,
>input=band, output=output_map_name, to=to_range)
> ```
>
> the former will print the output of `r.rescale`, the latter will not.
>
>
> Is there a way to get the output of `runModule`, while building a test
> suite?
>

It's a PyGRASS module, so just access `module.outputs.stdout` afterwards.
Please extend the documentation if needed.

Is the purpose of `expecting_stdout=False` in `runModule()` to test if a
> module emits something to stdout? [0]
>

Yes. It's for cases like when r.univar prints nothing when raster map
contains NULLs only (or region is outside its extent).

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

[GRASS-dev] [GRASS GIS] #3533: g.gui.tplot: add support to export time series values in a text file

2018-03-22 Thread GRASS GIS
#3533: g.gui.tplot: add support to export time series values in a text file
---+-
 Reporter:  veroandreo |  Owner:  grass-dev@…
 Type:  enhancement| Status:  new
 Priority:  normal |  Milestone:  7.6.0
Component:  wxGUI  |Version:  svn-trunk
 Keywords:  g.gui.tplot, temporal  |CPU:  Unspecified
 Platform:  Unspecified|
---+-
 Currently, G7:g.gui.tplot does not allow to export/output the time series
 values in the plot to a text file. Instead, this would be a nice addition
 to avoid an extra call to G7:t.rast.what, for example.

-- 
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] #3532: g.gui.tplot: add zonal statistics support

2018-03-22 Thread GRASS GIS
#3532: g.gui.tplot: add zonal statistics support
-+-
 Reporter:  veroandreo   |  Owner:  grass-dev@…
 Type:  enhancement  | Status:  new
 Priority:  normal   |  Milestone:  7.6.0
Component:  wxGUI|Version:  svn-trunk
 Keywords:  g.gui.tplot, temporal, zonal |CPU:  Unspecified
  statistics |
 Platform:  Linux|
-+-
 It would be very nice to have zonal statistics support in G7:g.gui.tplot
 to get time series plots representing areas. Currently, for STRDS, only
 time series of pixels are supported.

 Additionally, it would be nice to have a flag/check-box to get the
 standard deviation plotted as well.

-- 
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] #3109: d.grid: more enhancements

2018-03-22 Thread GRASS GIS
#3109: d.grid: more enhancements
--+---
  Reporter:  veroandreo   |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:  7.4.1
 Component:  Display  |Version:  unspecified
Resolution:   |   Keywords:  d.grid, gsoc2016, cartography
   CPU:  Unspecified  |   Platform:  Unspecified
--+---

Comment (by marisn):

 As this is a compilation of nice to have small cosmetic issues, then I'll
 add mine – rotate label background boxes with the text. At the moment text
 background is drawn as a bounding box an thus label inside might not align
 with the box itself.

-- 
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] #3294: g.gui.tplot: error when trying to plot a STVDS

2018-03-22 Thread GRASS GIS
#3294: g.gui.tplot: error when trying to plot a STVDS
-+-
  Reporter:  lrntct  |  Owner:  grass-dev@…
  Type:  defect  | Status:  reopened
  Priority:  normal  |  Milestone:  7.2.3
 Component:  wxGUI   |Version:  7.2.0
Resolution:  |   Keywords:
   CPU:  x86-64  |   Platform:  Linux
-+-

Comment (by lucadelu):

 In [changeset:"72490" 72490]:
 {{{
 #!CommitTicketReference repository="" revision="72490"
 g.gui.tplot: resolved problem with stdvs when no categories are set, see
 #3294
 }}}

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] Introduction

2018-03-22 Thread Stefan Blumentrath
Hi guys,

For me it works partly:

python ~/testmode.py

100%

.
100%

F
100%

.
==
FAIL: test_2 (__main__.Testrmode)
--
Traceback (most recent call last):
  File "/home/stefan.blumentrath/testmode.py", line 37, in test_2
msg="slope in degrees must be between 0 and 38.68939")
  File "/usr/local/grass-7.5.svn/etc/python/grass/gunittest/case.py", line 474, 
in assertRasterMinMax
self.fail(self._formatMessage(msg, stdmsg))
AssertionError: slope in degrees must be between 0 and 38.68939
The actual maximum (72.40761) is greater than the reference one (38.68939) for 
raster map slope (with minimum 0)

--
Ran 3 tests in 1.194s
FAILED (failures=1)


Something related to region settings (e.g. when reference values were 
generated)?


Cheers
Stefan

From: grass-dev [mailto:grass-dev-boun...@lists.osgeo.org] On Behalf Of Supreet 
Singh Gill
Sent: torsdag 22. mars 2018 11.15
To: Luca Delucchi 
Cc: GRASS-dev 
Subject: Re: [GRASS-dev] Introduction

but it is working for me, I attached the grass_cmd_output and 
test_keyvalue_result.
I tested on nc_spm_08_grass7

Thank You
Supreet Singh
https://singhsupreet.github.io/

On Thu, Mar 22, 2018 at 3:32 PM, Luca Delucchi 
> wrote:
On 22 March 2018 at 10:07, Supreet Singh Gill 
> wrote:
> Hi,
>

Hi,

> I attached the fixed file.
>

still not working

> Thank You
> Supreet Singh
> https://singhsupreet.github.io/
>

--
ciao
Luca

www.lucadelu.org

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

Re: [GRASS-dev] [GRASS GIS] #3294: g.gui.tplot: error when trying to plot a STVDS

2018-03-22 Thread GRASS GIS
#3294: g.gui.tplot: error when trying to plot a STVDS
-+-
  Reporter:  lrntct  |  Owner:  grass-dev@…
  Type:  defect  | Status:  reopened
  Priority:  normal  |  Milestone:  7.2.3
 Component:  wxGUI   |Version:  7.2.0
Resolution:  |   Keywords:
   CPU:  x86-64  |   Platform:  Linux
-+-

Comment (by lucadelu):

 In [changeset:"72486" 72486]:
 {{{
 #!CommitTicketReference repository="" revision="72486"
 g.gui.tplot: resolved problem with stdvs when no categories are set, see
 #3294
 }}}

-- 
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] #3294: g.gui.tplot: error when trying to plot a STVDS

2018-03-22 Thread GRASS GIS
#3294: g.gui.tplot: error when trying to plot a STVDS
-+-
  Reporter:  lrntct  |  Owner:  grass-dev@…
  Type:  defect  | Status:  reopened
  Priority:  normal  |  Milestone:  7.2.3
 Component:  wxGUI   |Version:  7.2.0
Resolution:  |   Keywords:
   CPU:  x86-64  |   Platform:  Linux
-+-

Comment (by lucadelu):

 In [changeset:"72485" 72485]:
 {{{
 #!CommitTicketReference repository="" revision="72485"
 g.gui.tplot: resolved problem with stdvs when no categories are set, see
 #3294
 }}}

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] Introduction

2018-03-22 Thread Supreet Singh Gill
but it is working for me, I attached the grass_cmd_output and
test_keyvalue_result.

I tested on nc_spm_08_grass7

Thank You
Supreet Singh
https://singhsupreet.github.io/

On Thu, Mar 22, 2018 at 3:32 PM, Luca Delucchi  wrote:

> On 22 March 2018 at 10:07, Supreet Singh Gill 
> wrote:
> > Hi,
> >
>
> Hi,
>
> > I attached the fixed file.
> >
>
> still not working
>
> > Thank You
> > Supreet Singh
> > https://singhsupreet.github.io/
> >
>
>
> --
> ciao
> Luca
>
> www.lucadelu.org
>
time=0.722s
status=succeeded
total=3
failures=0
errors=0
successes=3
skipped=0
expected_failures=0
unexpected_successes=0
tested_modules=r.mode,r.mode,r.mode
supplementary_files=
test_type=not-specified
cd "Desktop"
Working directory changed to:   
"/home/sharry/Desktop" 

(Thu Mar 22 15:41:11 2018)  
python testrmode.py 
.
.
.
GRASS_INFO_PERCENT: 0
GRASS_INFO_PERCENT: 3
GRASS_INFO_PERCENT: 6
GRASS_INFO_PERCENT: 9
GRASS_INFO_PERCENT: 12
GRASS_INFO_PERCENT: 15
GRASS_INFO_PERCENT: 18
GRASS_INFO_PERCENT: 21
GRASS_INFO_PERCENT: 24
GRASS_INFO_PERCENT: 27
GRASS_INFO_PERCENT: 30
GRASS_INFO_PERCENT: 33
GRASS_INFO_PERCENT: 36
GRASS_INFO_PERCENT: 39
GRASS_INFO_PERCENT: 42
GRASS_INFO_PERCENT: 45
GRASS_INFO_PERCENT: 48
GRASS_INFO_PERCENT: 51
GRASS_INFO_PERCENT: 54
GRASS_INFO_PERCENT: 57
GRASS_INFO_PERCENT: 60
GRASS_INFO_PERCENT: 63
GRASS_INFO_PERCENT: 66
GRASS_INFO_PERCENT: 69
GRASS_INFO_PERCENT: 72
GRASS_INFO_PERCENT: 75
GRASS_INFO_PERCENT: 78
GRASS_INFO_PERCENT: 81
GRASS_INFO_PERCENT: 84
GRASS_INFO_PERCENT: 87
GRASS_INFO_PERCENT: 90
GRASS_INFO_PERCENT: 93
GRASS_INFO_PERCENT: 96
GRASS_INFO_PERCENT: 99
GRASS_INFO_PERCENT: 100
GRASS_INFO_PERCENT: 0
GRASS_INFO_PERCENT: 3
GRASS_INFO_PERCENT: 6
GRASS_INFO_PERCENT: 9
GRASS_INFO_PERCENT: 12
GRASS_INFO_PERCENT: 15
GRASS_INFO_PERCENT: 18
GRASS_INFO_PERCENT: 21
GRASS_INFO_PERCENT: 24
GRASS_INFO_PERCENT: 27
GRASS_INFO_PERCENT: 30
GRASS_INFO_PERCENT: 33
GRASS_INFO_PERCENT: 36
GRASS_INFO_PERCENT: 39
GRASS_INFO_PERCENT: 42
GRASS_INFO_PERCENT: 45
GRASS_INFO_PERCENT: 48
GRASS_INFO_PERCENT: 51
GRASS_INFO_PERCENT: 54
GRASS_INFO_PERCENT: 57
GRASS_INFO_PERCENT: 60
GRASS_INFO_PERCENT: 63
GRASS_INFO_PERCENT: 66
GRASS_INFO_PERCENT: 69
GRASS_INFO_PERCENT: 72
GRASS_INFO_PERCENT: 75
GRASS_INFO_PERCENT: 78
GRASS_INFO_PERCENT: 81
GRASS_INFO_PERCENT: 84
GRASS_INFO_PERCENT: 87
GRASS_INFO_PERCENT: 90
GRASS_INFO_PERCENT: 93
GRASS_INFO_PERCENT: 96
GRASS_INFO_PERCENT: 99
GRASS_INFO_PERCENT: 100
GRASS_INFO_PERCENT: 0
GRASS_INFO_PERCENT: 3
GRASS_INFO_PERCENT: 6
GRASS_INFO_PERCENT: 9
GRASS_INFO_PERCENT: 12
GRASS_INFO_PERCENT: 15
GRASS_INFO_PERCENT: 18
GRASS_INFO_PERCENT: 21
GRASS_INFO_PERCENT: 24
GRASS_INFO_PERCENT: 27
GRASS_INFO_PERCENT: 30
GRASS_INFO_PERCENT: 33
GRASS_INFO_PERCENT: 36
GRASS_INFO_PERCENT: 39
GRASS_INFO_PERCENT: 42
GRASS_INFO_PERCENT: 45
GRASS_INFO_PERCENT: 48
GRASS_INFO_PERCENT: 51
GRASS_INFO_PERCENT: 54
GRASS_INFO_PERCENT: 57
GRASS_INFO_PERCENT: 60
GRASS_INFO_PERCENT: 63
GRASS_INFO_PERCENT: 66
GRASS_INFO_PERCENT: 69
GRASS_INFO_PERCENT: 72
GRASS_INFO_PERCENT: 75
GRASS_INFO_PERCENT: 78
GRASS_INFO_PERCENT: 81
GRASS_INFO_PERCENT: 84
GRASS_INFO_PERCENT: 87
GRASS_INFO_PERCENT: 90
GRASS_INFO_PERCENT: 93
GRASS_INFO_PERCENT: 96
GRASS_INFO_PERCENT: 99
GRASS_INFO_PERCENT: 100

--
Ran 3 tests in 0.722s
OK
(Thu Mar 22 15:41:12 2018) Command finished (1 sec) 
"""
Name:   r.mode test
Purpose:Tests r.mode and its flags/options.
	
Author: Supreet Singh
"""

from grass.gunittest.case import TestCase
from grass.gunittest.main import test

class Testrmode(TestCase):
output='rmode'
base='facility'
cover='soils_Kfactor'

@classmethod
def setUpClass(cls):
cls.use_temp_region()

@classmethod
def tearDownClass(cls):
cls.del_temp_region()

def tearDown(self):
self.runModule('g.remove', type='raster', flags='f', name=self.output)

def test_1(self):
facility='facility'
self.assertModule('r.mode', base=self.base, cover=self.cover, output=self.output)
self.assertRasterMinMax(map=facility, refmin=1, refmax=1,
	msg="facility in degrees must be between 1 and 1")

def test_2(self):
slope='slope'
self.assertModule('r.mode', base=self.base, cover=self.cover, output=self.output)
self.assertRasterMinMax(map=slope, refmin=0, refmax=38.68939,
	msg="slope in degrees must be between 0 and 38.68939")

def test_3(self):
elevation='elevation'

Re: [GRASS-dev] [GRASS GIS] #2736: t.rast.algebra output naming sheme

2018-03-22 Thread GRASS GIS
#2736: t.rast.algebra output naming sheme
--+-
  Reporter:  leohardtke   |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  closed
  Priority:  normal   |  Milestone:
 Component:  Default  |Version:  svn-trunk
Resolution:  fixed|   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by veroandreo):

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


Comment:

 This feature is now part of the new `suffix` option implemented in r72478
 for G7:t.rast.algebra. Closing

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] Introduction

2018-03-22 Thread Luca Delucchi
On 22 March 2018 at 10:07, Supreet Singh Gill  wrote:
> Hi,
>

Hi,

> I attached the fixed file.
>

still not working

> Thank You
> Supreet Singh
> https://singhsupreet.github.io/
>


-- 
ciao
Luca

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

Re: [GRASS-dev] [GRASS GIS] #3302: t.rast.algebra: add support for suffix option in output map names

2018-03-22 Thread GRASS GIS
#3302: t.rast.algebra: add support for suffix option in output map names
-+-
  Reporter:  veroandreo  |  Owner:  grass-dev@…
  Type:  | Status:  new
  enhancement|
  Priority:  normal  |  Milestone:  7.4.1
 Component:  Temporal|Version:  svn-trunk
Resolution:  |   Keywords:  t.rast.algebra, t.rast.mapcalc,
   CPU:  |  suffix
  Unspecified|   Platform:  Unspecified
-+-

Comment (by veroandreo):

 YAY!!! Just tested the 3 different suffix in G7:t.rast.algebra and they
 work as expected. Thanks! :)

-- 
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] #3531: i.ortho.transform strange error values

2018-03-22 Thread GRASS GIS
#3531: i.ortho.transform strange error values
---+-
 Reporter:  lucadelu   |  Owner:  grass-dev@…
 Type:  defect | Status:  new
 Priority:  normal |  Milestone:  7.4.1
Component:  Imagery|Version:  svn-trunk
 Keywords:  i.ortho.transform, errors  |CPU:  Unspecified
 Platform:  All|
---+-
 In i.ortho.transform the errors values should be in unit map, instead they
 are not.

 The following output should be in meters


 {{{
 i.ortho.transform group=14e_4955 format=fd,rd
  124913.338945 3859.010582
  150198.078715 5088.578812
  133623.527987 5489.400336
  1398691.354379 3806.687818
  2226283.515875 4635.457543
  56880.722508 1824.323495
  50751.426781 4719.033804
  180403.665422 6229.579394
  177841.993072 6430.734057
  122670.782614 3871.898352
  293407.606905 5335.958820
  142863.354959 5193.151599
  47473.832550 1457.690541
  53050.847913 2655.774660
  53087.326170 3581.397534
  52604.239630 3590.475141
 }}}


 If needed I can provide the dataset used for this example

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] Use 'from=' parameter in python script

2018-03-22 Thread Nikos Alexandris

[all deleted]

In the same script,

```
import grass.script as g
from grass.gunittest.case import TestCase
```

and

```
rescale_output = g.read_command('r.rescale', overwrite=True, verbose=True,
   input=band, output=output_map_name, to=to_range)
print rescale_output

cls.runModule('r.rescale', overwrite=True, verbose=True,
   input=band, output=output_map_name, to=to_range)
```

the former will print the output of `r.rescale`, the latter will not.


Is there a way to get the output of `runModule`, while building a test suite?
And avoid using a `grass.script` function?

Is the purpose of `expecting_stdout=False` in `runModule()` to test if a
module emits something to stdout? [0]

Thanks, Nikos

[0] 
https://grass.osgeo.org/grass74/manuals/libpython/_modules/gunittest/case.html#TestCase.runModule.


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

[GRASS-dev] [GSoC] Proposal draft - Improve GRASS integration in QGIS 3

2018-03-22 Thread Radek Novotný
Hello everyone,

Here is my proposal draft for an idea Improve GRASS integration in QGIS 3.
https://docs.google.com/document/d/1XlxRHvtaiebVIOvlq8G6Q5FuUkFigZ8DlQbaQ-y9keQ/edit?usp=sharing

I will be happy for your feedback, comments, and suggestions.

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

Re: [GRASS-dev] Introduction

2018-03-22 Thread Supreet Singh Gill
Hi,

I attached the fixed file.

Thank You
Supreet Singh
https://singhsupreet.github.io/

On Wed, Mar 21, 2018 at 9:17 PM, Luca Delucchi  wrote:

> On 31 January 2018 at 15:31, sharry gill  wrote:
> > Hello,
> >
>
> Hi Sharry
>
> >
> > I have attached a simple test, I wrote for r.mode.
> >
>
> I run it in nc_basic_spm_grass7 [0] but it fails
>
> GRASS 7.5.svn (nc_basic_spm_grass7):~ > python ~/testrmode.py
>
> ERROR: Raster map  not found
> ERROR: Raster map  not found
>
> E
> ERROR: Raster map  not found
> ERROR: Raster map  not found
>
> E
> ERROR: Raster map  not found
> ERROR: Raster map  not found
>
> F
> ==
> ERROR: test_1 (__main__.Testrmode)
> --
> Traceback (most recent call last):
>   File "/home/lucadelu/testrmode.py", line 31, in test_1
> msg="facility in degrees must be between 1 and 1")
>   File "/home/lucadelu/compilati/grass_trunk/dist.x86_64-pc-
> linux-gnu/etc/python/grass/gunittest/case.py",
> line 461, in assertRasterMinMax
> stdout = call_module('r.info', map=map, flags='r')
>   File "/home/lucadelu/compilati/grass_trunk/dist.x86_64-pc-
> linux-gnu/etc/python/grass/gunittest/gmodules.py",
> line 131, in call_module
> raise CalledModuleError(returncode, module, kwargs, errors)
> CalledModuleError: Module run 1 r.info ended with error
> Process ended with non-zero return code {'map': 'facility', 'flags':
> 'r', 'stderr': -1, 'stdout': -1}. See the following errors:
> ERROR: Raster map  not found
>
>
> ==
> ERROR: test_2 (__main__.Testrmode)
> --
> Traceback (most recent call last):
>   File "/home/lucadelu/testrmode.py", line 37, in test_2
> msg="slope in degrees must be between 0 and 38.68939")
>   File "/home/lucadelu/compilati/grass_trunk/dist.x86_64-pc-
> linux-gnu/etc/python/grass/gunittest/case.py",
> line 461, in assertRasterMinMax
> stdout = call_module('r.info', map=map, flags='r')
>   File "/home/lucadelu/compilati/grass_trunk/dist.x86_64-pc-
> linux-gnu/etc/python/grass/gunittest/gmodules.py",
> line 131, in call_module
> raise CalledModuleError(returncode, module, kwargs, errors)
> CalledModuleError: Module run 1 r.info ended with error
> Process ended with non-zero return code {'map': 'slope', 'flags': 'r',
> 'stderr': -1, 'stdout': -1}. See the following errors:
> ERROR: Raster map  not found
>
>
> ==
> FAIL: test_3 (__main__.Testrmode)
> --
> Traceback (most recent call last):
>   File "/home/lucadelu/testrmode.py", line 43, in test_3
> msg="geology in degrees must be between 34300 and 43600")
>   File "/home/lucadelu/compilati/grass_trunk/dist.x86_64-pc-
> linux-gnu/etc/python/grass/gunittest/case.py",
> line 468, in assertRasterMinMax
> self.fail(self._formatMessage(msg, stdmsg))
> AssertionError: geology in degrees must be between 34300 and 43600
> The actual minimum (217) is smaller than the reference one (34300) for
> raster map geology (with maximum 948)
>
> --
> Ran 3 tests in 0.905s
> FAILED (failures=1, errors=2)
>
> could you please fix it?
>
> > I am new to Open Source community so I came early, so I can get to know
> > about OSGeo and GRASS GIS.
> >
> > Thank You
> > Supreet
> >
>
> [0] https://grass.osgeo.org/sampledata/north_carolina/nc_
> basic_spm_grass7.tar.gz
>
> --
> ciao
> Luca
>
> www.lucadelu.org
>
"""
Name:   r.mode test
Purpose:Tests r.mode and its flags/options.
	
Author: Supreet Singh
"""

from grass.gunittest.case import TestCase
from grass.gunittest.main import test

class Testrmode(TestCase):
output='rmode'
base='facility'
cover='soils_Kfactor'

@classmethod
def setUpClass(cls):
cls.use_temp_region()

@classmethod
def tearDownClass(cls):
cls.del_temp_region()

def tearDown(self):
self.runModule('g.remove', type='raster', flags='f', name=self.output)

def test_1(self):
facility='facility'
self.assertModule('r.mode', base=self.base, cover=self.cover, output=self.output)
self.assertRasterMinMax(map=facility, refmin=1, refmax=1,
	msg="facility in degrees must be between 1 and 1")

def test_2(self):
slope='slope'
self.assertModule('r.mode', base=self.base, cover=self.cover, output=self.output)
self.assertRasterMinMax(map=slope, refmin=0, refmax=38.68939,
	msg="slope in degrees must be between 0 and 38.68939")

def test_3(self):
elevation='elevation'
self.assertModule('r.mode', base=self.base, cover=self.cover, 

Re: [GRASS-dev] [release planning] GRASS GIS 7.2.3

2018-03-22 Thread Markus Neteler
Hi,

GRASS GIS 7.2.3 - LTS got released!

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

Please package (I'll send out the usual email to the packagers later today)

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

Re: [GRASS-dev] [GRASS GIS] #3463: Compilation failure with >=glibc-2.14 due to missing rpc

2018-03-22 Thread GRASS GIS
#3463: Compilation failure with >=glibc-2.14 due to missing rpc
--+-
  Reporter:  marisn   |  Owner:  grass-dev@…
  Type:  defect   | Status:  closed
  Priority:  blocker  |  Milestone:  7.4.0
 Component:  Compiling|Version:  svn-trunk
Resolution:  fixed|   Keywords:  xrpc
   CPU:  Unspecified  |   Platform:  Linux
--+-
Changes (by devurandom):

 * cc: devurandom (added)


-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] Use 'from=' parameter in python script

2018-03-22 Thread Markus Neteler
On Thu, Mar 22, 2018 at 8:21 AM, Nikos Alexandris
 wrote:
...
> If I didn't miss anything, `grep` finds only 1 use of `r.rescale` within

FYI - you can find that best with "ag - the silver searcher" since you
can restrict the search to a programming language, here --python:

> a script. It is the addon `grass7/raster/r.mblend/r.mblend.py`, in line
> 270.

# core
ag --python r.rescale
gui/wxpython/iscatt/controllers.py
323:"(e. g. using r.rescale) below recommended
threshold.\n\n"

# software/grass-addons/grass7/
ag --python r.rescale
raster/r.mblend/r.mblend.py
207:gscript.run_command('r.rescale', input=dist_high, output=weights,

So: confirmed.

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

Re: [GRASS-dev] Use 'from=' parameter in python script

2018-03-22 Thread Nikos Alexandris

Nikos Alexandris wrote:


>
> how can I use the 'from' parameter in a python script? The following
> ```
> from_range=0,255
> to_range=0,511
> cls.runModule('r.rescale', input=band, output=output_map_name,
>from=from_range, to=to_range, overwrite=True)
> ```
>
> causes expectedly
> ```
> SyntaxError: invalid syntax
> ```



Vaclav Petras a écrit :


Try `from_`. I'm not sure at this point if it works in a gunittest (which
you seem to be using).

Vaclav


Nikos:


I already tried that and it does not work. Yes, trying to build tests for the 
"new" i.rgb.his.

Thank you, Nikos


Note to self: `r.rescale` works fine without the `from` parameter. The actual
minimum and the maximum values, of the `input` map are always used.

Thinking about: what would be a use case where the `from` values would need
to be user defined, which implies they would need to differ from the
map's actual minimum and maximum?

If I didn't miss anything, `grep` finds only 1 use of `r.rescale` within
a script. It is the addon `grass7/raster/r.mblend/r.mblend.py`, in line
270.

Nikos



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

[GRASS-dev] Interim report - OSGeo Community Sprint Bonn 2018 - GRASS team

2018-03-22 Thread Markus Neteler
Dear all,

please enjoy what we achieved to far at the GRASS Community Sprint Bonn 2018:

https://grasswiki.osgeo.org/wiki/Talk:GRASS_Community_Sprint_Bonn_2018

We'll be here till Sunday - more to come! Please join virtually as well:
https://grasswiki.osgeo.org/wiki/GRASS_GIS_Community_Sprint_Bonn_2018#Planned_participation

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

Re: [GRASS-dev] Use 'from=' parameter in python script

2018-03-22 Thread Nikos Alexandris


Le Jeudi 22 mars 2018, Vaclav Petras a écrit :
> On Wed, Mar 21, 2018 at 7:57 PM, Nikos Alexandris 
> wrote:
> >
> > how can I use the 'from' parameter in a python script? The following
> > ```
> > from_range=0,255
> > to_range=0,511
> > cls.runModule('r.rescale', input=band, output=output_map_name,
> >from=from_range, to=to_range, overwrite=True)
> > ```
> >
> > causes expectedly
> > ```
> > SyntaxError: invalid syntax
> > ```
> 
> 
> Try `from_`. I'm not sure at this point if it works in a gunittest (which
> you seem to be using).
> 
> Vaclav

I already tried that and it does not work. Yes, trying to build tests for the 
"new" i.rgb.his.

 Thank you, Nikos

-- 
Envoyé depuis mon Jolla
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] PROJ 5 support in trunk

2018-03-22 Thread Markus Neteler
On Tue, Mar 20, 2018 at 8:04 PM, Markus Metz
 wrote:
> Hi all,
>
> I have added support for the new PROJ 5+ API in trunk, finished with r72433.

That's really great! First OSGeo project :-)

It was a lot of work for you, thanks.

> This means, trunk is now using exclusively the new PROJ 5+ API if available.
>
> This new PROJ 5 API is available e.g. in Debian testing.
>
> Please test!
>
> During testing, I discovered some dangerous naming conflicts in GRASS and
> PROJ4/PROJ5: internal functions start both in GRASS and PROJ with pj_ which
> can lead to cryptic errors. Within GRASS, some but not all
> projection-related functions start with GPJ_, this should be adopted for
> those starting with pj_. Also the GRASS structure struct pj_info should be
> renamed to struct gpj_info.

BTW: Also GDAL now comes with support for PROJ 5, see
https://lists.osgeo.org/pipermail/gdal-dev/2018-March/048278.html

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