[GRASS-dev] [GRASS GIS] #2409: last call for options keys consolidation
GRASS GIS
trac at osgeo.org
Thu Nov 27 06:15:22 PST 2014
#2409: last call for options keys consolidation
----------------------------------+-----------------------------------------
Reporter: martinl | Owner: grass-dev@…
Type: task | Status: new
Priority: blocker | Milestone: 7.0.0
Component: Default | Version: unspecified
Keywords: standardized options | Platform: Unspecified
Cpu: Unspecified |
----------------------------------+-----------------------------------------
Comment(by wenzeslaus):
Replying to [comment:44 martinl]:
> Replying to [comment:41 annakrat]:
> > > "raster" shouldn't be abbreviated. "volume" should probably be
"raster_3d" (for which "raster3d" and "rast3d" are accepted
abbreviations).
> >
> > I don't like "raster_3d". If we rename "rast" to "raster", which seems
reasonable, I would go with "raster3d", even though you can't shorten it.
>
> in r63189 I renamed
>
> rast3d -> volume
>
> It means that current abbreviated option will still work expect of
`rast3d` which needs to be renamed to `volume`.
Why to volume? Although there was no agreement, we were often replacing
all "voxel" and "volumne" (and others) by "3D raster" so far. The only
three places I know about where "volume" is used are
[http://grass.osgeo.org/grass71/manuals/v.vol.rst.html v.vol.rst] (just
the name, not even the keyword), GUI menu/toolbox, and GUI for NVIZ.
I'm personally against "volume" because this term means too much other
things. (Does volume computations refer to 3D raster/voxels/voxel models
or to cubic meters of soil or water?) It even does not bring any
advantages for module family name (currently `r3`) which would be `v` but
`v` is already used.
If we are be replacing "3D raster", we should do it everywhere including
manual and module family name
([http://grass.osgeo.org/grass71/manuals/raster3D.html Manual: Raster3D
commands]).
--
Ticket URL: <http://trac.osgeo.org/grass/ticket/2409#comment:47>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list