[GRASS-dev] G_OPT_R_MAP vs G_OPT_R_INPUT

[Benjamin Ducke]

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.

Ben

> 
> 
> -----
> best regards
> Helmut
> --
> View this message in context: http://osgeo-org.1560.x6.nabble.com/G-OPT-R-MAP-vs-G-OPT-R-INPUT-tp5173026p5173030.html
> Sent from the Grass - Dev mailing list archive at Nabble.com.
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
> 



-- 
Dr. Benjamin Ducke
{*} Geospatial Consultant
{*} GIS Developer

Spatial technology for the masses, not the classes:
experience free and open source GIS at http://gvsigce.org