/usr/share/doc/gmt/html/man/grdcut.html is in gmt-doc 4.5.12-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 | <!-- Creator : groff version 1.22.2 -->
<!-- CreationDate: Thu Feb 27 18:12:23 2014 -->
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta name="generator" content="groff -Thtml, see www.gnu.org">
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<meta name="Content-Style" content="text/css">
<style type="text/css">
p { margin-top: 0; margin-bottom: 0; vertical-align: top }
pre { margin-top: 0; margin-bottom: 0; vertical-align: top }
table { margin-top: 0; margin-bottom: 0; vertical-align: top }
h1 { text-align: center }
</style>
<title>GRDCUT</title>
</head>
<body bgcolor="#ffffff">
<h1 align="center">GRDCUT</h1>
<a href="#NAME">NAME</a><br>
<a href="#SYNOPSIS">SYNOPSIS</a><br>
<a href="#DESCRIPTION">DESCRIPTION</a><br>
<a href="#OPTIONS">OPTIONS</a><br>
<a href="#GRID FILE FORMATS">GRID FILE FORMATS</a><br>
<a href="#GEOGRAPHICAL AND TIME COORDINATES">GEOGRAPHICAL AND TIME COORDINATES</a><br>
<a href="#EXAMPLES">EXAMPLES</a><br>
<a href="#SEE ALSO">SEE ALSO</a><br>
<hr>
<h2>NAME
<a name="NAME"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">grdcut −
Extract a subregion out of a grid file</p>
<h2>SYNOPSIS
<a name="SYNOPSIS"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em"><b>grdcut</b>
<i>input_file.grd</i> <b>−G</b><i>output_file.grd</i>
<b>−R</b><i>west</i>/<i>east</i>/<i>south</i>/<i>north</i>[<b>r</b>]
[ <b>−V</b> ] [
<b>−Z</b>[<b>n</b>]<i>min/max</i>] ] [
<b>−f</b>[<b>i</b>|<b>o</b>]<i>colinfo</i> ]</p>
<h2>DESCRIPTION
<a name="DESCRIPTION"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em"><b>grdcut</b>
will produce a new <i>output_file.grd</i> file which is a
subregion of <i>input_file.grd</i>. The subregion is
specified with <b>−R</b> as in other programs; the
specified range must not exceed the range of
<i>input_file.grd</i>. If in doubt, run <b><A HREF="grdinfo.html">grdinfo</A></b> to
check range. Alternatively, define the subregion indirectly
via a range check on the node values. Complementary to
<b>grdcut</b> there is <b><A HREF="grdpaste.html">grdpaste</A></b>, which will join
together two grid files along a common edge. <i><br>
input_file.grd</i></p>
<p style="margin-left:22%;">this is the input <i>.grd</i>
format file.</p>
<p style="margin-left:11%;"><b>−G</b><i>output_file.grd</i></p>
<p style="margin-left:22%;">this is the output <i>.grd</i>
format file.</p>
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p><b>−R</b></p></td>
<td width="8%"></td>
<td width="78%">
<p><i>xmin</i>, <i>xmax</i>, <i>ymin</i>, and <i>ymax</i>
specify the Region of interest. For geographic regions,
these limits correspond to <i>west, east, south,</i> and
<i>north</i> and you may specify them in decimal degrees or
in [+-]dd:mm[:ss.xxx][W|E|S|N] format. Append <b>r</b> if
lower left and upper right map coordinates are given instead
of w/e/s/n. The two shorthands <b>−Rg</b> and
<b>−Rd</b> stand for global domain (0/360 and
-180/+180 in longitude respectively, with -90/+90 in
latitude). Alternatively, specify the name of an existing
grid file and the <b>−R</b> settings (and grid
spacing, if applicable) are copied from the grid. For
calendar time coordinates you may either give (a) relative
time (relative to the selected <b><A HREF="gmtdefaults.html#TIME_EPOCH">TIME_EPOCH</A></b> and in the
selected <b><A HREF="gmtdefaults.html#TIME_UNIT">TIME_UNIT</A></b>; append <b>t</b> to
<b>−JX</b>|<b>x</b>), or (b) absolute time of the form
[<i>date</i>]<b>T</b>[<i>clock</i>] (append <b>T</b> to
<b>−JX</b>|<b>x</b>). At least one of <i>date</i> and
<i>clock</i> must be present; the <b>T</b> is always
required. The <i>date</i> string must be of the form
[-]yyyy[-mm[-dd]] (Gregorian calendar) or yyyy[-Www[-d]]
(ISO week calendar), while the <i>clock</i> string must be
of the form hh:mm:ss[.xxx]. The use of delimiters and their
type and positions must be exactly as indicated (however,
input, output and plot formats are customizable; see
<b><A HREF="gmtdefaults.html">gmtdefaults</A></b>). This defines the subregion to be cut
out.</p> </td></tr>
</table>
<h2>OPTIONS
<a name="OPTIONS"></a>
</h2>
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p style="margin-top: 1em"><b>−V</b></p></td>
<td width="8%"></td>
<td width="78%">
<p style="margin-top: 1em">Selects verbose mode, which will
send progress reports to stderr [Default runs
"silently"].</p> </td></tr>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p><b>−Z</b></p></td>
<td width="8%"></td>
<td width="78%">
<p>Determine the new rectangular region so that all nodes
outside this region are also outside the given
<i>z</i>-range [-inf/+inf]. To indicate no limit on min or
max, specify a hyphen (-). Normally, any NaNs encountered
are simply skipped. Use <b>−Zn</b> to consider a NaN
to be outside the <i>z</i>-range.</p></td></tr>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p><b>−f</b></p></td>
<td width="8%"></td>
<td width="78%">
<p>Special formatting of input and/or output columns (time
or geographical data). Specify <b>i</b> or <b>o</b> to make
this apply only to input or output [Default applies to
both]. Give one or more columns (or column ranges) separated
by commas. Append <b>T</b> (absolute calendar time),
<b>t</b> (relative time in chosen <b><A HREF="gmtdefaults.html#TIME_UNIT">TIME_UNIT</A></b> since
<b><A HREF="gmtdefaults.html#TIME_EPOCH">TIME_EPOCH</A></b>), <b>x</b> (longitude), <b>y</b>
(latitude), or <b>f</b> (floating point) to each column or
column range item. Shorthand
<b>−f</b>[<b>i</b>|<b>o</b>]<b>g</b> means
<b>−f</b>[<b>i</b>|<b>o</b>]0<b>x</b>,1<b>y</b>
(geographic coordinates).</p></td></tr>
</table>
<h2>GRID FILE FORMATS
<a name="GRID FILE FORMATS"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">By default
<b><A HREF="GMT.html">GMT</A></b> writes out grid as single precision floats in a
COARDS-complaint netCDF file format. However, <b><A HREF="GMT.html">GMT</A></b> is
able to produce grid files in many other commonly used grid
file formats and also facilitates so called
"packing" of grids, writing out floating point
data as 2- or 4-byte integers. To specify the precision,
scale and offset, the user should add the suffix
<b>=</b><i>id</i>[<b>/</b><i>scale</i><b>/</b><i>offset</i>[<b>/</b><i>nan</i>]],
where <i>id</i> is a two-letter identifier of the grid type
and precision, and <i>scale</i> and <i>offset</i> are
optional scale factor and offset to be applied to all grid
values, and <i>nan</i> is the value used to indicate missing
data. When reading grids, the format is generally
automatically recognized. If not, the same suffix can be
added to input grid file names. See <b><A HREF="grdreformat.html">grdreformat</A></b>(1)
and Section 4.17 of the GMT Technical Reference and Cookbook
for more information.</p>
<p style="margin-left:11%; margin-top: 1em">When reading a
netCDF file that contains multiple grids, <b><A HREF="GMT.html">GMT</A></b> will
read, by default, the first 2-dimensional grid that can find
in that file. To coax <b><A HREF="GMT.html">GMT</A></b> into reading another
multi-dimensional variable in the grid file, append
<b>?</b><i>varname</i> to the file name, where
<i>varname</i> is the name of the variable. Note that you
may need to escape the special meaning of <b>?</b> in your
shell program by putting a backslash in front of it, or by
placing the filename and suffix between quotes or double
quotes. The <b>?</b><i>varname</i> suffix can also be used
for output grids to specify a variable name different from
the default: "z". See <b><A HREF="grdreformat.html">grdreformat</A></b>(1) and
Section 4.18 of the GMT Technical Reference and Cookbook for
more information, particularly on how to read splices of 3-,
4-, or 5-dimensional grids.</p>
<h2>GEOGRAPHICAL AND TIME COORDINATES
<a name="GEOGRAPHICAL AND TIME COORDINATES"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">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 <b>−f</b> or
<b>−R</b> options. For example, both <b>−f0x
−f1t</b> and <b>−R</b> 90w/90e/0t/3t 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 <b><A HREF="gmtdefaults.html#TIME_UNIT">TIME_UNIT</A></b> and <b><A HREF="gmtdefaults.html#TIME_EPOCH">TIME_EPOCH</A></b>
in the .gmtdefaults file or on the command line. In
addition, the <b>unit</b> attribute of the time variable
will indicate both this unit and epoch.</p>
<h2>EXAMPLES
<a name="EXAMPLES"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">Suppose you
have used <b><A HREF="surface.html">surface</A></b> to grid ship gravity in the region
between 148E - 162E and 8N - 32N, and you do not trust the
gridding near the edges, so you want to keep only the area
between 150E - 160E and 10N - 30N, then:</p>
<p style="margin-left:11%; margin-top: 1em"><b>grdcut</b>
grav_148_162_8_32.nc <b>−G</b> grav_150_160_10_30.nc
<b>−R</b> 150/160/10/30 <b>−V</b> To return the
subregion of a grid such that any boundary strips where all
values are entirely above 0, try</p>
<p style="margin-left:11%; margin-top: 1em"><b>grdcut</b>
bathy.nc <b>−G</b> trimmed_bathy.nc <b>−Z</b>-/0
<b>−V</b></p>
<h2>SEE ALSO
<a name="SEE ALSO"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em"><b><i><A HREF="grdpaste.html">grdpaste</A></i></b>(1),
<i><A HREF="grdinfo.html">grdinfo</A></i>(1), <i><A HREF="GMT.html">GMT</A></i>(1)</p>
<hr>
</body>
</html>
|