[GRASS-dev] [GRASS GIS] #2136: Create standard options for map or file base name (prefix)
GRASS GIS
trac at osgeo.org
Fri Sep 12 08:57:16 PDT 2014
#2136: Create standard options for map or file base name (prefix)
-----------------------------------------+----------------------------------
Reporter: wenzeslaus | Owner: grass-dev@…
Type: defect | Status: new
Priority: blocker | Milestone: 7.0.0
Component: Parser | Version: svn-releasebranch64
Keywords: base name, prefix, basename | Platform: All
Cpu: All |
-----------------------------------------+----------------------------------
Comment(by wenzeslaus):
What is the status of separator? I still don't agree that double
underscore is a good idea and I would even think that no special separator
is a better option. In case of no special separator, if you still would
like to work with basename + suffix, I think that it is acceptable to
specify the basename (then the name can be parsed). It seems to me that
the case of parsing the mapname to work with suffixes will not be really
common (at least for maps created inside GRASS since the metadata should
tell you more).
Note that for modules which do not register maps to space-time dataset the
separator and suffix behavior are part of the API (so the decision is
blocker for 7.0). So, all interested, please, state you opinion.
Note also that the modules which produce space-time dataset could have
`basename` parameter as optional. The reasonable and expected default is
usage of dataset name as basename. I think that this different case than
`r.shaded.relief` creating by default map named `inputname.shade`. Do you
agree? But this is not a blocker.
--
Ticket URL: <http://trac.osgeo.org/grass/ticket/2136#comment:31>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list