[GRASS-dev] Speed map display in wxGUI on bigger monitors
Michael.Barton at asu.edu
Mon Aug 13 12:17:59 PDT 2012
The size of the monitor shouldn't have much (or anything in most cases) to do with this.
Which version is being used?
How is the display set? If it is set to constrain display resolution to match map, this could happen. However, the default behavior for a long time is to create display output at display resolution (depends on the size of the display window). Even with big monitors, this is not a huge file by GRASS GIS standards. However, the temp files that are created for the displays will be larger when larger windows are used on larger monitors (i.e., more pixels to render).
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University
Tempe, AZ 85287-2402
voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC)
fax: 480-965-7671(SHESC), 480-727-0709 (CSDC)
www: http://csdc.asu.edu, http://shesc.asu.edu
On Aug 13, 2012, at 12:00 PM, <grass-dev-request at lists.osgeo.org<mailto:grass-dev-request at lists.osgeo.org>>
From: Markus Neteler <neteler at osgeo.org<mailto:neteler at osgeo.org>>
Date: August 13, 2012 7:57:39 AM MST
To: GRASS developers list <grass-dev at lists.osgeo.org<mailto:grass-dev at lists.osgeo.org>>
Subject: Re: [GRASS-dev] Speed map display in wxGUI on bigger monitors
On Fri, Aug 3, 2012 at 4:19 PM, Markus Neteler <neteler at osgeo.org<mailto:neteler at osgeo.org>> wrote:
when working with the wxGUI on bigger monitors, it is rather slow
when it comes to map display.
Looking into the /tmp/ directory, I find fairly huge files which are
generated and then combined for display.
It is getting even worse when using GRASS over network.
Question: why the uncompressed PNM/PPM format used by g.pnmcomp?
... I am still interested to understand this...
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the grass-dev