<!-- Creator : groff version 1.19.2 -->
<!-- CreationDate: Wed Jul 14 08:43:38 2010 -->
<!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>GSHHS</title>
</head>
<body bgcolor="#ffffff">
<h1 align=center>GSHHS</h1>
<a href="#NAME">NAME</a><br>
<a href="#SYNOPSIS">SYNOPSIS</a><br>
<a href="#DESCRIPTION">DESCRIPTION</a><br>
<a href="#EXAMPLES">EXAMPLES</a><br>
<a href="#BUGS">BUGS</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">gshhs −
Extract ASCII listings from binary GSHHS or WDBII data
files</p>
<a name="SYNOPSIS"></a>
<h2>SYNOPSIS</h2>
<p style="margin-left:11%; margin-top: 1em"><b>gshhs</b>
<i>binaryfile.b</i> [ <b>−I</b><i>id</i> ] [
<b>−L</b> ] [ <b>−M</b> ] >
<i>asciifile.txt</i></p>
<a name="DESCRIPTION"></a>
<h2>DESCRIPTION</h2>
<p style="margin-left:11%; margin-top: 1em"><b>gshhs</b>
reads the binary coastline (GSHHS) or political boundary or
river (WDBII) files and extracts an ASCII listing. It
automatically handles byte-swabbing between different
architectures. Optionally, only segment header info can be
displayed. The header info has the format <i>ID npoints
hierarchical-level source area f_area west east south north
container ancestor</i>, where hierarchical levels for
coastline polygons go from 1 (shoreline) to 4 (lake inside
island inside lake inside land). Source is either W (World
Vector Shoreline) or C (CIA World Data Bank II); lower case
is used if a lake is a river-lake. The <i>west east south
north</i> is the enclosing rectangle, area is the polygon
area in km^2 while f_area is the actual area of the ancestor
polygon, container is the ID of the polygon that contains
this polygon (-1 if none), and ancestor is the ID of the
polygon in the full resolution set that was reduced to yield
this polygon (-1 if full resolution). For line data the
header is simply <i>ID npoints hierarchical-level source
west east south north <br>
binaryfile.b</i></p>
<p style="margin-left:22%;">GSHHS or WDBII binary data file
as distributed with the GSHHS data supplement. Any of the 5
standard resolutions (full, high, intermediate, low, crude)
can be used.</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>−I</b></p> </td>
<td width="8%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Only output
information for the polygon that matches <i>id</i> [default
outputs all polygons].</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">Only output a
listing of polygon or line segment headers [default outputs
headers and data records].</p></td>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p style="margin-top: 1em" valign="top"><b>−M</b></p> </td>
<td width="8%"></td>
<td width="78%">
<p style="margin-top: 1em" valign="top">Start all header
records with the GMT multiple segment indicator
’>’ [Default uses P for polygons and L for
lines].</p> </td>
</table>
<a name="EXAMPLES"></a>
<h2>EXAMPLES</h2>
<p style="margin-left:11%; margin-top: 1em">To convert the
entire intermediate GSHHS binary data to ASCII, run</p>
<p style="margin-left:11%; margin-top: 1em"><b>gshhs</b>
gshhs_i.b > gshhs_i.txt</p>
<p style="margin-left:11%; margin-top: 1em">To only get a
listing of the headers for the river data set at full
resolution, try</p>
<p style="margin-left:11%; margin-top: 1em"><b>gshhs</b>
wdb_rivers_f.b <b>−L</b> > riverlisting.txt</p>
<a name="BUGS"></a>
<h2>BUGS</h2>
<p style="margin-left:11%; margin-top: 1em">While the GSHHS
data is organized as a set of closed polygons, the rivers
and boundary data are just a set of line segments in no
particular order. Thus, it is not possible to extract
information pertaining to just one river or one country.</p>
<a name="SEE ALSO"></a>
<h2>SEE ALSO</h2>
<p style="margin-left:11%; margin-top: 1em"><i><A HREF="GMT.html">GMT</A></i>(1),
<i><A HREF="gshhs_dp.html">gshhs_dp</A></i>(1) <i><A HREF="gshhstograss.html">gshhstograss</A></i>(1)</p>
<hr>
</body>
</html>
distrib
>
Fedora
>
14
>
x86_64
>
media
>
os
>
by-pkgid
>
4b194777eaf705e440bb2ce282d32772
>
files
>
962
