[GRASS-dev] Module names (was: r.li (landscape indices))
Brad Douglas
rez at touchofmadness.com
Tue Jan 30 07:13:15 EST 2007
On Tue, 2007-01-30 at 12:45 +1300, Hamish wrote:
> FYI, the longest historic* names we have are 15-17 chars long:
> d.font.freetype
d.font.ttf? While it will do more than just TTF, the help command could
explain that it can use any font format FreeType can use.
> r.resamp.interp
I don't know if this can be shortened further without becoming cryptic.
> r.terraflow.short
Ideally, r.terraflow and r.terraflow.short should be combined with int
or float output options. The code is already in a common directory.
> v.build.polylines
v.build.lines?
> v.lidar.edgedetection -> v.lidar.edgedetect or v.lidar.edge ?
> (it is a shame to change as "edgedetection" explains the module well)
IMO, v.lidar.edge is best.
> v.lidar.growing -> v.lidar.classify
> (I think "region growing" is misleading & conflicts with GRASS's common
> use of "region" for raster bounds/resolution; -ing is bad grammar)
>
> v.lidar.correction -> v.lidar.filter
Or v.lidar.correct? You'd know the best naming convention for this
module better than I. I've only recently began to process raw LIDAR
data and haven't use the module, yet. Very soon, though! :-)
--
Brad Douglas <rez touchofmadness com> KB8UYR/6
Address: 37.493,-121.924 / WGS84 National Map Corps #TNMC-3785
More information about the grass-dev
mailing list