Nikos Alexandris n...@nikosalexandris.net
d.erase: I would like to do `d.erase black`. Black is a *good*
background color.
Vaclav Petras wrote:
One of the problems with `d.erase` is that it is not clear what it is
supposed to do. Remove maps from display? Set background? Zoom to
region?
On Fri, Nov 14, 2014 at 4:31 AM, Glynn Clements gl...@gclements.plus.com
wrote:
Vaclav Petras wrote:
I kindly ask command line users of d.* commands, especially those using
d.*
commands in scripts, to test and participate in discussions concerning
d.*
commands in GRASS GIS 7. For
On Fri, Nov 14, 2014 at 7:07 AM, Nikos Alexandris n...@nikosalexandris.net
wrote:
* Vaclav Petras wenzesl...@gmail.com [2014-11-12 09:35:32 -0500]:
I kindly ask command line users of d.* commands, especially those using
d.*
commands in scripts, to test and participate in discussions
On Fri, Nov 14, 2014 at 7:45 AM, Peter Löwe peter.lo...@gmx.de wrote:
Hi Nikos, dear all,
Isn't it possible to merge d.out.file and d.to.rast? Maybe instruct
to.rast with a flag or an explicit output name?
Nikos
I strongly support this. The cumbersome re-import of the monitor
Vaclav Petras wrote:
I kindly ask command line users of d.* commands, especially those using d.*
commands in scripts, to test and participate in discussions concerning d.*
commands in GRASS GIS 7. For example, d.out.file was added (relatively)
lately to 7 and there is new command d.to.rast.
* Vaclav Petras wenzesl...@gmail.com [2014-11-12 09:35:32 -0500]:
I kindly ask command line users of d.* commands, especially those using d.*
commands in scripts, to test and participate in discussions concerning d.*
commands in GRASS GIS 7. For example, d.out.file was added (relatively)
César Augusto Ramírez Franco wrote:
As far as I understand, d.out.file only works with X monitors,
This appears to be the case, although I have no idea why.
The basic operation of d.out.file is to run d.save to extract the
list of commands used to generate the display, then replay those
I kindly ask command line users of d.* commands, especially those using d.*
commands in scripts, to test and participate in discussions concerning d.*
commands in GRASS GIS 7. For example, d.out.file was added (relatively)
lately to 7 and there is new command d.to.rast. They are designed to work
Dear Csar, dear all,
thanks for your input, but the core problem remains:
When a Shell-script is invoked from the GRASS-shell (GRASS6.4.2 on Suse Linux on a HPC cluster) with a monitor (x0, PNG, etc.) being already activated (d.mon start / d.mon select), a g.gisenv _within_ the script will
Hello Peter,
I'm sorry for misunderstanding your question, I thought that starting the
monitor INSIDE the script would be adequate for you, I have tested this and
couldn't reproduce your problem:
I created a test.sh file on my current directory and made it executable
with the following contents:
Hi Csar,
thanks for your follow-up work in this issue: Thats exactly the workflow I was looking for. So the issue got already fixed between GRASS6.4.2 and 6.4.4. Could you please verify the behaviour of d.out.file in GRASS6.4.4 when a PNG monitor is being used ?
Best,
Peter
Hi Peter,
As far as I understand, d.out.file only works with X monitors, the workflow
for a PNG monitor would be as follows:
export GRASS_PNGFILE=test.png
export GRASS_WIDTH=800
export GRASS_HEIGHT=600
d.mon start=PNG
d.rast somerastermap
d.vect somevectormap
d.mon stop=PNG
You could do this
12 matches
Mail list logo
