20041207: gpmap watch and warnings

Patrick,

RGB definitions can be done for COLORS=...
but not in defining colors in pther parameters.

The easiest way to define a different mapping of
colors than the $GEMTBL/luts/coltbl.xwp is to
create a coltbl.xwp file in the working directory of
your scripts where you have defined the colors 
as needed to be referenced in your parameters.
Once you have a prefered color table, your script can 
copy it into any directory where you are working.

The county line thickness is set at "2" in gpmap and
isn't modifyable at this time.

In the GPWARN program I created, the colors/types are defined
in $GEMTBL/unidata/'gpwarn.config, but you can override the line
parameters in a file in the script working directory as
well as the coltbl.xwp mentioned above (since tables are always searched
first in the working directory, and then the distribution locations).

Neither program identifies a "Potentially Dangerous Situation"
box.

Steve Chiswell



>From: "Patrick L. Francis" <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200412072222.iB7MMQlI011346

>
>>Note that gpmap also has warning capabilities now, but gpwarn
>>will still work as you have done.
>
>re gpmap...
>
>the advancements with gpmap seem to make gpwarn almost
>unnecessary :) ... however I'm afraid my learning curve may
>not quite be up to par...
>
>example 1:
>
>  the way i read the docs on the watch parameter
>http://my.unidata.ucar.edu/content/software/gempak/help_and_documentation/manu
> al/chap3/chap3.php?parm=watch
>
>states that we can differentiate between thunderstorm
>and tornado watches, and specify our 'preferred' colors
>for each (tyvm!) ... however, it can not differentiate
>and color code the difference between a PDS watch
>and standard watch.. is that correct?
>
>example 2:
>
>on the excitement of being able to predefine
>colors i began the process of outlining wstm
>parameters... now.. according to these docs:
>http://my.unidata.ucar.edu/content/software/gempak/help_and_documentation/manu
> al/chap3/chap3.php?parm=colors
>
>we can specify an RGB value for a color
>to make it what we want.. for example
>i wanted to try a white / vanilla / gray coloration
>as follows:
>
>!##### winter storm warning, winter storm watch, winter storm advisory
>WSTM = LAST|31;1;4=255:0:224|N|N|Y (won't take gray)
>
>assuming my syntax was incorrect i tried several
>variations to no avail.
>
>example #3 ... I can not seem to find a way to
>allow gpmap to draw smaller county outlines.. i.e.
>county outlines in a line-size of '1'
>
>ref current sample: http://unidata.bgsu.edu:81/data/gempak/web/chiztest.gif
>
>>I like your legend.
>
>ty.. it will be better once i work out my kinks :)
>
>
>#3 .. clarification
>
>>bulletin it it includes that, but is doesn't parse the bulletin for the "$$"
>>pieces.
>
>to make sure i understood this portion, ldm / pqact 'can not' (as it is)
>write data to a file structure based upon state in a semi-iwin format?
>
>>Robb Kambic had a perl decoder to chop out zones I believe that
>>would be a good starting point if needed to modify for
>>other types of products.
>
>never heard of him but sounds like a nice guy :)
>
>thanks again..
>
>--patrick
>
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publicly available
through the web.  If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.