/usr/share/doc/gmt/html/man/gmt2kml.html is in gmt-doc 4.5.11-1build1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
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 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 | <!-- Creator : groff version 1.19.2 -->
<!-- CreationDate: Tue Nov 5 09:45:47 2013 -->
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta name="generator" content="groff -Thtml, see www.gnu.org">
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<meta name="Content-Style" content="text/css">
<style type="text/css">
p { margin-top: 0; margin-bottom: 0; }
pre { margin-top: 0; margin-bottom: 0; }
table { margin-top: 0; margin-bottom: 0; }
</style>
<title>GMT2KML</title>
</head>
<body bgcolor="#ffffff">
<h1 align=center>GMT2KML</h1>
<a href="#NAME">NAME</a><br>
<a href="#SYNOPSIS">SYNOPSIS</a><br>
<a href="#DESCRIPTION">DESCRIPTION</a><br>
<a href="#OPTIONS">OPTIONS</a><br>
<a href="#EXAMPLES">EXAMPLES</a><br>
<a href="#LIMITATIONS">LIMITATIONS</a><br>
<a href="#MAKING KMZ FILES">MAKING KMZ FILES</a><br>
<a href="#KML HIERARCHY">KML HIERARCHY</a><br>
<a href="#SEGMENT INFORMATION">SEGMENT INFORMATION</a><br>
<a href="#SEE ALSO">SEE ALSO</a><br>
<hr>
<a name="NAME"></a>
<h2>NAME</h2>
<p style="margin-left:11%; margin-top: 1em">gmt2kml −
Convert GMT data tables to KML files for Google Earth</p>
<a name="SYNOPSIS"></a>
<h2>SYNOPSIS</h2>
<p style="margin-left:11%; margin-top: 1em"><b>gmt2kml</b>
[ <i>infile(s)</i> ] [
<b>−Aa</b>|<b>g</b>|<b>s</b>[<i>alt</i>|<b>x</b><i>scale</i>]
] [ <b>−C</b><i>cpt</i> ] [
<b>−D</b><i>descriptfile</i> ] [
<b>−E</b>[<i>altitude</i>] ] [
<b>−Fe</b>|<b>s</b>[<i>cpt</i>]|<b>t</b>|<b>l</b>|<b>p</b>
] [ <b>−Gf|n[-|</b><i>fill</i>] ] [
<b>−H</b>[<b>i</b>][<i>nrec</i>] ] [
<b>−I</b><i>icon</i> ] [ <b>−K</b>] [
<b>−L</b><i>col1:name1,col2:name2,...</i> ] [
<b>−N</b>[+|<i>name_template</i>|<i>name</i>] ] [
<b>−O</b>] [
<b>−Q</b>[<b>s</b>|<b>l</b>|<b>p</b>]<i>transparency</i>
] [ <b>−Ra</b>|<i>w/e/s/n</i> ] [
<b>−Sc</b>|<b>n</b><i>scale</i>] ] [
<b>−T</b><i>title</i>[/<i>foldername</i>] ] [
<b>−V</b> ] [ <b>−W</b>-|<i>pen</i> ] [
<b>−Z</b><i>args</i> ] [
<b>−:</b>[<b>i</b>|<b>o</b>] ] [
<b>−bi</b>[<b>s</b>|<b>S</b>|<b>d</b>|<b>D</b>[<i>ncol</i>]|<b>c</b>[<i>var1</i><b>/</b><i>...</i>]]
] [ <b>−f</b>[<b>i</b>|<b>o</b>]<i>colinfo</i> ] [
<b>−m</b>[<b>i</b>|<b>o</b>][<i>flag</i>] ] [ >
<i>output.kml</i> ]</p>
<a name="DESCRIPTION"></a>
<h2>DESCRIPTION</h2>
<p style="margin-left:11%; margin-top: 1em"><b>gmt2kml</b>
reads one or more GMT table file and converts them to a
single output file using Google Earth’s KML format.
Data may represent points, lines, or polygons, and you may
specify additional attributes such as title, altitude mode,
colors, pen widths, transparency, regions, and data
descriptions. You may also extend the feature down to ground
level (assuming it is above it) and use custom icons for
point symbols. <br>
The input file should contain the following columns: <i><br>
lon lat</i> [ <i>alt</i> ] [ <i>timestart</i> [
<i>timestop</i> ] ] <br>
where <i>lon</i> and <i>lat</i> are required for all
features, <i>alt</i> is optional for all features (see also
<b>−A</b> and <b>−C</b>), and <i>timestart</i>
and <i>timestop</i> apply to events and timespan features.
<i><br>
infile(s)</i></p>
<p style="margin-left:22%;">ASCII (or binary, see
<b>−bi</b>) data file(s) to be operated on. If not
given, standard input will be read.</p>
<a name="OPTIONS"></a>
<h2>OPTIONS</h2>
<p style="margin-left:11%; margin-top: 1em">No space
between the option flag and the associated arguments.</p>
<table width="100%" border=0 rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p style="margin-top: 1em" valign="top"><b>−A</b></p> </td>
<td width="8%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Select one of three
altitude modes recognized by Google Earth that determines
the altitude (in m) of the feature: <b>a</b> absolute
altitude, <b>g</b> altitude relative to sea surface or
ground, <b>s</b> altitude relative to seafloor. To plot the
features at a fixed altitude, append an altitude <i>alt</i>
(in m). Use 0 to clamp the features to the chosen reference
surface. Append <b>x</b><i>scale</i> to scale the altitude
from the input file by that factor. If no value is appended,
the altitude (in m) is read from the 3rd column of the input
file. [By default the features are clamped to the sea
surface or ground].</p></td>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p style="margin-top: 1em" valign="top"><b>−C</b></p> </td>
<td width="8%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Use color palette
for assigning colors to the symbol, event, or timespan
icons, based on the value in the 3rd column of the input
file. Ignored when plotting lines or polygons.</p></td>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p style="margin-top: 1em" valign="top"><b>−D</b></p> </td>
<td width="8%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">File with HTML
snippets that will be included as part of the main
description content for the KML file [no description]. See
SEGMENT INFORMATION below for feature-specific
descriptions.</p> </td>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p style="margin-top: 1em" valign="top"><b>−E</b></p> </td>
<td width="8%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Extrude feature
down to ground level [no extrusion].</p></td>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p style="margin-top: 1em" valign="top"><b>−F</b></p> </td>
<td width="8%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Sets the feature
type. Choose from points (<b>e</b>vent, <b>s</b>ymbol, or
<b>t</b>imespan), <b>l</b>ine, or <b>p</b>olygon [symbol].
The first two columns of the input file should contain
(<i>lon, lat</i>). When altitude or value is required (i.e.,
no <i>altitude</i> value was given with <b>−A</b>, or
<b>−C</b> is set), the third column needs to contain
the <i>altitude</i> (in m). The event (<b>−Fe</b>) is
a symbol that should only be active at a particular
<i>time</i>, given in the next column. Timespan
(<b>−Ft</b>) is a symbol that should only be active
during a particular time period indicated by the next two
columns (<i>timestart, timestop</i>). Use NaN to indicate
unbounded time limits. If used, times should be in ISO
format yyyy-mm-ddThh:mm:ss[.xxx] or in GMT relative time
format (see <b>−f</b>).</p></td>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p style="margin-top: 1em" valign="top"><b>−G</b></p> </td>
<td width="8%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Set fill color for
symbols, extrusions and polygons (<b>−Gf</b>) [Default
is lightorange] or text labels (<b>−Gn</b>) [Default
is white]. Optionally, use <b>−Gf-</b> to turn off
polygon fill, and <b>−Gn-</b> to disable labels. (See
SPECIFYING FILL below).</p></td>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p style="margin-top: 1em" valign="top"><b>−H</b></p> </td>
<td width="8%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Input file(s) has
header record(s). If used, the default number of header
records is <b><A HREF="gmtdefaults.html#N_HEADER_RECS">N_HEADER_RECS</A></b>. Use <b>−Hi</b> if
only input data should have header records [Default will
write out header records if the input data have them]. Blank
lines and lines starting with # are always skipped.</p></td>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p style="margin-top: 1em" valign="top"><b>−I</b></p> </td>
<td width="8%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Specify the URL to
an alternative icon that should be used for the symbol
[Default is a Google Earth circle]. If the URL starts with +
then we will prepend http://maps.google.com/mapfiles/kml/ to
the name. [Default is a local icon with no directory
path].</p> </td>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p style="margin-top: 1em" valign="top"><b>−K</b></p> </td>
<td width="8%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Allow more KML code
to be appended to the output later [finalize the KML
file].</p> </td>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p style="margin-top: 1em" valign="top"><b>−L</b></p> </td>
<td width="8%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Extended data
given. Append one or more strings of the form
<i>col</i>:<i>name</i> separated by commas. We will expect
the listed data columns to exist in the input and they will
be encoded in the KML file as Extended Data sets, whose
attributes will be available in the Google Earth balloon
when the item is selected.</p></td>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p style="margin-top: 1em" valign="top"><b>−N</b></p> </td>
<td width="8%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">By default, if
multisegment headers contain a <b>−L</b>"label
string" then we use that for the name of the KML
feature (polygon, line segment or set of symbols). Default
names for these segments are "Line %d" and
"Point Set %d", depending on the feature, where %d
is a sequence number of line segments within a file. Each
point within a line segment will be named after the line
segment plus a sequence number. Default is simply
"Point %d".</p></td>
</table>
<p style="margin-left:22%;">Alternatively, select one of
these options: (1) append <b>+</b> to supply individual
symbol labels directly at the end of the data record, (2)
append a string that may include %d or a similar integer
format to assign unique name IDs for each feature, with the
segment number (for lines and polygons) or point number
(symbols) appearing where %d is placed, (3) give no
arguments to turn symbol labeling off; line segments will
still be named.</p>
<table width="100%" border=0 rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="11%"></td>
<td width="4%">
<p style="margin-top: 1em" valign="top"><b>−O</b></p> </td>
<td width="7%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Appended KML code
to an existing KML file [initialize a new KML file].</p></td>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="4%">
<p style="margin-top: 1em" valign="top"><b>−Q</b></p> </td>
<td width="7%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Set the
transparency level for the selected feature (<b>e</b>,
<b>s</b>, <b>t</b>, <b>l</b>, or <b>p</b>, plus <b>n</b> for
name labels). Transparency goes from 0 (fully transparent)
to 1 (opaque) [0.75 for polygons, 1 for symbols, lines, and
labels].</p> </td>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="4%">
<p style="margin-top: 1em" valign="top"><b>−R</b></p> </td>
<td width="7%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Issue a single
Region tag. Append <i>w/e/s/n</i> to set a particular region
(will ignore points outside the region), or append <b>a</b>
to determine and use the actual domain of the data (single
file only) [no region tags issued].</p></td>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="4%">
<p style="margin-top: 1em" valign="top"><b>−S</b></p> </td>
<td width="7%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Scale icons or
labels. Here, <b>−Sc</b> sets a scale for the symbol
icon, whereas <b>−Sn</b> sets a scale for the name
labels [1 for both].</p></td>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="4%">
<p style="margin-top: 1em" valign="top"><b>−T</b></p> </td>
<td width="7%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Sets the document
title [GMT Data Document]. Optionally, append
/<i>FolderName</i>; this allows you, with <b>−O</b>,
<b>−K</b>, to group features into folders within the
KML document. [The default folder name is "<i>Name</i>
Features", where <i>Name</i> is Point, Event, Timespan,
Line, or Polygon].</p></td>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="4%">
<p style="margin-top: 1em" valign="top"><b>−V</b></p> </td>
<td width="7%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Selects verbose
mode, which will send progress reports to stderr [Default
runs "silently"].</p></td>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="4%">
<p style="margin-top: 1em" valign="top"><b>−W</b></p> </td>
<td width="7%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Set pen attributes
for lines or polygon outlines. Append pen attributes to use
[Defaults: width = 1p, color = black, texture = solid].
Optionally, use <b>−W-</b> to turn off polygon outline
Note that for KML the pen width is given as integer pixel
widths so you must specify pen width as <i>n</i><b>p</b>,
where <i>n</i> is an integer. (See SPECIFYING PENS
below).</p> </td>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="4%">
<p style="margin-top: 1em" valign="top"><b>−Z</b></p> </td>
<td width="7%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Set one or more
attributes of the Document and Region tags. Append
<b>+a</b><i>alt_min/alt_max</i> to specify limits on
visibility based on altitude. Append
<b>+l</b><i>lod_min/lod_max</i> to specify limits on
visibility based on Level Of Detail, where <i>lod_max</i> ==
-1 means it is visible to infinite size. Append
<b>+f</b><i>fade_min/fade_max</i> to fade in and out over a
ramp [abrupt]. Append <b>+v</b> to make a feature <i>not</i>
visible when loaded [visible]. Append <b>+o</b> to open a
folder or document in the sidebar when loaded [closed].</p></td>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="4%">
<p style="margin-top: 1em" valign="top"><b>−:</b></p> </td>
<td width="7%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Toggles between
(longitude,latitude) and (latitude,longitude) input and/or
output. [Default is (longitude,latitude)]. Append <b>i</b>
to select input only or <b>o</b> to select output only.
[Default affects both].</p></td>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="4%">
<p style="margin-top: 1em" valign="top"><b>−bi</b></p> </td>
<td width="7%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Selects binary
input. Append <b>s</b> for single precision [Default is
<b>d</b> (double)]. Uppercase <b>S</b> or <b>D</b> will
force byte-swapping. Optionally, append <i>ncol</i>, the
number of columns in your binary input file if it exceeds
the columns needed by the program. Or append <b>c</b> if the
input file is netCDF. Optionally, append
<i>var1</i><b>/</b><i>var2</i><b>/</b><i>...</i> to specify
the variables to be read. [Default is 2 input columns].</p></td>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="4%">
<p style="margin-top: 1em" valign="top"><b>−f</b></p> </td>
<td width="7%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Special formatting
of input and/or output columns (time or geographical data).
Specify <b>i</b> or <b>o</b> to make this apply only to
input or output [Default applies to both]. Give one or more
columns (or column ranges) separated by commas. Append
<b>T</b> (absolute calendar time), <b>t</b> (relative time
in chosen <b><A HREF="gmtdefaults.html#TIME_UNIT">TIME_UNIT</A></b> since <b><A HREF="gmtdefaults.html#TIME_EPOCH">TIME_EPOCH</A></b>),
<b>x</b> (longitude), <b>y</b> (latitude), or <b>f</b>
(floating point) to each column or column range item.
Shorthand <b>−f</b>[<b>i</b>|<b>o</b>]<b>g</b> means
<b>−f</b>[<b>i</b>|<b>o</b>]0<b>x</b>,1<b>y</b>
(geographic coordinates).</p></td>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="4%">
<p style="margin-top: 1em" valign="top"><b>−m</b></p> </td>
<td width="7%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Multiple segment
file(s). Segments are separated by a special record. For
ASCII files the first character must be <i>flag</i> [Default
is ’>’]. For binary files all fields must be
NaN and <b>−b</b> must set the number of output
columns explicitly. By default the <b>−m</b> setting
applies to both input and output. Use <b>−mi</b> and
<b>−mo</b> to give separate settings to input and
output. The <b>−m</b> option make sure that segment
headers in the input files are copied to output, but it has
no effect on the data selection. Selection is always done
point by point, not by segment.</p></td>
</table>
<p style="margin-left:11%; margin-top: 1em"><b>SPECIFYING
PENS</b></p>
<table width="100%" border=0 rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="11%"></td>
<td width="4%">
<p valign="top"><i>pen</i></p></td>
<td width="7%"></td>
<td width="78%">
<p valign="top">The attributes of lines and symbol outlines
as defined by <i>pen</i> is a comma delimetered list of
<i>width</i>, <i>color</i> and <i>texture</i>, each of which
is optional. <i>width</i> can be indicated as a measure
(points, centimeters, inches) or as <b>faint</b>,
<b>thin</b>[<b>ner</b>|<b>nest</b>],
<b>thick</b>[<b>er</b>|<b>est</b>],
<b>fat</b>[<b>ter</b>|<b>test</b>], or <b>obese</b>.
<i>color</i> specifies a gray shade or color (see SPECIFYING
COLOR below). <i>texture</i> is a combination of dashes
‘-’ and dots ‘.’.</p></td>
</table>
<p style="margin-left:11%; margin-top: 1em"><b>SPECIFYING
COLOR</b></p>
<table width="100%" border=0 rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="11%"></td>
<td width="7%">
<p valign="top"><i>color</i></p></td>
<td width="4%"></td>
<td width="78%">
<p valign="top">The <i>color</i> of lines, areas and
patterns can be specified by a valid color name; by a gray
shade (in the range 0−255); by a decimal color code
(r/g/b, each in range 0−255; h-s-v, ranges
0−360, 0−1, 0−1; or c/m/y/k, each in range
0−1); or by a hexadecimal color code (#rrggbb, as used
in HTML). See the <b><A HREF="gmtcolors.html">gmtcolors</A></b> manpage for more
information and a full list of color names.</p></td>
</table>
<a name="EXAMPLES"></a>
<h2>EXAMPLES</h2>
<p style="margin-left:11%; margin-top: 1em">To convert a
file with point locations (lon, lat) into a KML file with
red circle symbols, try</p>
<p style="margin-left:11%; margin-top: 1em">gmt2kml
mypoints.txt <b>−Gf</b> red <b>−Fs</b> >
mypoints.kml</p>
<p style="margin-left:11%; margin-top: 1em">To convert a
multisegment file with lines (lon, lat) separated by
multisegment headers that contain a <b>−L</b>
labelstring with the feature name, selecting a thick white
pen, and title the document, try</p>
<p style="margin-left:11%; margin-top: 1em">gmt2kml
mylines.txt <b>−W</b> thick,white <b>−Fl
−T</b>"Lines from here to there" >
mylines.kml</p>
<p style="margin-left:11%; margin-top: 1em">To convert a
multisegment file with polygons (lon, lat) separated by
multisegment headers that contain a <b>−L</b>
labelstring with the feature name, selecting a thick black
pen and semi-transparent yellow fill, giving a title to the
document, and prescribing a particular region limit, try</p>
<p style="margin-left:11%; margin-top: 1em">gmt2kml
mypolygons.txt <b>−Gf</b> yellow <b>−Qp</b> 0.5
<b>−Fp −T</b>"My polygons"
<b>−R</b> 30/90/-20/40 > mypolygons.kml</p>
<p style="margin-left:11%; margin-top: 1em">To convert a
file with point locations (lon, lat, time) into a KML file
with green circle symbols that will go active at the
specified time and stay active going forward, try</p>
<p style="margin-left:11%; margin-top: 1em">awk
’{print $1, $2, $3, "NaN"}’
mypoints.txt | gmt2kml <b>−Gf</b> green
<b>−Ft</b> > mytimepoints.kml</p>
<a name="LIMITATIONS"></a>
<h2>LIMITATIONS</h2>
<p style="margin-left:11%; margin-top: 1em">Google Earth
has trouble displaying filled polygons across the Dateline.
For now you must manually break any polygon crossing the
dateline into a west and east polygon and plot them
separately.</p>
<a name="MAKING KMZ FILES"></a>
<h2>MAKING KMZ FILES</h2>
<p style="margin-left:11%; margin-top: 1em">Using the KMZ
format is preferred as it takes less space. KMZ is simply a
KML file and any data files, icons, or images referenced by
the KML, contained in a zip archive. One way to organize
large data sets is to split them into groups called Folders.
A Document can contain any number of folders. Using scripts
you can create a composite KML file using the
<b>−K</b>, <b>−O</b> options just like you do
with GMT plots. See <b>−T</b> for switching between
folders and documents.</p>
<a name="KML HIERARCHY"></a>
<h2>KML HIERARCHY</h2>
<p style="margin-left:11%; margin-top: 1em"><b><A HREF="GMT.html">GMT</A></b>
stores the different features in hierarchical folders, by
feature type (when using <b>−O</b>, <b>−K</b> or
<b>−T/</b><i>foldername</i>), by input file (if not
standard input), and by line segment (using the name from
the segment header, or <b>−N</b>). This makes it more
easy in Google Earth to switch on or off parts of the
contents of the Document. The following is a crude
example:</p>
<p style="margin-left:11%; margin-top: 1em">[ KML header
information - not present if <b>−O</b> was given ]
<br>
<Document><name>GMT Data Document</name>
<br>
<Folder><name>Point Features</name> <br>
<!--This level of folder is inserted only when using -O,
-K> <br>
<Folder><name>file1.dat</name> <br>
<!--One folder for each input file (not when standard
input)> <br>
<Folder><name>Point Set 0</name> <br>
<!--One folder per line segment> <br>
<!--Points from the first line segment in file file1.dat
go here> <br>
<Folder><name>Point Set 1</name> <br>
<!--Points from the second line segment in file file1.dat
go here> <br>
</Folder> <br>
</Folder> <br>
<Folder><name>Line Features</name> <br>
<Folder><name>file1.dat</name> <br>
<!--One folder for each input file (not when standard
input)> <br>
<Placemark><name>Line 0</name> <br>
<!--Here goes the first line segment> <br>
</Placemark> <br>
<Placemark><name>Line 1</name> <br>
<!--Here goes the second line segment> <br>
</Placemark> <br>
</Folder> <br>
<Folder> <br>
</Document> <br>
[ KML trailer information - not present if <b>−K</b>
was given ]</p>
<a name="SEGMENT INFORMATION"></a>
<h2>SEGMENT INFORMATION</h2>
<p style="margin-left:11%; margin-top: 1em"><b>gmt2kml</b>
will scan the segment headers for substrings of the form
<b>−L</b>"<i>some label</i>" [also see
<b>−N</b> discussion] and <b>−D</b>"<i>some
description</i>". If present, these are parsed to
supply name and description tags for the current
feature.</p>
<a name="SEE ALSO"></a>
<h2>SEE ALSO</h2>
<p style="margin-left:11%; margin-top: 1em"><i><A HREF="gmtdefaults.html">gmtdefaults</A></i>(1),
<i><A HREF="GMT.html">GMT</A></i>(1), <i><A HREF="img2google.html">img2google</A></i>(1), <i><A HREF="kml2gmt.html">kml2gmt</A></i>(1),
<i><A HREF="ps2raster.html">ps2raster</A></i>(1)</p>
<hr>
</body>
</html>
|