Register
Login
Resources
Docs Blog Datasets Glossary Case Studies Tutorials & Webinars
Product
Data Engine LLMs Platform Enterprise
Pricing Explore
Connect to our Discord channel

mgd77list.rst 25 KB

You have to be logged in to leave a comment. Sign In
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
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
  1. .. index:: ! mgd77list
  2. .. include:: ../module_supplements_purpose.rst_
  3. *********
  4. mgd77list
  5. *********
  6. |mgd77list_purpose|
  7. Synopsis
  8. --------
  9. .. include:: ../../common_SYN_OPTs.rst_
  10. **gmt mgd77list** *GEODAS-ids* |-F|\ *columns*\ [,\ *logic*][:\ *bittests*]
  11. [ |-A|\ **c**\|\ **d**\|\ **f**\|\ **m**\|\ **t**\ *code*\ [**+f**] ]
  12. [ |-D|\ **A**\|\ **a**\ *startdate* ]
  13. [ |-D|\ **B**\|\ **b**\ *stopdate* ]
  14. [ |-E| ]
  15. [ |-G|\ **a**\ *startrec* ]
  16. [ |-G|\ **b**\ *stoprec* ]
  17. [ |-I|\ *ignore* ]
  18. [ |-L|\ [*corrtable*] ]
  19. [ |-N|\ **d**\|\ **s**\ *unit* ]
  20. [ |-Q|\ **a**\|\ **c**\|\ **v**\ *min*/*max* ]
  21. [ |SYN_OPT-R| ]
  22. [ |-S|\ **a**\ *startdist* ]
  23. [ |-S|\ **b**\ *stopdist* ]
  24. [ |-T|\ [**m**\|\ **e**] ]
  25. [ |SYN_OPT-V| ]
  26. [ |-W|\ *weight* ]
  27. [ |-Z|\ **n**\|\ **p** ]
  28. [ |SYN_OPT-bo| ]
  29. [ |SYN_OPT-h| ]
  30. [ |SYN_OPT-j| ]
  31. [ |SYN_OPT--| ]
  32. |No-spaces|
  33. Description
  34. -----------
  35. **mgd77list** reads MGD77 files and produces an ASCII
  36. [or binary] table. The MGD77 files contain track
  37. information such as leg-id, time and position, geophysical observables
  38. such as gravity, magnetics, and bathymetry, and control codes and
  39. corrections such as Eotvos and diurnal corrections. The MGD77+ extended
  40. netCDF files may also contain additional user columns (for a listing of
  41. available columns, use :doc:`mgd77info` **-C**, and to learn how to add
  42. your own custom columns, see :doc:`mgd77manage`). The user may extract any
  43. combination of these parameters, any of 8 computed quantities (distance,
  44. heading, course-change, velocity, Carter correction, Eotvos correction
  45. and gravity and magnetic global reference fields), calendar sub-units of
  46. time (year, month, day, hour, min, sec), the GEODAS id, and finally a
  47. preset weight (see **-W**). A sub-section can be specified by passing
  48. time- or distance-intervals along track or by selecting a geographical
  49. region. Finally, each output record may be required to pass any number
  50. of logical tests involving data values or bit flags. If multiple cruises
  51. are requested then they are separated by segment headers.
  52. Required Arguments
  53. ------------------
  54. .. include:: explain_ncid.rst_
  55. .. _-F:
  56. **-F**\ *columns*\ [,\ *logic*][:\ *bittests*]
  57. The required *columns* string must be a comma-separated list of
  58. parameter abbreviations given in the desired output order. Any
  59. parameters given in UPPER case must not be NaN in a record for
  60. output to occur. Unless specified separately, the output format (if
  61. ASCII) is controlled by the GMT parameter :term:`FORMAT_FLOAT_OUT`.
  62. The available column abbreviations for information stored in the
  63. files (some columns may be NaN) are:
  64. **recno**
  65. The record number counter.
  66. **drt**
  67. The digital record type, usually 3 or 5 (for Y2K-compliant cruises).
  68. **id**
  69. The survey ID string (leg name).
  70. **ngdcid**
  71. The 8-character NGDC (now NCEI) cruise ID string (usually the file prefix).
  72. **time**
  73. Choose between Absolute calendar time (**atime**, the default) in
  74. the format dictated by the GMT parameters :term:`FORMAT_DATE_OUT` and
  75. :term:`FORMAT_CLOCK_OUT`, Relative time (**rtime**) in the format
  76. dictated by the GMT parameters :term:`FORMAT_FLOAT_OUT` and
  77. :term:`TIME_SYSTEM` (or :term:`TIME_EPOCH` and :term:`TIME_UNIT`)), or
  78. Fractional year (**ytime**) in the format dictated by
  79. :term:`FORMAT_FLOAT_OUT`.
  80. **lon**
  81. Longitude in the format dictated by the GMT parameter
  82. :term:`FORMAT_GEO_OUT`.
  83. **lat**
  84. Longitude in the format dictated by the GMT parameter
  85. :term:`FORMAT_GEO_OUT`.
  86. **twt**
  87. Two-Way Travel time (in s).
  88. **depth**
  89. Corrected bathymetry (in m, positive below sea level).
  90. **mtf1**
  91. Magnetic Total Field intensity from sensor 1 (in nTesla).
  92. **mtf2**
  93. Magnetic Total Field intensity from sensor 2 (in nTesla).
  94. **mag**
  95. Residual magnetic anomaly (in nTesla).
  96. **gobs**
  97. Observed gravity (in mGal).
  98. **faa**
  99. Free-air gravity anomaly (in mGal).
  100. **ptc**
  101. Position Type Code (1 = fix, 3 = interpolated, 9 = unspecified).
  102. **bcc**
  103. Bathymetric Correction Code, indicating the procedure used to
  104. convert travel time to depth. (01-55 = Matthews' zone used to
  105. correct the depth, 59 = Matthews' corrections used but the zones is
  106. unspecified in the data record, 60 = S. Kuwahara formula for T-S, 61
  107. = Wilson formula for T-S, 62 = Del Grosso formula for T-S, 63 =
  108. Carter's tables, 88 = Other, described in header sections, 99 =
  109. unspecified).
  110. **btc**
  111. Bathymetric Type Code, indicating how the bathymetry value was
  112. obtained (1 = observed, 3 = interpolated, 9 = unspecified).
  113. **msens**
  114. Magnetic sensor for used to evaluate the residual field (1 = 1st or
  115. leading sensor, 2 = 2nd or trailing sensor, 9 = unspecified).
  116. **msd**
  117. Depth (or altitude) of the magnetic sensor (in m, positive below
  118. sealevel).
  119. **diur**
  120. Magnetic diurnal correction (in nTesla).
  121. **eot**
  122. Eotvos correction (in mGal).
  123. **sln**
  124. Seismic Line Number string.
  125. **sspn**
  126. Seismic Shot Point Number string.
  127. **nqc**
  128. Navigation Quality Code (5 = suspected, by source institution, 6 =
  129. suspected, by NCEI, 9 = no problems identified).
  130. In addition, the following derived navigational quantities can be requested:
  131. **year**
  132. The year of each record.
  133. **month**
  134. The month of each record.
  135. **day**
  136. The day of the month of each record.
  137. **hour**
  138. The hour of each record.
  139. **min**
  140. The minutes of each record.
  141. **sec**
  142. The decimal seconds of each record.
  143. **dist**
  144. Along-track distance from start of leg. For method of calculation,
  145. see **-j** [spherical great circle distances], and for distance
  146. units, see **-N** [km].
  147. **az**
  148. Ship azimuth (heading) measured clockwise from north (in degrees).
  149. **cc**
  150. Ship course change (change in heading) measured clockwise from north
  151. (in degrees).
  152. **vel**
  153. Ship speed; see **-N** for units [m/s].
  154. Finally, the following computed quantities can be requested:
  155. **weight**
  156. Weight assigned to this data set (see **-W**).
  157. **carter**
  158. Carter depth correction, if **twt** is present in file (in m). Sign:
  159. Correction is to be added to uncorrected depths to yield a corrected
  160. depth.
  161. **igrf**
  162. International geomagnetic reference field (total field) (in nTesla).
  163. **ngrav**
  164. International Gravity reference Field ("normal gravity") (in mGal).
  165. Field is selected based on the parameter Gravity Theoretical Formula
  166. Code in the cruise's MGD77 header. If this is not set or is invalid
  167. we default to the IGF 1980. Alternatively, specify the field
  168. directly using **-Af** (see that option for more details).
  169. **ceot**
  170. Calculated Eotvos correction from navigation, using E =
  171. 7.5038 \* V \* cos(lat) \* sin(az) + 0.004154 \* V^2
  172. (in mGal). Sign: Correction is to be added to uncorrected faa to
  173. yield a corrected faa.
  174. The following short-hand flags are also recognized:
  175. **mgd77**
  176. This results in all 27 MGD77 fields being written out in the official MGD77 order.
  177. **mgd77t**
  178. The full set of all 26 columns in the MGD77T specification.
  179. **geo**
  180. This limits the output to 10 fields (**time**, **lon**, **lat** plus
  181. the seven geophysical observations **twt**, **depth**, **mtf1**,
  182. **mtf2**, **mag**, **gobs**, and **faa**).
  183. **dat**
  184. As **mgd77t** but in plain table order.
  185. **all**
  186. This returns all data columns in the file.
  187. **allt**
  188. As mgd77t but with time items written as a date-time string.
  189. By appending **+** to any of these set we will also append **dist**,
  190. **azim**, **cc**, **vel**, and **weight** as listed above.
  191. As an option, logical tests may be added for any of the observations
  192. by appending ,\ *logic*, which is itself composed of one or more
  193. comma-separated instructions of the form *par*\ **OP**\ *value*,
  194. where *par* is one of the parameters listed above, **OP** is a
  195. logical operator (<, <=, =, !=, >=, >, \|), and *value* is a
  196. constant used in the comparison. Floating point parameters are
  197. compared numerically; character parameters are compared lexically
  198. (after leading and trailing blanks have been removed). The bit
  199. comparison (\|) means that at least one of the bits in *value* must
  200. be turned on in *par*. At least one of the tests must be true for
  201. the record to be output, except for tests using UPPER case
  202. parameters which all must be true for output to occur. Notes:
  203. (1) Specifying a test does not imply that the corresponding column will
  204. be included in the output stream; it must be present in *columns*
  205. for that to occur. (2) Some of the operators are special UNIX
  206. characters and you are advised to place quotes around the entire
  207. argument to **-F**. (3) The logical tests only apply to observed
  208. data; derived data (such as distances, velocities, etc.) must be
  209. limited using program options such as **-D**, **-Q**, **-S**, etc.
  210. Finally, for MGD77+ files you may optionally append :*bittests*
  211. which is : (a colon) followed by one or more comma-separated +-*col*
  212. terms. This compares specific bitflags only for each listed column.
  213. Here, + means the chosen bit must be 1 (ON) whereas - means it must
  214. be 0 (OFF). All bit tests given must be passed. By default, MGD77+
  215. files that have the special **MGD77_flags** column present will use
  216. those flags, and observations associated with ON-bits (meaning they
  217. are flagged as bad) will be set to NaN; append : with no trailing
  218. information to turn this behavior off (i.e., no bit flags will be
  219. consulted). Note that these record-based flags are different from
  220. any systematic corrections along track; the latter are deactivated
  221. by **-T**.
  222. Optional Arguments
  223. ------------------
  224. .. _-A:
  225. **-A**\ **c**\|\ **d**\|\ **f**\|\ **m**\|\ **t**\ *code*\ [**+f**]
  226. By default, corrected depth (**depth**), magnetic residual anomaly
  227. (**mag**), free-air gravity anomaly (**faa**), and the derived
  228. quantity Carter depth correction (**carter**) are all output as is
  229. (if selected in **-F**); this option adjusts that behavior. For each
  230. of these columns there are 2-4 ways to adjust the data. Append
  231. **c**\ (arter), **d**\ (epth), **f**\ (aa), or **m**\ (ag) and
  232. select the *code* for the procedure you want applied. You may select
  233. more than one procedure for a data column by summing their numerical
  234. *code*\ s (1, 2, 4, and 8). E.g., **-Ac**\ 3 will first try method
  235. **-Ac**\ 1 to estimate a Carter correction but if **depth** is NaN
  236. we will next try **-Ac**\ 2 which only uses **twt**. In all cases,
  237. if any of the values required by an adjustment procedure is NaN then
  238. the result will be NaN. This is also true if the original anomaly is
  239. NaN. Append **+f** to recalculate anomalies even if the anomaly in
  240. the file is NaN. Additionally, you can use **-At** to create fake
  241. times for cruises that has no time; these are based on distances and
  242. cruise duration.
  243. **-Ac**
  244. Determines how the **carter** correction term is calculated. Below,
  245. C(\ **twt**) stands for the Carter-corrected depth (it also depends
  246. on **lon**, **lat**), U(\ **twt**, *v*) is the uncorrected depth (=
  247. **twt** \* *v* / 2) using as *v* the "Assumed Sound Velocity"
  248. parameter in the MGD77 header (if it is a valid velocity, otherwise
  249. we default to 1500 m/s); alternatively, append your preferred
  250. velocity *v* in m/s, TU(\ **depth**, *v*) is the 2-way travel time
  251. estimated from the (presumably) uncorrected **depth**, and
  252. TC(\ **depth**) is the 2-way travel time obtained by inverting the
  253. (presumably) corrected **depth** using the Carter correction
  254. formula. Select from
  255. **-Ac1**\ [,\ *v*] returns difference between U(\ **twt**, *v*) and **depth** [Default].
  256. **-Ac2**\ [,\ *v*] returns difference between U(\ **twt**, *v*) and Carter (**twt**).
  257. **-Ac4**\ [,\ *v*] returns difference between (assumed uncorrected) **depth** and Carter (TU(**depth**)).
  258. **-Ac8**\ [,\ *v*] returns difference between U(TC(\ **depth**), *v*) and **depth**.
  259. **-Ad**
  260. Determines how the **depth** column output is obtained:
  261. **-Ad1** returns **depth** as stored in the data set [Default].
  262. **-Ad2**\ [,\ *v*] returns calculated uncorrected depth U(\ **twt**, *v*).
  263. **-Ad4** returns calculated corrected depth C(\ **twt**).
  264. **-Af**
  265. Determines how the **faa** column output is obtained. If **ngrav**
  266. (i.e., the International Gravity reference Field (IGF), or "normal
  267. gravity") is required it is selected based on the MGD77 header
  268. parameter "Theoretical Gravity Formula Code"; if this code is not
  269. present or is invalid we default to 4. Alternatively, append the
  270. preferred *field* (1-4) to select 1 (Heiskanen 1924), 2 (IGF 1930),
  271. 3 (IGF 1967) or 4 (IGF 1980). Select from
  272. **-Af1**\ [,\ *field*] returns **faa** as stored in the data set
  273. [Default]. Optionally, sets the IGF *field* to use if you also have
  274. requested **ngrav** as an output column in **-F**.
  275. **-Af2**\ [,\ *field*] returns the difference between **gobs** and
  276. **ngrav** (with optional *field* directive).
  277. **-Af4**\ [,\ *field*] returns the combination of **gobs** + **eot** -
  278. **ngrav** (with optional *field* directive).
  279. **-Af8**\ [,\ *field*] returns the combination of **gobs** +
  280. **pred_eot** - **ngrav** (with optional *field* directive).
  281. **-Am**
  282. Determines how the **mag** column output is obtained. There may be
  283. one or two total field measurements in the file (**mtf1** and
  284. **mtf2**), and the column **msens** may state which one is the
  285. leading sensor (1 or 2; it may also be undefined). Select from
  286. **-Am1** returns **mag** as stored in the data set [Default].
  287. **-Am2** returns the difference between **mgfx** and **igrf**, where
  288. **x** is the leading sensor (**1** or **2**) indicated by the
  289. **msens** data field (defaults to **1** if unspecified).
  290. **-Am4** returns the difference between **mgfx** and **igrf**, where
  291. **x** is the sensor (**2** or **1**) *not* indicated by the
  292. **msens** data field (defaults to **2** if unspecified).
  293. **-Amc**\ *offset* applies a correction to compensate
  294. for the fact that the magnetic field was not acquired at the same
  295. position as the ship's position [i.e., the navigation]. This is
  296. accomplished by re-interpolating the total magnetic field to what it
  297. would have been if it were measured at the ship's position (remember,
  298. it probably was measured *offset* meters behind). Due to this
  299. interpolation step, bad navigation, namely too many repeated points,
  300. may cause trouble. Measures are taken to minimize this effect but
  301. they aren't 100% fool proof. The interpolation method is controlled
  302. by the GMT default :term:`GMT_INTERPOLANT`. Append **e** for meter, **f**
  303. for feet, **k** for km, **M** for miles, **n** for nautical miles,
  304. or **u** for survey feet [Default is **e** (meters)].
  305. .. _-D:
  306. **-Da**\ *startdate*
  307. Do not list data collected before *startdate*
  308. (yyyy-mm-dd\ **T**\ [hh:mm:ss]) [Default is start of cruise]. Use
  309. **-DA** to exclude records whose time is undefined (i.e., NaN).
  310. [Default reports those records].
  311. **-Db**\ *stopdate*
  312. Do not list data collected on or after *stopdate*
  313. (yyyy-mm-dd\ **T**\ [hh:mm:ss]). [Default is end of cruise]. Use **-DB**
  314. to exclude records whose time is undefined (i.e., NaN). [Default
  315. reports those records].
  316. .. _-E:
  317. **-E**
  318. Exact match: Only output records that match all the requested
  319. geophysical columns [Default outputs records that matches at least
  320. one of the observed columns].
  321. .. _-G:
  322. **-Ga**\ *startrec*
  323. Do not list records before *startrec* [Default is 0, the first
  324. record].
  325. **-Gb**\ *stoprec*
  326. Do not list data after *stoprec*. [Default is the last record].
  327. .. _-I:
  328. **-I**\ *ignore*
  329. Ignore certain data file formats from consideration. Append
  330. **a\|c\|m\|t** to ignore MGD77 ASCII, MGD77+ netCDF, MGD77T ASCII, or plain
  331. tab-separated ASCII table files, respectively. The option may be
  332. repeated to ignore more than one format. [Default ignores none].
  333. .. _-L:
  334. **-L**\ [*corrtable*]
  335. Apply optimal corrections to columns where such corrections are
  336. available. Append the correction table to use [Default uses the
  337. correction table mgd77_corrections.txt in the **$MGD77_HOME**
  338. directory]. For the format of this file, see CORRECTIONS below.
  339. .. _-N:
  340. **-Nd**\|\ **s**\ *unit*
  341. Append **d** for distance or **s** for speed, then give the desired
  342. *unit* as **e** (meter or m/s), **f** (feet or feet/s), **k** (km or
  343. km/hr), **m** (miles or miles/hr), **n** (nautical miles or knots),
  344. or **u** (survey feet or sfeet/s). [Default is **-Ndk** **-Nse** (km
  345. and m/s)].
  346. .. _-Q:
  347. **-Qa**\ *min*/*max*
  348. Specify an accepted range (*min*/*max*) of azimuths. Records whose
  349. track azimuth falls outside this range are ignored [0/360].
  350. **-Qc**\ *min*/*max*
  351. Specify an accepted range (*min*/*max*) of course changes. Records
  352. whose track course change falls outside this range are ignored
  353. [-360/+360]. Use **-QC** to take the absolute value of the course
  354. change before the test [Default uses signed course changes].
  355. **-Qv**\ *min*/*max*
  356. Specify an accepted range (*min*/*max*; or just *min* if there is no
  357. upper limit) of velocities. Records whose track speed falls outside
  358. this range are ignored [0/infinity].
  359. .. _-R:
  360. .. |Add_-Rgeo| unicode:: 0x20 .. just an invisible code
  361. .. include:: ../../explain_-Rgeo.rst_
  362. .. _-S:
  363. **-Sa**\ *startdist*
  364. Do not list data that are less than *startdist* meter along track
  365. from port of departure. Append **e** for meter, **f** for feet,
  366. **k** for km, **m** for miles, **n** for nautical miles, or **u**
  367. for survey feet [Default is 0e (meters)].
  368. **-Sb**\ *stopdist*
  369. Do not list data that are *stopdist* or more meters along track from
  370. port of departure. Append **e** for meter, **f** for feet, **k** for
  371. km, **m** for miles, **n** for nautical miles, or **u** for survey
  372. feet [Default is end of track].
  373. .. _-T:
  374. **-T**\ [**m**\|\ **e**]
  375. Turns OFF the otherwise automatic adjustment of values based on
  376. correction terms that are stored in the MGD77+ file and used to
  377. counteract such things as wrong units used by the source institution
  378. when creating the original MGD77 file from which the MGD77+ file
  379. derives (the option has no effect on plain MGD77 ASCII files).
  380. Append **m** or **e** to limit the option to the MGD77 or extended
  381. columns set only [Default applies to both]. Note that record-based
  382. E77 flags (MGD77+ format only) are not considered systematic corrections.
  383. Instead, the application of these bit-flags can be controlled via
  384. the : (colon) modifier to OPT(F).
  385. .. _-V:
  386. .. |Add_-V| unicode:: 0x20 .. just an invisible code
  387. .. include:: ../../explain_-V.rst_
  388. .. _-W:
  389. **-W**\ *weight*
  390. Set the weight for these data. Weight output option must be set in
  391. **-F**. This is useful if the data are to be processed with the
  392. weighted averaging techniques offered by :doc:`blockmean </blockmean>`,
  393. :doc:`blockmedian </blockmedian>`, and :doc:`blockmode </blockmode>` [1].
  394. .. _-Z:
  395. **-Z**\ **n**\|\ **p**
  396. Append the sign you want for **depth**, **carter**, and **msd**
  397. values below sea level (**-Zn** gives negative bathymetry) [Default
  398. is **-Zp** for positive down].
  399. .. |Add_-bo| replace:: ignored if **-bo** is selected. Likewise,
  400. string-fields cannot be selected. Note that if time is one of the
  401. binary output columns it will be stored as Unix-time (seconds since
  402. 1970). To read this information in GMT to obtain absolute calendar
  403. time will require you to use **-**\ **-TIME_SYSTEM=1**.
  404. .. include:: ../../explain_-bo.rst_
  405. .. |Add_-h| unicode:: 0x20 .. just an invisible code
  406. .. include:: ../../explain_-h.rst_
  407. .. include:: ../../explain_distcalc.rst_
  408. .. include:: ../../explain_help.rst_
  409. Examples
  410. --------
  411. To get a (distance, heading, gravity, bathymetry) listing from
  412. 01010047.mgd77, starting at June 3 1971 20:45 and ending at distance =
  413. 5000 km, use the following command:
  414. ::
  415. gmt mgd77list 01010047 -Da1971-06-03T20:45 -Sb5000 -Fdist,azim,faa,depth > myfile.txt
  416. To make input for :doc:`blockmean </blockmean>` and :doc:`surface </surface>` using free-air anomalies
  417. from all the cruises listed in the file cruises.lis, but only the data
  418. that are inside the specified area, and make the output binary:
  419. ::
  420. gmt mgd77list `cat cruises.lis` -Flon,lat,faa -R-40/-30/25/35 -bo > allgrav.b
  421. To extract the locations of depths exceeding 9000 meter that were not
  422. interpolated (**btc** != 1) from all the cruises listed in the file
  423. cruises.lis:
  424. ::
  425. gmt mgd77list `cat cruises.lis` -F"depth,DEPTH>9000,BTC!=1" > really_deep.txt
  426. To extract dist, faa, and grav12_2 from records whose depths are
  427. shallower than 3 km and where none of the requested fields are NaN, from
  428. all the MGD77+ netCDF files whose cruise ids are listed in the file
  429. cruises.lis, we try
  430. ::
  431. gmt mgd77list `cat cruises.lis` -E -Ia -F"dist,faa,grav12_2,depth<3000" > \
  432. shallow_grav.txt
  433. To extract dist, faa, and grav12_2 from all the MGD77+ netCDF files
  434. whose cruise ids are listed in the file cruises.lis, but only retrieve
  435. records whose bitflag for faa indicates BAD values, we try
  436. ::
  437. gmt mgd77list `cat cruises.lis` -E -Ia -F"dist,faa,grav12_2:+faa" > bad_grav.txt
  438. To output lon, lat, mag, and faa from all the cruises listed in the file
  439. cruises.lis, but recalculate the two residuals based on the latest
  440. reference fields, try:
  441. ::
  442. gmt mgd77list `cat cruises.lis` -Flon,lat,mag,faa -Af2,4 -Am2 > data.txt
  443. Recalculated Anomalies
  444. ----------------------
  445. When recalculated anomalies are requested (either explicitly via the
  446. **-A** option or implicitly via E77 metadata in the MGD77+ file) we only
  447. do so for the records whose original anomaly was not a NaN. This
  448. restriction is implemented since many anomaly columns contains
  449. corrections, usually in the form of hand-edited changes, that cannot be
  450. duplicated from the corresponding observation.
  451. Igrf
  452. ----
  453. The IGRF calculations are based on a Fortran program written by Susan
  454. Macmillan, British Geological Survey, translated to C via f2c by Joaquim
  455. Luis, U Algarve, and adapted to GMT-style by Paul Wessel.
  456. Igf
  457. ---
  458. The equations used are reproduced here using coefficients extracted
  459. directly from the source code (let us know if you find errors):
  460. (1) g = 978052.0 \* [1 + 0.005285 \* sin^2(lat) - 7e-6 \* sin^2(2\*lat)
  461. + 27e-6 \* cos^2(lat) \* cos^2(lon-18)]
  462. (2) g = 978049.0 \* [1 + 0.0052884 \* sin^2(lat) - 0.0000059 \*
  463. sin^2(2\*lat)]
  464. (3) g = 978031.846 \* [1 + 0.0053024 \* sin^2(lat) - 0.0000058 \*
  465. sin^2(2\*lat)]
  466. (4) g = 978032.67714 \* [(1 + 0.00193185138639 \* sin^2(lat)) / sqrt (1
  467. - 0.00669437999013 \* sin^2(lat))]
  468. Corrections
  469. -----------
  470. The correction table is an ASCII file with coefficients and parameters
  471. needed to carry out corrections. Comment records beginning with # are
  472. allowed. All correction records are of the form
  473. *cruiseID observation correction*
  474. where *cruiseID* is a NCEI prefix, *observation* is one of the
  475. abbreviations for geophysical observations listed under **-F** above,
  476. and *correction* consists of one or more *term*\ s that will be summed
  477. up and then **subtracted** from the observation before output. Each
  478. *term* must have this exact syntax:
  479. *factor*\ [\*[*function*]([*scale*](\ *abbrev*\ [-*origin*]))[^\ *power*]]
  480. where terms in brackets are optional (the brackets themselves are not
  481. used but regular parentheses must be used as indicated). No spaces are
  482. allowed except between *term*\ s. The *factor* is the amplitude of the
  483. basis function, while the optional *function* can be one of sin, cos, or
  484. exp. The optional *scale* and *origin* can be used to translate the
  485. argument (before giving it to the optional function). The argument
  486. *abbrev* is one of the abbreviations for observations listed above. If
  487. *origin* is given as **T** it means that we should replace it with the
  488. value of *abbrev* for the very first record in the file (this is usually
  489. only done for *time*). If the first record entry is NaN we revert
  490. *origin* to zero. Optionally, raise the entire expression to the given
  491. *power*, before multiplying by the amplitude. The following is an
  492. example of fictitious corrections to the cruise 99999999, implying the
  493. **depth** should have the Carter correction removed, **faa** should have
  494. a linear trend removed, the magnetic anomaly (**mag**) should be
  495. corrected by a strange dependency on ship heading and latitude, and
  496. **gob**\ s needs to have 10 mGal added (hence given as -10):
  497. 99999999 depth 1.0\*((carter))
  498. 99999999 faa 14.1 1e-5\*((time-T))
  499. 99999999 mag 0.5\*cos(0.5\*(azim-19))^2 1.0\*exp(-1e-3(lat))^1.5
  500. 99999999 gobs -10
  501. See Also
  502. --------
  503. :doc:`blockmean </blockmean>`,
  504. :doc:`blockmedian </blockmedian>`,
  505. :doc:`blockmode </blockmode>`,
  506. :doc:`mgd77convert`,
  507. :doc:`mgd77info`,
  508. :doc:`mgd77manage`,
  509. :doc:`mgd77track`,
  510. :doc:`surface </surface>`,
  511. References
  512. ----------
  513. The Marine Geophysical Data Exchange Format - MGD77, see
  514. `<http://www.ngdc.noaa.gov/mgg/dat/geodas/docs/mgd77.txt>`_
  515. IGRF, see `<http://www.ngdc.noaa.gov/IAGA/vmod/igrf/>`_
Tip!

Press p or to see the previous file or, n or to see the next file

Comments

Loading...