Skip to content

Commit 654dfad

Browse files
committed
Built site for gh-pages
1 parent 4df0c5f commit 654dfad

50 files changed

Lines changed: 391 additions & 351 deletions

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

.nojekyll

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
b4b85027
1+
247b6574

assets/subduction.jpg

-183 KB
Binary file not shown.

documentation/common_features/justify.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -415,7 +415,7 @@ <h2 id="toc-title">On this page</h2>
415415
<h1>Justify</h1>
416416
<pre><code>justify = "code"</code></pre>
417417
<p>Where <em>code</em> is a two chars code made up of the initials of the six: - three letter codes for horizontal (Left, Center, Right) - vertical (Top, Middle, Bottom) alignments. This gives the Nine anchor points relative to any text string may be specified by combining any of three letter codes for horizontal and vertical.</p>
418-
<p>See <a href="https://docs.generic-mapping-tools.org/latest/GMT_Docs.html#placement-of-text">here</a> for graphical display.</p>
418+
<p>See <a href="https://docs.generic-mapping-tools.org/latest/reference/features.html#placement-of-text">here</a> for graphical display.</p>
419419
<p>Examples:</p>
420420
<ul>
421421
<li><em>justify=“LB”</em></li>

documentation/common_opts/common_opts.html

Lines changed: 19 additions & 19 deletions
Large diffs are not rendered by default.
19.4 KB
Loading

documentation/common_opts/explain_F_box.html

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -407,9 +407,9 @@
407407

408408
<pre><code>- **clearance=val** where *val* is either *gap* or *(xgap,ygap)*, or *(lgap,rgap,bgap,tgap)* where these items are uniform, separate in x- and y-direction, or individual side spacings between the map embellishment and the border for each side.
409409

410-
- **fill=color**, where *color* is any valid color setting (see [Setting color](../common_features/color.qmd), to fill the scale panel [no fill].
410+
- **fill=color**, where *color* is any valid color setting (see [Setting color](../common_features/color.qmd)), to fill the scale panel [no fill].
411411

412-
- **inner=true** to draw a secondary, inner border as well. We use a uniform *gap* between borders of *2p* and the `MAP_DEFAULTS_PEN` unless other values are specified (like **inner="gap/pen"**).
412+
- **inner=true** to draw a secondary, inner border as well. We use a uniform *gap* between borders of *2p* and the [MAP_DEFAULTS_PEN](https://docs.generic-mapping-tools.org/latest/gmt.conf.html#term-MAP_DEFAULTS_PEN) unless other values are specified (like **inner="gap/pen"**).
413413

414414
- **pen=pen**, to specify different [Pen attributes](../common_features/pens.qmd) attributes.
415415

documentation/common_opts/explain_grd_coord.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -413,7 +413,7 @@ <h2 id="toc-title">On this page</h2>
413413

414414
<section id="geographical-and-time-coordinates" class="level2">
415415
<h2 class="anchored" data-anchor-id="geographical-and-time-coordinates">Geographical And Time Coordinates</h2>
416-
<p>When the output grid type is netCDF, the coordinates will be labeled “longitude”, “latitude”, or “time” based on the attributes of the input data or grid (if any) or on the <strong>colinfo</strong> or <strong>region</strong> options. For example, both <strong>colinfo=“0x”</strong> <strong>colinfo=“1t”</strong> and <strong>region=“90w/90e/0t/3t”</strong> will result in a longitude/time grid. When the x, y, or z coordinate is time, it will be stored in the grid as relative time since epoch as specified by <code>TIME_UNIT</code> and <code>TIME_EPOCH</code> in the <code>gmt.conf</code> file or on the command line. In addition, the <strong>unit</strong> attribute of the time variable will indicate both this unit and epoch.</p>
416+
<p>When the output grid type is netCDF, the coordinates will be labeled “longitude”, “latitude”, or “time” based on the attributes of the input data or grid (if any) or on the <strong>colinfo</strong> or <strong>region</strong> options. For example, both <strong>colinfo=“0x”</strong> <strong>colinfo=“1t”</strong> and <strong>region=“90w/90e/0t/3t”</strong> will result in a longitude/time grid. When the x, y, or z coordinate is time, it will be stored in the grid as relative time since epoch as specified by <a href="https://docs.generic-mapping-tools.org/latest/gmt.conf.html#term-TIME_UNIT">TIME_UNIT</a> and <a href="https://docs.generic-mapping-tools.org/latest/gmt.conf.html#term-TIME_EPOCH">TIME_EPOCH</a> in the <code>gmt.conf</code> file or on the command line. In addition, the <strong>unit</strong> attribute of the time variable will indicate both this unit and epoch.</p>
417417

418418

419419
</section>

documentation/common_opts/opt_I.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -407,7 +407,7 @@
407407

408408
<ul>
409409
<li><strong>I</strong> or <strong>inc</strong> or <strong>increment</strong> or <strong>spacing</strong> : – <em>inc=x_inc</em> <strong>|</strong> <em>inc=(x_inc, y_inc)</em> <strong>|</strong> <em>inc=“xinc[+e|n][/yinc[+e|n]]”</em><br>
410-
Specify the grid increments or the block sizes. More at <a href="../../documentation/common_opts/common_opts.html#inc">spacing</a></li>
410+
Specify the grid increments or the block sizes. More at <a href="../../documentation/common_opts/common_opts.html#spacing">spacing</a></li>
411411
</ul>
412412

413413

documentation/common_opts/opt_R_3D.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -407,7 +407,7 @@
407407

408408
<ul>
409409
<li><strong>R</strong> or <strong>region</strong> or <strong>limits</strong> : – <em>limits=(xmin, xmax, ymin, ymax, zmin, zmax)</em> <strong>|</strong> <em>limits=(BB=(xmin, xmax, ymin, ymax, zmin, zmax),)</em> <strong>|</strong> …more<br>
410-
Specify the region of interest. Default limits are computed from data extents. More at <a href="../../documentation/common_opts/common_opts.html#limits">limits</a></li>
410+
Specify the region of interest. Default limits are computed from data extents. More at <a href="../../documentation/common_opts/opt_R.html">limits</a></li>
411411
</ul>
412412

413413

documentation/common_opts/opt__distunits.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -406,7 +406,7 @@
406406

407407

408408
<p><strong>Units</strong></p>
409-
<p>For map distance unit, append unit d for arc degree, m for arc minute, and s for arc second, or e for meter [Default unless stated otherwise], f for foot, k for km, M for statute mile, n for nautical mile, and u for US survey foot. By default we compute such distances using a spherical approximation with great circles (-jg) using the authalic radius (see <code>PROJ_MEAN_RADIUS</code>). You can use -jf to perform “Flat Earth” calculations (quicker but less accurate) or -je to perform exact geodesic calculations (slower but more accurate; see <code>PROJ_GEODESIC</code> for method used).</p>
409+
<p>For map distance unit, append unit d for arc degree, m for arc minute, and s for arc second, or e for meter [Default unless stated otherwise], f for foot, k for km, M for statute mile, n for nautical mile, and u for US survey foot. By default we compute such distances using a spherical approximation with great circles (-jg) using the authalic radius (see <a href="https://docs.generic-mapping-tools.org/latest/gmt.conf.html#term-PROJ_MEAN_RADIUS">PROJ_MEAN_RADIUS</a>). You can use -jf to perform “Flat Earth” calculations (quicker but less accurate) or -je to perform exact geodesic calculations (slower but more accurate; see <a href="https://docs.generic-mapping-tools.org/latest/gmt.conf.html#term-PROJ_GEODESIC">PROJ_GEODESIC</a> for method used).</p>
410410

411411

412412

0 commit comments

Comments
 (0)