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

contour_common.rst_ 8.3 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
  1. |No-spaces|
  2. Description
  3. -----------
  4. Reads an ASCII [or binary] *table* and produces a raw
  5. contour plot by triangulation. By default, the optimal Delaunay
  6. triangulation is performed (using either Shewchuk's [1996] or Watson's
  7. [1982] method as selected during GMT installation; run the module with argument
  8. **-** to see which method is selected), but the user may optionally
  9. provide a second file with network information, such as a triangular
  10. mesh used for finite element modeling. In addition to contours, the area
  11. between contours may be painted according to the CPT.
  12. Alternatively, the *x, y, z* positions of the contour lines may be saved to
  13. one or more output files (or stdout) and no plot is produced.
  14. Required Arguments
  15. ------------------
  16. .. _-J:
  17. .. |Add_-J| unicode:: 0x20 .. just an invisible code
  18. .. include:: explain_-J.rst_
  19. .. _-R:
  20. .. |Add_-R| unicode:: 0x20 .. just an invisible code
  21. .. include:: explain_-R.rst_
  22. .. |Add_-Rz| unicode:: 0x20 .. just an invisible code
  23. .. include:: explain_-Rz.rst_
  24. Optional Arguments
  25. ------------------
  26. .. |Add_intables| unicode:: 0x20 .. just an invisible code
  27. .. include:: explain_intables.rst_
  28. .. _-A:
  29. **-A**\ [**n**\|\ *contours*][*labelinfo*]
  30. *contours* is annotation interval in data units; it is ignored if
  31. contour levels are given in a file via **-C**. [Default is no annotations]. Prepend
  32. **n** to disable all annotations implied by **-C**. To just select a few specific
  33. contours give them as a comma-separated string; if only a single contour please add
  34. a trailing comma so it is seen as a list and not a contour interval. The optional
  35. *labelinfo* controls the specifics of the label formatting and consists
  36. of a concatenated string made up of any of the following control arguments:
  37. .. include:: explain_clabelinfo.rst_
  38. .. _-B:
  39. .. include:: explain_-B.rst_
  40. .. _-C:
  41. **-C**\ *contours*
  42. The contours to be drawn may be specified in one of four possible ways:
  43. (1) If *contours* is a string with suffix ".cpt" and can be opened as a
  44. file, it is assumed to be a CPT. The color
  45. boundaries are then used as contour levels. If the CPT has
  46. annotation flags in the last column then those contours will be
  47. annotated. By default all contours are labeled; use **-An** to
  48. disable all annotations.
  49. (2) If *contours* is a file but not a CPT, it is expected to contain
  50. one record per contour, with information given in the order
  51. *contour-level* [*angle*] **C**\|\ **c**\|\ **A**\|\ **a** [*pen*],
  52. where items in brackets are optional. The levels marked **C** (or **c**)
  53. are contoured, while the levels marked **A** (or **a**) are both contoured
  54. and annotated. If the annotation *angle* is present we will plot the label
  55. at that fixed angle [aligned with the contour]. Finally, a contour-
  56. specific *pen* may be present and will override the pen set by **-W**
  57. for this contour level only. **Note**: Please specify *pen* in proper
  58. format so it can be distinguished from a plain number like *angle*.
  59. (3) If *contours* is a string with comma-separated values it is interpreted
  60. as those specific contours only. To indicate a single specific contour
  61. you must append a trailing comma to separate it from a contour interval.
  62. The **-A** option offers the same list choice so they may be used together
  63. to plot only specific annotated and non-annotated contours.
  64. (4) If no argument is given in modern mode then we select the current CPT.
  65. (5) Otherwise, *contours* is interpreted as a constant contour interval.
  66. If a file is given and **-T** is set, then only contours marked with
  67. upper case C or A will have tick-marks. In all cases the contour
  68. values have the same units as the file. Finally, if neither **-C**
  69. nor **-A** are set then we auto-compute suitable contour and annotation
  70. intervals from the data range, yielding approximately 10-20 contours.
  71. .. _-D:
  72. **-D**\ [*template*]
  73. .. include:: explain_contdump.rst_
  74. .. _-E:
  75. **-E**\ *indexfile*
  76. Give name of file with network information. Each record must contain
  77. triplets of node numbers for a triangle [Default computes these
  78. using Delaunay triangulation (see :doc:`triangulate`)].
  79. .. _-G:
  80. **-G**
  81. .. include:: explain_contlabel.rst_
  82. .. _-I:
  83. **-I**
  84. Color the triangles using the CPT.
  85. .. _-L:
  86. **-L**\ *pen* :ref:`(more ...) <set-pens>`
  87. Draw the underlying triangular mesh using the specified pen
  88. attributes [Default is no mesh].
  89. .. _-N:
  90. **-N**
  91. Do NOT clip contours or image at the boundaries [Default will clip
  92. to fit inside region **-R**].
  93. .. _-Q:
  94. **-Q**\ [*cut*][**+z**]
  95. Do not draw contours with less than *cut* number of points [Draw all contours].
  96. Alternatively, give instead a minimum contour length in distance units
  97. (see `Units`_ for available units and how distances are computed),
  98. including **c** (Cartesian distances using user coordinates) or **C** for plot
  99. length units in current plot units after projecting the coordinates.
  100. Optionally, append **z** to exclude the zero contour.
  101. .. _-S:
  102. **-S**\ [**p**\|\ **t**]
  103. Skip all input *xyz* points that fall outside the region [Default
  104. uses all the data in the triangulation]. Alternatively, use **-St**
  105. to skip triangles whose three vertices are all outside the region.
  106. **-S** with no modifier is interpreted as **-Sp**.
  107. .. _-T:
  108. **-T**\ [**h**\|\ **l**][**+a**][**+d**\ *gap*\ [/*length*]][**+l**\ [*labels*]]
  109. Will draw tick marks pointing in the downward direction every *gap*
  110. along the innermost closed contours only; append **+a** to tick all closed
  111. contours. Append **+d**\ *gap* and optionally tick
  112. mark *length* (append units as **c**, **i**, or **p**) or use defaults
  113. [15\ **p**/3\ **p**]. User may choose to tick only local highs or local
  114. lows by specifying **-Th** or **-Tl**, respectively. Append
  115. **+l**\ *labels* to annotate the centers of closed innermost contours
  116. (i.e., the local lows and highs). If no *labels* is appended we use -
  117. and + as the labels. Appending exactly two characters, e.g., **+l**\ *LH*,
  118. will plot the two characters (here, L and H) as labels. For more elaborate
  119. labels, separate the low and high label strings with a comma (e.g.,
  120. **+l**\ *lo*,\ *hi*). If a file is given by **-C** and **-T** is set,
  121. then only contours marked with upper case C or A will have tick marks
  122. [and annotations].
  123. .. _-U:
  124. .. include:: explain_-U.rst_
  125. .. _-V:
  126. .. |Add_-V| unicode:: 0x20 .. just an invisible code
  127. .. include:: explain_-V.rst_
  128. .. _-W:
  129. **-W**\ [*type*]\ *pen*\ [**+c**\ [**l**\|\ **f**]] :ref:`(more ...) <set-pens>`
  130. *type*, if present, can be **a** for annotated contours or **c** for
  131. regular contours [Default]. The *pen* sets the attributes for the
  132. particular line. Default pen for annotated contours: 0.75p,black.
  133. Regular contours use pen 0.25p,black. Normally, all contours are drawn
  134. with a fixed color determined by the pen setting. If the modifier **+cl** is appended
  135. then the color of the contour lines are taken from the CPT (see
  136. **-C**). If instead modifier **+cf** is appended then the color from the cpt
  137. file is applied to the contour annotations. Select **+c** for both effects.
  138. .. _-X:
  139. .. include:: explain_-XY.rst_
  140. .. |Add_-bi| replace:: [Default is 3 input columns]. Use 4-byte integer triplets for node ids (**-E**).
  141. .. include:: explain_-bi.rst_
  142. .. |Add_-bo| replace:: [Default is 3 output columns].
  143. .. include:: explain_-bo.rst_
  144. .. |Add_-d| unicode:: 0x20 .. just an invisible code
  145. .. include:: explain_-d.rst_
  146. .. |Add_-e| unicode:: 0x20 .. just an invisible code
  147. .. include:: explain_-e.rst_
  148. .. |Add_-h| unicode:: 0x20 .. just an invisible code
  149. .. include:: explain_-h.rst_
  150. .. include:: explain_-icols.rst_
  151. .. |Add_-l| replace:: Normally, the annotated contour is selected for the legend. You can select the regular contour instead, or both of them, by considering the *label* to be of the format [*annotcontlabel*][/*contlabel*]. If either label contains a slash (/) character then use | as the separator for the two labels instead.
  152. .. include:: explain_-l.rst_
  153. .. include:: explain_-qi.rst_
  154. .. include:: explain_colon.rst_
  155. .. |Add_perspective| unicode:: 0x20 .. just an invisible code
  156. .. include:: explain_perspective.rst_
  157. .. include:: explain_-t.rst_
  158. .. include:: explain_help.rst_
  159. .. include:: explain_distunits.rst_
Tip!

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

Comments

Loading...