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

earthtide.rst 4.6 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
  1. .. index:: ! earthtide
  2. .. include:: ../module_supplements_purpose.rst_
  3. *********
  4. earthtide
  5. *********
  6. |earthtide_purpose|
  7. Synopsis
  8. --------
  9. .. include:: ../../common_SYN_OPTs.rst_
  10. **gmt earthtide**
  11. |-T|\ [*min/max*\ /]\ *inc*\ [**+n**] \|\ |-T|\ *file*\|\ *list*
  12. |-G|\ *grdfile*
  13. [ |-C|\ *x|e,y|n,z|v* ]
  14. [ |SYN_OPT-I| ]
  15. [ |-L|\ *lon/lat* ]
  16. [ |SYN_OPT-R| ]
  17. [ |-S| ]
  18. [ |SYN_OPT-V| ]
  19. [ |SYN_OPT-r| ]
  20. [ |SYN_OPT--| ]
  21. |No-spaces|
  22. Description
  23. -----------
  24. Compute the three components of solid Earth tides as time-series or grids. Optionally compute also Sun and Moon position in lon,lat.
  25. The output can be either in the form of a grid or as a table printed to stdout. The format of the table data is:
  26. *time north east vertical* in units of meters.
  27. Required Arguments
  28. ------------------
  29. Either **-G**, **-S** or **-L**
  30. .. _-G:
  31. **-G**\ *grdfile*
  32. Write one or more tide component directly to grids; no table data are written to standard output.
  33. If more than one component are specified via **-C** then *grdfile* must contain the format flag %s
  34. so that we can embed the component code in the file names (*n* for north; *e* for east and *v* for vertical).
  35. If only one component is selected with **-C** than no code is appended to grid name (an no need to
  36. set the format flag %s). The grid(s) are computed at the time set by **-T**, if that option is used, or
  37. at the *now* time calculated in UTC from the computer clock.
  38. .. _-S:
  39. **-S**
  40. Output position of Sun and Moon in geographical coordinates plus distance
  41. in meters. Output is a Mx7 matrix where M is the number of times (set by -T)
  42. and columns are time, sun_lon, sun_lat, sun_dist moon_lon, moon_lat, moon_dist
  43. .. _-L:
  44. **-L**\ *lon/lat*
  45. Geographical coordinate of the location where to compute a time-series. Coordinates are geodetic (ellipsoidal)
  46. latitude and longitude. GRS80 ellipsoid is used. (Which can be considered equivalent to the WGS84 ellipsoid at
  47. the sub-millimeter level.)
  48. Optional Arguments
  49. ------------------
  50. .. _-C:
  51. **-C**\ **x**\|\ **e**,\ **y**\|\ **n**,\ **z**\|\ **v**
  52. Select which component to write to individual grids. Requires **-G**.
  53. Append comma-separated codes for available components: **x** or **e** for the east component;
  54. **y** or **n** for the north component; and **z** or **v** for the vertical component.
  55. For example, **-Ce**,\ **v**, will write 2 grids. One with east and other with the vertical components.
  56. If **-G** is set but not **-C** then the default is to write the vertical component.
  57. .. _-I:
  58. .. |Add_-I| replace:: Used only with **-G**. If not set, defaults to **-I30m**
  59. .. include:: ../../explain_-I.rst_
  60. .. _-R:
  61. .. |Add_-R| replace:: Used only with **-G**. If not set, defaults to **-Rd**
  62. .. include:: ../../explain_-R.rst_
  63. .. _-T:
  64. **-T**\ [*min/max*\ /]\ *inc*\ [**+n**] \|\ |-T|\ *file*\|\ *list*
  65. Make evenly spaced time-steps from *min* to *max* by *inc*. Append +n to indicate *inc* is the number of t-values
  66. to produce over the range instead. Append a valid time unit (d|h|m|s) to the increment. If only *min* is given then
  67. we use that date and time for the calculations. If no **-T** is provided get
  68. current time in UTC from the computer clock. If no **-G** or **-S** are provided then **-T** is interpreted to mean compute
  69. a time-series at the location specified by **-L**, thus then **-L** becomes mandatory.
  70. When **-G** and **-T**, only first time T series is considered. Finally, dates may range from 1901 through 2099.
  71. For details on array creation, see `Generate 1D Array`_.
  72. .. |Add_-bo| unicode:: 0x20 .. just an invisible code
  73. .. include:: ../../explain_-bo.rst_
  74. .. include:: ../../explain_-ocols.rst_
  75. .. |Add_nodereg| unicode:: 0x20 .. just an invisible code
  76. .. include:: ../../explain_nodereg.rst_
  77. .. _-V:
  78. .. |Add_-V| unicode:: 0x20 .. just an invisible code
  79. .. include:: ../../explain_-V.rst_
  80. .. include:: ../../explain_help.rst_
  81. .. include:: /explain_array.rst_
  82. Examples
  83. --------
  84. To compute a global grid of the vertical component with a grid step of 30m at noon of 18 Jun 2018,
  85. (note: we are using the defaults for **-R** and **-I**) try
  86. ::
  87. gmt earthtide -T2018-06-18T12:00:00 -Gsolid_tide_up.grd
  88. To obtain a one day long time-series, starting at same date, at the -7 *W*, 37 *N* and 1 minute interval, try
  89. ::
  90. gmt earthtide -T2018-06-18T/2018-06-19T/1m -L-7/37 > solid_tide.dat
  91. The get the Sun and Moon position in geographical coordinates at the *now* time
  92. ::
  93. gmt earthtide -S
  94. Notes
  95. -----
  96. #. All times, both input and output, are in UTC.
  97. References
  98. ----------
  99. http://geodesyworld.github.io/SOFTS/solid.htm
  100. See Also
  101. --------
  102. :doc:`gmt.conf </gmt.conf>`, :doc:`gmt </gmt>`,
Tip!

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

Comments

Loading...