[GRASS-dev] [GRASS GIS] #2143: d.legend: add option to output legend definition as text
GRASS GIS
trac at osgeo.org
Fri Feb 7 20:40:00 PST 2014
#2143: d.legend: add option to output legend definition as text
-----------------------------------+----------------------------------------
Reporter: wenzeslaus | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: trivial | Milestone: 7.0.0
Component: Display | Version: svn-trunk
Keywords: d.legend, text output | Platform: All
Cpu: All |
-----------------------------------+----------------------------------------
Comment(by wenzeslaus):
Replying to [comment:1 hamish]:
>
> see r.colors.out (which does most of you are asking for in this ticket I
think) and the approach taken by various grass6 addon modules:
r.colors.out_sld (Mapserver), r.colors.out_vtk (Paraview/VisIt), r.out.gmt
(also creates the GMT color table), and r.out.gdal.
>
> .. or for something local/custom just parse the $MAPSET/colr/ file
directly.
>
I was not testing these but it seems to me that I would end up in re-
implementing `d.legend`, e.g. when putting there labels or when forcing
other types of legend than the map would use by default.
> I haven't looked at it in a while, but I imagine the HTML display driver
might have some web-friendly code in it too?
>
Last time when I was testing HTML driver I got the impression that it
supports only HTML tag map and that even this is not finished. Probably
the big issue is what HTML driver is supposed to do anyway? Legend
rendered as what in HTML and how this fits together with HTML tag map. But
this is different topic.
> Do you have specific plans on how you'd use the output? or is this more
a general idea?
>
The motivation was the ability to create legend for HTML pages, or
alternatively LaTeX reports. But the idea is general, e.g. font and
generally handling of labels could be important for any output which is
trying to be something more than an raster image.
> As the primary author of the current d.legend I'm not exactly
enthusiastic about messing too much with what is already working well.
It's a complicated monolith, and I'd appreciate anyone thinking about
changing it to please contact me first for advice. (or the change will
risk be dropped like the fontscale option soon will be)
>
Adding there text output is actually trying to avoid the need for bigger
changes in `d.legend` (some super visualizations can be then done
outside).
''The other things are related to wiki:GSoC/2014, so they should be
discussed at mailing list, or the ideas should be updated directly when it
is clear.''
--
Ticket URL: <http://trac.osgeo.org/grass/ticket/2143#comment:3>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list