/usr/share/doc/gmt/html/man/x2sys_get.html is in gmt-doc 4.5.11-1build1.
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 | <!-- Creator : groff version 1.19.2 -->
<!-- CreationDate: Tue Nov 5 09:45:52 2013 -->
<!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; }
pre { margin-top: 0; margin-bottom: 0; }
table { margin-top: 0; margin-bottom: 0; }
</style>
<title>X2SYS_GET</title>
</head>
<body bgcolor="#ffffff">
<h1 align=center>X2SYS_GET</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="#EXAMPLES">EXAMPLES</a><br>
<a href="#NOTE">NOTE</a><br>
<a href="#SEE ALSO">SEE ALSO</a><br>
<hr>
<a name="NAME"></a>
<h2>NAME</h2>
<p style="margin-left:11%; margin-top: 1em">x2sys_get
− Get track listing from the x2sys track index
databases</p>
<a name="SYNOPSIS"></a>
<h2>SYNOPSIS</h2>
<p style="margin-left:11%; margin-top: 1em"><b>x2sys_get
−T</b><i>TAG</i> [ <b>−C</b> ] [ <b>−D</b>
] [ <b>−E</b> ] [ <b>−F</b><i>flags</i> ] [
<b>−L</b>[<i>list</i>] ] [ <b>−N</b><i>flags</i>
] [ <b>−Qe</b>|<b>i</b> ] [
<b>−R</b><i>west</i>/<i>east</i>/<i>south</i>/<i>north</i>[<b>r</b>]
] [ <b>−V</b> ] ]</p>
<a name="DESCRIPTION"></a>
<h2>DESCRIPTION</h2>
<p style="margin-left:11%; margin-top: 1em"><b>x2sys_get</b>
will return the names of the track data files in the x2sys
data base for this TAG that match the given requirements.
You may choose a specific region and optionally ask only for
tracks that meet certain data criteria. Finally, you may
select an option to list all possible pairs that might
generate crossovers.</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 style="margin-top: 1em" valign="top"><b>−T</b></p> </td>
<td width="8%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Specify the x2sys
<i>TAG</i> which tracks the attributes of this data
type.</p> </td>
</table>
<a name="OPTIONS"></a>
<h2>OPTIONS</h2>
<p style="margin-left:11%; margin-top: 1em">No space
between the option flag and the associated arguments.</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 style="margin-top: 1em" valign="top"><b>−C</b></p> </td>
<td width="8%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Instead of
reporting the track names, just output the coordinates of
the center of each bin that has at least one track with the
specified data.</p></td>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p style="margin-top: 1em" valign="top"><b>−D</b></p> </td>
<td width="8%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Only report the
track names [Default adds the availability of data for each
field].</p> </td>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p style="margin-top: 1em" valign="top"><b>−E</b></p> </td>
<td width="8%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Append the file
extension to all reported tracks [no extension].</p></td>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p style="margin-top: 1em" valign="top"><b>−F</b></p> </td>
<td width="8%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Give a
comma-separated list of column names (as described in the
definition file) that should all be present within the
selected region. [Default selects all data columns]. A track
will be included in the returned list if at least one bin
reports that the track has all of the listed columns.</p></td>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p style="margin-top: 1em" valign="top"><b>−L</b></p> </td>
<td width="8%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Crossover mode.
Return a list of track pairs that should be checked for
possible crossovers. The list is determined from the
bin-index data base on the assumption that tracks occupying
the same bin are very likely to intersect. By default we
return all possible pairs in the data base. Append the name
of a file with a list of tracks if you want to limit the
output to those pairs that involve at least one of the track
names in your list. The output is suitable for the
<b>−K</b> option in <b><A HREF="x2sys_cross.html">x2sys_cross</A></b>.</p></td>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p style="margin-top: 1em" valign="top"><b>−N</b></p> </td>
<td width="8%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Give a
comma-separated list of column names (as described in the
definition file) that all must be absent. A track will be
excluded from the returned list if at least one bin reports
that the track some all of the listed columns.</p></td>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p style="margin-top: 1em" valign="top"><b>−Q</b></p> </td>
<td width="8%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Append <b>e</b> for
external COEs only, and <b>i</b> for internal COEs only
[Default is all COEs]. This applies to the crossover setup
only and requires <b>−L</b>.</p></td>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p style="margin-top: 1em" valign="top"><b>−R</b></p> </td>
<td width="8%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top"><i>west, east,
south,</i> and <i>north</i> specify the Region of interest,
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
Cartesian data just give <i>xmin/xmax/ymin/ymax</i>. This
option limits the tracks to those that fall at least partly
inside the specified domain.</p></td>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p style="margin-top: 1em" valign="top"><b>−V</b></p> </td>
<td width="8%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Selects verbose
mode, which will send progress reports to stderr [Default
runs "silently"].</p></td>
</table>
<a name="EXAMPLES"></a>
<h2>EXAMPLES</h2>
<p style="margin-left:11%; margin-top: 1em">To find all the
tracks associated with the tag MGD77, restricted to occupy a
certain region in the south Pacific, and have at least free
air anomalies and bathymetry, try</p>
<p style="margin-left:11%; margin-top: 1em"><b>x2sys_get
−V −T</b> MGD77 <b>−R</b> 180/240/-60/-30
<b>−F</b> faa,depth</p>
<p style="margin-left:11%; margin-top: 1em">To find all the
tracks associated with the tag MGD77 that have depth but not
twt, try</p>
<p style="margin-left:11%; margin-top: 1em"><b>x2sys_get
−V −T</b> MGD77 <b>−F</b> depth
<b>−N</b> twt</p>
<p style="margin-left:11%; margin-top: 1em">To find all the
pairs associated with the tag MGD77 that might intersect
each other, but only those pairs which involves tracks in
your list new.lis, try</p>
<p style="margin-left:11%; margin-top: 1em"><b>x2sys_get
−V −T</b> MGD77 <b>−L</b> new.lis >
xpairs.lis</p>
<a name="NOTE"></a>
<h2>NOTE</h2>
<p style="margin-left:11%; margin-top: 1em">The tracks that
are returned all have the requested data (<b>−F</b>)
within the specified region (<b>−R</b>). Furthermore,
the columns of Y and N for other data types also reflect the
content of the track portion within the selected region.</p>
<a name="SEE ALSO"></a>
<h2>SEE ALSO</h2>
<p style="margin-left:11%; margin-top: 1em"><i><A HREF="x2sys_binlist.html">x2sys_binlist</A></i>(1),
<i><A HREF="x2sys_cross.html">x2sys_cross</A></i>(1), <i><A HREF="x2sys_datalist.html">x2sys_datalist</A></i>(1),
<i><A HREF="x2sys_init.html">x2sys_init</A></i>(1), <i><A HREF="x2sys_list.html">x2sys_list</A></i>(1),
<i><A HREF="x2sys_put.html">x2sys_put</A></i>(1), <i><A HREF="x2sys_report.html">x2sys_report</A></i>(1),
<i><A HREF="x2sys_solve.html">x2sys_solve</A></i>(1)</p>
<hr>
</body>
</html>
|