On Mar 11, 2008, at 8:10 AM, [EMAIL PROTECTED] wrote:

Date: Tue, 11 Mar 2008 12:06:17 -0000
From: "GRASS GIS" <[EMAIL PROTECTED]>
Subject: [GRASS-dev] [GRASS GIS] #89: d.legend: option to get info
        from stdin instead of raster
To: undisclosed-recipients:;
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="utf-8"

#89: d.legend: option to get info from stdin instead of raster
------------------------- +--------------------------------------------------
 Reporter:  hamish       |       Owner:  [email protected]
     Type:  enhancement  |      Status:  new
 Priority:  minor        |   Milestone:  6.4.0
Component:  default      |     Version:  unspecified
 Keywords:               |
------------------------- +-------------------------------------------------- this was code wish # 391 over on the old gforge tracker. moving it here. http://wald.intevation.org/tracker/index.php? func=detail&aid=391&group_id=21&atid=188

 Hamish


 ----

 Hi,

It would be nice if d.legend could look for "map=-" and if so take legend cat and color info from stdin. That way vector maps and custom legends could be made without resorting to tricks like making a dummy raster file
 to hold
 that info.  [see v.colors addon script]

If data is fed from stdin (signaled by map=-) create categorical legend
 using that data. Data format: "cat|label|color"

 e.g.
 {{{
 d.legend -m map="-" <<EOF
 1|Main Street|255:0:0
 2|Elm Street|0:255:0
 3|Old Coach Road|0:0:255
 EOF
 }}}

In this way d.legend could work as a system module by the GUI instead of
 a user module, and be useful for non-raster tasks too.


 see expanded thread on the -dev mailing list:
  http://thread.gmane.org/gmane.comp.gis.grass.devel/19852/focus=19952


 Hamish

Ironically, I'm stuck in the" North Carolina data set" with a plane delay after a stint in Washington. But have a chance to catch up on email.

This is an excellent idea BUT please don't limit it to stdin. Allow this to be a load from file option so that it can be used from the GUI too.

Michael
_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev

Reply via email to