table of contents
other versions
- buster 7.6.0-1
- testing 7.8.5-1
- unstable 7.8.5-1
- experimental 7.8.6~rc2-1~exp1
displaydrivers(1grass) | Grass User's Manual | displaydrivers(1grass) |
Display drivers¶
The current command line rendering mechanism is direct rendering into a file. The driver is selected by setting the GRASS_RENDER_IMMEDIATE variable or by running d.mon module.List of available display drivers:
- Cairo driver
- PNG driver
- PS driver (Postscript)
- HTMLMAP driver
NOTES¶
GRASS_RENDER_COMMAND¶
If environmental variable GRASS_RENDER_COMMAND is defined, rendering is redirected by display library to the given external command defined by this variable. Currently only Python scrips are supported.Lets start with simple example of Python script called
render.py:
#!/usr/bin/env python import os import sys import grass.script as grass from grass.script import task as gtask os.environ[’GRASS_RENDER_IMMEDIATE’] = ’default’ os.environ[’GRASS_RENDER_FILE’] = ’output.png’ cmd, dcmd = gtask.cmdstring_to_tuple(sys.argv[1]) grass.run_command(’d.text’, text="Test of GRASS_RENDER_COMMAND redirection") os.environ[’GRASS_RENDER_FILE_READ’] = ’TRUE’ grass.run_command(cmd, **dcmd)After defining GRASS_RENDER_COMMAND variable (example for Bash):
export GRASS_RENDER_COMMAND=render.pyDisplay GRASS modules like d.rast or d.vect will be executed by render.py program. For example the command
d.vect roadsmajorproduces output PNG file output.png which will contain rendered features from vector map roadsmajor and sample text "Test of GRASS_RENDER_COMMAND redirection".
SEE ALSO¶
d.mon, variablesSOURCE CODE¶
Available at: Display drivers source code (history)Main index | Display index | Topics index | Keywords index | Graphical index | Full index
© 2003-2019 GRASS Development Team, GRASS GIS 7.6.0 Reference Manual
GRASS 7.6.0 |