Hi,
2015-05-13 8:03 GMT+02:00 Pietro peter.z...@gmail.com:
#% description: Name of vector map with interested segments of rivers
- label
As you can see the description of the parameter add the default
description set in G_OPT_V_INPUT and in a new line the description
added manually in the
Hi Martin,
On Wed, May 13, 2015 at 11:08 AM, Martin Landa landa.mar...@gmail.com wrote:
Hi,
2015-05-13 8:03 GMT+02:00 Pietro peter.z...@gmail.com:
#% description: Name of vector map with interested segments of rivers
- label
Therefore I should use label instead of description, something
Hi devs,
I found a strange r.cross behaviour, the output includes a random 0
category without any label information. Here an example in the NC sample
location:
g.version -rg
version=7.0.0
date=2015
revision=0
build_date=2015-01-24
build_platform=x86_64-unknown-linux-gnu
#2676: r.neighbors on large rasters
---+-
Reporter: dnewcomb | Owner: grass-dev@…
Type: enhancement| Status: new
Priority: normal | Milestone: 7.0.1
Component:
On Wed, May 13, 2015 at 9:47 AM, Pietro peter.z...@gmail.com wrote:
Hi Martin,
On Wed, May 13, 2015 at 11:08 AM, Martin Landa landa.mar...@gmail.com
wrote:
Hi,
2015-05-13 8:03 GMT+02:00 Pietro peter.z...@gmail.com:
#% description: Name of vector map with interested segments of rivers
#2676: r.neighbors on large rasters
--+---
Reporter: dnewcomb | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.0.1
Component: Default |Version:
Dear all,
I found an inconsistency of behaviors between G_OPT_R_INPUT and
G_OPT_V_INPUT, here the test code:
{{{
#!/usr/bin/env python
# -- coding: utf-8 --
#%module
#% description: Test
#% keywords: test
#%end
#%option G_OPT_R_INPUT
#% key: discharge
#% description: Name of river discharge
#2480: v.class.ml: ImportError: No module named training_extraction
--+
Reporter: mlennert | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Component: Addons
* Pietro peter.z...@gmail.com [2015-05-13 08:03:04 +0200]:
Dear all,
I found an inconsistency of behaviors between G_OPT_R_INPUT and
G_OPT_V_INPUT, here the test code:
{{{
#!/usr/bin/env python
# -- coding: utf-8 --
#%module
#% description: Test
#% keywords: test
#%end
#%option