[GRASS-dev] [GRASS GIS] #2509: d.mon output overwrite
GRASS GIS
trac at osgeo.org
Sun Dec 7 08:29:31 PST 2014
#2509: d.mon output overwrite
-------------------------+--------------------------------------------------
Reporter: martinl | Owner: martinl
Type: defect | Status: assigned
Priority: normal | Milestone: 7.0.0
Component: Display | Version: unspecified
Keywords: d.mon | Platform: Unspecified
Cpu: Unspecified |
-------------------------+--------------------------------------------------
Comment(by wenzeslaus):
This applies to any `d.*` command which is drawing something.
Start GRASS and use in terminal:
{{{
d.rast elevation
}}}
`map.png` now contains image of elevation raster.
{{{
d.vect streams
}}}
`map.png` now contains image of streams vector.
You don't need to call `d.mon` in order to write to a file named
`map.png`. So, I'm not sure if what you are reporting, is an bug. It is
perhaps just undocumented feature. The unchecked overwrite is a bit
inconsistent but it also makes sense in this case. I recently learned
about this behavior in [http://lists.osgeo.org/pipermail/grass-
dev/2014-December/072250.html discussion related to r63227 - in
grass/trunk/scripts] ([http://osgeo-org.1560.x6.nabble.com/Re-GRASS-
SVN-r63227-in-grass-trunk-scripts-d-correlate-d-out-file-d-rast-
leg-d-redraw-d-shadedmap-d-t-td5175707.html nabble],
[http://comments.gmane.org/gmane.comp.gis.grass.devel/61537 gmane]).
I don't have any idea what should be the right behavior. It would be good
to have different use cases to understand how it is actually used (or
supposed to be used).
--
Ticket URL: <http://trac.osgeo.org/grass/ticket/2509#comment:2>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list