[Shake-dev] Seattle high-resolution shakemap

Bill Gustafson billg at ess.washington.edu
Thu Jan 25 01:49:15 GMT 2007


Hmmm....
 
Never mind, at least until I get to the next sticking point.  I adjusted 
the mmi_xres and mmi_yres to 7.1c, and it worked.  I've run into this 
before - something about our configuration makes nearneighbor fail, when 
the resolutions are the same, but when you use grd_sample (for a finer 
grid) it's okay.

Thanks,

Bill

Bill Gustafson wrote:
> Hi All,
>
> I'm trying to implement a high resolution version of shakemap for the 
> Seattle area.
> My approach is to take our existing low-resolution shakemap and modify 
> it as needed.  Is this reasonable, our am I shooting myself in the 
> foot already?
>
> I am trying to use the strictbound entry in grind.conf.  This worked 
> okay in the low resolution version, to limit the display output to the 
> area that I wanted (strictbound : -122.55 47.34 -121.9 47.92)
>
> I have a site velocity data set that has been created at 0.002 degree 
> resolution.  I have set my input grid and output grid in grind to this 
> (7.2 seconds, right?).
>
> I set the lonspan to 0.5 which is less than the  the .65  degrees  
> that my velocity data set had.  If this isn't set, grind proceeded to 
> consume all of the available memory on my system, and eventually 
> output an out of memory error.
> Anyway, grind appears to work okay with that.  Mapping then fails with 
> a problem finding the mmi.grd file as:
>
> Done with tvmap
> Running: /usr/local/GMT4.0/bin//grdimage 
> /cwd2/earthworm-crepitio/SEASHAKE/bin/../data/0102281854/mapping/mmi.grd 
> -P -R-122.401004/-121.901004/47.579/47.919/10/3000 -JM10.0 
> -C/cwd2/earthworm-crepitio/SEASHAKE/bin/../lib/mapping/Ii_ntsc.cpt
> grdimage: No such file or directory 
> [/cwd2/earthworm-crepitio/SEASHAKE/bin/../data/0102281854/mapping/mmi.grd] 
>
> mapping: Error running command:
> /usr/local/GMT4.0/bin//grdimage 
> /cwd2/earthworm-crepitio/SEASHAKE/bin/../data/0102281854/mapping/mmi.grd 
> -P -R-122.401004/-121.901004/47.579/47.919/10/3000 -JM10.0 
> -C/cwd2/earthworm-crepitio/SEASHAKE/bin/../lib/mapping/Ii_ntsc.cpt|
>
> I've attached my grind.conf and mapping.conf - anyone have any insight?
>
> Thanks,
>
> Bill
>
> ------------------------------------------------------------------------
>
> # VERSION: 1.32	DO NOT REMOVE OR CHANGE THIS LINE
> ###########################################################################
> # ampfactor_file
> # File containing the amplitude corrections for velocity and acceleration
> # as a function of Q/T/M and amplitude; the path is relative to $shake_home;
> # there is no default -- this field is require d if -qtm is specified
> ###########################################################################
> ampfactor_file		: lib/sitecorr/site_corr_cdmg.dat
>
> ###########################################################################
> # qtm_file
> # File of site shear velocity as a function of position; the path is 
> # relative to $shake_home; there is no default -- this field is required
> # if -qtm is specified
> ###########################################################################
> #qtm_file		: lib/sitecorr/usgs_cgs_geology_60s.bin
> # New file from Eli 1/04
> #qtm_file                : lib/sitecorr/waor45.bin
>
> qtm_file                : lib/sitecorr/sea_hires.bin
>
> ###########################################################################
> # stavel_file
> # File of site shear velocity for seismic stations; the path is 
> # relative to $shake_home; there is no default -- this field is required
> # if -qtm is specified (unless you are running the Global ShakeMap system);
> # the file format is:
> #
> #	"Latitude","Longitude","Site","Ptype"
> #	lat,lon,station_code,shear_velocity
> #	...
> #
> # Note that the first line of the file is ignored, and could be blank.
> ###########################################################################
> stavel_file             : lib/grind/dig_pnw.txt
> #stavel_file		: lib/grind/socalmasterstatlist.txt
>
> ###########################################################################
> # Culling radii:
> #	cthresh - epicenter to station distance within which the computed
> #                 epicenter will not be used as a data point
> #	pthresh - phantom (richter) station to real station distance within 
> #                 which the phantom will not be used as a data point
> #
> # Defaults:
> #	cthresh		 0.0
> #	pthresh		 0.0
> ###########################################################################
> #cthresh		: 15.0
> #pthresh		: 10.0
> # JJL -- One of the old parameters seems to have gone away here.  I'm going
> # to put the old one here, but comment it out.
> # creject is in the old file, but wasn't initially in this one.
> # WTG - 17 Apr 06 - ditto
> cthresh         : 15.0
> pthresh         : 10.0
> #creject         : 25.0
>
>
>
> ###########################################################################
> # The input and output grid intervals specify the sample rate of the 
> # interpolated grids manipulated (input_?_grid_interval) or output 
> # (output_?_grid_interval) by grind; the default is 1.5 minutes
> #
> # input_x_grid_interval  : <floating point value><units>
> # output_x_grid_interval : <floating point value><units>
> # input_y_grid_interval  : <floating point value><units>
> # output_y_grid_interval : <floating point value><units>
> #
> # Where <units> is one of:
> #	m => minutes
> #	c => seconds
> #
> # e.g.:
> #	input_x_grid_interval	: 30c
> #	output_x_grid_interval	: 2.5m
> #
> # (and both input_ and output_y_grid_interval would default to 1.5m).
> ###########################################################################
> #input_x_grid_interval	: 1m
> #output_x_grid_interval	: 1m
> #input_y_grid_interval	: 1m
> #output_y_grid_interval	: 1m
>
> # Copied from old files by JJL 1-29-2004
> # Copied from old files by WTG 17 Aug 06 - comments are JJL's
> # Original input
> # input_x_grid_interval : 1.5m
> # changed for eli at 45 seconds
> #input_x_grid_interval   : 45c
> input_x_grid_interval   : 7.2c
> #Original output changed by JJL because nearneighbor complains about the larger grid not dividing evenly into the map size.
> #output_x_grid_interval  : 1.5m
> #output_x_grid_interval  : 45c
> output_x_grid_interval  : 7.2c
> # Original
> #input_y_grid_interval  : 1.5m
> # changed for eli
> #input_y_grid_interval   : 45c
> input_y_grid_interval   : 7.2c
> #Original output changed by JJL (see above comment)
> #output_y_grid_interval  : 1.5m
> #output_y_grid_interval  : 45c
> output_y_grid_interval  : 7.2c
>
>
>
> ###########################################################################
> # surface_tension provides the value passed to the GMT 'surface' program
> # via the -T option; the value must be between zero and one; the default
> # is 0.4, but we've changed it to 0.9 here because that seems to pull
> # the amplitude at the edges of the map down to the data point better.
> ###########################################################################
> # The one in the old file was 0.4, I'm leaving it here fo rhe moment. JJL 1-29-2004
> # WTG 17 Apr 06 - and then must have changed it bacl - it was 0.9 when
> #I copied it over
> surface_tension		: 0.9
>
> ###########################################################################
> # mapbuf determines the amount of padding to add to the edges of the
> # mapped region to avoid quirkiness at the map edges; the default is
> # 0.4 degrees to each edge
> ###########################################################################
> mapbuf	: 0.0
> #mapbuf	: 0.1
> #mapbuf	: 0.4
>
> ###########################################################################
> # lonspan specifies the width of the map in degrees of longitude; this 
> #   value can be overridden on the command line; the default is 2.5
> # latspan specifies the height of the map in degrees of latitude; this
> #   value can be overridden on the command line; the default value is
> #   'llratio * lonspan'
> # llratio specifies the latspan/lonspan ratio to use when setting latspan
> #   when latspan is not specified either here or on the command line; the 
> #   default is the cosine of the event latitude.  Most regions will want
> #   to specify a fixed ratio in order to generate maps of a consistent
> #   shape.  Regions that span very large areas of latitude may find
> #   it easier to not specify llratio below and let the default system
> #   take over.
> ###########################################################################
> # WTG - 17 Apr 06 - not specified in version on Magro
>
> #llratio : 0.666667
>
> ###########################################################################
> # bad_station specifies stations to flag as bad under certain circumstances
> # the format of the statement is:
> #
> #	bad_station : code mag start_date-[end_date [mag start_date-[...]]]
> #
> # Where 'code' is the station code, 'mag' is the event magnitude cutoff 
> # below which the station is considered bad, 'start_date' is the event 
> # date to begin applying the cutoff, and 'end_date' is the event date 
> # at which the cutoff no longer applies; dates are given in the yyyymmdd
> # format, and are UTC (i.e. GMT) dates; a missing end date implys dates 
> # inclusive of the current date; multiple 'mag start_date-end_date' groups 
> # are allowed, e.g.:
> #
> #	bad_station : BC3 3.8 19990101-19990407 2.2 19990407-
> #
> # In the above example, the station 'BC3' will be flagged as bad for
> # events smaller than 3.8 from January 1, 1999 to April 7, 1999 and
> # for events smaller than 2.2 from April 7, 1999 to the present.  The
> # station will not be flagged for events before January 1, 1999
> ###########################################################################
> #bad_station             : RIN 9.9 20011001
> #bad_station		: DAN 9.9 20010105-20010302
>
> #bad_station		: MWC 4.0 19980101-
> #bad_station		: BC3 3.8 19980101-
> #bad_station		: PLS 4.1 19980101-
> #bad_station		: BAR 3.8 19980101-
> #bad_station		: ELC 3.8 19980101-
> #bad_station		: MPM 9.9 19980101-
>
> bad_station             : WMC 3.0 19980101-
>
> ###########################################################################
> # regression specifies which regression relation to use for particular
> # magnitude ranges. Regressions are defined by the name of the module that
> # encapsulates its rules.
> # 
> # The format of the statement is:
> #
> #	regression : regression-module min-mag max-mag [depth-min depth-mag]
> #
> # Where 'regression-module' is the name of the module for the regression
> # relation, 'min-mag' and 'max-mag' are the minimum and maximum magnitudes
> # over which the relation should be used.
> #
> # For example:
> #
> #	regression : BJF97 0.0 9.9 0 30
> #
> # In the above example, the module Regression::BJF97 will be used to 
> # calculate the regression values for events over the magnitude range of 
> # 0.0 <= mag < 9.9 and for depths < 30 km.
> #
> # Multiple regression: lines can be used, in which case the first line
> # that meets the current magnitude and depth parameters.
> #
> # If the event has no depth parameter then the regression: depth limits are 
> # ignored.
> #
> ###########################################################################
> regression : HazusPGV 4.3 9.9 0 39
> regression : Youngs97 0.0 9.9 39 100
> regression : Small 0.0 4.3 0 39
> #regression : HazusPGV 5.3 9.9 
> #regression : Small 0.0 5.3
>
> ###########################################################################
> # outlier_deviation_level specifies how many standard deviations define
> # an outlier.
> # 
> # The format of the statement is:
> #
> #	outlier_deviation_level : level
> #
> # Where 'level' is the number of standard deviations defining outliers.
> # This number can be any positive float. The default is 3.
> #
> # outlier_max_mag specifies a magnitude above which the automatic flagging
> # of outliers will no longer take place (this cutoff will have no effect
> # on manually flagged stations placed in the flagged_stations.txt file in
> # the input directory (which always supersedes any automatic flagging);
> # the purpose of this parameter is to prevent valid data from being 
> # flagged because a long fault rupture might cause stations far from
> # the epicenter but close to the rupture to show very high amplitudes;
> # the default is 7.0; The format of the statement is:
> #
> #	outlier_max_mag : magnitude
> #
> # Examples:
> #
> #	outlier_deviation_level : 2
> #	outlier_max_mag         : 8.2
> #
> ###########################################################################
> outlier_deviation_level : 3
> outlier_max_mag         : 7.0
>
> ###########################################################################
> # pga_accepted_halfwidth and pgv_accepted_halfwidth specify the minimum 
> # regions above and below the pga and pgv regression curves in which data 
> # values must be accepted (not flagged as outliers). This halfwidth 
> # overrides the outlier bounds based on the standard deviation of the 
> # regression curve, which may be very narrow, particularly at large distances.
> # 
> # The format of the statement is:
> #
> #	pga_accepted_halfwidth : halfwidth
> #	pgv_accepted_halfwidth : halfwidth
> #
> # Where 'halfwidth' is a positive float. The default for both parameters
> # is 0.01.
> ###########################################################################
> # WTG - 17 Apr 06 set to values from Magro
> #pga_accepted_halfwidth : 0.01
> #pgv_accepted_halfwidth : 0.01
> pga_accepted_halfwidth : 0.3
> pgv_accepted_halfwidth : 0.3
>
> ###########################################################################
> # estimate_x_grid_interval and estimate_y_grid_interval specify the size
> # of grid elements in the grids of estimated amplitude values. Values are
> # in units of degrees.
> #
> # The estimate grid is normally much coarser than the input or output
> # grids. It is used to fill large gaps in the data distribution and is
> # applied prior to interpolation to the "input" grid defined above.
> # 
> # The format of the statements is:
> #
> #	estimate_x_grid_interval : interval
> #	estimate_y_grid_interval : interval
> #
> # Where 'interval' is a positive float. The default for both parameters
> # is 0.3 degrees.
> ###########################################################################
> # WTG - 17 Apr 06 set to values from Magro
> #estimate_x_grid_interval : 0.1
> #estimate_y_grid_interval : 0.1
> estimate_x_grid_interval : 0.1
> estimate_y_grid_interval : 0.1
>
> ###########################################################################
> # bias parameters: because the attenuation relations are averages of events
> # of varying mechanisms, they do no necessarily accurately reflect the
> # mechanics of any specific event, nor are we guaranteed that the initial
> # earthquake magnitude is accurate.  To overcome these deficiencies, we
> # compute a factor by which the predicted ground motions are multiplied
> # to bring them in line with the event data.  This factor is computed by
> # minimizing the difference between the data values at the seismic stations
> # and the estimated values at those locations.  The minimization is in 
> # either a least squares sense or an absolute deviation sense.  Because
> # there is naturally a lot of scatter in seismic data, the absolute
> # deviation (i.e. L1 norm) seems like a better bet and, in fact, has
> # proved to be so in practice.
> #
> # bias_norm: acceptable values are 'l2' (for least squares) or 'l1' (for
> #   absolute deviation); the default is 'l1'.
> # bias_max_range: distance (in kilometers) beyond which seismic stations 
> #   will be excluded from the bias calculation; this helps to insure that 
> #   the bias is computed using the (hopefully) more accurate near-source 
> #   data; the default is 120km.
> # bias_min_stations: sets the minimum number of seismic stations (within the 
> #   search radius that are required to compute the bias; fewer than this 
> #   number will result in the bias being set to 1.0, and a warning message 
> #   being issued; the default is 6.
> # bias_max_mag: earthquake magnitude above which the bias calculation is
> #   not performed; this insures (for areas like southern California) that
> #   a long fault rupture will not confuse the bias calculation; the default
> #   is 7.0.
> # bias_max_bias: the maximum value that the bias is allowed to take; this
> #   is the maximum factor by which all estimates (including, possibly, the 
> #   centroid) are multiplied; the default is 4.0; this parameter also
> #   sets the minimum bias, which is (1.0 / bias_max_bias).
> # bias_log_bias: determines whether the bias is calculated with linear
> #   or log amplitude.  Valid values are 'true' and 'false'.  Defaults 
> #   to false in order to maintain consistency with earlier versions.
> #
> # Examples:
> #
> #	bias_norm         : l1
> #	bias_max_range    : 120
> #	bias_min_stations : 6
> #	bias_max_mag      : 7.0
> #	bias_max_bias     : 4.0
> #	bias_log_amp	  : true
> #
> ###########################################################################
> # WTG - 17 Apr 06 set to values from Magro
> bias_norm         : l1
> #bias_max_range    : 120
> bias_max_range    : 150
> #bias_min_stations : 6
> bias_min_stations : 4
> #bias_max_mag      : 7.0
> bias_max_mag      : 6.5
> bias_max_bias     : 4.0
> bias_log_amp	  : false
>
> ###########################################################################
> # For scenarios: 
> # master list of stations for forward modeling (if not specified, 
> #	uses stavel_file)
> # filename to dump forward estimates
> # forward modeling estimate grid intervals and number of grids
> ###########################################################################
> #fwstatlist		: lib/grind/socalmasterstatlist.txt
> fwstatlist              : lib/grind/dig_pnw.txt
> fwdata_file		: forward.xml
>
> ###########################################################################
> # These are the defaults for the estimate grid for scenarios
> # (much finer than the usual richter coarse grid)
> # fw_x_grid_interval : 0.075
> # fw_y_grid_interval : 0.075
> ###########################################################################
> fw_x_grid_interval : 0.075
> fw_y_grid_interval : 0.075
>
> ###########################################################################
> # rounding_fix: correction factor ADDED to lat/lon map boundary to fix
> # roundoff errors if the map boundary is past the edge of the QTM grid.
> # Playing with the rounding_fix parameter in grind.conf may fix this. 
> # The order is N S E W
> # Default is 0 0 0 0 (no correction)
> #
> # For Utah:
> # rounding_fix: 0.000 0.0001 -0.0001 0.000
> #
> # (from Kris Pankow)
> ###########################################################################
> #rounding_fix: 0.000 0.0001 -0.0001 0.000
>
>
> ###########################################################################
> # strictbound: fixes the map in place and size given by the argument.
> # There is no default and this parameter is not required.
> # Usage:
> #
> #	strictbound : W/S/E/N
> #
> # For example:
> #
> #	strictbound : -118.5/33.5/-117.5/34.25
> #
> # Would center a 1.0 degree by 0.75 degree map approximately over Los
> # Angeles.
> #Seattle Shakemap
> #47.34 - 47.92
> #   121.9 122.55
> #strictbound : -122.55/47.34/-121.9/47.92
> ###########################################################################
> strictbound : -122.55 47.34 -121.9 47.92
>
>   
> ------------------------------------------------------------------------
>
> # VERSION: 1.33	DO NOT REMOVE OR CHANGE THIS LINE
> ###########################################################################
> # organization
> # Specify the name of the map-producing organization for inclusion in
> # map titles; don't get carried away here, there isn't much room; statement
> # format is:
> #
> #	organization : Name of Organization
> #
> # Example:
> #
> #	organization : USGS
> #
> ###########################################################################
> organization : PNSN 
>
> ###########################################################################
> # mmi_?res specify the spatial resolution of the mmi grid; these values
> # MUST be set to the same resolution as the standard topography;
> # mmi_?hires specify the spatial resolution of the mmi grid when the
> # "-hires" option is used; the values MUST be set to the same resolution
> # as the high-resolution topography (if high-resolution topography is used).
> # The hires values are only important if mapping is run with -hires.
> # The statement format is:
> #
> # mmi_xres   : <floating point value><units>
> # mmi_yres   : <floating point value><units>
> # mmi_xhires : <floating point value><units>
> # mmi_yhires : <floating point value><units>
> #
> # Where <units> is one of:
> #	' ' => degrees (i.e. no units specified)
> #	'm' => minutes
> #	'c' => seconds
> #
> # e.g.:
> #	mmi_xres   : 0.5m
> #	mmi_yres   : 0.5m
> #	mmi_xhires : 0.05m
> #	mmi_yhires : 0.05m
> #
> # The default value is '30c' for low-resolution and 3c for high-resolution.
> ###########################################################################
> # WTG - 17 Apr 06 - updated from Magro
> #mmi_xres	: 9c
> #mmi_yres	: 9c
> #mmi_xres        : 31.0c
> #mmi_yres        : 31.0c
> #mmi_xhires	: 3c
> #mmi_yhires	: 3c
> mmi_xres        : 7.2c
> mmi_yres        : 7.2c
> mmi_xhires	: 7.2c
> mmi_yhires	: 7.2c
>
> ###########################################################################
> # network_color specifies the fill color of the stations plotted on the
> # maps based on the source network.  The color codes are defined in
> # colors.conf.  The default is yellow.  Statement format:
> #
> #	network_color : <network_code> <color code> [<symbol> [<size>]]
> #
> # The network code is the official two-character network code 
> # assigned to the source network and is given by the "netid" attribute
> # of the "station" tag in the input XML. The symbol is the symbol code
> # given to the GMT program 'psxy' via the -S option.  See the psxy man
> # page for information on the allowable symbols (but common ones are:
> # a = star, c = circle, d = diamond, s = square, t = triangle, x = cross).
> # The default symbol is 't' (triangle).  Size is the size of the symbol as 
> # defined by psxy. The default size is given by the station_size parameter 
> # elsewhere in this file, and defaults to 0.12.
> #
> # Example:
> #
> #	network_color : CE blue t 0.12
> #
> # This parameter is intended to replace "station_color" (see below), 
> # however both are still used to facilitate the transition.  
> # network_color is used preferentially over station_color
> # Known networks:
> #	CI	SCSN
> #	CE	CGS/CSMIP
> #	AZ	ANZA
> #	NP	NSMP
> #	NC	NCSN
> #	BK	Berkeley
> #	NN	Nevada
> #	XP	Tremor
> #	PG	PG&E
> #	HI	Historic
> #	UK	Unknown
> #	US	US National Network
> ###########################################################################
> #network_color   : CI red t 0.12
> #network_color   : CE blue t 0.12
> #network_color   : AZ yellow t 0.12
> #network_color   : NP green t 0.12
> #network_color	: NC orange t 0.12
> #network_color	: BK turquoise t 0.12
> #network_color   : NN darkblue t 0.12
> #network_color   : XP darkgreen t 0.12
> #network_color   : PG magenta t 0.12
> #network_color   : HI yellowgreen t 0.12
> network_color   : UK grey t 0.12
> network_color   : US darkred t 0.12
> network_color   : UW red t 0.12
> network_color   : NP blue t 0.12
>
> ###########################################################################
> # station_color specifies the fill color of the stations plotted on the
> # maps based on the source network. The color codes are defined in 
> # colors.conf. The default is yellow.  Statement format:
> #
> #	station_color : <color code> <network>
> #
> # where <network> specifies the data source from the stationlist.dtd, and
> # <color code> specifies the color code from colors.conf.  The network
> # should be the exact string found in the 'source' attribute of the input
> # XML file (e.g. "SCSN and Trinet" or "ANZA Regional Network").
> #
> # NOTE: This parameter is now deprecated.  network_color should be used
> # instead.
> # station_color   : red SCSN and TriNet
> # station_color   : red SCSN
> # station_color   : blue CDMG
> # station_color   : blue CGS
> # station_color   : blue California Strong Motion Instrumentation Program
> # station_color   : yellow ANZA Regional Network
> # station_color   : green NSMP
> # station_color   : green United States National Strong-Motion Instrumentation Network
> # station_color   : green United States National Strong-Motion Network
> # station_color   : green HIST
> ###########################################################################
> station_color   : red PNSN
> station_color   : blue NSMP
> station_color   : cyan USNSN
> station_color   : orange OTHER
>
>
>
> ###########################################################################
> # station_symbol -- specifies the symbol used to identify seismic stations
> # on the maps if they are not specified by network_color statements; See
> # the manual page for the GMT command 'psxy' for allowable values; the
> # default is 't' (for triangle).
> #
> # station_size -- specifies the size of the station symbols on the maps, 
> # in inches, if they are not specified by network_color statements; the 
> # default is 0.12.
> #
> # Statement format:
> #
> #	station_symbol : <symbol_character>
> #	station_size   : <size in inches>
> #
> ###########################################################################
> station_symbol 	: t
> station_size 	: 0.10
> #station_size 	: 0.12
>
> ###########################################################################
> # estimate_symbol -- specifies the symbol used to identify the "phantom"
> # stations (i.e., the estimated ground motion control points); see
> # the manual page for the GMT command 'psxy' for allowable values; the
> # default is 'c' (for circle).
> #
> # estimate_size -- specifies the size of the symbols used to identify
> # the "phantom" stations, in inches; the default is 0.06.
> #
> # Statement format:
> #
> #	estimate_symbol : <symbol_character>
> #	estimate_size   : <size in inches>
> #
> ###########################################################################
> estimate_symbol	: c
> estimate_size	: 0.06
>
> ###########################################################################
> # contour_color specifies the color of the PGA/PGV contours on the maps;
> #   the default is yellow
> # ncontours is the approximate number of contours on the contour plots
> # contour_width specifies the width of the PGA/PGV contours (default 8)
> # highway_color specifies the color of the highways (default darkgrey)
> # highway_width specifies the width of the highways (default 8)
> # fault_color specifies the color of the faults (default darkred)
> # fault_width specifies the width of the faults (default 8)
> # border_width specifies the width of the state/national/coastal 
> #   borders (default 8)
> # water_color specifies the color of the wet areas (default lightblue)
> # epicenter_color specifies the fill color of the star (black outline)
> #   that marks the epicenter (default is for an unfilled star)
> # epicenter_size determines the size of the star that represents the
> #   earthquake epicenter, in inches
> # main_title_size is the font size of the main title at the top of the plots
> # sub_title_size is the font size of the subtitle at the top of the plots
> # city_dot_size specifies the size, in inches, of the dot marking the
> #   locations of cities
> # city_name_size: point size of the font used to label cities (this
> #   parameter is overridden if the *_label versions of the city files
> #   are used (see elsewhere in this config for an explanation of the _label
> #   versions of the city name files)
> # tv_* are the equivalent of the non-tv parameters above, but are used
> #   to configure the TV map
> #
> #       contour_color     : <color code>
> #	ncontours	  : <number of contours>
> #	contour_width     : <line width>
> #	highway_color     : <color code>
> #	highway_width     : <line width>
> #	fault_color       : <color code>
> #	fault_width       : <line width>
> #	border_width      : <line width>
> #	water_color       : <color code>
> #	epicenter_color   : <color code>
> #	epicenter_size    : <symbol size in inches>
> #	main_title_size   : <font point size>
> #	sub_title_size    : <font point size>
> #	city_dot_size	  : <symbol size in inches>
> #	city_name_size    : <font point size>
> #	tv_highway_width  : <line width>
> #	tv_highway_color  : <color code>
> #	tv_border_width   : <line width>
> #	tv_city_dot_size  : <symbol size in inches>
> #
> # where <color code> specifies a color code defined in colors.conf.
> ###########################################################################
> # WTG - 17 Apr 06 - Mods from Magro
> #contour_color	  : white
> contour_color     : yellow
> ncontours	  : 8
> #contour_width	  : 5
> contour_width     : 8
> #highway_color	  : lightgrey
> #highway_width	  : 6
> highway_color     : darkgrey
> highway_width     : 4
> fault_color	  : darkred
> fault_width	  : 4
> #border_width	  : 5
> border_width	  : 2
> water_color	  : lightblue
> #epicenter_size	  : 0.30
> epicenter_size	  : 0.12
> main_title_size   : 15
> sub_title_size    : 12
> city_dot_size	  : 0.08
> city_name_size    : 9
> tv_highway_width  : 8
> tv_highway_color  : lightgrey
> tv_border_width   : 10
> tv_city_dot_size  : 0.08
>
> ###########################################################################
> # ff_width/ff_color specify the width and color of the finite fault (when
> # one is supplied in the input directory.  ff_width is given in points,
> # ff_color is one of the colors given in color.conf.  The defaults are:
> # ff_width (12), ff_color (darkgrey).
> #
> # Example:
> #
> #	ff_width : 9
> #	ff_color : black
> #
> ###########################################################################
> ff_width : 12
> ff_color : darkgrey
>
> ###########################################################################
> # xorig/yorig specify the position (in inches) of the lower left corner
> # of the maps, effectively specifying the left and bottom margins of the
> # plots.
> # Statement format:
> #
> #	xorig : <position>
> #	yorig : <position>
> #
> # Where <position> is given in inches; the default is 1.0 inches for both
> # xorig and yorig
> ###########################################################################
> xorig		: 1.0
> yorig		: 1.0
>
> ###########################################################################
> # width specifies the width (in inches) of the maps.
> # tvwidth specifies the width (in inches) of the tvmaps.
> # Statement format:
> #
> #	width   : <width>
> #	tvwidth : <width>
> #
> # Where <width> is given in inches; the default is 6.5 inches for the
> # normal maps, 10.0 inches for the tvmaps.
> # Note: the height of the map will be determined by the width, lonspan, 
> # latspan and the projection used; the value for any given map can be
> # found in the <shake_home>/data/<event_id>/mapping directory in the
> # file "geometry_map.txt"
> ###########################################################################
> width		: 6.5
> tvwidth		: 10.0
>
> ###########################################################################
> # map_axes specifies the format for the plotting and annotation of the
> # the axes on the maps.
> # Statement format:
> #
> #	map_axes : <string>
> #
> # Where <string> is the string to be given as the argument to the -B
> # flag of the GMT psbasemap command; the default is 'a60mf30mWSen'.
> ###########################################################################
> #map_axes	: a60mf30m/a30mf30mWSen
> map_axes	: a15mf15m/a15mf15mWSen
>
> ###########################################################################
> # map_data_dir: A directory in which one may store various map files; this
> # entry is only used to substitute for the "<MAP_DIR>" string in config
> # statements below; the string "<SHAKE_HOME>" in the value portion of this
> # statement will be replaced with the path of the ShakeMap installation;
> # this statement is not required and will default to <shake_home/lib/mapping
> # the statement has the form:
> #
> #	map_data_dir : <path>
> #
> ###########################################################################
> map_data_dir	: <SHAKE_HOME>/lib/mapping
>
> ###########################################################################
> # topo_cmap, ii_cmap, ii_tvmap_cmap: GMT colormaps used for topography,
> # the instrumental intensity map, and the TV version of the instrumental 
> # intensity map, respectively; these entries are required, though they 
> # could be empty files if you do not plot topography or II or the TV map, 
> # respectively; the statements have the form:
> #
> #	topo_cmap     : <path>
> #	ii_cmap       : <path>
> #	ii_tvmap_cmap : <path>
> #
> # sd_cmap is the GMT colormap used for the uncertainty (standard
> # deviation) maps.  It uses the same form as the other statements:
> #
> #	sd_cmap	      : <path>
> #
> # If path contains the string "<MAP_DIR>", it will be replaced with the
> # path given by map_data_dir (see above)
> ###########################################################################
> topo_cmap	: <MAP_DIR>/tan.cpt
> ii_cmap  	: <MAP_DIR>/Ii.cpt
> ii_tvmap_cmap  	: <MAP_DIR>/Ii_ntsc.cpt
> sd_cmap         : <MAP_DIR>/sd.cpt
>
> ###########################################################################
> # Map statements; if omitted, the corresponding feature will not be plotted;
> # see the mapping program for file format documentation and the southern 
> # California files supplied with the distribution for examples of these
> # files; the statements are:
> #
> #	map_roads           : <path>
> #	map_faults          : <path>
> #	map_cities          : <path>
> #	map_cities_label    : <path>
> #	map_topo            : <path>
> #	map_topo_hires      : <path>
> #	map_intensity       : <path>
> #	map_intensity_hires : <path>
> #
> # map_topo is the normal GMT (.grd) topography file; 
> # map_topo_hires is the high-resolution topography used by the -hires 
> #  option -- specifying the high-resolution topography files is not 
> #  necessary unless mapping is run with -hires.  Many regions use the
> #  resolution topography by default and therefore do not need to specify
> #  this parameter; 
> # map_intensity is an optional file that contains the pre-computed 
> #  topographic intensity from the map_topo file; if map_intensity is 
> #  omitted or does not exist, the intensity will be computed using 
> #  grdgradient with the options -A325 -Nt; if the file is specified but 
> #  does not exist, it will be written to the specified location, otherwise 
> #  it will be "<MAP_DIR>/intensity.grd"; the same holds for 
> #  map_intensity_hires, but if unspecified it will be written to 
> #  "<MAP_DIR>/intensity_hires.grd"; if this is going to happen,
> #  make sure that the user running mapping has permission to write in 
> #  these directories.
> #
> # map_cities consists of three space-separated columns: lon, lat, and 
> #  city name (multiple word names are supported).  If the city name is 
> #  followed with a '#', the city is not plotted on the map.  If map_cities
> #  is used, the city name will be centered above the dot representing
> #  the city.  The bottom of the city name text will be 0.02 degrees
> #  above the dot.
> #
> # map_cities_label allows for greater control of the placement and style
> #  of the city name as it appears on the plot.  If map_cities_label is 
> #  defined, it will be used in preference to map_cities.  The file specified 
> #  by map_cities_label has nine columns:
> #	latitude		: the latitude of the city
> #	label_lat_offset	: the latitude offset of the label from
> #				  the city location (relative to "justify")
> #	longitude		: the longitude of the city
> #	label_lon_offset	: the longitude offset of the label from
> #				  the city location (relative to "justify")
> #	font_size		: the text font size as defined by pstext
> #	angle			: the text angle as defined by pstext
> #	font			: the text font as defined by pstext
> #	justify			: the text justification as defined by pstext
> #	city_name		: the name of the city
> #  As with map_cities, if the city name is followed by a '#' the city
> #  will be omitted.  See the GMT documentation for 'pstext' for an
> #  explanation of the various fields.  The _label form of map_cities
> #  is now perferred.
> #
> # If path contains the string "<MAP_DIR>", it will be replaced with the
> # path given by map_data_dir (see above)
> ###########################################################################
> # WTG 17 Apr 06 - change from Magro
> map_roads       : <MAP_DIR>/pnw_hiway_big.txt
> map_faults      : <MAP_DIR>/pnw_faults.txt
> map_cities      : <MAP_DIR>/pnw_cities.txt
> map_topo  	: <MAP_DIR>/pnw_30.grd
> #map_roads	    : <MAP_DIR>/ca_roads.xy
> #map_faults          : <MAP_DIR>/ca_faults.xy
> #map_cities	    : dummy
> #map_cities_label    : <MAP_DIR>/us_cities.txt
> #map_topo  	    : <MAP_DIR>/cal_neva_9c.grd
> #map_intensity  	    : <MAP_DIR>/cal_neva_9ci.grd
> #map_topo_hires      : <MAP_DIR>/cal_neva_9c.grd
> #map_intensity_hires : <MAP_DIR>/cal_neva_9ci.grd
>
> ###########################################################################
> # big_cities: a list of large cities suitable for the TV map
> # very_big_cities: a list of very large cities suitable for the TV map
> #                  at large scales
> #
> # big_cities_label and very_big_cities_label are also supported.  See
> # the discussion of map_cities_label, above, for the file format.
> # As with big_cities_label, the _label versions of these parameters
> # are now preferred.
> ###########################################################################
> # WTG 17 Apr 06 - change from Magro
> big_cities              : <MAP_DIR>/pnw_bigcities.txt
> #big_cities_label        : <MAP_DIR>/bigcities_label.txt
> very_big_cities         : <MAP_DIR>/pnw_bigcities.txt
> #
> #big_cities		: dummy
> #big_cities_label	: <MAP_DIR>/ca_bigcities_label.txt
> #very_big_cities		: dummy
> #very_big_cities_label	: <MAP_DIR>/ca_verybigcities_label.txt
>
> ###########################################################################
> # use_gmt_coast: determines whether or not the gmt command 'pscoast' is
> # used to draw the coastline and fill in the areas covered by water;
> # valid values are 'true' or 'false'; the default is 'true';
> #
> # Example:
> #
> #	use_gmt_coast : false
> #
> ###########################################################################
> # WTG 17 Apr 06 - change from Magro
> use_gmt_coast : true
>
> ###########################################################################
> # These parameters allow some customization of the intensity plot:
> #  faults_on_mmi determines whether or not the mapped fault traces will
> #    be plotted (the default is 'false')
> #  stations_on_mmi determines whether or not open triangles are plotted
> #    at the locations of the seismic stations (the default is 'true')
> #  filled_stations_on_mmi determines whether or not filled triangles are 
> #    plotted at the locations of the seismic stations (the default is 'false')
> #
> #	faults_on_mmi          : <true | false>
> #	stations_on_mmi        : <true | false>
> #	filled_stations_on_mmi : <true | false>
> ###########################################################################
> # WTG 17 Apr 06 - change from Magro
> #faults_on_mmi		: true
> faults_on_mmi		: false
> stations_on_mmi		: true
> filled_stations_on_mmi 	: true
>
> ###########################################################################
> # psxy_addon: allows for customized overlays by providing the user with
> # access to the GMT psxy command.  Multiple psxy_addon lines are supported,
> # and run in the order they appear.  psxy is run with the generic options
> # needed by ShakeMap (setting the map boundaries, -O -K, etc.).  The 
> # arguments to this option consist of a file name (the file is expected to
> # reside in the "map_data_dir", see above), followed by any special flags
> # that the user finds appropriate for psxy.  The file is expected to be
> # in a format that psxy will understand.  The layers are added on top of
> # the pscoast layer.  The default is to do nothing.
> #
> # For example the California ShakeMap groups set 'use_gmt_coast'
> # to false, and use these lines to draw their water boundaries:
> #
> #	psxy_addon : line_cal_coast.xy -M -G120/160/220
> #	psxy_addon : line_cal_ow_streams.xy -M -W1/100/140/200
> #	psxy_addon : line_cal_lakes.xy -M -G120/160/220 -W1/100/140/200
> #	psxy_addon : line_cal_drylakes.xy -M -W2/100/140/200
> #	psxy_addon : line_cal_islands.xy -M -W1/140/180/240
> #	psxy_addon : line_usa_west_borders.xy -M -W4/0/0/100
> #
> ###########################################################################
> # WTG 17 Apr 06 - change from Magro
> #psxy_addon : line_cal_coast.xy -M -G120/160/220
> #psxy_addon : line_cal_ow_streams.xy -M -W1/100/140/200
> #psxy_addon : line_cal_lakes.xy -M -G120/160/220 -W1/100/140/200
> #psxy_addon : line_cal_drylakes.xy -M -W2/100/140/200
> #psxy_addon : line_cal_islands.xy -M -W1/140/180/240
> #psxy_addon : line_cal_borders.xy -M -W4/0/0/100
>
> ###########################################################################
> # pstext_addon: allows for customized overlays by providing the user with
> # access to the GMT pstext command.  Multiple pstext_addon lines are supported,
> # and run in the order they appear.  pstext is run with the generic options
> # needed by ShakeMap (setting the map boundaries, -O -K, etc.).  The 
> # arguments to this option consist of a file name (the file is expected to
> # reside in the "map_data_dir", see above), followed by any special flags
> # that the user finds appropriate for pstext.  The file is expected to be
> # in a format that pstext will understand.  The layers are added on top of
> # the layer that prints city names.  The default is to do nothing.
> #
> # Example:
> #
> #	pstext_addon : fault_names.txt
> #
> ###########################################################################
> # WTG 17 Apr 06 - change from Magro
> #psxy_addon: north_ps_wat.txt -M -W2 -G120/160/220
> #psxy_addon: north_ps_wat.txt -M -W3
> #psxy_addon: south_ps_wat.txt -M -G120/160/220
> #psxy_addon: south_ps_wat.txt -M -W3
> #psxy_addon: ps_land.txt -M -G100/200/100
> #psxy_addon: ps_land.txt -M -W2
> # Fault trace for Seattle Fault Scenerio
> # psxy_addon:
>
>
> ###########################################################################
> # noscenariosplash: option to turn off 'Scenario' sign on scenario maps
> ###########################################################################
> noscenariosplash: false
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> Shake-dev mailing list
> Shake-dev at scsnmail.gps.caltech.edu
> http://unix1.gps.caltech.edu/mailman/listinfo/shake-dev
>   


-- 
Bill Gustafson          Res Eng/Sr Comp Spc
KSRSL/PNSN              Phone: (206)685-8266/(206)543-8928
Dept. of Earth and Space Sciences
Box 351310, UW, Seattle, WA  98195-1310
http://alumnus.caltech.edu/~billg/bill.htm





More information about the Shake-dev mailing list