This is an automated email from the git hooks/post-receive script.
sebastic pushed a commit to branch master
in repository gmt-gshhg.
commit 8c037285c54b5e49274942c5a43ea3e247284d6f
Author: Bas Couwenberg <sebas...@xs4all.nl>
Date: Sun Jun 7 17:27:26 2015 +0200
Imported Upstream version 2.3.4
---
COPYING.LESSERv3 | 165 +++++++++++++
COPYINGv3 | 674 +++++++++++++++++++++++++++++++++++++++++++++++++++++
LICENSE.TXT | 23 ++
README.TXT | 256 ++++++++++++++++++++
binned_GSHHS_c.nc | Bin 0 -> 125828 bytes
binned_GSHHS_f.nc | Bin 0 -> 31896036 bytes
binned_GSHHS_h.nc | Bin 0 -> 8426069 bytes
binned_GSHHS_i.nc | Bin 0 -> 2195592 bytes
binned_GSHHS_l.nc | Bin 0 -> 539523 bytes
binned_border_c.nc | Bin 0 -> 51064 bytes
binned_border_f.nc | Bin 0 -> 2117936 bytes
binned_border_h.nc | Bin 0 -> 498416 bytes
binned_border_i.nc | Bin 0 -> 207148 bytes
binned_border_l.nc | Bin 0 -> 88824 bytes
binned_river_c.nc | Bin 0 -> 219467 bytes
binned_river_f.nc | Bin 0 -> 7609718 bytes
binned_river_h.nc | Bin 0 -> 2257314 bytes
binned_river_i.nc | Bin 0 -> 898855 bytes
binned_river_l.nc | Bin 0 -> 355145 bytes
19 files changed, 1118 insertions(+)
diff --git a/COPYING.LESSERv3 b/COPYING.LESSERv3
new file mode 100644
index 0000000..65c5ca8
--- /dev/null
+++ b/COPYING.LESSERv3
@@ -0,0 +1,165 @@
+ GNU LESSER GENERAL PUBLIC LICENSE
+ Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+
+ This version of the GNU Lesser General Public License incorporates
+the terms and conditions of version 3 of the GNU General Public
+License, supplemented by the additional permissions listed below.
+
+ 0. Additional Definitions.
+
+ As used herein, "this License" refers to version 3 of the GNU Lesser
+General Public License, and the "GNU GPL" refers to version 3 of the GNU
+General Public License.
+
+ "The Library" refers to a covered work governed by this License,
+other than an Application or a Combined Work as defined below.
+
+ An "Application" is any work that makes use of an interface provided
+by the Library, but which is not otherwise based on the Library.
+Defining a subclass of a class defined by the Library is deemed a mode
+of using an interface provided by the Library.
+
+ A "Combined Work" is a work produced by combining or linking an
+Application with the Library. The particular version of the Library
+with which the Combined Work was made is also called the "Linked
+Version".
+
+ The "Minimal Corresponding Source" for a Combined Work means the
+Corresponding Source for the Combined Work, excluding any source code
+for portions of the Combined Work that, considered in isolation, are
+based on the Application, and not on the Linked Version.
+
+ The "Corresponding Application Code" for a Combined Work means the
+object code and/or source code for the Application, including any data
+and utility programs needed for reproducing the Combined Work from the
+Application, but excluding the System Libraries of the Combined Work.
+
+ 1. Exception to Section 3 of the GNU GPL.
+
+ You may convey a covered work under sections 3 and 4 of this License
+without being bound by section 3 of the GNU GPL.
+
+ 2. Conveying Modified Versions.
+
+ If you modify a copy of the Library, and, in your modifications, a
+facility refers to a function or data to be supplied by an Application
+that uses the facility (other than as an argument passed when the
+facility is invoked), then you may convey a copy of the modified
+version:
+
+ a) under this License, provided that you make a good faith effort to
+ ensure that, in the event an Application does not supply the
+ function or data, the facility still operates, and performs
+ whatever part of its purpose remains meaningful, or
+
+ b) under the GNU GPL, with none of the additional permissions of
+ this License applicable to that copy.
+
+ 3. Object Code Incorporating Material from Library Header Files.
+
+ The object code form of an Application may incorporate material from
+a header file that is part of the Library. You may convey such object
+code under terms of your choice, provided that, if the incorporated
+material is not limited to numerical parameters, data structure
+layouts and accessors, or small macros, inline functions and templates
+(ten or fewer lines in length), you do both of the following:
+
+ a) Give prominent notice with each copy of the object code that the
+ Library is used in it and that the Library and its use are
+ covered by this License.
+
+ b) Accompany the object code with a copy of the GNU GPL and this license
+ document.
+
+ 4. Combined Works.
+
+ You may convey a Combined Work under terms of your choice that,
+taken together, effectively do not restrict modification of the
+portions of the Library contained in the Combined Work and reverse
+engineering for debugging such modifications, if you also do each of
+the following:
+
+ a) Give prominent notice with each copy of the Combined Work that
+ the Library is used in it and that the Library and its use are
+ covered by this License.
+
+ b) Accompany the Combined Work with a copy of the GNU GPL and this license
+ document.
+
+ c) For a Combined Work that displays copyright notices during
+ execution, include the copyright notice for the Library among
+ these notices, as well as a reference directing the user to the
+ copies of the GNU GPL and this license document.
+
+ d) Do one of the following:
+
+ 0) Convey the Minimal Corresponding Source under the terms of this
+ License, and the Corresponding Application Code in a form
+ suitable for, and under terms that permit, the user to
+ recombine or relink the Application with a modified version of
+ the Linked Version to produce a modified Combined Work, in the
+ manner specified by section 6 of the GNU GPL for conveying
+ Corresponding Source.
+
+ 1) Use a suitable shared library mechanism for linking with the
+ Library. A suitable mechanism is one that (a) uses at run time
+ a copy of the Library already present on the user's computer
+ system, and (b) will operate properly with a modified version
+ of the Library that is interface-compatible with the Linked
+ Version.
+
+ e) Provide Installation Information, but only if you would otherwise
+ be required to provide such information under section 6 of the
+ GNU GPL, and only to the extent that such information is
+ necessary to install and execute a modified version of the
+ Combined Work produced by recombining or relinking the
+ Application with a modified version of the Linked Version. (If
+ you use option 4d0, the Installation Information must accompany
+ the Minimal Corresponding Source and Corresponding Application
+ Code. If you use option 4d1, you must provide the Installation
+ Information in the manner specified by section 6 of the GNU GPL
+ for conveying Corresponding Source.)
+
+ 5. Combined Libraries.
+
+ You may place library facilities that are a work based on the
+Library side by side in a single library together with other library
+facilities that are not Applications and are not covered by this
+License, and convey such a combined library under terms of your
+choice, if you do both of the following:
+
+ a) Accompany the combined library with a copy of the same work based
+ on the Library, uncombined with any other library facilities,
+ conveyed under the terms of this License.
+
+ b) Give prominent notice with the combined library that part of it
+ is a work based on the Library, and explaining where to find the
+ accompanying uncombined form of the same work.
+
+ 6. Revised Versions of the GNU Lesser General Public License.
+
+ The Free Software Foundation may publish revised and/or new versions
+of the GNU Lesser General Public License from time to time. Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns.
+
+ Each version is given a distinguishing version number. If the
+Library as you received it specifies that a certain numbered version
+of the GNU Lesser General Public License "or any later version"
+applies to it, you have the option of following the terms and
+conditions either of that published version or of any later version
+published by the Free Software Foundation. If the Library as you
+received it does not specify a version number of the GNU Lesser
+General Public License, you may choose any version of the GNU Lesser
+General Public License ever published by the Free Software Foundation.
+
+ If the Library as you received it specifies that a proxy can decide
+whether future versions of the GNU Lesser General Public License shall
+apply, that proxy's public statement of acceptance of any version is
+permanent authorization for you to choose that version for the
+Library.
diff --git a/COPYINGv3 b/COPYINGv3
new file mode 100644
index 0000000..94a9ed0
--- /dev/null
+++ b/COPYINGv3
@@ -0,0 +1,674 @@
+ GNU GENERAL PUBLIC LICENSE
+ Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
+
+ The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works. By contrast,
+the GNU General Public License is intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users. We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors. You can apply it to
+your programs, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
+
+ To protect your rights, we need to prevent others from denying you
+these rights or asking you to surrender the rights. Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received. You must make sure that they, too, receive
+or can get the source code. And you must show them these terms so they
+know their rights.
+
+ Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+ For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software. For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+ Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so. This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software. The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable. Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products. If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+ Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary. To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+ TERMS AND CONDITIONS
+
+ 0. Definitions.
+
+ "This License" refers to version 3 of the GNU General Public License.
+
+ "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+ "The Program" refers to any copyrightable work licensed under this
+License. Each licensee is addressed as "you". "Licensees" and
+"recipients" may be individuals or organizations.
+
+ To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy. The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+
+ A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+ To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy. Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+ To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies. Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+ An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License. If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+ 1. Source Code.
+
+ The "source code" for a work means the preferred form of the work
+for making modifications to it. "Object code" means any non-source
+form of a work.
+
+ A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+ The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form. A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+ The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities. However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work. For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+ The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+ The Corresponding Source for a work in source code form is that
+same work.
+
+ 2. Basic Permissions.
+
+ All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met. This License explicitly affirms your unlimited
+permission to run the unmodified Program. The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work. This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+ You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force. You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright. Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+ Conveying under any other circumstances is permitted solely under
+the conditions stated below. Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+ 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+ No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+ When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+ 4. Conveying Verbatim Copies.
+
+ You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+ You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+ 5. Conveying Modified Source Versions.
+
+ You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+ a) The work must carry prominent notices stating that you modified
+ it, and giving a relevant date.
+
+ b) The work must carry prominent notices stating that it is
+ released under this License and any conditions added under section
+ 7. This requirement modifies the requirement in section 4 to
+ "keep intact all notices".
+
+ c) You must license the entire work, as a whole, under this
+ License to anyone who comes into possession of a copy. This
+ License will therefore apply, along with any applicable section 7
+ additional terms, to the whole of the work, and all its parts,
+ regardless of how they are packaged. This License gives no
+ permission to license the work in any other way, but it does not
+ invalidate such permission if you have separately received it.
+
+ d) If the work has interactive user interfaces, each must display
+ Appropriate Legal Notices; however, if the Program has interactive
+ interfaces that do not display Appropriate Legal Notices, your
+ work need not make them do so.
+
+ A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit. Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+ 6. Conveying Non-Source Forms.
+
+ You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+ a) Convey the object code in, or embodied in, a physical product
+ (including a physical distribution medium), accompanied by the
+ Corresponding Source fixed on a durable physical medium
+ customarily used for software interchange.
+
+ b) Convey the object code in, or embodied in, a physical product
+ (including a physical distribution medium), accompanied by a
+ written offer, valid for at least three years and valid for as
+ long as you offer spare parts or customer support for that product
+ model, to give anyone who possesses the object code either (1) a
+ copy of the Corresponding Source for all the software in the
+ product that is covered by this License, on a durable physical
+ medium customarily used for software interchange, for a price no
+ more than your reasonable cost of physically performing this
+ conveying of source, or (2) access to copy the
+ Corresponding Source from a network server at no charge.
+
+ c) Convey individual copies of the object code with a copy of the
+ written offer to provide the Corresponding Source. This
+ alternative is allowed only occasionally and noncommercially, and
+ only if you received the object code with such an offer, in accord
+ with subsection 6b.
+
+ d) Convey the object code by offering access from a designated
+ place (gratis or for a charge), and offer equivalent access to the
+ Corresponding Source in the same way through the same place at no
+ further charge. You need not require recipients to copy the
+ Corresponding Source along with the object code. If the place to
+ copy the object code is a network server, the Corresponding Source
+ may be on a different server (operated by you or a third party)
+ that supports equivalent copying facilities, provided you maintain
+ clear directions next to the object code saying where to find the
+ Corresponding Source. Regardless of what server hosts the
+ Corresponding Source, you remain obligated to ensure that it is
+ available for as long as needed to satisfy these requirements.
+
+ e) Convey the object code using peer-to-peer transmission, provided
+ you inform other peers where the object code and Corresponding
+ Source of the work are being offered to the general public at no
+ charge under subsection 6d.
+
+ A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+ A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling. In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage. For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product. A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+ "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source. The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+ If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information. But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+ The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed. Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+ Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+ 7. Additional Terms.
+
+ "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law. If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+ When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it. (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.) You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+ Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+ a) Disclaiming warranty or limiting liability differently from the
+ terms of sections 15 and 16 of this License; or
+
+ b) Requiring preservation of specified reasonable legal notices or
+ author attributions in that material or in the Appropriate Legal
+ Notices displayed by works containing it; or
+
+ c) Prohibiting misrepresentation of the origin of that material, or
+ requiring that modified versions of such material be marked in
+ reasonable ways as different from the original version; or
+
+ d) Limiting the use for publicity purposes of names of licensors or
+ authors of the material; or
+
+ e) Declining to grant rights under trademark law for use of some
+ trade names, trademarks, or service marks; or
+
+ f) Requiring indemnification of licensors and authors of that
+ material by anyone who conveys the material (or modified versions of
+ it) with contractual assumptions of liability to the recipient, for
+ any liability that these contractual assumptions directly impose on
+ those licensors and authors.
+
+ All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10. If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term. If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+ If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+ Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+ 8. Termination.
+
+ You may not propagate or modify a covered work except as expressly
+provided under this License. Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+ However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+ Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+ Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License. If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+ 9. Acceptance Not Required for Having Copies.
+
+ You are not required to accept this License in order to receive or
+run a copy of the Program. Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance. However,
+nothing other than this License grants you permission to propagate or
+modify any covered work. These actions infringe copyright if you do
+not accept this License. Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+ 10. Automatic Licensing of Downstream Recipients.
+
+ Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License. You are not responsible
+for enforcing compliance by third parties with this License.
+
+ An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations. If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+ You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License. For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+ 11. Patents.
+
+ A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based. The
+work thus licensed is called the contributor's "contributor version".
+
+ A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version. For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+ Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+ In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement). To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+ If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients. "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+ If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+ A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License. You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+ Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+ 12. No Surrender of Others' Freedom.
+
+ If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all. For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+ 13. Use with the GNU Affero General Public License.
+
+ Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work. The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+
+ 14. Revised Versions of this License.
+
+ The Free Software Foundation may publish revised and/or new versions of
+the GNU General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+ Each version is given a distinguishing version number. If the
+Program specifies that a certain numbered version of the GNU General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation. If the Program does not specify a version number of the
+GNU General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+ If the Program specifies that a proxy can decide which future
+versions of the GNU General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+ Later license versions may give you additional or different
+permissions. However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+ 15. Disclaimer of Warranty.
+
+ THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+ 16. Limitation of Liability.
+
+ IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+ 17. Interpretation of Sections 15 and 16.
+
+ If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+ END OF TERMS AND CONDITIONS
+
+ How to Apply These Terms to Your New Programs
+
+ If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+ To do so, attach the following notices to the program. It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+ <one line to give the program's name and a brief idea of what it does.>
+ Copyright (C) <year> <name of author>
+
+ This program is free software: you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation, either version 3 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program. If not, see <http://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+ If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
+ <program> Copyright (C) <year> <name of author>
+ This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License. Of course, your program's commands
+might be different; for a GUI interface, you would use an "about box".
+
+ You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU GPL, see
+<http://www.gnu.org/licenses/>.
+
+ The GNU General Public License does not permit incorporating your program
+into proprietary programs. If your program is a subroutine library, you
+may consider it more useful to permit linking proprietary applications with
+the library. If this is what you want to do, use the GNU Lesser General
+Public License instead of this License. But first, please read
+<http://www.gnu.org/philosophy/why-not-lgpl.html>.
diff --git a/LICENSE.TXT b/LICENSE.TXT
new file mode 100644
index 0000000..51701a1
--- /dev/null
+++ b/LICENSE.TXT
@@ -0,0 +1,23 @@
+$LastChangedDate: 2013-11-24 09:26:07 -1000 (Sun, 24 Nov 2013) $
+$Revision: 594 $
+
+As of GSHHG 2.2.2, GSHHG is distributed under the GNU Lesser General Public
+License (LGPL) version 3 or later. Copies of the The GNU General Public
+License (GPL) and the GNU Lesser General Public License (LGPL) are
+distributed along with the sources. Refer to the files COPYINGv3 and
+COPYING.LESSERv3.
+
+Permission to use, copy, modify, and distribute (with no more than a
+reasonable redistribution fee) this data and its documentation for
+any purpose is hereby granted, provided that the above copyright notice
+appear in all copies, that both that copyright notice and this
+permission notice appear in supporting documentation, and that the name
+of GSHHG not be used in advertising or publicity pertaining to
+distribution of the software without specific, written prior permission.
+ The GSHHG package may be included in a bundled distribution of software
+for which a fee may be charged. The University of Hawaii (UH) and the
+National Oceanic and Atmospheric Administration (NOAA) make no
+representations about the suitability of this software for any purpose.
+It is provided "as is" without expressed or implied warranty. It is
+provided with no support and without obligation on the part of UH or
+NOAA, to assist in its use, correction, modification, or enhancement.
diff --git a/README.TXT b/README.TXT
new file mode 100644
index 0000000..651ef70
--- /dev/null
+++ b/README.TXT
@@ -0,0 +1,256 @@
+$LastChangedDate: 2014-12-30 10:20:36 -1000 (Tue, 30 Dec 2014) $
+$Revision: 622 $
+
+--------------------------------------------------------------------
+Global Self-consistent Hierarchical High-resolution Geography, GSHHG
+
+ Version 2.3.4 Jan 1, 2015
+ Distributed under the Lesser GNU Public License
+
+Corrected formatting error in the binary versions of the borders
+and rivers files. Added "Lake" Maelaren (Sweden) to the coastline
+which reverted 11 "lakes" to their proper status as islands.
+
+Earlier GSHHG Version-specific comments:
+====================================================================
+Version 2.3.3 Nov 2014:
+
+Removed the obsolete Saudi-Kuwait Neutral Zone diamond-shaped border
+and replaced with something resembling what Google Earth shows.
+
+Version 2.3.2 August 2014:
+
+Removed several internal crossovers for the two new Antarctica
+polygons. All other polygons are unchanged.
+
+Version 2.3.1 July 2014:
+
+Updated to include Peter I Island near Antarctica which had gone
+missing during the switch to the Antarctica data source for 2.3.0.
+
+Version 2.3.0 Feb 2014:
+
+This data set consists of three related components:
+
+GSHHS: Global Self-consistent Hierarchical High-resolution Shorelines:
+ These originate as individual polygons at five different
+ resolutions. The ocean-land shorelines derive from WVS (World
+ Vector Shoreline project) [Soluri and Woodson, 1990] while the
+ polygons for lakes, islands-in-lakes, and ponds-in-islands-
+ in-lakes derive from WDBII [Gorny, 1977], which is a much older
+ and lower-quality data product. Our compilation combines these
+ data into a self-consistent product; see Wessel and Smith [1996]
+ for processing details. Over the years we have manually added
+ new data in areas that were poorly represented in the original
+ data set; however, as users zoom in closely they can see that
+ the old data may in places be mis-registered relative to recent
+ data such as used in Google Earth.
+AC: Starting with release 2.3.0 we have replaced the poor Antarctica
+ polygon and associated islands with newer and more accurate
+ data from Bohlander and Scambos (2007) via Atlas of the Cryosphere.
+ This lets us consider two polygon: ice-line and grounding line.
+ New processing was needed to allow a run-time switch on which
+ polygon to use (since it changes how many islands to include).
+ Antarctic ice-front polygons are given level 5 while Antarctic
+ grounding-line polygons are given level 6. Non-GMT users of these
+ data should skip one of these two levels are reset the other one
+ to level = 1. The next GMT5 release 5.2.0 will allow users to
+ select their Antarctica coastline while older versions will simply
+ use the ice-front line as the single Antarctica coastline; the
+ grounding line data are not visible to those versions.
+
+WDBII: CIA World Data Bank II lineaments for borders and rivers.
+ Over the years, political boundaries have changed and we have
+ updated these to reflect realities based on feedback from our
+ users. As mentioned above, WDBII is also used for lakes.
+
+GSHHG is distributed in several representations:
+
+ 1. The binary and shapefile distributions provide the complete
+ GSHHS polygons and WDBII lineaments in their five resolutions
+ (i.e., after our full processing), and differ only in the
+ file formats (native binary data files versus standard GIS
+ shapefiles). These distributions are normally used by
+ users interested to use these data outside the standard
+ GMT-based environment, or GMT users who wish to access the
+ whole GSHHS polygons.
+ 2. The netCDF distribution provides specially processed netCDF
+ representations of GSHHS and WDBII where the polygons and
+ lines have been subdivided and indexed to deliver rapid map-
+ making for GMT. Users who wish to access GSHHG outside of
+ GMT are advised to use the binary and shapefile version of
+ the actual polygons as there is no user documentation for
+ how to access the netCDF files.
+
+Many thanks to Tom Kratzke, Metron Inc., for patiently testing
+many draft versions of GSHHS and reporting inconsistencies such as
+erratic data points and crossings.
+
+References:
+
+Bohlander, J. and T. Scambos. 2007. Antarctic coastlines and grounding line
+ derived from MODIS Mosaic of Antarctica (MOA), Boulder, Colorado USA:
+ National Snow and Ice Data Center.
+Gorny, A. J. (1977), World Data Bank II General User GuideRep. PB 271869,
+ 10pp, Central Intelligence Agency, Washington, DC.
+Soluri, E. A., and V. A. Woodson (1990), World Vector Shoreline,
+ Int. Hydrograph. Rev., LXVII(1), 27–35.
+Wessel, P., and W. H. F. Smith (1996), A global, self-consistent, hierarchical,
+ high-resolution shoreline database, J. Geophys. Res., 101(B4),
8741–8743.
+
+Earlier GSHHG Version-specific comments:
+====================================================================
+Version 2.2.4 Nov 2013: We added three missing lakes (Mono, Trinity,
+and Isabella) in California, plus two islands in Lake Mono. Also found
+a bug in polygon_consistency that failed to find some spikes (~20-25
+polygons affected), as well as an incorrect lake in Antarctica.
+--------------------------------------------------------------------
+
+====================================================================
+Version 2.2.3 July 2013: We eliminated ~120 spikes (< 2m thick excursions)
+from a few dozen full resolution polygons. Also fixed an old mistake
+in Baffin Island in all but the crude resolution; this also converted
+two mislabeled "lakes" into islands in the full and high resolution data.
+--------------------------------------------------------------------
+
+Version 2.2.2 January 2013: We have removed Sandy Island, Coral Sea
+(non feature), shifted Society Island polygons ~1 arc minute to the west,
+and replaced Mehetia Island with better data. Furthermore, 50 islands
+that were imprecise duplicates of more accurate WVS features were removed.
+Apart from the Agalega islands, these duplicates were mostly found in
+the Red Sea, the Persian Gulf, and in the Cook-Austral region. GSHHG is
+now released under the lesser GNU License, v3 or any earlier version.
+--------------------------------------------------------------------
+
+Version 2.2.1 July 2012: We have renamed the product GSHHG since it
+contains more than just shorelines (we distribute political boundaries
+and rivers as well). The GSHHG building and distribution is now
+fully decoupled from GMT. We have also changed the name of the
+netCDF files for GMT to use the more standard extension *.nc.
+Furthermore, the packages have been renamed for clarity and follow
+the form gshhg-{gmt,bin,shp}-<version>.{tar,zip}
+
+There are no significant changes to the actual data features, other
+than a glitch in SA-NT border in Australia and removal of 7 zero-length
+border segments. Following the rebranding to GSHHG the names of the
+distribution files have changed as well.
+--------------------------------------------------------------------
+
+Version 2.2.0 July 2011: The area of small (< 0.1 km^2) polygons
+got truncated to 0. This would cause gshhs to consider them
+as lines (borders or rivers) instead of polygons. Furthermore,
+the areas were recomputed using the WGS-84 ellipsoid as the previous
+area values were based on a spherical calculation. Thanks to
+José Luis García Pallero for pointing this out. We now store
+the area with a magnitude scale tuned to each polygon. Also, the
+greenwich flag is now a 2-bit flag composed of 1 (crosses Greenwich),
+2 (crosses Dateline), 3 (both) or 0 (no such crossing). See gshhs.[ch] for
+details. Finally, the binary gshhs files now store Antarctica in
+-180/+180 range so as to avoid a jump when dumped to ASCII.
+Also, the WDBII shapefiles only had the first 3 levels of rivers;
+version 2.2.0 has all 11. Finally, to be able to detect the river-lake
+features in the WDBII binary files we set the river flag to 1 if a closed
feature.
+--------------------------------------------------------------------
+
+Version 2.1.1 March 2011: Relatively minor fixes to low-resolution
+polygons, including editing errors introduced in v 2.1, removing
+a few spikes from 4-5 polygons, and fixing Germany-Poland border
+near the Baltic Sea.
+--------------------------------------------------------------------
+
+Version 2.1 July 2010: Fixes lack of river-lake flag in the binary
+and shapefile release. Shapefile polygons of level = 2 and with a
+negative area are river-lakes. Also include WDBII border and river
+data as shapefiles.
+--------------------------------------------------------------------
+
+version 2.0 July 15, 2009: Differs from the previous version 1.x in
+the following ways.
+
+1. Free from internal and external crossings and erratic spikes
+ at all five resolutions.
+2. The original Eurasiafrica polygon has been split into Eurasia
+ (polygon # 0) and Africa (polygon # 1) along the Suez canal.
+3. The original Americas polygon has now been split into North
+ America (polygon # 2) and South America (polygon # 3) along
+ the Panama canal.
+4. Antarctica is now polygon # 4 and Australia is polygon # 5, in
+ all the five resolutions.
+5. Fixed numerous problems, including missing islands and lakes
+ in the Amazon and Nile deltas.
+6. Flagged "riverlakes" which are the fat part of major rivers so
+ they may easily be identified by users.
+7. Determined container ID for all polygons (== -1 for level 1
+ polygons) which is the ID of the polygon that contains a smaller
+ polygon.
+8. Determined full-resolution ancestor ID for lower res polygons,
+ i.e., the ID of the polygon that was reduced to yield the lower-
+ res version.
+9. Ensured consistency across resolutions (i.e., a feature that is
+ an island at full resolution should not become a lake in low!).
+10. Sorted tables on level, then on the area of each feature.
+11. Made sure no feature is missing in one resolution but
+ present in the next lower resolution.
+12. Store both the actual area of the lower-res polygons and the
+ area of the full-resolution ancestor so users may exclude fea-
+ tures that represent less that a fraction of the original full
+ area.
+
+There was some duplication and wrong levels assigned to maritime
+political boundaries in the Persian Gulf that has been fixed.
+
+These changes required us to enhance the GSHHG C-structure used to
+read and write the data. As of version 2.0 the header structure is
+
+struct GSHHG { /* Global Self-consistent Hierarchical High-resolution
Shorelines */
+ int id; /* Unique polygon id number, starting at 0 */
+ int n; /* Number of points in this polygon */
+ int flag; /* = level + version << 8 + greenwich << 16 + source
<< 24 + river << 25 */
+ /* flag contains 5 items, as follows:
+ * low byte: level = flag & 255: Values: 1 land, 2 lake, 3
island_in_lake, 4 pond_in_island_in_lake
+ * 2nd byte: version = (flag >> 8) & 255: Values: Should be 12 for
GSHHG release 12 (i.e., version 2.2)
+ * 3rd byte: greenwich = (flag >> 16) & 1: Values: Greenwich is 1
if Greenwich is crossed
+ * 4th byte: source = (flag >> 24) & 1: Values: 0 = CIA WDBII, 1 =
WVS
+ * 4th byte: river = (flag >> 25) & 1: Values: 0 = not set, 1 =
river-lake and level = 2
+ */
+ int west, east, south, north; /* min/max extent in micro-degrees */
+ int area; /* Area of polygon in 1/10 km^2 */
+ int area_full; /* Area of original full-resolution polygon in 1/10
km^2 */
+ int container; /* Id of container polygon that encloses this polygon
(-1 if none) */
+ int ancestor; /* Id of ancestor polygon in the full resolution set
that was the source of this polygon (-1 if none) */
+};
+
+Some useful information:
+
+A) To avoid headaches the binary files were written to be big-endian.
+ If you use the GMT supplement gshhg it will check for endian-ness and if
needed will
+ byte swab the data automatically. If not then you will need to deal with
this yourself.
+
+B) In addition to GSHHS we also distribute the files with political boundaries
and
+ river lines. These derive from the WDBII data set.
+
+C) As to the best of our knowledge, the GSHHG data are geodetic longitude,
latitude
+ locations on the WGS-84 ellipsoid. This is certainly true of the WVS data
(the coastlines).
+ Lakes, riverlakes (and river lines and political borders) came from the
WDBII data set
+ which may have been on WGS072. The difference in ellipsoid is way less
then the data
+ uncertainties. Offsets have been noted between GSHHG and modern GPS
positions.
+
+D) Originally, the gshhs_dp tool was used on the full resolution data to
produce the lower
+ resolution versions. However, the Douglas-Peucker algorithm often produce
polygons with
+ self-intersections as well as create segments that intersect other
polygons. These problems
+ have been corrected in the GSHHG lower resolutions over the years. If you
use gshhs_dp to
+ generate your own lower-resolution data set you should expect these
problems.
+
+E) The shapefiles release was made by formatting the GSHHG data using the
extended GMT/GIS
+ metadata understood by OGR, then using ogr2ogr to build the shapefiles.
Each resolution
+ is stored in its own subdirectory (e.g., f, h, i, l, c) and each level
(1-4) appears in
+ its own shapefile. Thus, GSHHS_h_L3.shp contains islands in lakes for the
high res
+ data. Because of GIS limitations some polygons that straddle the Dateline
(including
+ Antarctica) have been split into two parts (east and west).
+
+F) The netcdf-formatted coastlines distributed with GMT derives directly from
GSHHG; however
+ the polygons have been broken into segments within tiles. These files are
not meant
+ to be used by users other than via GMT tools (pscoast, grdlandmask, etc).
+
+Paul Wessel Primary contact: pwes...@hawaii.edu
+Walter H. F. Smith
diff --git a/binned_GSHHS_c.nc b/binned_GSHHS_c.nc
new file mode 100644
index 0000000..67d676c
Binary files /dev/null and b/binned_GSHHS_c.nc differ
diff --git a/binned_GSHHS_f.nc b/binned_GSHHS_f.nc
new file mode 100644
index 0000000..98b5f94
Binary files /dev/null and b/binned_GSHHS_f.nc differ
diff --git a/binned_GSHHS_h.nc b/binned_GSHHS_h.nc
new file mode 100644
index 0000000..49e9965
Binary files /dev/null and b/binned_GSHHS_h.nc differ
diff --git a/binned_GSHHS_i.nc b/binned_GSHHS_i.nc
new file mode 100644
index 0000000..3a907e1
Binary files /dev/null and b/binned_GSHHS_i.nc differ
diff --git a/binned_GSHHS_l.nc b/binned_GSHHS_l.nc
new file mode 100644
index 0000000..9b95deb
Binary files /dev/null and b/binned_GSHHS_l.nc differ
diff --git a/binned_border_c.nc b/binned_border_c.nc
new file mode 100644
index 0000000..d83dcc3
Binary files /dev/null and b/binned_border_c.nc differ
diff --git a/binned_border_f.nc b/binned_border_f.nc
new file mode 100644
index 0000000..1e2a0f8
Binary files /dev/null and b/binned_border_f.nc differ
diff --git a/binned_border_h.nc b/binned_border_h.nc
new file mode 100644
index 0000000..9fa4332
Binary files /dev/null and b/binned_border_h.nc differ
diff --git a/binned_border_i.nc b/binned_border_i.nc
new file mode 100644
index 0000000..00f6eff
Binary files /dev/null and b/binned_border_i.nc differ
diff --git a/binned_border_l.nc b/binned_border_l.nc
new file mode 100644
index 0000000..1e44100
Binary files /dev/null and b/binned_border_l.nc differ
diff --git a/binned_river_c.nc b/binned_river_c.nc
new file mode 100644
index 0000000..524cdfd
Binary files /dev/null and b/binned_river_c.nc differ
diff --git a/binned_river_f.nc b/binned_river_f.nc
new file mode 100644
index 0000000..929c8c4
Binary files /dev/null and b/binned_river_f.nc differ
diff --git a/binned_river_h.nc b/binned_river_h.nc
new file mode 100644
index 0000000..aa6da9d
Binary files /dev/null and b/binned_river_h.nc differ
diff --git a/binned_river_i.nc b/binned_river_i.nc
new file mode 100644
index 0000000..e37e300
Binary files /dev/null and b/binned_river_i.nc differ
diff --git a/binned_river_l.nc b/binned_river_l.nc
new file mode 100644
index 0000000..1bc564a
Binary files /dev/null and b/binned_river_l.nc differ
--
Alioth's /usr/local/bin/git-commit-notice on
/srv/git.debian.org/git/pkg-grass/gmt-gshhg.git
_______________________________________________
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
