[GRASS-user] Display output question

GRASS GRASS user
1

Hi all,

What's the command-line equivalent to using the JPG export in the
display manager? (I would like to script outputs from a number of
workspace - GRC - files).

Cheers,
Richard

2

Hi,

not JPEG, but I would use d.out.png or

d.mon start=PNG
d.*
d.mon stop=PNG

see [1] for more details

Jachym

[1] http://grass.osgeo.org/grass64/manuals/html64_user/pngdriver.html

Richard Chirgwin píše v Út 17. 02. 2009 v 10:40 +1100:

Hi all,

What's the command-line equivalent to using the JPG export in the
display manager? (I would like to script outputs from a number of
workspace - GRC - files).

Cheers,
Richard
_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

--
Jachym Cepicky
e-mail: jachym.cepicky gmail com
URL: http://les-ejk.cz
GPG: http://les-ejk.cz/pgp/JachymCepicky.pgp

3

Jachym Cepicky wrote:

not JPEG, but I would use d.out.png or

d.mon start=PNG
d.*
d.mon stop=PNG

You will get better forward compatibility using the mechanism which
Moritz suggested (GRASS_RENDER_IMMEDIATE et al). Immediate rendering
works in both 6.x and 7.0, while d.mon only works in 6.x.

--
Glynn Clements <glynn@gclements.plus.com>

4

Glynn Clements wrote:

Jachym Cepicky wrote:

not JPEG, but I would use d.out.png or

d.mon start=PNG
d.*
d.mon stop=PNG
    
You will get better forward compatibility using the mechanism which
Moritz suggested (GRASS_RENDER_IMMEDIATE et al). Immediate rendering
works in both 6.x and 7.0, while d.mon only works in 6.x.
  

Thanks all,

There's a follow-up question regarding d.mon-based approaches, in that
it doesn't seem to support transparency, which is supported in the map
display - is this correct?

I will check out the rendering mechanism, but found a (brutal)
workaround. However, I will share it ...

The problem was to quickly get jpgs from a very large number of maps, so
I had a friend write a script. The script watches the Grass temp
directory and executes gdal_translate on new PPN outputs after the
screen is rendered - which meant the person creating the output files
just had to draw the map display, rather than drawing the display, going
to the output menu, navigate to the directory and type in a filename.

There were, in all, a couple of hundred maps, it was taking days to
render them all!

I know about using ps.map but didn't have time to write the scripts ...

Cheers,
Richard

5

Richard Chirgwin wrote:

>> not JPEG, but I would use d.out.png or
>>
>> d.mon start=PNG
>> d.*
>> d.mon stop=PNG
>>
>
> You will get better forward compatibility using the mechanism which
> Moritz suggested (GRASS_RENDER_IMMEDIATE et al). Immediate rendering
> works in both 6.x and 7.0, while d.mon only works in 6.x.
>
Thanks all,

There's a follow-up question regarding d.mon-based approaches, in that
it doesn't seem to support transparency, which is supported in the map
display - is this correct?

Correct; translucency is implemented by g.pnmcomp, used by the GUI.

Note that translucency won't work with the GRASS_PNG_READ=TRUE
approach either. You have to set GRASS_PNGFILE to a different file for
each d.* command, then use g.pnmcomp's opacity= option.

--
Glynn Clements <glynn@gclements.plus.com>