[GRASS-dev] [GRASS GIS] #2509: d.mon output overwrite

GRASS GIS trac at osgeo.org
Sun Dec 7 09:17:19 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 martinl):

 Replying to [comment:2 wenzeslaus]:
 > This applies to any `d.*` command which is drawing something.

 This ticket is just related to `d.mon` (when you start a new monitor).

 > 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.

 `map.png` contains both raster and vector map, which is OK.

 > You don't need to call `d.mon` in order to write to a file named
 `map.png`. So, I'm not sure

 I am not sure what you are referring to. Anyway `d.mon out=` checks if the
 file exists. If `--overwrite` is given than the file is overwritten. If
 you use `--overwrite` together with `-u` flag that the file is open
 'update' mode, ie. new data are rendered on the top of the existing file.

 This ticket is related to the fact that `d.mon` behaves differently when
 launched without `output` option (when using default display driver output
 file).

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/2509#comment:3>
GRASS GIS <http://grass.osgeo.org>



More information about the grass-dev mailing list