[GRASS-dev] [GRASS GIS] #318: d.vect.thematic - I have enhanced some features - but wish more

GRASS GIS trac at osgeo.org
Wed Oct 1 12:15:03 EDT 2008


#318: d.vect.thematic - I have enhanced some features - but wish more
-------------------------+--------------------------------------------------
 Reporter:  aprasad      |       Owner:  grass-dev at lists.osgeo.org
     Type:  enhancement  |      Status:  new                      
 Priority:  major        |   Milestone:  6.4.0                    
Component:  default      |     Version:  6.3.0                    
 Keywords:               |    Platform:  All                      
      Cpu:  Unspecified  |  
-------------------------+--------------------------------------------------
 NOTE: # I modified d.vect.thematic (see attached file) to put the legend
 into png file if monitor=none and also to render thematic map into png
 file if no monitor is running....I ALSO HAVE ONE ENHANCEMENT WISH I WILL
 OUTLINE IN THE END....
 Assuming that you have not started any monitors, it renders to png (starts
 monitor png1) and outputs to ${map}_thematic.png. Also, if monitor=none,
 the legend is rendered to ${map}_thematic_leg.png. I don't stop the png1
 monitor in case you want to add other display commands - so, if you want
 to add display commands to the ${map}_thematic.png after
 d_vect_thematic.sh has run, simply do, for eg.:
 d.mon sel=png1
 d.vect ewstates type=boundary
 d.mon stop=png1

 This will be very useful for shell scripting of grass commands. You may
 want to streamline the process to make the solution more elegant.

 ENHANCEMENT WISH: Currently if you choose themecalc=custom_breaks
 breakpoints=""
 colorscheme=custom_gradient - you have the option to use just startcolor
 and endcolor and let the script grade the colors in between. One would
 want to use custom colors for each break - supplied as an option or as an
 external file (RGB values etc.) using the breakpoints specified. This
 seems like a logical thing to want and should not be difficult to
 implement ... I will not attempt it as I am sure there are others who will
 do it better and quicker.
 Thanks much.

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/318>
GRASS GIS <http://grass.osgeo.org>


More information about the grass-dev mailing list