, with the contents changed as follows:
is specified by editing to
;mapname="LR BkBlAqGrYeOrReViWh200" ; rainbow style, nv <= 17 mapname="LR BlWhRe" ; blue/white/red, nv <= 17
is specified by editing to
;mapname="LR BkBlAqGrYeOrReViWh200" ; rainbow style, nv <= 17 mapname="nrl_sirkes" ; NRL, nv <= 17
is specified by editing to
;mapname="LR BkBlAqGrYeOrReViWh200" ; rainbow style, nv <= 17 mapname="gsdtol" ; grayscale, nv <= 17
It may be an idea to change the color of land here...
is specified by editing to
;mapname="LR BkBlAqGrYeOrReViWh200" ; rainbow style, nv <= 17 mapname="default" ; tigerstripes, nv <= 17
contour.sh --help contour.sh / ncl-metno 1.2 >>> >>> >>> Syntax: >>> ======= >>> >>> contour.sh <option> <file> <variable> [<d3node> (<d4node>)] >>> where >>> <option> specifies dimensions and geo- or nongeo-grid >>> implemented: >>> [234]d - [234]D fields >>> [234]dmap - [234]D fields, dims. are lon & lat >>> [234]dMap - [234]D fields, lon & lat are 2d fields >>> ...[234]d[mM]ap will be displayed on a geogr. map >>> <file> name of the netcdf file >>> <variable> name of requested variable on the netcdf file >>> (case sensitive) >>> <d3node> node no. of third dimension >>> if <option> is one of 2d, 2dmap and a fourth >>> argument is present, or if <d3node> is negative, >>> this will be interpreted as a flag that will cause >>> the ncl script to remain (see examples below) >>> <d4node> node no. of fourth dimension >>> >>> Special case: >>> If <option> is one of [234]dMap, the name of the 2d longitude and >>> latitude variable may be specified on the command line: >>> contour.sh <option> <lonname> <latname> <file> <variable> [<d3node> (<d4node>)] >>> (Alternatively, if these names are not 'lon' or 'lat', 'userdef.ncl' may >>> be edited when option is one of [234]dMap.) >>> >>> The script will produce an eps-file and a png-file. >>> >>> >>> User specifications: >>> ==================== >>> >>> By copying the default spec.s from