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

GMT_Chapter_1.tex 12 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
  1. %------------------------------------------
  2. % $Id$
  3. %
  4. % The GMT Documentation Project
  5. % Copyright (c) 2000-2012.
  6. % P. Wessel, W. H. F. Smith, R. Scharroo, and J. Luis
  7. %------------------------------------------
  8. %
  9. \chapter{Preface}
  10. \label{ch:1}
  11. \thispagestyle{headings}
  12. While \GMT\ has served the map-making and data processing needs of scientists since 1988\footnote{Version
  13. 1.0 was then informally released at the Lamont-Doherty Earth Observatory.}, the current global use was
  14. heralded by the first official release in \emph{EOS Trans. AGU} in the fall of 1991. Since then,
  15. \GMT\ has grown to become a standard tool for many users, particularly in the Earth and Ocean Sciences.
  16. Development has at times been rapid, and numerous releases have seen the light of day since the early
  17. versions. For a detailed history of the changes from release to release, see file \filename{ChangeLog}
  18. in the main \GMT\ directory. For a nightly snapshot of ongoing activity, see the online
  19. \htmladdnormallink{ChangeLog}{http://\GMTSITE/gmt/gmt_changelog.php} page.
  20. The success of \GMT\ is to a large degree due to the input of the user community. In fact, most of the
  21. capabilities and options in \GMT\ programs originated as user requests.
  22. We would like to hear from you should you have any suggestions for future enhancements and modification.
  23. Please send your comments to the
  24. \htmladdnormallink{GMT help list}{mailto:gmt-help@lists.hawaii.edu}.
  25. \section{What is new in \gmt\ 5.x?}
  26. \GMT\ 5 represents a new branch of \GMT\ development that preserves the capabilities of the previous
  27. versions while adding new tricks to many of the tools. Furthermore, we have added system-wide
  28. capabilities for handling PDF transparency, dealing with GIS aspatial data, and eliminated the need
  29. for the \Opt{m} option. Our \PS\ library \GMTprog{PSL} has seen a complete rewrite as well and produce
  30. shorter and more compact \PS.
  31. However, the big news is for developers who wish to leverage \GMT\ in their
  32. own applications. We have completely revamped the code base so that high-level \GMT\ functionality
  33. is now accessible via \GMT\ ``modules''. These are high-level functions named after their corresponding
  34. programs (.e.g., \GMTfunc{GMT\_grdimage}) that contains all of the functionality of that program within
  35. the function. While currently callable from C/C++ only, we have built several of the Matlab interface
  36. modules as well and will soon start on the Python version. Developers should consult the GMT API Documentation for more details.
  37. Most of the \GMT\ default parameters have changed named in order to group parameters into logical groups
  38. and to use more consistent naming. A new default parameter has been added as well:
  39. \textbf{MAP\_ANNOT\_ORTHO}, which controls whether axes annotations for Cartesian plots are horizontal or
  40. orthogonal to the individual axes.
  41. Because of the default name changes and other command-line changes (such as making \Opt{m} obsolete), we
  42. recommend that users of \GMT\ 4 consider learning the new rules and defaults. However, to ease the
  43. transition to \GMT\ 5 you may use the \-\-enable-compat switch when running configure , thus allowing the use
  44. of many obsolete default names and command switches (you will receive a warning instead).
  45. \subsection{Overview of \gmt\ 5.0.0b [Aug-25, 2011]}
  46. This version shares the same bug fixes applied to \GMT\ 4.5.7, released July 15, 2011.
  47. Several new programs have been added; some have been promoted from earlier supplements:
  48. \begin{description}
  49. \item [\GMTprog{gmt2kml}]: A \GMTprog{psxy}-like tool to produce KML overlays for Google Earth.
  50. \item [\GMTprog{gmtdp}]: A line-reduction tool for coastlines and similar lines.
  51. \item [\GMTprog{gmtstitch}]: Join individual lines whose end points match within given tolerance.
  52. \item [\GMTprog{gmtwhich}]: Return the full path to specified data files.
  53. \item [\GMTprog{kml2gmt}]: Extract GMT data tables from Google Earth KML files.
  54. \item [\GMTprog{gmtspatial}]: Perform geospatial operations on lines and polygons.
  55. \item [\GMTprog{gmtvector}]: Perform basic vector manipulation in 2-D and 3-D.
  56. \end{description}
  57. Here is a list of the recent enhancement to various programs to date; we expect more to be added
  58. before \GMT\ 5 becomes the official version and \GMT\ 4 will be retired:
  59. \begin{enumerate}
  60. \item All programs now use consistent, standardized choices for plot dimension units (\textbf{c}m, \textbf{i}nch, or
  61. \textbf{p}oint;
  62. we no longer consider \textbf{m}eter a plot length unit), and projected distances (choose spherical arc lengths in \textbf{d}egree,
  63. \textbf{m}inute, and \textbf{s}econd [was \textbf{c}], or distances in m\textbf{e}ter [Default], \textbf{f}eet [new],
  64. \textbf{k}m, \textbf{M}iles [was sometimes \textbf{i} or \textbf{m}], or \textbf{n}autical miles).
  65. \item All program that reads data tables can now process multi-segment tables automatically. This means
  66. programs that did not have this capability (e.g., \GMTprog{filter1}) now can filter segments
  67. separately; consequently, there is no longer a \Opt{m} option.
  68. \item All program that reads data tables can now process the aspatial metadata in OGR/GMT files with the new \Opt{a} option.
  69. These are produced by \progname{ogr2ogr} (a GDAL tool) when selecting the -f ``GMT'' output format. See Appendix Q
  70. for an explanation of the OGR/GMT file format. Because all GIS information is encoded via \GMT\ comment lines
  71. these files can also be used in \GMT\ 4 (the GIS metadata is simply skipped).
  72. \item All program that read data tables can control which columns to read and in what order with the new \Opt{i} option.
  73. \item All program that write data tables can control which columns to write and in what order with the new \Opt{o} option.
  74. \item All program that write data tables can specify a custom binary format using the enhanced \Opt{b} option.
  75. \item All program that read data tables can control how records with NaNs are handled with the new \Opt{s} option.
  76. \item All program that read grids can use new common option \Opt{n} to control grid interpolation settings and boundary conditions.
  77. \item All program that read grids can now handle Arc/Info float binary files (GRIDFLOAT) and ESRI .hdr formats.
  78. \item All program that read grids now set boundary conditions to aid further processing. If a subset then the
  79. boundary conditions are taken from the surrounding grid values.
  80. \item There is now defaults parameters that control which algorithms to use for Fourier transforms and triangulation.
  81. \item \GMT\ 5 only produces \PS\ and no longer has a setting for EPS. We made this decision since a) our EPS effort was always
  82. very approximate (no consideration of font metrics. etc.) and often wrong, and b) \GMTprog{ps2raster} handles it exactly.
  83. \item The \Opt{B} option can now handle irregular and custom annotations (see Section \ref{sec:custaxes}).
  84. It also has an automatic mode which will select optimal intervals.
  85. \item All plot programs can take a new \Opt{p} option for perspective view from infinity. In \GMT\ 4, only some
  86. programs could do this (e.g., \GMTprog{pscoast}) and it took a program-specific option, typically \Opt{E} and
  87. sometimes an option \Opt{Z} would be needed as well. This information is now all passed via \Opt{p} and
  88. applies across all \GMT\ plotting programs.
  89. \item All plot programs can take a new \Opt{t} option to modify the PDF transparency level. However, as \PS\ has
  90. no provision for transparency you can only see the effect if you convert it to PDF.
  91. \item All text can now optionally be filled with patterns and/or drawn with outline pens. In the past, only
  92. \GMTprog{pstext} could plot outline fonts via \Opt{S}\emph{pen}. Now, any text can be an outline text
  93. by manipulating the corresponding FONT defaults (e.g., \textbf{FONT\_TITLE}).
  94. \item All color or fill specifications may append @\emph{transparency} to change the PDF transparency level for that item.
  95. See \Opt{t} for limitations on how to visualize this transparency.
  96. \item \GMTprog{gmtconvert} now has optional PCRE (regular expression) support; Thanks to Florian Wobbe.
  97. \item \GMTprog{grdblend} can take list of grids on the command line and blend, and now has more blend choices. Grids no
  98. longer have to have same registration or spacing.
  99. \item \GMTprog{grdfilter} can now do spherical filtering (with wrap around longitudes and over poles) for non-global grids.
  100. We have also begun implementing Open MP threads to speed up calculations on multi-core machines. Finally, we have
  101. added rectangular filtering and automatic resampling to input resolution for high-pass filters.
  102. \item \GMTprog{grdmask} has new option \Opt{Ni}$|$I$|$p$|$P to set inside of polygons to the polygon IDs.
  103. These may come from OGR aspatial values, segment head \Opt{L}ID,
  104. or a running number, starting at a specified origin [0].
  105. Now correctly handles polygons with perimeters and holes.
  106. \item \GMTprog{grdtrack} has a new \Opt{C}, \Opt{D} options to automatically create an equidistant set of cross-sectional
  107. profiles given input line segments; one or more grids can then be sampled at these locations. Finally, \Opt{N}
  108. will not skip points that are outside the grid domain but return NaN as sampled value.
  109. \item \GMTprog{mapproject} has a new \Opt{N} option to do geodetic/geocentric conversions; it combines with \Opt{I}
  110. for inverse conversions. Also, we have extended \Opt{A} to accept \Opt{A}\textbf{o}$|$\textbf{O} to compute line orientations (-90/90).
  111. \item \GMTprog{makecpt} and \GMTprog{grd2cpt} has a new \Opt{F} option to specify output color representation, e.g.,
  112. to output the CPT table in h-s-v format despite originally being given in r/g/b.
  113. \item \GMTprog{minmax} has new option \Opt{A} to select what group to report on (all input, per file, or per segment).
  114. \item \GMTprog{gmtconvert} has new option \Opt{Q} to select a particular segment number.
  115. \item \GMTprog{gmtmath} and \GMTprog{grdmath} now support simple replacement macros via user files
  116. \filename{.grdmath} and \filename{.gmtmath}. This mechanism works by replacing the macro name
  117. with the equivalent arguments in the program argument lists.
  118. \item \GMTprog{grdvolume} has enhanced \Opt{T}, now \Opt{T}[\textbf{c}$|$\textbf{h}] for ORS estimates based on max curvature or height.
  119. \item \GMTprog{ps2raster} has added a \Opt{TF} option to create multi-page PDF files.
  120. \item \GMTprog{pscontour} now similar to \GMTprog{grdcontour} in the options it takes, e.g., \Opt{C} in particular.
  121. In \GMT\ 4, the program could only read a CPT file and not take a specific contour interval.
  122. \item \GMTprog{psscale} has a new option \Opt{T} that paints a rectangle behind the color bar.
  123. \item \GMTprog{psxy.c} and \GMTprog{psxyz.c} can take symbol modifier \textbf{+s}\emph{scale}[\emph{unit}][/\emph{origin}][{ \bf l}]
  124. in \Opt{S} to adjust scales read from files. This is used when you have data in the third column that should be
  125. used for symbol size but they need to be offset (by \emph{origin}) and scaled by (\emph{scale}) first; \textbf{l} means
  126. take the logarithm of the data column first. Also, the custom symbol macro languages has been expanded considerably
  127. to allow for complicated, multi-parameter symbols; see Appendix N for details.
  128. \item \GMTprog{pstext.c} can take simplified input via new option \Opt{F} to set fixed font (including size), angle, and justification. If
  129. these parameters are fixed for all the text strings then the input can simply be \emph{x y text}.
  130. \end{enumerate}
  131. Several supplements have new feature as well:
  132. \begin{enumerate}
  133. \item The spotter programs can now read Gplates rotations directly as well as write this format.
  134. Now, \GMTprog{rotconverter} can extract plate circuit rotations on-the-fly from the Gplates rotation file.
  135. \end{enumerate}
Tip!

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

Comments

Loading...