On Mon, Oct 7, 2013 at 8:52 PM, Markus Neteler <[email protected]> wrote:
> r.series | r.statistics2 | t.rast.aggregate.* | t.vect.what.strds
> ...
>     method   Aggregate operation
>              options: average,count,median,mode,minimum,min_raster,maximum,
>                       max_raster,stddev,range,sum,variance,diversity,slope,
>                       offset,detcoeff,tvalue,quart1,quart3,perc90,quantile,
>                       skewness,kurtosis
>
> r.in.lidar | r.in.xyz | r3.in.xyz | r.statistics
>      method   Statistic to use for raster values
>                options: n,min,max,range,sum,mean,stddev,variance,coeff_var,
>                         median,percentile,skewness,trimmean
>                default: mean
>
> I would suggest to streamline this (and personally opt for the
> r.series way of naming the methods; e.g., the "n" is easily
> overlooked, the "count" less so).

+1

Moreover min and max are functions in python, so from my point of view
it is much better minimum and maximum to avoid possible conflicts.

Pietro
_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev

Reply via email to