[GRASS-dev] G_OPT_R_MAP vs G_OPT_R_INPUT

[Moritz Lennert]

On 14/11/14 14:25, Benjamin Ducke wrote:
> On 14/11/14 14:14, Helmut Kudrnovsky wrote:
>> NikosAlexandris wrote
>>> What is the difference between G_OPT_R_MAP and G_OPT_R_INPUT? Which and
>>> why should I prefer for my script(s)?
>>>
>>> Is there a step-by-step run-through of all options for composing header
>>> definitions?
>>>
>>> --
>>> Nikos
>>> _______________________________________________
>>> grass-dev mailing list
>>
>>> grass-dev at .osgeo
>>
>>> http://lists.osgeo.org/mailman/listinfo/grass-dev
>>
>> see
>>
>> http://grass.osgeo.org/programming7/gis_8h.html#a5521b5269c52afe64e5051348b08fc69
>>
>
> But that table doesn't really answer the question,
> does it? For both "G_OPT_R_INPUT" and "G_OPT_R_MAP"
> it lists "old input raster map". AFAIU, "G_OPT_R_MAP"
> is for modules that use only one input raster map.
> In those cases, the corresponding input option should
> be named "map=". "G_OPT_R_INPUT" would then be for
> modules that have either several raster map inputs or
> raster and vector maps as inputs. The corresponding
> input options would then be called "raster=" and
> "vector=" in case of exactly one raster and one vector
> input map. Further special cases are covered by
> "G_OPT_R_BASE", "G_OPT_R_ELEV", etc.: They all exist
> for semantical purposes. All of them stand for raster
> input maps.

I've always understood the difference between MAP and INPUT as

- MAP: used for modules which treat a map, but do not have input+output 
logic (e.g. r.category, r.colors, etc)
- INPUT: used for modules that have input + output logic (r.cost, 
r.mfilter, etc)

The difference between one or multiple inputs is covered by

G_OPT_R_INPUT vs G_OPT_R_INPUTS.

Moritz