|
gmtdefaults − To list current GMT defaults |
|
gmtdefaults −D[u|s] | −L |
|
gmtdefaults lists the GMT parameter defaults if the option −D is used. There are three ways to change some of the settings: (1) Use the command gmtset, (2) use any texteditor to edit the file .gmtdefaults4 in your home or current directory (if you do not have this file, run gmtdefaults -D > ~/.gmtdefaults4 to get one with the system default settings), or (3) overrid any parameter by specifying one or more −−PARAMETER=VALUE statements on the commandline of any GMT command (PARAMETER and VALUE are any combination listed below). The first two options are permanent changes until explicitly changed back, while the last option is emphemeral and only applies to the single GMT command that received the override. GMT can provide default values in US or SI units. This choice is determined by the contents of the gmt.conf file in GMT’s share directory. |
|
−D |
Print the system GMT defaults to standard output. Append u for US defaults or s for SI defaults. [−D alone gives current choice in gmt.conf]. |
||
|
−L |
Print the user’s currently active defaults to standard output. |
|
Your currently active defaults come from the .gmtdefaults4 file in the current working directory, if present; else from the .gmtdefaults4 file in your home directory, if present; else from the system defaults set at the time GMT was compiled. |
|
The following is a list of the parameters that are user-definable in GMT. The parameter names are always given in UPPER CASE. The parameter values are case-insensitive unless otherwise noted. The system defaults are given in brackets [ for SI (and US) ]. Those marked * can be set on the command line as well (the corresponding option is given in parentheses). Note that default distances and lengths below are given in both cm or inch; the chosen default depends on your choice of default unit (see MEASURE_UNIT). You can explicitly specify the unit used for distances and lengths by appending c (cm), i (inch), m (meter), or p (points). When no unit is indicated the value will be assumed to be in the unit set by MEASURE_UNIT. Note that the printer resolution DOTS_PR_INCH is always the number of dots or pixels per inch. Several parameters take only TRUE or FALSE. |
|
If the angle between the map boundary and the annotation baseline is less than this minimum value (in degrees), the annotation is not plotted (this may occur for certain oblique projections.) Give a value in the range 0−90. [20] |
|
If an annotation would be plotted less than this minimum distance from its closest neighbor, the annotation is not plotted (this may occur for certain oblique projections.) [0] |
|
Font used for upper annotations, etc. [Helvetica].
Specify either the font number or the font name (case
sensitive!). The 35 available fonts are: |
|
Font size (> 0) in points for map annotations. [14] |
|
Font to use for time axis secondary annotations. See ANNOT_FONT_PRIMARY for available fonts [Helvetica]. |
|
Font size (> 0) for time axis secondary annotations in points [16]. |
|
Distance from end of tickmark to start of annotation [0.2c (or 0.075i)]. A negative offset will place the annotation inside the map border. |
|
Distance from base of primary annotation to the top of the secondary annotation [0.2c (or 0.075i)] (Only applies to time axes with both primary and secondary annotations). |
|
Sets which axes to draw and annotate. Case sensitive: Upper case means both draw and annotate, lower case means draw axis only. [WESN]. |
|
Color used to draw map boundaries and annotations. Give a red/green/blue triplet, with each element in the 0−255 range. [0/0/0] (black). |
|
Choose between plain and fancy (thick boundary, alternating black/white frame; append + for rounded corners) [fancy]. For some map projections (e.g., Oblique Mercator), plain is the only option even if fancy is set as default. In general, fancy only applies to situations where the projected x and y directions parallel the lon and lat directions (e.g., rectangular projections, polar projections). |
|
Names the eight bit character set being used for text in files and in command line parameters. This allows GMT to ensure that the PostScript output generates the correct characters on the plot.. Choose from Standard, Standard+, ISOLatin1, ISOLatin1+, and ISO-8859-x (where x is in the ranges 1-10 or 13-15). See Appendix F for details [ISOLatin1+ (or Standard+)]. |
|
Color used for the background of images (i.e., when z < lowest colortable entry). Give a red/green/blue triplet, with each element in the 0−255 range. [0/0/0] (black) |
|
Color used for the foreground of images (i.e., when z > highest colortable entry). Give a red/green/blue triplet, with each element in the 0−255 range. [255/255/255] (white) |
|
Selects which operator to use when rendering bit-mapped color images. Due to the lack of the colorimage operator in some PostScript implementations, GMT offers 2 different options: adobe (Adobe’s colorimage definition)
[Default]. |
|
Selects if color palette files contain rgb values (r,g,b in 0-255 range) or HSV values (h in 0-360, s,v in 0-1 range). A COLOR_MODE setting in the color palette file will override this setting. [rgb]. |
|
Color used for the non-defined areas of images (i.e., where z == NaN). Give a red/green/blue triplet, with each element in the 0−255 range. [128/128/128] (gray) |
|
Output format (C language printf syntax) to be used when printing double precision floating point numbers. For geographic coordinates, see OUTPUT_DEGREE_FORMAT. [%lg]. |
|
Determines what symbol is used to plot the degree symbol on geographic map annotations. Choose between ring, degree, colon, or none [ring]. |
|
Resolution of the plotting device (dpi). Note that in order to be as compact as possible, GMT PostScript output uses integer formats only so the resolution should be set depending on what output device you are using. E.g, using 300 and sending the output to a Linotype 300 phototypesetter (2470 dpi) will not take advantage of the extra resolution (i.e., positioning on the page and line thicknesses are still only done in steps of 1/300 inch; of course, text will look smoother) [300]. |
|
The (case sensitive) name of the ellipsoid used for the map projections [WGS-84]. Choose among WGS-84 1984 World Geodetic System [Default] Note that for some global projections, GMT may default to GRS-80 Sphere regardless of ellipsoid actually chosen. A warning will be given when this happens. If a different ellipsoid name than those mentioned here is given, GMT will attempt to open a file with that name in the current directory, and read a single record that contains the ellipsoid name, year, major-axis (in m), minor-axis (in m), and flattening (f) from the first record, where the fields must be separated by white-space (not commas). This way a custom ellipsoid (e.g., those used for other planets) may be used. A negative flattening means GMT will recalculate flattening from the two radii. |
|
This setting determines what character will separate ASCII output data columns written by GMT. Choose from tab, space, comma, and none [tab]. |
|
Thickness of pen used to draw plain map frame in dpi units or points (append p) [1.25p]. |
|
Width (> 0) of map borders for fancy map frame [0.2c (or 0.075i)]. |
|
Global x-scale (> 0) to apply to plot-coordinates before plotting. Normally used to shrink the entire output down to fit a specific height/width [1.0]. |
|
Same, but for y-coordinates [1.0]. |
|
Size (>= 0) of grid cross at lon-lat intersections. 0 means draw continuous gridlines instead [0]. |
|
Pen thickness used to draw grid lines in dpi units or points (append p) [0.25p]. |
|
Size (>= 0) of grid cross at secondary lon-lat intersections. 0 means draw continuous gridlines instead [0]. |
|
Default file format for grids, with optional scale, offset and invalid value, written as ff/scale/offset/invalid. The 2-letter format indicator can be one of [bcnsr][bsifd]. The first letter indicates native GMT binary, old format NetCDF, COARDS-compliant NetCDF, Surfer format or Sun Raster format. The second letter stands for byte, short, int, float and double, respectively. When /invalid is omitted the appropriate value for the given format is used (NaN or largest negative). When /scale/offset is omitted, /1.0/0.0 is used. [nf]. |
|
Pen thickness used to draw grid lines in dpi units or points (append p) [0.5p]. |
|
If TRUE, all gridfile names are examined to see if they use the file extension shorthand discussed in Section 4.17 of the GMT Technical Reference and Cookbook. If FALSE, no filename expansion is done [FALSE]. |
|
Font to use when plotting headers. See ANNOT_FONT_PRIMARY for available fonts [Helvetica]. |
|
Font size (> 0) for header in points [36]. |
|
Distance from top of axis annotations (or axis label, if present) to base of plot header [0.5c (or 0.1875i)]. |
|
Minimum saturation (0−1) assigned for most negative intensity value [1.0]. |
|
Maximum saturation (0−1) assigned for most positive intensity value [0.1]. |
|
Minimum value (0−1) assigned for most negative intensity value [0.3]. |
|
Maximum value (0−1) assigned for most positive intensity value [1.0]. |
|
Formatting template that indicates how an input clock string is formatted. This template is then used to guide the reading of clock strings in data fields. To properly decode 12-hour clocks, append am or pm (or upper case) to match your data records. As examples, try hh:mm, hh:mm:ssAM, etc. [hh:mm:ss]. |
|
Formatting template that indicates how an input date string is formatted. This template is then used to guide the reading of date strings in data fields. You may specify either Gregorian calendar format or ISO week calendar format. Gregorian calendar: Use any combination of yyyy (or yy for 2-digit years; if so see Y2K_OFFSET_YEAR), mm (or o for abbreviated month name in the current time language), and dd, with or without delimiters. For day-of-year data, use jjj instead of mm and/or dd. Examples can be ddmmyyyy, yy-mm-dd, dd-o-yyyy, yyyy/dd/mm, yyyy-jjj, etc. ISO Calendar: Expected template is yyyy[-]W[-]ww[-]d, where ww is ISO week and d is ISO week day. Either template must be consistent, e.g., you cannot specify months if you don’t specify years. Examples are yyyyWwwd, yyyy-Www, etc. [yyyy-mm-dd]. |
|
Determines if linear (linear), Akima’s spline (akima), or natural cubic spline (cubic) should be used for 1-D interpolations in various programs [akima]. |
|
(* −H) Specifies whether input/output ASCII files have header record(s) or not [FALSE]. |
|
Specifies how many header records to expect if −H is turned on [1]. |
|
Font to use when plotting labels below axes. See ANNOT_FONT_PRIMARY for available fonts [Helvetica]. |
|
Font size (> 0) for labels in points [24]. |
|
Distance from base of axis annotations to the top of the axis label [0.3c (or 0.1125i)]. |
|
Determines the maximum length (> 0) of individual straight line-segments when drawing arcuate lines [0.025c (or 0.01i)] |
|
Changes the default map scale factor used for the Polar Stereographic [0.9996], UTM [0.9996], and Transverse Mercator [1] projections in order to minimize areal distortion. Provide a new scale-factor or leave as default. |
|
Sets the height (> 0) on the map of the map scale bars drawn by various programs [0.2c (or 0.075i)]. |
|
Sets the unit length. Choose between cm, inch, m, and point. [cm]. Note that, in GMT, one point is defined as 1/72 inch (the PostScript definition), while it is often defined as 1/72.27 inch in the typesetting industry. There is no universal definition. |
|
(* −c) Number of plot copies to make [1]. |
|
This integer is a sum of 6 bit flags (most of which only are relevant for oblique projections): If bit 1 is set (1), annotations will occur wherever a gridline crosses the map boundaries, else longitudes will be annotated on the lower and upper boundaries only, and latitudes will be annotated on the left and right boundaries only. If bit 2 is set (2), then longitude annotations will be plotted horizontally. If bit 3 is set (4), then latitude annotations will be plotted horizontally. If bit 4 is set (8), then oblique tickmarks are extended to give a projection equal to the specified tick_length. If bit 5 is set (16), tickmarks will be drawn normal to the border regardless of gridline angle. If bit 6 is set (32), then latitude annotations will be plotted parallel to the border. To set a combination of these, add up the values in parentheses. [1]. |
|
Formatting template that indicates how an output clock string is to be formatted. This template is then used to guide the writing of clock strings in data fields. To use a floating point format for the smallest unit (e.g. seconds), append .xxx, where the number of x indicates the desired precision. If no floating point is indicated then the smallest specified unit will be rounded off to nearest integer. For 12-hour clocks, append am, AM, a.m., or A.M. (GMT will replace a|A with p|P for pm). If your template starts with a leading hyphen (-) then each integer item (y,m,d) will be printed without leading zeros (default uses fixed width formats). As examples, try hh:mm, hh.mm.ss, hh:mm:ss.xxxx, hha.m., etc. [hh:mm:ss]. |
|
Formatting template that indicates how an output date string is to be formatted. This template is then used to guide the writing of date strings in data fields. You may specify either Gregorian calendar format or ISO week calendar format. Gregorian calendar: Use any combination of yyyy (or yy for 2-digit years; if so see Y2K_OFFSET_YEAR), mm (or o for abbreviated month name in the current time language), and dd, with or without delimiters. For day-of-year data, use jjj instead of mm and/or dd. As examples, try yy/mm/dd, yyyy=jjj, dd-o-yyyy, dd-mm-yy, yy-mm, etc. ISO Calendar: Expected template is yyyy[-]W[-]ww[-]d, where ww is ISO week and d is ISO week day. Either template must be consistant, e.g., you cannot specify months if you don’t specify years. As examples, try yyyyWww, yy-W-ww-d, etc. If your template starts with a leading hyphen (-) then each integer item (y,m,d) will be printed without leading zeros (default uses fixed width formats) [yyyy-mm-dd]. |
|
Formatting template that indicates how an output geographical coordinate is to be formatted. This template is then used to guide the writing of geographical coordinates in data fields. The template is in general of the form [+|-]D or [+|-]ddd[:mm[:ss]][.xxx][F]. The various terms have the following purpose: + means output longitude in the 0 to 360 range
[-180/+180] The default is +D. |
|
Sets the color of the imaging background, i.e., the paper. Give a red/green/blue triplet, with each element in the 0−255 range. [255/255/255] (white). |
|
(* −P) Sets the orientation of the page. Choose portrait or landscape [landscape]. |
|
Sets the physical format of the current plot paper [A4]. The following formats (and their widths and heights in points) are recognized (Additional site-specific formats may be specified in the gmtmedia.d file in $GMTHOME/share; see that file for details): Media width height For a completely custom format (e.g., for large format plotters) you may also specify Custom_WxH, where W and H are in points. To force the printer to request a manual paper feed, append ’-’ to the media name, e.g., A3- will require the user to insert a A3 paper into the printer’s manual feed slot. To indicate you are making an EPS file, append ’+’ to the media name. Then, GMT will attempt to issue a tight bounding box [Default Bounding Box is the paper dimension]. |
|
Formatting template that indicates how an output clock string is to be plotted. This template is then used to guide the formatting of clock strings in plot annotations. See OUTPUT_CLOCK_FORMAT for details. [hh:mm:ss]. |
|
Formatting template that indicates how an output date string is to be plotted. This template is then used to guide the plotting of date strings in data fields. See OUTPUT_DATE_FORMAT for details. In addition, you may use a single o instead of mm (to plot month name) and u instead of W[-]ww to plot "Week ##". Both of these text strings will be affected by the TIME_LANGUAGE setting. [yyyy-mm-dd]. |
|
Formatting template that indicates how an output geographical coordinate is to be plotted. This template is then used to guide the plotting of geographical coordinates in data fields. See OUTPUT_DEGREE_FORMAT for details. In addition, you can append A which plots the absolute value of the coordinate. The default is +ddd:mm:ss. Not all items may be plotted as this depends on the annotation interval. |
|
Determines whether PostScript output should use RGB or CMYK when specifying color. Select from rgb or cmyk [rgb]. |
|
Determines if PostScript images are compressed using the Run-Length Encoding scheme (rle), LZW compression (lzw), or not at all (none) [none]. |
|
Determines whether images created in PostScript should use ascii or binary format. The latter takes up less space and executes faster but may choke some printers, especially those off serial ports. Select ascii or bin [ascii]. |
|
Determines how the ends of a line segment will be drawn. Choose among a butt cap (default) where there is no projection beyond the end of the path, a round cap where a semicircular arc with diameter equal to the linewidth is drawn around the end points, and square cap where a half square of size equal to the linewidth extends beyond the end of the path [butt]. |
|
Determines what happens at kinks in line segments. Choose among a miter join where the outer edges of the strokes for the two segments are extended until they meet at an angle (as in a picture frame; if the angle is too acute, a bevel join is used instead, with threshold set by PS_MITER_LIMIT), round join where a circular arc is used to fill in the cracks at the kinks, and bevel join which is a miter join that is cut off so kinks are triangular in shape [miter]. |
|
Sets the threshold angle (integer in 0-180 range) used for mitered joins. 0 and 180 are special flag values that imply the PostScript default [11] and always bevels, respectively. Other values sets the acute angle used to decide between mitered and bevelled. |
|
The length of a tickmark. Normally, tickmarks are drawn on the outside of the map boundaries. To select interior tickmarks, use a negative tick_length [0.2c (or 0.075i)]. |
|
The pen thickness to be used for tickmarks in dpi units or points (append p) [0.5p]. |
|
Controls how primary month-, week-, and weekday-names are formatted. Choose among full, abbreviated, and character. If the leading f, a, or c are replaced with F, A, and C the entire annotation will be in upper case. |
|
Controls how secondary month-, week-, and weekday-names are formatted. Choose among full, abbreviated, and character. If the leading f, a, or c are replaced with F, A, and C the entire annotation will be in upper case. |
|
This parameter is active only when TIME_SYSTEM is set to OTHER. It is a string of the form yyyy-mm-ddThh:mm:ss (Gregorian) or yyyy-Www-ddThh:mm:ss (ISO) indicating the value of the calendar and clock at the origin (zero point) of relative time units. |
|
Used when input calendar data should be truncated and adjusted to the middle of the relevant interval. In the following discussion, the unit u can be one of these time units: (y year, o month, u ISO week, d day, h hour, m minute, and c second). TIME_IS_INTERVAL can have any of the following three values: (1) OFF [Default]. No adjustment, time is decoded as given. (2) +nu. Activate interval adjustment for input by truncate to previous whole number of n units and then center time on the following interval. (3) -nu. Same, but center time on the previous interval. For example, with TIME_IS_INTERVAL = +1o, an input data string like 1999-12 will be interpreted to mean 1999-12-15T12:00:00.0 (exactly middle of December), while if TIME_IS_INTERVAL = OFF then that date is interpreted to mean 1999-12-1T00:00:00.0 (start of December). |
|
Determines if partial intervals at the start and end of an axis should be annotated. If the range of the partial interval exceeds the specified fraction of the normal interval stride we will place the annotation centered on the partial interval [0.5]. |
|
Language to use when plotting calendar items such as
months and days. Select from: If your language is not supported, please examine the $GMTHOME/share/time/us.d file and make a similar file. Please submit it to the GMT Developers for official inclusion. |
|
Determines what the time epoch relative time refers to
and what the units are. Choose from one of the preset
systems below (epoch and units are indicated): |
|
This parameter is active only when TIME_SYSTEM is set to OTHER, and specifies the units of relative time data. Choose y (year), d (day), h (hour), m (minute), or c (second). |
|
When weeks are indicated on time axes, this parameter determines the first day of the week for Gregorian calendars. (The ISO weekly calendar always begins weeks with Monday.) [Monday (or Sunday)]. |
|
(* −U) Specifies if a UNIX system time stamp should be plotted at the lower left corner of the plot [FALSE]. |
|
(* −U) Sets the position of the UNIX time stamp relative to the current plots lower left corner [-2c/-2c (or -0.75i/-0.75i)]. |
|
Determines the shape of the head of a vector. Normally (i.e., for vector_shape = 0), the head will be triangular, but can be changed to an arrow (1) or an open V (2). Intermediate settings give something in between. Negative values (up to -2) are allowed as well [0]. |
|
(* −V) Determines if GMT programs should display run-time information or run silently [FALSE]. |
|
Sets the default length (> 0) of the x-axis [25c (or 9i)]. |
|
Sets the default length (> 0) of the y-axis [15c (or 6i)]. |
|
(* −X) Sets the x-coordinate of the origin on the paper for a new plot [2.5c (or 1i)]. For an overlay, the default offset is 0. |
|
(* −Y) Sets the y-coordinate of the origin on the paper for a new plot [2.5c (or 1i)]. For an overlay, the default offset is 0. |
|
When 2-digit years are used to represent 4-digit years (see various DATE_FORMATs), Y2K_OFFSET_YEAR gives the first year in a 100-year sequence. For example, if Y2K_OFFSET_YEAR is 1729, then numbers 29 through 99 correspond to 1729 through 1799, while numbers 00 through 28 correspond to 1800 through 1828. [1950]. |
|
(* −:) Set if the first two columns of input and output files contain (latitude,longitude) or (y,x) rather than the expected (longitude,latitude) or (x,y). FALSE means we have (x,y) both on input and output. TRUE means both input and output should be (y,x). IN means only input has (y,x), while OUT means only output should be (y,x). [FALSE]. |
|
Determines if the annotations for a y-axis (for linear projections) should be plotted horizontally (hor_text) or vertically (ver_text) [hor_text]. |
|
To get a copy of the GMT parameter defaults in your home directory, run gmtdefaults −D > ~/.gmtdefaults4 You may now change the settings by editing this file using a text editor of your choice, or use gmtset to change specified parameters on the command line. |
|
If you have typographical errors in your .gmtdefaults4 file(s), a warning message will be issued, and the GMT defaults for the affected parameters will be used. |