/usr/share/doc/gmt/html/man/grdreformat.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 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 | <!-- Creator : groff version 1.22.2 -->
<!-- CreationDate: Thu Feb 27 18:12:48 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>GRDREFORMAT</title>
</head>
<body bgcolor="#ffffff">
<h1 align="center">GRDREFORMAT</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="#FORMAT IDENTIFIER">FORMAT IDENTIFIER</a><br>
<a href="#GMT STANDARD NETCDF FILES">GMT STANDARD NETCDF FILES</a><br>
<a href="#NATIVE BINARY FILES">NATIVE BINARY FILES</a><br>
<a href="#GRID VALUES PRECISION">GRID VALUES PRECISION</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">grdreformat
− Converting between different grid file formats.</p>
<h2>SYNOPSIS
<a name="SYNOPSIS"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em"><b>grdreformat</b>
<i>ingrdfile</i>[<i>=id</i>[<i>/scale/offset</i>[<i>/NaNvalue</i>]]]
<i>outgrdfile</i>[<i>=id</i>[<i>/scale/offset</i>[<i>/NaNvalue</i>]]]
[ <b>−N</b> ] [
<b>−R</b><i>west</i>/<i>east</i>/<i>south</i>/<i>north</i>[<b>r</b>]
] [ <b>−f</b>[<b>i</b>|<b>o</b>]<i>colinfo</i> ] [
<b>−V</b> ]</p>
<h2>DESCRIPTION
<a name="DESCRIPTION"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em"><b>grdreformat</b>
reads a grid file in one format and writes it out using
another format. As an option the user may select a subset of
the data to be written and to specify scaling, translation,
and NaN-value. <i><br>
ingrdfile</i></p>
<p style="margin-left:22%;">The grid file to be read.
Append format =<i>id</i> code if not a standard
COARDS-compliant netCDF grid file. If =<i>id</i> is set (see
below), you may optionally append <i>scale</i> and
<i>offset</i>. These options will scale the data and then
offset them with the specified amounts after reading. <br>
If <i>scale</i> and <i>offset</i> are supplied you may also
append a value that represents ’Not-a-Number’
(for floating-point grids this is unnecessary since the IEEE
NaN is used; however integers need a value which means no
data available.)</p>
<p style="margin-left:11%;"><i>outgrdfile</i></p>
<p style="margin-left:22%;">The grid file to be written.
Append format =<i>id</i> code if not a standard
COARDS-compliant netCDF grid file. If =<i>id</i> is set (see
below), you may optionally append <i>scale</i> and
<i>offset</i>. These options are particularly practical when
storing the data as integers, first removing an offset and
then scaling down the values. Since the scale and offset are
applied in reverse order when reading, this does not affect
the data values (except for round-offs). <br>
If <i>scale</i> and <i>offset</i> are supplied you may also
append a value that represents ’Not-a-Number’
(for floating-point grids this is unnecessary since the IEEE
NaN is used; however integers need a value which means no
data available.)</p>
<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>−N</b></p></td>
<td width="8%"></td>
<td width="78%">
<p style="margin-top: 1em">Suppress the writing of the
<b><A HREF="GMT.html">GMT</A></b> header structure. This is useful when you want to
write a native grid to be used by <b><A HREF="grdraster.html">grdraster</A></b>. It only
applies to native grids and is ignored for netCDF
output.</p> </td></tr>
<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>).</p> </td></tr>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p><b>−V</b></p></td>
<td width="8%"></td>
<td width="78%">
<p>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>−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>FORMAT IDENTIFIER
<a name="FORMAT IDENTIFIER"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">By default,
grids will be written as floating point data stored in
binary files using the netCDF format and meta-data
structure. This format is conform the COARDS conventions.
<b><A HREF="GMT.html">GMT</A></b> versions prior to 4.1 produced netCDF files that
did not conform to these conventions. Although these files
are still supported, their use is deprecated. To write other
than floating point COARDS-compliant netCDF files, append
the =<i>id</i> suffix to the filename <i>outgrdfile</i>.
<br>
When reading files, <b>grdreformat</b> and other <b><A HREF="GMT.html">GMT</A></b>
programs will automatically recognize any type of netCDF
grid file. These can be in either COARDS-compliant or
pre-4.1 format, and contain floating-point or integer data.
To read other types of grid files, append the =<i>id</i>
suffix to the filename <i>ingrdfile</i>.</p>
<p style="margin-left:11%; margin-top: 1em"><i>id GMT 3
netCDF legacy formats</i> <b><br>
cb</b> GMT netCDF format (byte) (deprecated) <b><br>
cs</b> GMT netCDF format (short) (deprecated) <b><br>
ci</b> GMT netCDF format (int) (deprecated) <b><br>
cf</b> GMT netCDF format (float) (deprecated) <b><br>
cd</b> GMT netCDF format (double) (deprecated)</p>
<p style="margin-left:11%; margin-top: 1em"><i>id GMT
native binary formats</i> <b><br>
bm</b> GMT native, C-binary format (bit-mask) <b><br>
bb</b> GMT native, C-binary format (byte) <b><br>
bs</b> GMT native, C-binary format (short) <b><br>
bi</b> GMT native, C-binary format (int) <b><br>
bf</b> GMT native, C-binary format (float) <b><br>
bd</b> GMT native, C-binary format (double)</p>
<p style="margin-left:11%; margin-top: 1em"><i>id GMT 4
netCDF standard</i> <b><br>
nb</b> GMT netCDF format (byte) (COARDS-compliant) <b><br>
ns</b> GMT netCDF format (short) (COARDS-compliant) <b><br>
ni</b> GMT netCDF format (int) (COARDS-compliant) <b><br>
nf</b> GMT netCDF format (float) (COARDS-compliant)
[DEFAULT] <b><br>
nd</b> GMT netCDF format (double) (COARDS-compliant)</p>
<p style="margin-left:11%; margin-top: 1em"><i>id Misc
formats</i> <b><br>
rb</b> SUN rasterfile format (8-bit standard) <b><br>
rf</b> GEODAS grid format GRD98 (NGDC) <b><br>
sf</b> Golden Software Surfer format 6 (float) <b><br>
sd</b> Golden Software Surfer format 7 (double, read-only)
<b><br>
af</b> Atlantic Geoscience Center format AGC (float) <b><br>
gd</b> Import through GDAL (convert to float) --
NON-STANDARD</p>
<h2>GMT STANDARD NETCDF FILES
<a name="GMT STANDARD NETCDF FILES"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">The standard
format used for grdfiles is based on netCDF and conforms to
the COARDS conventions. Files written in this format can be
read by numerous third-party programs and are
platform-independent. Some disk-space can be saved by
storing the data as bytes or shorts in stead of integers.
Use the <i>scale</i> and <i>offset</i> parameters to make
this work without loss of data range or significance. For
more details, see Appendix B.</p>
<p style="margin-left:11%; margin-top: 1em"><b>Multi-variable
grid files</b> <br>
By default, <b><A HREF="GMT.html">GMT</A></b> programs will read the first
2-dimensional grid contained in a COARDS-compliant netCDF
file. Alternatively, use
<i>ingrdfile</i><b>?</b><i>varname</i> (ahead of any
optional suffix <b>=</b><i>id</i>) to specify the requested
variable <i>varname</i>. Since <b>?</b> has special meaning
as a wildcard, escape this meaning by placing the full
filename and suffix between quotes.</p>
<p style="margin-left:11%; margin-top: 1em"><b>Multi-dimensional
grids</b> <br>
To extract one <i>layer</i> or <i>level</i> from a
3-dimensional grid stored in a COARDS-compliant netCDF file,
append both the name of the variable and the index
associated with the layer (starting at zero) in the form:
<i>ingrdfile</i><b>?</b><i>varname</i><b>[</b><i>layer</i><b>]</b>.
Alternatively, specify the value associated with that layer
using parentheses in stead of brackets:
<i>ingridfile</i><b>?</b><i>varname</i><b>(</b><i>level</i><b>)</b>.
<br>
In a similar way layers can be extracted from 4- or even
5-dimensional grids. For example, if a grid has the
dimensions (parameter, time, depth, latitude, longitude), a
map can be selected by using:
<i>ingridfile</i><b>?</b><i>varname</i><b>(</b><i>parameter,time,depth</i><b>)</b>.
<br>
Since question marks, brackets and parentheses have special
meanings on the command line, escape these meanings by
placing the full filename and suffix between quotes.</p>
<h2>NATIVE BINARY FILES
<a name="NATIVE BINARY FILES"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">For binary
native <b><A HREF="GMT.html">GMT</A></b> files the size of the <b><A HREF="GMT.html">GMT</A></b> grdheader
block is <i>hsize</i> = 892 bytes, and the total size of the
file is <i>hsize</i> + <i>nx</i> * <i>ny</i> *
<i>item_size</i>, where <i>item_size</i> is the size in
bytes of each element (1, 2, 4). Bit grids are stored using
4-byte integers, each holding 32 bits, so for these files
the size equation is modified by using ceil (<i>nx</i> / 32)
* 4 instead of <i>nx</i>. Note that these files are
platform-dependent. Files written on Little Endian machines
(e.g., PCs) can not be read on Big Endian machines (e.g.,
most workstations). Also note that it is not possible for
<b><A HREF="GMT.html">GMT</A></b> to determine uniquely if a 4-byte grid is float
or int; in such cases it is best to use the <i>=ID</i>
mechanism to specify the file format. In all cases a native
grid is considered to be signed (i.e., there are no
provision for unsigned short ints or unsigned bytes). For
header and grid details, see Appendix B.</p>
<h2>GRID VALUES PRECISION
<a name="GRID VALUES PRECISION"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">Regardless of
the precision of the input data, GMT programs that create
grid files will internally hold the grids in 4-byte floating
point arrays. This is done to conserve memory and
furthermore most if not all real data can be stored using
4-byte floating point values. Data with higher precision
(i.e., double precision values) will lose that precision
once GMT operates on the grid or writes out new grids. To
limit loss of precision when processing data you should
always consider normalizing the data prior to
processing.</p>
<h2>EXAMPLES
<a name="EXAMPLES"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">To extract the
second layer from a 3-dimensional grid named temp from a
COARDS-compliant netCDF file climate.grd:</p>
<p style="margin-left:11%; margin-top: 1em"><b>grdreformat</b>
climate.grd?temp[1] temp.grd <b>-V</b></p>
<p style="margin-left:11%; margin-top: 1em">To create a
4-byte native floating point grid from the COARDS-compliant
netCDF file data.grd:</p>
<p style="margin-left:11%; margin-top: 1em"><b>grdreformat</b>
data.grd ras_data.b4=bf <b>−V</b></p>
<p style="margin-left:11%; margin-top: 1em">To make a
2-byte short integer file, scale it by 10, subtract 32000,
setting NaNs to -9999, do</p>
<p style="margin-left:11%; margin-top: 1em"><b>grdreformat</b>
values.grd shorts.i2=bs/10/-32000/-9999 <b>−V</b></p>
<p style="margin-left:11%; margin-top: 1em">To create a Sun
standard 8-bit rasterfile for a subset of the data file
image.grd, assuming the range in image.grd is 0-1 and we
need 0-255, run</p>
<p style="margin-left:11%; margin-top: 1em"><b>grdreformat</b>
image.grd <b>−R</b>-60/-40/-40/-30 image.ras8=rb/255/0
<b>−V</b></p>
<p style="margin-left:11%; margin-top: 1em">To convert
etopo2.grd to etopo2.i2 that can be used by
<b><A HREF="grdraster.html">grdraster</A></b>, try</p>
<p style="margin-left:11%; margin-top: 1em"><b>grdreformat</b>
etopo2.grd etopo2.i2=bs <b>−N −V</b></p>
<h2>SEE ALSO
<a name="SEE ALSO"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em"><b><i><A HREF="GMT.html">GMT</A></i></b>(1),
<i><A HREF="grdmath.html">grdmath</A></i>(1)</p>
<hr>
</body>
</html>
|