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
|
- .. index:: ! grd2kml
- .. include:: module_core_purpose.rst_
- *******
- grd2kml
- *******
- |grd2kml_purpose|
- Synopsis
- --------
- .. include:: common_SYN_OPTs.rst_
- **gmt grd2kml** *grid*
- [ |-A|\ **a**\|\ **g**\|\ **s**\ [*altitude*] ]
- [ |-C|\ *cpt* ]
- [ |-E|\ *URL* ]
- [ |-F|\ *filtercode* ]
- [ |-H|\ *factor* ]
- [ |-I|\ [*intensfile*\|\ *intensity*\|\ *modifiers*] ]
- [ |-L|\ *tilesize* ]
- [ |-N|\ *prefix* ]
- [ |-S|\ [*extra*] ]
- [ |-T|\ *title* ]
- [ |-W|\ *cfile*\|\ *pen*\ [**+s**\ *scale*/*limit*] ]
- [ |SYN_OPT-V| ]
- [ |SYN_OPT-f| ]
- [ |SYN_OPT--| ]
- |No-spaces|
- Description
- -----------
- **grd2kml** reads a 2-D grid file and makes a *quadtree* of
- PNG or JPG images and KML wrappers for Google Earth using the selected
- tile size. We downsample the grid depending on the
- viewing level in the quadtree using a Gaussian filter, but other
- filters can be selected as well.
- Optionally, illumination may be added by providing a grid file with
- intensities in the (-1,+1) range or by giving instructions to derive intensities
- from the input data grid automatically (see **-I**). Values outside the (-1,+1) intensity range will be
- clipped. Map colors are specified via a color palette lookup table. Contour overlays are optional.
- If plain tiles are selected (i.e., no contours specified) then the PNG tiles are written directly from
- :doc:`grdimage`. Otherwise, we must first make a PostScript plot that is then converted to raster image via
- :doc:`psconvert`.
- Required Arguments
- ------------------
- *grid*
- A 2-D gridded data set (See GRID FILE FORMATS below.)
- Optional Arguments
- ------------------
- .. _-A:
- **-A**\ **a**\|\ **g**\|\ **s**\ [*altitude*]
- Select one of three altitude modes recognized by Google Earth that
- determines the altitude (in m) of the tile layer: **a** absolute
- altitude, **g** altitude relative to sea surface or ground, **s**
- altitude relative to seafloor or ground. To plot the tiles at a
- fixed altitude, append an altitude *altitude* (in m). Use 0 to clamp the
- features to the chosen reference surface. [By default the tiles are clamped
- to the sea surface or ground].
- .. _-C:
- .. include:: use_cpt_grd.rst_
- .. _-E:
- **-E**\ *URL*
- Instead of hosting all files on your computer, you may prepend a remote site URL. Then,
- the top-level *prefix*\ .kml file will use this URL to find all other files it references.
- After building completes you must place the entire *prefix* directory at the remote
- location pointed to by the *URL* [local files only]. With this arrangement you can
- share the *prefix*\ .kml with others (say, via email or for download) and users can
- open the file in their Google Earth and access the remote files from your server as needed.
- .. _-F:
- **-F**\ *filtercode*
- Specifies the filter to use for the downsampling of the grid for more
- distant viewing. Choose among **b**\ oxcar, **c**\ osine arch,
- **g**\ aussian, or **m**\ edian [Gaussian]. The filter width is set
- automatically depending on the level.
- .. _-H:
- **-H**\ *factor*
- Improve the quality of rasterization by passing the sub-pixel smoothing factor
- to psconvert (same as **-H** option in psconvert) [no sub-pixel smoothing].
- Ignored when **-W** is not used.
- .. _-I:
- **-I**\ [*intensfile*\|\ *intensity*\|\ *modifiers*]
- Gives the name of a grid file with intensities in the (-1,+1) range,
- or a constant intensity to apply everywhere (affects the ambient light).
- Alternatively, derive an intensity grid from the input data grid *grid*
- via a call to :doc:`grdgradient`; append **+a**\ *azimuth* and **+n**\ *args*
- to specify azimuth and intensity arguments for that module or just give **+d**
- to select the default arguments (**+a**\ -45\ **+nt**\ 1). If you want a more
- specific intensity scenario then run :doc:`grdgradient` separately first.
- [Default is no illumination].
- .. _-L:
- **-L**\ *tilesize*
- Sets the fixed size of the image building blocks. Must be an integer that
- is radix 2. Typical values are 256 or 512 [256]. **Note**: For global
- grids (here meaning 360-degree longitude range), we will select a
- *tilesize* of 360 if **-L** is not specified.
- .. _-N:
- **-N**\ *prefix*
- Sets a unique name prefixed used for the top-level KML filename *and* the
- directory where all referenced KML files and raster images will be written [GMT_Quadtree].
- .. _-S:
- **-S**\ [*extra*]
- Add extra layers beyond that necessary to capture the full resolution of the data [none].
- This will let GMT interpolate your grid and make more tiles, versus letting Google Earth
- interpolate the last resolution raster images.
- .. _-T:
- **-T**\ *title*
- Sets the title of the top-level document (i.e., its description).
- .. _-V:
- .. |Add_-V| unicode:: 0x20 .. just an invisible code
- .. include:: explain_-V.rst_
- .. _-W:
- **-W**\ *cfile*\|\ *pen*\ [**+s**\ *scale*/*limit*]
- Supply a file with records each holding a contour value and a contour pen.
- We then overlay the selected contour lines on top of the image [no contours].
- Consequently, **-W** triggers the tile creation via PostScript and thus is slower.
- If *cfile* is not a valid file we assume you instead gave a *pen* and want
- to draw all the contours implied by the *cpt* specified in **-C**. The contours
- are overlain via calls to :doc:`grdcontour`. **Note**: The contour pen width(s)
- refer to the highest tile level and are reduced by a factor of *scale* [sqrt(2)] for each
- lower level. Contours with scaled pen widths < *limit* [0.1] points are skipped (except
- for pen widths that exactly equal 0 or "faint"). Use **+s** to change these values.
- .. |Add_-f| unicode:: 0x20 .. just an invisible code
- .. include:: explain_-f.rst_
- Quadtree building
- -----------------
- We extend the input grid vi :doc:`grdcut` to obtain a square dimension that can be repeatedly divided by 2
- until we arrive at tiles with the original grid increments. For global grids this mean we
- extend the grid to a 360 x 360 Cartesian region and an initial grid increment of one
- degree. This is the first global tile. As the quartering of tiles and halving of grid
- increment continue we may not end exactly at the original grid spacing but at the largest
- increment less than or equal to the original increment. For non-global grids, e.g., smaller
- (local or regional) grids, we extend the domain to a radix-2 multiple of the *tilesize*
- times the grid increment. This initial tile is then quartered and the grid increment halved
- until we reach the original grid increment. Tiles that have all NaNs are not produced.
- THe tiles are inherently pixel-registered. Thus, if a global grid has gridline-registration then
- we are down-sampling the extended grid onto a pixel-registered coarser grid. Because these
- nodes do not coincide with the original nodes we widen the filter width by a factor of sqrt(2).
- We detect if NaNs are present in any tile and if so produce a transparent PNG tile; otherwise we
- make an opaque JPG tile.
- Contour overlays
- ----------------
- Because each tile is a fixed size image (e.g., 512x512 pixels) but the amount of data represented
- changes by factors of 4 for each new level, we cannot use a constant thickness contour pen for all
- levels. Thus, the pen you supply must be considered the final pen applied to the highest resolution
- map overlays. Furthermore, because the *dpi* here is very small compared to regular GMT plots, it is
- important to improve the appearance of the contours by using sub-pixel smoothing (**-H**). Both
- generating PostScript tiles and using sub-pixel smoothing adds considerable processing time over
- plain tiles.
- Notes
- -----
- The intensity grid can be created from the data grid using
- :doc:`grdgradient` and, optionally, modified by :doc:`grdmath` or
- :doc:`grdhisteq`. Custom intensity grids built with several different
- illumination angles can be combined with :doc:`grdmath`. For a single
- illumination angle the automatic illumination can be used instead.
- Examples
- --------
- .. include:: explain_example.rst_
- To test a quadtree image representation of the coarse topography grid earth_relief_06m, using
- the optimally determined tile size, auto color, and supplying a suitable title, try::
- gmt grd2kml @earth_relief_06m -NEarth6m -T"Earth Relief 6x6 arc minutes" -Cearth
- To make a quadtree image representation of the large topography grid file ellice_basin.nc,
- supplying automatic shading based on the topography, and using 512x512 tiles,
- supplying a suitable title, and using color masking for unmapped area, try::
- gmt grd2kml ellice_basin.nc -I+d -Nellice -L512 -T"Ellice Basin Bathymetry"
- See Also
- --------
- :doc:`gmt`,
- :doc:`gmt.conf`,
- :doc:`gmt2kml`,
- :doc:`grdgradient`,
- :doc:`grdhisteq`,
- :doc:`grdimage`,
- :doc:`grdmath`,
- :doc:`kml2gmt`,
- :doc:`psconvert`
|