[GRASS-dev] [GRASS GIS] #2509: d.mon output overwrite
#2509: d.mon output overwrite
-+--
Reporter: martinl | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Component: Display | Version: unspecified
Keywords: d.mon|Platform: Unspecified
Cpu: Unspecified |
-+--
`d.mon` checks output file only if `output` option is given
{{{
d.mon cairo out=map.png
ERROR: option output: map.png exists.
}}}
but not when using default file name of given display driver.
{{{
d.mon cairo
}}}
--
Ticket URL: http://trac.osgeo.org/grass/ticket/2509
GRASS GIS http://grass.osgeo.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2509: d.mon output overwrite
#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 | -+-- Changes (by martinl): * cc: grass-dev@… (added) * owner: grass-dev@… = martinl * status: new = assigned -- Ticket URL: http://trac.osgeo.org/grass/ticket/2509#comment:1 GRASS GIS http://grass.osgeo.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2509: d.mon output overwrite
#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
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2509: d.mon output overwrite
#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
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] Addons builds and manuals
Hi Martin and Markus, The logs about building addons are not updated. I'm also not sure about addons manual pages. I think that i.theilsen from yesterday should be visible but it is not. Is this related? I though that it is not. The logs are recent just the overall log is outdated. Vaclav http://wingrass.fsv.cvut.cz/grass70/addons/grass-7.0.0svn/logs/ALL.html http://wingrass.fsv.cvut.cz/grass70/addons/grass-7.0.0svn/logs/ http://grass.osgeo.org/grass70/manuals/addons/ ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2509: d.mon output overwrite
#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 neteler): Replying to [comment:2 wenzeslaus]: You don't need to call `d.mon` in order to write to a file named `map.png`. Is this a known feature and the default? I just discovered this recently, especially since the d.* modules do not print a message that map.png was generated. So I find these files scattered all over my disk :-) In essence, is the default driver the cairo or png driver, and controlled by the variables listed in http://grass.osgeo.org/grass70/manuals/variables.html#list-of-selected- grass-environment-variables-for-rendering ? -- Ticket URL: http://trac.osgeo.org/grass/ticket/2509#comment:4 GRASS GIS http://grass.osgeo.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2509: d.mon output overwrite
#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):
Replying to [comment:4 neteler]:
So I find these files scattered all over my disk :-)
This might be something different but probably related. Call of `d.rast`
when `d.mon wx0` is active causes creation of `map.png` in the current
directory:
{{{
ls map.png
ls: cannot access map.png: No such file or directory
d.mon wx0
ls map.png
ls: cannot access map.png: No such file or directory
d.rast elevation
ls map.png
map.png
}}}
I observe this for a long time already but until recently I wasn't able to
find a cause. No further investigation done, however.
--
Ticket URL: http://trac.osgeo.org/grass/ticket/2509#comment:5
GRASS GIS http://grass.osgeo.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2286: Duplicate calls to d.rast when using wx monitor and d.rast command line
#2286: Duplicate calls to d.rast when using wx monitor and d.rast command line --+- Reporter: hcho | Owner: grass-dev@… Type: defect| Status: new Priority: major | Milestone: 7.0.0 Component: Display | Version: svn-trunk Keywords: d.mon, rendering |Platform: Linux Cpu: x86-64| --+- Changes (by wenzeslaus): * keywords: d.mon = d.mon, rendering Comment: Do you think this is related to (or the same as) comment:5:ticket:2509 (creating unnecessary map.png in current directory when `d.mon wx0` is active)? -- Ticket URL: http://trac.osgeo.org/grass/ticket/2286#comment:4 GRASS GIS http://grass.osgeo.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] Rast_add_d_colour
Yann Chemin wrote: OK, I found why I got lost in all that... there is no file appearing in colr/ with the rules made in the code. Are you calling Rast_write_colors()? Also, if the map isn't in the current mapset, the file will go into current mapset/colr2/mapset/map rather than the mapset containing the map. -- Glynn Clements gl...@gclements.plus.com ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] Rast_add_d_colour
Yes Glynns, that was my missing part, writing the file. and sleep too. :-) On 8 December 2014 at 10:37, Glynn Clements gl...@gclements.plus.com wrote: Yann Chemin wrote: OK, I found why I got lost in all that... there is no file appearing in colr/ with the rules made in the code. Are you calling Rast_write_colors()? Also, if the map isn't in the current mapset, the file will go into current mapset/colr2/mapset/map rather than the mapset containing the map. -- Glynn Clements gl...@gclements.plus.com -- ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] GRASS 7 - Ubuntu package build problem on Launchpad
Hi all, I did small investigation why Ubuntu package of GRASS 7 is failing to build on Launchpad. The problem is caused by building single page documentation (make htmldocs-single). This make command is also failing on my computer. Building multi-page documentation (make htmldocs) is running without problem. I am not able to figure out the problem with 'single-page' build, since I do not use Doxygen at all. So the question is if somebody is able to fix 'htmldocs-single' or it is possible at least temporary substitute 'htmldocs-single' to 'htmldocs' to allow building the package. -- Ivan Minčík ivan.min...@gmail.com GPG: 0x79529A1E http://imincik.github.io/0x79529A1E.key ivan.min...@gista.sk GPG: 0xD714B02C http://imincik.github.io/0xD714B02C.key ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
