Re: [GRASS-dev] [GRASS GIS] #3015: Add legend title

2016-11-02 Thread GRASS GIS
#3015: Add legend title
--+-
  Reporter:  annakrat |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  reopened
  Priority:  normal   |  Milestone:  7.2.0
 Component:  Display  |Version:  svn-releasebranch72
Resolution:   |   Keywords:  d.legend, gsoc2016, cartography
   CPU:  Unspecified  |   Platform:  All
--+-

Comment (by annakrat):

 I backported r69160. Please test this and #3132 and both could be closed.

--
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [GRASS GIS] #3132: d.mon + d.vect: ERROR: Option does not accept multiple answers

2016-11-02 Thread GRASS GIS
#3132: d.mon + d.vect: ERROR: Option  does not accept multiple answers
--+-
  Reporter:  neteler  |  Owner:  martinl
  Type:  defect   | Status:  assigned
  Priority:  normal   |  Milestone:  7.2.0
 Component:  wxGUI|Version:  svn-releasebranch72
Resolution:   |   Keywords:  wx0, d.vect
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by annakrat):

 In [changeset:"69765" 69765]:
 {{{
 #!CommitTicketReference repository="" revision="69765"
 d.mon + d.vect: ERROR: Option  does not accept multiple answers (see
 #3132), merge from trunk r69160
 }}}

--
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] Default behavior of g.list displaying all mapsets content

2016-11-02 Thread Martin Landa
Hi,

2016-11-02 11:51 GMT+01:00 Margherita Di Leo :
> what about a -c flag that prints only maps in current mapset?

g.list type=rast mapset=.

-1 for another flag since the user can list maps from current maps by
`mapset=.`. Ma

-- 
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Default behavior of g.list displaying all mapsets content

2016-11-02 Thread Margherita Di Leo
Hi,

sorry for bringing back this topic again,

On Wed, Oct 19, 2016 at 2:17 PM, Margherita Di Leo 
wrote:

>
>
> On Wed, Oct 19, 2016 at 11:56 AM, Margherita Di Leo 
> wrote:
>
>>
>>
>> On Wed, Oct 19, 2016 at 11:47 AM, Moritz Lennert <
>> mlenn...@club.worldonline.be> wrote:
>>
>>> On 19/10/16 11:22, Margherita Di Leo wrote:
>>>


>>> There was a discussion about these questions on the ML at the time:
>>> https://lists.osgeo.org/pipermail/grass-dev/2014-October/071381.html
>>
>>
>> I must have missed that, or perhaps I had no strong opinion at that time,
>> sorry about that.
>>
>
> It seems to me that the whole thread ended up with a general agreement
> that the -m should be reverted?
>

what about a -c flag that prints only maps in current mapset?

Regards,


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

Re: [GRASS-dev] Standard option identifiers

2016-11-02 Thread Markus Metz
On Tue, Nov 1, 2016 at 2:10 AM, pablo zader  wrote:
> Hi list
>
> I'm developing some script in "grass gis", and I have some doubt that the
> documentation will not answer me
> (https://grass.osgeo.org/programming7/gis_8h.html)
>
> What is the diference betwen G_OPT_R_INPUT  and G_OPT_R_MAP ?

The key for G_OPT_R_INPUT is "input", while the key for G_OPT_R_MAP is
"map". Typically, you would use G_OPT_R_INPUT if the module also has
an output option and G_OPT_R_MAP if the module does not have an output
option, e.g. r.info.

HTH,

Markus M

>
> if I have a geoprocess has two input raster layers, which of these two
> options standares I use to define these inputs?
>
> Another related question: what are the values that support the keyword
> "type" in the definition of the head of the code?
>
> In my example, I implemented a script with python scripting library, it
> takes two raster layers as inputs and outputs a raster layer.
> The defintion header is:
>
> option: G_OPT_R_INPUT
> type : string
>
> option: G_OPT_R_INPUT
> type : string
>
> It is correct?
>
> Or, the correct is:
>
> option: G_OPT_R_INPUT
> type : raster
>
> option: G_OPT_R_INPUT
> type : raster
>
> Thanks in advanced
>
>
> --
> Pablo J. Zader
> Universidad Nacional de Córdoba
> GIS and remote sensing developer
> --
> Lic. en Cs. de la Computación
> Mgtr. Aplicaciones en Espaciales de Alerta y Respuesta Temprana a
> Emergencias
> --
> pablo.za...@gmail.com
>
> "Los Grandes Hombres hablan sobre ideas...
>  Los Hombres Promedio hablan sobre cosas...
>  Los Hombres Pequeños hablan.. de otros Hombres.
>
> del libro Matemática estas ahi? A. Paenza "
>
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev