[DebianGIS-dev] r834 - in packages: . drawmap drawmap/branches drawmap/branches/upstream drawmap/branches/upstream/current
frankie at alioth.debian.org
frankie at alioth.debian.org
Fri May 18 12:29:03 UTC 2007
Author: frankie
Date: 2007-05-18 12:29:03 +0000 (Fri, 18 May 2007)
New Revision: 834
Added:
packages/drawmap/
packages/drawmap/branches/
packages/drawmap/branches/upstream/
packages/drawmap/branches/upstream/current/
packages/drawmap/branches/upstream/current/COPYING
packages/drawmap/branches/upstream/current/COPYING_NOTE
packages/drawmap/branches/upstream/current/Makefile
packages/drawmap/branches/upstream/current/README
packages/drawmap/branches/upstream/current/WHATS_NEW
packages/drawmap/branches/upstream/current/attrib_codes
packages/drawmap/branches/upstream/current/attributes
packages/drawmap/branches/upstream/current/big_buf_io.c
packages/drawmap/branches/upstream/current/big_buf_io_z.c
packages/drawmap/branches/upstream/current/colors.h
packages/drawmap/branches/upstream/current/dem.c
packages/drawmap/branches/upstream/current/dem.h
packages/drawmap/branches/upstream/current/dem_sdts.c
packages/drawmap/branches/upstream/current/dlg.c
packages/drawmap/branches/upstream/current/dlg.h
packages/drawmap/branches/upstream/current/dlg_sdts.c
packages/drawmap/branches/upstream/current/drawmap.1n
packages/drawmap/branches/upstream/current/drawmap.c
packages/drawmap/branches/upstream/current/drawmap.h
packages/drawmap/branches/upstream/current/font_5x8.h
packages/drawmap/branches/upstream/current/font_6x10.h
packages/drawmap/branches/upstream/current/gtopo30.c
packages/drawmap/branches/upstream/current/gunzip.c
packages/drawmap/branches/upstream/current/gzip.h
packages/drawmap/branches/upstream/current/ll2utm.1n
packages/drawmap/branches/upstream/current/ll2utm.c
packages/drawmap/branches/upstream/current/llsearch.1n
packages/drawmap/branches/upstream/current/llsearch.c
packages/drawmap/branches/upstream/current/raster.h
packages/drawmap/branches/upstream/current/sdts2dem.1n
packages/drawmap/branches/upstream/current/sdts2dem.c
packages/drawmap/branches/upstream/current/sdts2dlg.1n
packages/drawmap/branches/upstream/current/sdts2dlg.c
packages/drawmap/branches/upstream/current/sdts_utils.c
packages/drawmap/branches/upstream/current/sdts_utils.h
packages/drawmap/branches/upstream/current/unblock_dem.1n
packages/drawmap/branches/upstream/current/unblock_dem.c
packages/drawmap/branches/upstream/current/unblock_dlg.1n
packages/drawmap/branches/upstream/current/unblock_dlg.c
packages/drawmap/branches/upstream/current/utilities.c
packages/drawmap/branches/upstream/current/utm2ll.1n
packages/drawmap/branches/upstream/current/utm2ll.c
packages/drawmap/tags/
Log:
[svn-inject] Installing original source of drawmap
Added: packages/drawmap/branches/upstream/current/COPYING
===================================================================
--- packages/drawmap/branches/upstream/current/COPYING (rev 0)
+++ packages/drawmap/branches/upstream/current/COPYING 2007-05-18 12:29:03 UTC (rev 834)
@@ -0,0 +1,339 @@
+ GNU GENERAL PUBLIC LICENSE
+ Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+ 675 Mass Ave, Cambridge, MA 02139, USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users. This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it. (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.) 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
+this service 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 make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have. 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.
+
+ We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+ Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software. If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+ Finally, any free program is threatened constantly by software
+patents. We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary. To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+ GNU GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License. The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language. (Hereinafter, translation is included without limitation in
+the term "modification".) Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+ 1. You may copy and distribute 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 and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+ 2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+ a) You must cause the modified files to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+ b) You must cause any work that you distribute or publish, that in
+ whole or in part contains or is derived from the Program or any
+ part thereof, to be licensed as a whole at no charge to all third
+ parties under the terms of this License.
+
+ c) If the modified program normally reads commands interactively
+ when run, you must cause it, when started running for such
+ interactive use in the most ordinary way, to print or display an
+ announcement including an appropriate copyright notice and a
+ notice that there is no warranty (or else, saying that you provide
+ a warranty) and that users may redistribute the program under
+ these conditions, and telling the user how to view a copy of this
+ License. (Exception: if the Program itself is interactive but
+ does not normally print such an announcement, your work based on
+ the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+ 3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+ a) Accompany it with the complete corresponding machine-readable
+ source code, which must be distributed under the terms of Sections
+ 1 and 2 above on a medium customarily used for software interchange; or,
+
+ b) Accompany it with a written offer, valid for at least three
+ years, to give any third party, for a charge no more than your
+ cost of physically performing source distribution, a complete
+ machine-readable copy of the corresponding source code, to be
+ distributed under the terms of Sections 1 and 2 above on a medium
+ customarily used for software interchange; or,
+
+ c) Accompany it with the information you received as to the offer
+ to distribute corresponding source code. (This alternative is
+ allowed only for noncommercial distribution and only if you
+ received the program in object code or executable form with such
+ an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it. For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable. However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+ 4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License. Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+ 5. You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Program or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+ 6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions. You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+ 7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+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
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all. For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices. Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+ 8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded. In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+ 9. The Free Software Foundation may publish revised and/or new versions
+of the 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 a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation. If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+ 10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission. For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this. Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+ NO WARRANTY
+
+ 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, 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.
+
+ 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE 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.
+
+ END OF TERMS AND CONDITIONS
+
+ Appendix: 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
+convey 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) 19yy <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 2 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, write to the Free Software
+ Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+ Gnomovision version 69, Copyright (C) 19yy name of author
+ Gnomovision 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, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary. Here is a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+ `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+ <signature of Ty Coon>, 1 April 1989
+ Ty Coon, President of Vice
+
+This 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 Library General
+Public License instead of this License.
Added: packages/drawmap/branches/upstream/current/COPYING_NOTE
===================================================================
--- packages/drawmap/branches/upstream/current/COPYING_NOTE (rev 0)
+++ packages/drawmap/branches/upstream/current/COPYING_NOTE 2007-05-18 12:29:03 UTC (rev 834)
@@ -0,0 +1,26 @@
+
+October 11, 1998
+
+I have had a request to change the licensing on "drawmap" so that it is subject
+to the GNU Library General Public License rather than the plain old GNU General
+Public License. This would allow it to be incorporated into packages that, for
+whatever reason, can't be distributed in source-code form.
+
+However, after examining the situation in depth, I have decided not to do this.
+My primary reason is that I have incorporated large portions of the "gzip"
+package into drawmap, in order to allow compressed files to be read efficiently.
+The "gzip" package is licensed under the GNU General Public License, and it
+isn't within my legal power to change the licensing of that code. The only
+obvious way to change the licensing on "drawmap" would be to split it into two
+separately-distributed chunks: one containing the modified "gzip" code, and the
+other containing the remainder of "drawmap". While this would be possible, it
+doesn't seem worthwhile, since the only portion of "drawmap" that has much
+utility as a stand-alone library is the "gzip" portion itself.
+
+If you have an interest in using other portions of "drawmap" under the terms of
+the GNU Library General Public License, then I suggest you contact me at the
+contact address in the README file. I don't object to such use, as long as you
+understand that the "gzip" code is not mine to control.
+
+Fred M. Erickson
+
Added: packages/drawmap/branches/upstream/current/Makefile
===================================================================
--- packages/drawmap/branches/upstream/current/Makefile (rev 0)
+++ packages/drawmap/branches/upstream/current/Makefile 2007-05-18 12:29:03 UTC (rev 834)
@@ -0,0 +1,93 @@
+# =========================================================================
+# Makefile - Information for building drawmap, and associated programs.
+# Copyright (c) 1997,1998,1999,2000 Fred M. Erickson
+#
+# 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 2, 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, write to the Free Software
+# Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
+# =========================================================================
+
+
+
+# If you want a copyright notice inserted into the image, then
+# comment out the first version of NAME, and uncomment the
+# second, and put your name inside the quotes.
+NAME=\"\"
+#NAME=\"Fred M. Erickson\"
+
+CFLAGS = -O
+
+
+
+all: drawmap ll2utm utm2ll unblock_dlg unblock_dem llsearch sdts2dem sdts2dlg man
+
+drawmap: drawmap.c dem.c dem_sdts.c dlg.c dlg_sdts.c sdts_utils.c big_buf_io.c big_buf_io_z.c gunzip.c \
+ utilities.c gtopo30.c gzip.h font_5x8.h font_6x10.h raster.h drawmap.h colors.h dlg.h dem.h sdts_utils.h
+ $(CC) -DCOPYRIGHT_NAME="${NAME}" $(CFLAGS) -o drawmap drawmap.c dem.c dem_sdts.c dlg.c dlg_sdts.c \
+ sdts_utils.c gtopo30.c big_buf_io.c big_buf_io_z.c gunzip.c utilities.c -lm
+
+ll2utm: ll2utm.c utilities.c
+ $(CC) $(CFLAGS) -o ll2utm ll2utm.c utilities.c -lm
+
+utm2ll: utm2ll.c utilities.c
+ $(CC) $(CFLAGS) -o utm2ll utm2ll.c utilities.c -lm
+
+unblock_dlg: unblock_dlg.c
+ $(CC) $(CFLAGS) -o unblock_dlg unblock_dlg.c
+
+unblock_dem: unblock_dem.c
+ $(CC) $(CFLAGS) -o unblock_dem unblock_dem.c
+
+llsearch: llsearch.c big_buf_io.c utilities.c
+ $(CC) $(CFLAGS) -o llsearch llsearch.c big_buf_io.c utilities.c -lm
+
+sdts2dem: sdts2dem.c sdts_utils.c dem.c dem_sdts.c big_buf_io.c big_buf_io_z.c gunzip.c \
+ utilities.c gzip.h drawmap.h dem.h sdts_utils.h
+ $(CC) $(CFLAGS) -o sdts2dem sdts2dem.c dem.c dem_sdts.c sdts_utils.c big_buf_io.c big_buf_io_z.c gunzip.c utilities.c -lm
+
+sdts2dlg: sdts2dlg.c dlg.c dlg_sdts.c sdts_utils.c big_buf_io.c big_buf_io_z.c gunzip.c \
+ utilities.c gzip.h drawmap.h dlg.h sdts_utils.h
+ $(CC) $(CFLAGS) -o sdts2dlg sdts2dlg.c dlg.c dlg_sdts.c sdts_utils.c big_buf_io.c big_buf_io_z.c gunzip.c utilities.c -lm
+
+man: drawmap.1 ll2utm.1 utm2ll.1 llsearch.1 unblock_dlg.1 unblock_dem.1 sdts2dem.1 sdts2dlg.1
+
+drawmap.1: drawmap.1n
+ nroff -man drawmap.1n > drawmap.1
+
+ll2utm.1: ll2utm.1n
+ nroff -man ll2utm.1n > ll2utm.1
+
+utm2ll.1: utm2ll.1n
+ nroff -man utm2ll.1n > utm2ll.1
+
+llsearch.1: llsearch.1n
+ nroff -man llsearch.1n > llsearch.1
+
+unblock_dlg.1: unblock_dlg.1n
+ nroff -man unblock_dlg.1n > unblock_dlg.1
+
+unblock_dem.1: unblock_dem.1n
+ nroff -man unblock_dem.1n > unblock_dem.1
+
+sdts2dem.1: sdts2dem.1n
+ nroff -man sdts2dem.1n > sdts2dem.1
+
+sdts2dlg.1: sdts2dlg.1n
+ nroff -man sdts2dlg.1n > sdts2dlg.1
+
+clean:
+ rm -f drawmap ll2utm utm2ll unblock_dlg unblock_dem llsearch sdts2dem sdts2dlg \
+ drawmap.1 ll2utm.1 utm2ll.1 llsearch.1 unblock_dlg.1 unblock_dem.1 sdts2dem.1 sdts2dlg.1 \
+ drawmap.o dem.o dem_sdts.o dlg.o dlg_sdts.o sdts_utils.o big_buf_io.o \
+ big_buf_io_z.o gunzip.o utilities.o ll2utm.o utm2ll.o unblock_dlg.o unblock_dem.o llsearch.o sdts2dem.o sdts2dlg.o
+
Added: packages/drawmap/branches/upstream/current/README
===================================================================
--- packages/drawmap/branches/upstream/current/README (rev 0)
+++ packages/drawmap/branches/upstream/current/README 2007-05-18 12:29:03 UTC (rev 834)
@@ -0,0 +1,130 @@
+
+Some notes on drawmap. Updated on August 2, 2001.
+
+First, how to build it. Edit the Makefile if you want a copyright
+notice on all of the maps you generate. Then, simply type:
+
+make
+
+If you aren't on a Linux(TM) system, or similar Unix(TM) system, you will
+probably end up giving up and deleting the whole mess. Otherwise, you
+should end up with eight executables: drawmap, llsearch, ll2utm, utm2ll,
+block_dem, block_dlg, sdts2dem, and sdts2dlg. There should also be eight
+formatted manual pages, whose file names end with a ".1" extension; and
+eight unformatted manual pages, whose file names end with a ".1n"
+extension.
+
+Install things wherever you want. On my system, the executables go into
+/usr/local/bin, the manual pages with a ".1" extension get compressed
+(with gzip) and go into /usr/local/man/cat1, and the manual pages with
+a ".1n" extension get compressed (with gzip) and go into /usr/local/man/man1.
+(You don't have to install both the ".1" and ".1n" versions if you don't
+want to. The ".1n" version is probably the most useful, since it allows
+you to reformat the manual pages into various output formats.)
+
+I have resisted the urge to hard-code any pathnames, library locations,
+and what-have-you into the code. There is one compile-time option you can
+invoke by editing the Makefile. If you provide your name, it will be
+compiled into the program, and a copyright notice, with your name in it,
+will be added to the bottom of each map you generate. I am unsure about
+the copyright status of a map generated by drawmap, since anyone else
+can generate the same map using the same data, but the feature was easy
+to add in, so I did.
+
+
+
+Second, how to use it. You need some data. Once you have at least one
+Digital Elevation Model (DEM) file, using drawmap is as simple as typing:
+
+ drawmap -d name_of_your_dem_file
+
+The output will be in a file called "drawmap.sun" and you should be able
+to view it with image viewers like "xv" and "ImageMagick". Sources of
+downloadable data are listed in the manual page. There is a lot of useful
+information in the manual page; you might want to give it a read.
+In particular, there are some usage examples near the end of the page.
+
+
+
+Drawmap grew out of my curiosity regarding what could be done with the
+available USGS data files. It was originally intended just to play
+with Digital Elevation Model (DEM) files. Later I added processing
+for Digital Line Graph (DLG) files, GTOPO30 files, and Geographic Names
+Information System (GNIS) files. Because of this history as an experimental
+testbed, drawmap was never actually designed. Instead, it grew
+by accretion, with major sections being reworked from time to
+time as I decided to try new approaches. There have even been a
+couple of top-to-bottom reworks, as I found it desirable to try a
+much different approach to one thing or another. The addition of
+support for SDTS files considerably increased the complexity of the
+program. Thus, if you are looking for elegant structure and logical
+design, you may be disappointed. On the flip side, it is copiously
+commented, and you should find it reasonably straightforward to modify.
+Keeping straight all of the various translations and rotations of data
+can be mind-numbing; but that pretty much goes with the territory when
+you work on a program like this.
+
+Also, in order to minimize its memory footprint, drawmap uses malloc()
+to get the space it needs, and then uses pointers to access it. I find
+the resulting code much more difficult to work with than code that
+simply allocates a 2-dimensional array and uses two index values to
+access the data. Thus, if I plan to do a major rework on the code,
+I sometimes convert it back to using arrays, do what needs doing,
+and then convert it to using pointers. Some people prefer to
+define macros that simulate arrays on the one-dimensional malloc()
+memory. Others may prefer to define C++ objects to hide all of the
+messy details. I like simplicity. Your mileage may vary.
+
+I have a to-do list of things that would be nice to have. Near the
+top of the list is to improve the handling of text. The routine that
+adds text annotations to the image is very crude. I cobbled it together
+one night because I needed the capability to add cursors and text in
+order to test out some algorithms, and I have never gone back to improve
+it. Only two bitmapped fonts are available, and they can only be
+printed horizontally. It would be super cool (and perhaps even swell)
+to have a bigger set of prettier fonts that could be scaled and rotated.
+This would be particularly nice for plotting hypsographic contour lines
+with the traditional elevation numbers printed along selected contours.
+(Although trying to do that sort of thing automatically would be a
+challenging task, indeed.)
+
+It would also be a good idea to try to make the thing portable. At
+present, it has only been compiled (by me) under Linux. Based on past
+experience, I assume that it will readily port to other Unix systems.
+However, porting it to Windows(TM) might not be fun.
+
+Another possibility would be to re-write it to be an X-Window
+application. This would allow some interactive features to be added
+and would also provide instant access to a large set of fonts and
+drawing primitives. However, there are already systems like that
+available, and I am not sure I want to produce yet another big,
+clunky, non-portable thingamabob that nobody uses because they
+can't get the thing to compile on their machines. I know how
+disappointed I am when I go to the trouble to download something,
+and then find out I need some large support package before I can
+use the software.
+
+If you like the kind of resolution available in a 7.5-minute
+topographic map, you might want to look into the availability of
+DRG files. DRG files are scanned-in versions of the standard
+USGS 7.5-minute map sheets. The USGS sells these files on CD-ROM,
+but they are also available on-line for some locales. For example,
+the state of Montana has a server providing all of the available
+DRG files for Montana. In fact, a number of states provide such
+a service. There are also a few sites that aren't tied to particular
+states, but have a smorgasbord of files from various locations.
+DRG files have no connection to drawmap. I mention them here simply
+because you might find them of interest.
+
+I hope you find drawmap both useful and fun. Remember though, that it
+is basically an experimental testbed, and not a commercial product.
+Use it at your own risk. Drawmap, and all associated software and
+documentation, are provided "as is", and are licensed under the GNU
+General Public License. See the file "COPYING" for license details.
+
+Fred M. Erickson
+603 15th Street
+Havre, MT 59501-5339
+
+fme at ttc-cmc.net
+
Added: packages/drawmap/branches/upstream/current/WHATS_NEW
===================================================================
--- packages/drawmap/branches/upstream/current/WHATS_NEW (rev 0)
+++ packages/drawmap/branches/upstream/current/WHATS_NEW 2007-05-18 12:29:03 UTC (rev 834)
@@ -0,0 +1,371 @@
+
+
+Aug 2 2001:
+Changes in drawmap between version 2.4 and version 2.5:
+
++ Version 2.4 used a relatively simple interpolation algorithm to map
+ 24K DEM data into the map image. It didn't warp the data blocks to
+ completely fill the corresponding latitude/longitude squares.
+ Version 2.5 uses a more sophisticated algorithm, which does warp
+ the data, and consequently produces better data registration at the
+ seams between data blocks, along with more accurate placement of data
+ points.
+
+ The "LIMITS" section, at the end of the drawmap manual page, has
+ been modified to reflect this change.
+
++ User-specified attribute restrictions were being ignored for
+ SDTS DLG files. They should no longer be ignored. (Thanks
+ to BM for reporting this problem.)
+
++ Some 7.5 minute DEM files use SDTS conventions that are different
+ from those of the bulk of the files I have examined. For example,
+ while it appears that most files specify a sequence of (x,y) coordinates
+ as an ISO 8211 2-dimensional cartesian array, some files specify them
+ as simple repeating pairs. I am not sure that this particular construct
+ is standards-compliant, but I have modified drawmap to try to handle it
+ anyway. (Thanks to TF for reporting this problem.)
+
+ There are also cases where, for example, data items are stored as integers
+ (in ASCII decimal, or straight binary) for one quad, while the same items
+ are stored as real numbers for another. This sort of thing is allowed under
+ the standard. (Under the standard, there are six acceptable ways to store
+ elevations.) Drawmap doesn't try to handle every possible format variation.
+ It does try to handle the ones that I have sample files for. I made several
+ changes in this release to support additional subfield formats. However,
+ files that drawmap cannot handle may still be lurking out there.
+
++ Due to floating point rounding errors, sdts2dem (and possibly sdts2dlg)
+ did not always determine correct output file names. This has (hopefully)
+ been fixed. It is a bit difficult to be sure, because I don't know of
+ any firm limits on the values that can appear in an SDTS DEM or DLG file,
+ and the SDTS files themselves may contain errors. In any case, the
+ file-name generation code has been made more robust.
+
++ Some 7.5 minute DEM files appear to contain 32767 or -32767 as markers
+ for non-valid data. Drawmap was unaware of this and treated the values
+ as valid elevations. Such values are now discarded.
+
++ Moved the comment blocks to the ends of the manual pages.
+ For some reason, having them at the beginning caused a
+ whole bunch of blank pages to be output at the beginning
+ of a formatted page.
+
++ Improved handling of return values in get_a_line(). As far as
+ I know, the unimproved routine works okay with drawmap; but
+ the improvements should make get_a_line() more robust for
+ people who want to use the routine in their own software.
+
++ Made a couple of minor changes to make drawmap more portable.
+
++ Fixed some minor miscellaneous problems.
+
+
+
+
+
+
+Mar 26 2001:
+Changes in drawmap between version 2.3 and version 2.4:
+
++ Drawmap can now handle DEM files with elevations in feet.
+
++ Some clarifications have been added to the manual page,
+ including an example of the use of GTOPO30 files.
+
++ There is some additional installation information in the
+ README file.
+
+
+
+
+
+
+Jan 16 2001:
+Changes in drawmap between version 2.2 and version 2.3:
+
++ This point release is partly the result of downloading more
+ test data for more parts of the USA, and fixing whatever new
+ problems might show up. There are, however, several new
+ options and general modifications, and also a few bug fixes.
+ These are described below, although some of the minor bug
+ fixes are omitted.
+
++ Added the -r option to allow the sharpness of the shaded
+ relief to be varied. The default is fully-shaded relief,
+ which was the only available shading in previous releases.
+ The new option allows the darkness of shadows to be
+ reduced, in steps, until all shading disappears and only
+ simple color bands remain.
+
++ Added the -z option, which adjusts the color table so that
+ it exactly spans the range of elevations in the given
+ data. This ensures that all available colors are used in
+ the map; but at the cost of having each color represent
+ a peculiar range of elevations.
+
++ Added the -m option, which allows limited enhancement
+ of light/dark shading in shaded-relief maps.
+
++ Added the -t option, to shut off generation of tick
+ marks and latitude/longitude markings.
+
++ In response to a request, added the -C option, which works
+ the same as the -c option, except that it fills in the
+ space between contour lines with solid colors.
+
++ In past releases, the -c option located contour lines in
+ the centers of the elevation bands. In other words, if
+ the contour interval was 100 meters, then the first contour
+ would be at 50 meters, with the next at 150 meters.
+ In this release the code has been modified so that contour
+ lines are on the edges of the elevation bands. In other
+ words, if the contour interval is 100 meters, then the
+ contours are at 100 meters, 200 meters, and so on.
+
++ A few of the GTOPO30 files were rejected because quantization
+ error caused some consistency checking to fail. Loosened
+ up the checks slightly so that the files now pass muster.
+
++ Updated the color scheme for drawing DLG vector data.
+ Changed railroads and pipelines to black, and changed
+ vegetative features to green.
+
++ Added support for more attribute types, including
+ 190/UNPAVED. Fixed a few attributes that have special
+ cases, such as range and township numbers that can
+ take forms like "10 1/2E".
+
++ Some USGS SDTS DLG files have attributes whose record
+ IDs double back and duplicate other record IDs in the file.
+ (Wilmington Delaware 24K DLG HY 1379127.HY.sdts.tar.gz
+ and 1379151.HY.sdts.tar.gz are examples.) I would guess
+ that this is a bug in the SDTS files, since it would leave
+ no way to distinguish between attributes. (One could use
+ the record number in the ISO 8211 header, but I don't
+ think this is considered legitimate under the standard.)
+ One way or the other, this was causing drawmap some
+ indigestion, so the software has been fixed to deal with
+ the problem as best it can. Drawmap prints a warning
+ message when this situation occurs.
+
++ Beefed up the test program, tacked onto the end of
+ sdts_utils.c, so that it is a useful viewing tool
+ for SDTS files.
+
+
+
+
+
+
+Aug 1 2000:
+Changes in drawmap between version 2.1 and version 2.2:
+
++ Added the sdts2dem and sdts2dlg programs to convert
+ SDTS transfers into the `classic' DEM and `optional'
+ DLG formats. I wrote these primarily to allow me
+ to test drawmap's SDTS capabilities, but they should
+ be generally useful.
+
++ Improved the handling of SDTS files. In particular,
+ we no longer ignore some of the minor attribute files,
+ so all attributes should be included. Improved the
+ handling of attributes overall. This includes
+ specific support for attributes with special needs.
+
++ There were a number of minor repairs and upgrades here
+ and there.
+
++ Decreased the default memory footprint a bit, by changing
+ some long variables to shorts in some of the larger
+ arrays. Unfortunately, new feature development probably
+ devoured a lot of these savings.
+
++ Modified the -h option to automatically include a blue
+ surface at sea level.
+
++ Modified the -i option to include the DLG name, and the
+ type of data in the file, when printing info about DLG files.
+
+
+
+
+
+Jul 23 2000:
+Changes in drawmap between version 2.0 and version 2.1:
+
++ Added support for the NAD-83 datum and the WGS-84 datum.
+
++ Drawmap can now read SDTS-format DEM and DLG files.
+
++ At the request of a drawmap user, I added GTOPO30
+ files to the set of files drawmap can read. This should
+ provide at least some map-drawing capability for people
+ who can't get DEM data for their countries of interest.
+
++ There were a number of minor repairs and upgrades here
+ and there.
+
++ Changed the names of block_dem and block_dlg to unblock_dem
+ and unblock_dlg so that they are consistent with the
+ equivalent "dd" commands.
+
+
+
+
+
+Jul 8 2000:
+Changes in drawmap between version 1.10 and version 2.0:
+
++ This was a fairly major restructuring of drawmap, mainly to
+ get it to handle DEM and DLG data at the 7.5-minute
+ resolution.
+
++ In past versions of drawmap, data smoothing was done when
+ the image resolution and data resolution were the same.
+ This version of drawmap no longer smooths when the source
+ data and target image have close to the same resolution.
+ In addition, the code implementing smoothing has been
+ clarified, so that the smoothing behavior should be easier
+ to understand and modify.
+
++ Restructured the shaded relief code to allow it to handle
+ data from DEMs in various resolutions. Also moved most of
+ the color definitions into colors.h so that users can more
+ easily modify the color scheme. Provided four separate
+ color map tables, selectable by the "-n" option, so that
+ users can choose between a variety of color schemes.
+ "Natural" colors are now the default, rather than the
+ garish high-perception colors used in previous versions.
+
+ Also toned down the red and blue that are used to draw
+ streams and roads. They were a bit distracting.
+
++ Added a new "-w" option to allow flat sea-level areas to be
+ automatically colored blue.
+
++ Removed the requirement that the x and y dimensions be even.
+ This was done primarily because 7.5-minute DEMs often have
+ odd dimensions.
+
++ Drawmap no longer tries to create an image file until after
+ most error checking is done. This should reduce the incidence
+ of half-created image files being left behind after an error.
+
++ Drawmap now uses Redfearn's formulas to convert UTM coordinates
+ to latitude/longitude coordinates and vice versa. However,
+ the program still uses linear interpolation from the corners
+ of the data blocks to transfer DEM data into the map image.
+
++ There are two new stand-alone commands, utm2ll and ll2utm that
+ convert latitude/longitude coordinates to UTM coordinates and
+ vice versa. They currently only support the NAD-27 datum,
+ but can be easily modified to use others.
+
++ The dem_dlg_info program has been deleted. It is replaced by
+ the "-i" option to drawmap.
+
++ The height-field program in the height_field subdirectory has
+ been deleted. It is replaced by the "-h" option to drawmap.
+ The code that tried to generate "povray" objects for roads,
+ lakes, towns, and so on, is no longer present in any form.
+ It produced crude results and didn't seem very useful.
+
+
+
+
+
+Jun 18 2000:
+Changes in drawmap between version 1.9 and version 1.10:
+
++ The USGS has changed the format of both types of GNIS
+ files. Modified drawmap to handle the new formats.
+ NOTE: Files in the old formats will no longer work.
+
++ Cleaned up a few minor things here and there.
+
+
+
+
+
+Jun 3 2000:
+Changes in drawmap between version 1.8 and version 1.9:
+
++ Some of the newer USGS 100K DLG files contain newlines.
+ (Older ones did not.)
+ Modified drawmap to handle this new wrinkle.
+
++ Provided a new program called dem_dlg_info, to print
+ out some useful information from the headers of DEM
+ and DLG files.
+
++ Dropped the block_std program, since standard-format
+ files have disappeared from the USGS web site.
+
++ Added manual pages for block_opt and dem_dlg_info.
+
+
+
+
+
+Jan 3 2000:
+Changes in drawmap between version 1.7 and version 1.8:
+
++ Clarified the code comments and the manual page for drawmap.
+
++ Included the povray_height_field directory, which contains
+ a modified version of drawmap that will produce information
+ that the ``povray'' package can use to make 3-dimensional
+ renderings of terrain.
+
++ There were no changes in the operation of drawmap --- only
+ changes in the code comments. The primary purpose of this
+ release was to add the drawmap_height_field program.
+
+
+
+
+
+Jan 16 1999:
+Changes in drawmap between version 1.6 and version 1.7:
+
++ removed restrictions on the size of contouring intervals
+
++ added code to allow use on big-endian machines
+
++ added gaussian smoothing for oversampled maps to reduce checkerboard effect
+
++ changed DLG line-drawing algorithm to produce better map registration
+
++ changed drawmap and llsearch to handle the new GNIS format
+
+
+
+
+
+Dec 11 1998:
+Changes in drawmap between version 1.3 and version 1.6:
+
++ Fixed a portability bug, and an obscure bug in the code that
+ draws tick marks at the edges of the image.
+
++ Added some new information about licensing (see the file "COPYING_NOTE").
+
++ Added a new option "-c", that draws contour lines instead of the normal
+ shaded relief.
+
+
+
+
+
+Oct 12 1998:
+Changes in drawmap between version 1.3 and version 1.5
+(there was no version 1.4):
+
++ Fixed a portability bug, and an obscure bug in the code that
+ draws tick marks at the edges of the image.
+
++ Added some new information about licensing (see the file "COPYING_NOTE").
+
++ Added a new option "-c", that draws contour lines instead of the normal
+ shaded relief.
Added: packages/drawmap/branches/upstream/current/attrib_codes
===================================================================
--- packages/drawmap/branches/upstream/current/attrib_codes (rev 0)
+++ packages/drawmap/branches/upstream/current/attrib_codes 2007-05-18 12:29:03 UTC (rev 834)
@@ -0,0 +1,946 @@
+NOTE: THIS IS AN EXTRACT FROM A USGS DOCUMENT. THE ORIGINAL DOCUMENT WAS OBTAINED FROM A USGS WEB SITE.
+
+
+
+
+ APPENDIX D.--DLG Attribute Codes
+
+
+
+Valid Minor Codes for the Coincident Feature Parameter
+
+ Code Base Category
+
+ 0002 Hypsography
+
+ 0005 Hydrography
+
+ 0007 Surface Cover
+
+ 0009 Boundary
+
+ 0015 Survey Control
+
+ Transportation Systems
+
+ 0017 Roads and Trails
+
+ 0018 Railroads
+
+ 0019 Pipelines, Transmission Lines, Miscellaneous
+ Transportation
+
+ 0020 Manmade Features
+
+
+
+
+ APPENDIX D.--DLG Attribute Codes--continued
+__________________________________________________________________________________________________________________________________
+ MAJOR MINOR
+DATA CATEGORY TYPE OF CODE APPLICATION CODE CODE DESCRIPTION
+__________________________________________________________________________________________________________________________________
+Hypsography Feature identification Nodes 020 NONE
+
+ Areas 020 0100 Void area
+
+ Lines 020 0200 Contour (index or intermediate)
+ 0201 Carrying contour
+ 0202 Supplementary contour
+ 0203 Continuation contour
+ 0204 Amended contour
+ 0205 Bathymetric contour
+ *0206 Depth curve
+ 0207 Watershed divides
+ 0208 Closure line
+
+ Points 020 0300 Spot elevation, less than
+ (degenerate lines) third order,
+
+ 020 0301 Spot elevation, less than
+ third order, not at ground
+ level.
+
+ Multiple element 020 NONE
+ types
+
+ Descriptive Multiple element 020 0600- Decimal fractions of feet
+ types 0609 or meters
+ 0610 Approximate
+ 0611 Depression
+ 0612 Glacier or snow field
+ 0613 Underwater
+ 0614 Best estimate of contour
+ elevation value
+
+ 020 0000 Photorevised feature
+__________________________________________________________________________________________________________________________________
+* denotes a code which is no longer being used to encode features, but which may appear in older files.
+
+
+
+
+ APPENDIX D.--DLG Attribute Codes--continued
+__________________________________________________________________________________________________________________________________
+ MAJOR MINOR
+DATA CATEGORY TYPE OF CODE APPLICATION CODE CODE DESCRIPTION
+__________________________________________________________________________________________________________________________________
+Hypsography Parameter Multiple element 02N ---- Elevation in whole feet or
+ (cont'd.) types meters, right-justified
+ 026 00-- Major category associated
+ with a spot height, not at
+ ground elevation.
+ 029 00-- Coincident feature
+__________________________________________________________________________________________________________________________________
+Hydrography Feature identification Nodes 050 0001 Upper origin of stream
+ 0002 Upper origin of stream at water body
+ 0003 Sink, channel no longer evident
+ 0004 Stream entering water body
+ 0005 Steam exiting water body
+
+ Areas 050 0100 Alkali flat
+ 0101 Reservoir
+ 0102 Covered reservoir
+ 0103 Glacier or permanent snowfield
+ 0104 Salt evaporator
+ 0105 Inundation area
+ 0106 Fish hatchery or farm
+ 0107 Industrial water impoundment
+ 0108 Area to be submerged
+ 0109 Sewage disposal pond or
+ filtration beds
+ 0110 Tailings pond
+ 0111 Marsh, wetland, swamp, bog
+ 0112 Mangrove area
+ 0113 Rice field
+ 0114 Cranberry bog
+ 0115 Flats (tidal, mud, sand, gravel)
+ 0116 Bays, estuaries, gulfs, oceans, seas
+ 0117 Shoal
+ 0118 Soda evaporator
+ 0119 Duck Pond
+ 0120 Void area
+
+
+
+
+ APPENDIX D.--DLG Attribute Codes--continued
+__________________________________________________________________________________________________________________________________
+ MAJOR MINOR
+DATA CATEGORY TYPE OF CODE APPLICATION CODE CODE DESCRIPTION
+__________________________________________________________________________________________________________________________________
+Hydrography Feature identification Lines 050 0200 Shoreline
+ (cont'd.) (cont'd.) 0201 Manmade shoreline
+ 0202 Closure line
+ 0203 Indefinite shoreline
+ 0204 Apparent limit
+ 0205 Outline of a Carolina bay
+ 0206 Danger Curve
+ 0207 Apparent shoreline
+
+ Points 050 0300 Spring
+ 0301 Non-flowing well
+ 0302 Flowing well
+ 0303 Riser
+ 0304 Geyser
+ 0305 Windmill
+ 0306 Cistern
+
+ Multiple element 050 0400 Rapids
+ types 0401 Falls
+ 0402 Gravel pit or quarry filled with water
+ 0403 Gaging station
+ 0404 Pumping station
+ 0405 Water intake
+ 0406 Dam or weir
+ 0407 Canal lock or sluice gate
+ 0408 Spillway
+ 0409 Gate (flood, tidal, head, check)
+ 0410 Rock
+ 0411 Crevasse
+ 0412 Stream
+ 0413 Braided stream
+ 0414 Ditch or canal
+ 0415 Aqueduct
+ 0416 Flume
+ 0417 Penstock
+ 0418 Siphon
+ 0419 Channel in water area
+
+
+
+
+ APPENDIX D.--DLG Attribute Codes--continued
+__________________________________________________________________________________________________________________________________
+ MAJOR MINOR
+DATA CATEGORY TYPE OF CODE APPLICATION CODE CODE DESCRIPTION
+__________________________________________________________________________________________________________________________________
+Hydrography Feature identification Multiple element 050 0420 Wash or ephemeral drain
+ (cont'd.) (cont'd.) types (cont'd.) 0421 Lake or pond
+ 0422 Coral reef
+ 0423 Sand in open water
+ 0424 Spoil area
+ 0425 Fish ladders
+ 0426 Holiday area
+
+ Descriptive Multiple element 050 0601 Underground
+ types 0602 Overpassing
+ 0603 Elevated
+ 0604 Tunnel
+ 0605 Right bank
+ 0606 Left bank
+ 0607 Under construction
+ 0608 Salt
+ 0609 Unsurveyed
+ 0610 Intermittent
+ 0611 Abandoned or discontinued
+ 0612 Submerged or sunken
+ *0613 Wooded
+ 0614 Dry
+ 0615 Mineral or hot (sulphur, alkali, etc.)
+ 0616 Navigable, transportation
+ 0617 Underpassing
+ 0618 Earthen construction
+ 0619 Interpolated elevation
+ 0621- Decimal fractions of feet or meters
+ 0629
+
+ 050 0000 Photorevised feature
+
+ Parameter Multiple element 05N ---- Water surface elevation, actual or
+ types interpolated, N=1 for feet,
+ 2 for meters, 6 for feet below datum,
+ and 7 for meters below datum.
+ Elevation value in four spaces,
+ right justified.
+
+
+
+
+ APPENDIX D.--DLG Attribute Codes--continued
+__________________________________________________________________________________________________________________________________
+ MAJOR MINOR
+DATA CATEGORY TYPE OF CODE APPLICATION CODE CODE DESCRIPTION
+__________________________________________________________________________________________________________________________________
+Hydrography Parameter (cont'd.) Multiple element 053 0--- Angle of clockwise rotation (nearest
+ (cont'd.) types (cont'd) whole degree)
+ 055 ---- River mile, value in four spaces,
+ right justified
+ 058 0000 Best estimate of classification
+ or position
+ 059 00-- Coincident feature
+__________________________________________________________________________________________________________________________________
+Boundaries Feature identification Nodes 090 0001 Monumented point on a boundary
+
+ Areas 090 0100 Civil township, district, precinct,
+ or barrio
+ 0101 Incorporated city, village, town,
+ borough, or hamlet
+ 0103 National park, monument, lakeshore,
+ seashore, parkway, battlefield, or
+ recreation area
+ 0104 National forest or grassland
+ 0105 National wildlife refuge, game
+ preserve, or fish hatchery
+ 0106 National scenic waterway, riverway,
+ wild and scenic river, or
+ wilderness area
+ 0107 Indian reservation
+ 0108 Military reservation
+ 0110 Federal prison
+ 0111 Miscellaneous Federal reservation
+ 0129 Miscellaneous State reservation
+ 0130 State park, recreation area
+ arboretum, or lake
+ 0131 State wildlife refuge, game preserve,
+ or fish hatchery
+ 0132 State forest or grassland
+ 0133 State prison
+ 0134 County game preserve
+
+
+
+
+ APPENDIX D.--DLG Attribute Codes--continued
+__________________________________________________________________________________________________________________________________
+ MAJOR MINOR
+DATA CATEGORY TYPE OF CODE APPLICATION CODE CODE DESCRIPTION
+__________________________________________________________________________________________________________________________________
+Boundaries (cont'd.) Feature identification Areas (cont'd.) 090 0150 Large park (city, county, or private)
+ (cont'd.) 0151 Small park (city, county, or private)
+ 0197 Canada
+ 0198 Mexico
+ 0199 Open water
+
+ Lines 090 0201 Indefinite (or approximate) boundary
+ 0202 Disputed boundary
+ 0203 Historical line
+ 0204 Boundary closure claim
+
+ Points 090 0301 Reference monuments for boundary
+ (degenerate lines) points
+
+ Multiple element 090 NONE
+ types
+
+ Descriptive Multiple element 090 0000 Photorevised feature
+ types
+
+ Parameter Multiple element 091 00-- State FIPS code
+ types 092 0--- County or county equivalent FIPS code
+ 095 ---- Monument number
+ 096 XXYY Alphabetic portion of any monument
+ number substitute numeric equivalent
+ of alphabetic for XX and for YY ass
+ follows: 00 blank, 01 = A, 02 = B,
+ 03 = C, 04 = D, 05 = E, 06 = F,
+ 07 = G, 08 = H, 09 = I, 10 = J,
+ 11 = K, 12 = L, 13 = M, 14 = N,
+ 15 = O, 16 = P, 17 = Q, 18 = R,
+ 19 = S, 20 = T, 21 = U, 22 = V,
+ 23 = W, 24 = X, 25 = Y, 26 = Z.
+ 098 0000 Best estimate of classification
+ or position.
+ 099 00-- Coincident feature
+
+
+
+
+ APPENDIX D.--DLG Attribute Codes--continued
+__________________________________________________________________________________________________________________________________
+ MAJOR MINOR
+DATA CATEGORY TYPE OF CODE APPLICATION CODE CODE DESCRIPTION
+__________________________________________________________________________________________________________________________________
+Transportation, Roads, Feature identification Nodes 170 0001 Bridge abutment
+ and Trails 0002 Tunnel portal
+ 0004 Gate
+ 0005 Cul-de-sac
+ 0006 Dead end
+ 0007 Drawbridge
+
+ 170 0100 Void area
+
+ Lines 170 0201 Primary route, class 1, symbol
+ undivided
+ 0202 Primary route, class 1, symbol
+ divided by centerline
+ 0203 Primary route, class 1, divided,
+ lanes separated
+ 0204 Primary route, class 1, one way, other
+ than divided highway
+ 0205 Secondary route, class 2, symbol
+ undivided
+ 0206 Secondary route, class 2, symbol
+ divided by centerline
+ 0207 Secondary route, class 2, symbol
+ divided, lanes separated
+ 0208 Secondary route, class 2, one way,
+ other then divided highway
+ 0209 Road or street, class 3
+ 0210 Road or street, class 4
+ 0211 Trail, class 5, other than four-wheel
+ drive vehicle
+ 0212 Trail, class 5, four-wheel-drive
+ vehicle
+ 0213 Footbridge
+ 0214 Ferry crossing
+ 0215 Perimeter of parking area
+ 0216 Arbitrary extension of line (join or
+ closure)
+
+
+
+
+ APPENDIX D.--DLG Attribute Codes--continued
+__________________________________________________________________________________________________________________________________
+ MAJOR MINOR
+DATA CATEGORY TYPE OF CODE APPLICATION CODE CODE DESCRIPTION
+__________________________________________________________________________________________________________________________________
+Transportation, Roads, Feature identification Lines (cont'd.) 0217 Road or street, class 3, symbol
+ and trails (cont'd.) (cont'd.) divided by centerline
+ 0218 Road or street, class 3, divided
+ lanes separated
+ 0221 Road in street, class 3, one way
+ 0222 Road in transition
+
+ Points NONE
+ (degenerate lines)
+
+ Multiple element 170 0401 Traffic circle
+ type 0402 Cloverleaf or interchange
+ 0403 Toll gate, toll plaza or perimeter or
+ toll plaza
+ 0404 Weigh station
+ 0405 Nonstandard section of road
+ *170 0600 Historical
+
+ Descriptive Multiple element 170 0601 In tunnel
+ types 0602 Overpassing, on bridge
+ 0603 Under construction, classification
+ known
+ 0604 Under construction, classification
+ unknown
+ 0605 Labeled "old railroad grade"
+ 0606 Submerged or in ford
+ 0607 Underpassing
+ *0608 Limited access
+ 0609 Toll road
+ 0610 Privately operated or controlled
+ public access
+ 0611 Proposed
+ 0612 Double-decked
+ 0613 In service facility or rest area
+ 0614 Elevated
+ 0615 Bypass route
+ 0616 Alternate route
+
+
+
+
+ APPENDIX D.--DLG Attribute Codes--continued
+__________________________________________________________________________________________________________________________________
+ MAJOR MINOR
+DATA CATEGORY TYPE OF CODE APPLICATION CODE CODE DESCRIPTION
+__________________________________________________________________________________________________________________________________
+Transportation, Roads, Descriptive Multiple element 170 0617 Business route
+ and trails (cont'd.) (cont'd.) types (cont'd.) 0618 On drawbridge
+ 0619 Spur
+ 0620 Loop
+ 0621 Connector
+ 0622 Truck route
+ 0650 Road width 46-55 feet, 0.025 inches
+ at 1:24,000
+ 0651 Road width 56-65 feet, 0.030 inches
+ at 1:24,000
+ 0652 Road width 66-75 feet, 0.035 inches
+ at 1:24,000
+ 0653 Road width 76-85 feet, 0.040 inches
+ at 1:24,000
+ 0654 Road width 86-95 feet, 0.045 inches
+ at 1:24,000
+ 0655 Road width 96-105 feet, 0.050 inches
+ at 1:24,000
+ 0656 Road width 106-115 feet, 0.055 inches
+ at 1:24,000
+ 0657 Road width 116-125 feet, 0.060 inches
+ at 1:24,000
+ 0658 Road width 126-135 feet, 0.065 inches
+ at 1:24,000
+ 0659 Road width 136-145 feet, 0.070 inches
+ at 1:24,000
+
+ 170 0000 Photorevised feature
+
+ Parameter Multiple element 171 ---- Number of lanes
+ types 172 ---- Interstate route number
+ 173 ---- U.S. route number
+ 174 ---- State route number
+ 175 ---- Reservation, park, or military route
+ number
+ 176 ---- County route
+
+
+
+
+ APPENDIX D.--DLG Attribute Codes--continued
+__________________________________________________________________________________________________________________________________
+ MAJOR MINOR
+DATA CATEGORY TYPE OF CODE APPLICATION CODE CODE DESCRIPTION
+__________________________________________________________________________________________________________________________________
+Transportation, Road, Parameter (cont'd.) Multiple element 177 XXYY Alphabetic portion of any route
+ and Trails (cont'd.) types (cont'd.) number. Substitute numeric equiva-
+ lent of alphabetic for XX and for YY
+ as follows: 00 = blank, 01 = A,
+ 02 = B, 03 = C, 04 = D, 05 = E,
+ 06 = F, 07 = G, 08 = H, 09 = I,
+ 10 = J, 11 = K, 12 = L, 13 = M,
+ 14 = N, 15 = O, 16 = P, 17 = Q,
+ 18 = R, 19 = S, 20 = T, 21 = U,
+ 22 = V, 23 = W, 24 = X, 25 = Y,
+ 26 = Z.
+ 178 0000 Best estimate of position or
+ classification
+ 179 00-- Coincident feature
+__________________________________________________________________________________________________________________________________
+Transportation, Feature identification Nodes 180 0001 Bridge abutment
+ Railroads 0002 Tunnel portal
+ 0007 Drawbridge
+
+ Areas 180 0100 Void area
+
+ Lines 180 0201 Railroad
+ 0202 Railroad in street or road
+ 0204 Carline
+ 0205 Cog railroad, incline railway,
+ logging tram
+ 0207 Ferry crossing
+ 0208 Railroad siding
+ 0209 Perimeter or limit of yard
+ 0210 Arbitrary line extension
+ 0211 Closure line
+
+ Points 180 NONE
+ (degenerate lines)
+
+ Multiple element 180 0400 Railroad station, perimeter of
+ types station
+ 0401 Turntable
+ 0402 Roundhouse
+ *180 0600 Historical
+
+
+
+
+ APPENDIX D.--DLG Attribute Codes--continued
+__________________________________________________________________________________________________________________________________
+ MAJOR MINOR
+DATA CATEGORY TYPE OF CODE APPLICATION CODE CODE DESCRIPTION
+__________________________________________________________________________________________________________________________________
+Transportation, Descriptive Multiple element 180 0601 In tunnel
+ Railroads (cont'd.) types 0602 Overpassing, on bridge
+ 0603 Abandoned
+ 0604 Dismantled
+ 0605 Underpassing
+ 0606 Narrow gauge
+ 0607 In snowshed or under structure
+ 0608 Under construction
+ 0609 Elevated
+ 0610 Rapid transit
+ 0611 On drawbridge
+ 0612 Private
+ 0613 U.S. Government
+ 0614 Juxtaposition
+
+ 180 0000 Photorevised feature
+ Parameter Multiple element 181 ---- Number of tracks
+ types 188 0000 Best estimate of position or
+ classification
+ 189 00-- Coincident feature
+__________________________________________________________________________________________________________________________________
+Transportation, Feature identification Nodes 190 0001 End of transmission line at
+ Pipelines, Trans- power station, substation, or
+ mission Lines, hydroelectric plant
+ Miscellaneous Trans- 0002 End of pipeline at oil or gas
+ portation Features field
+ 0003 End of pipeline at refinery,
+ depot, or tank farm
+
+ Areas 190 0100 Void area
+
+ Lines 190 0201 Pipeline
+ 0202 Power transmissiion line
+ 0203 Telephone or telegraph line
+ 0204 Aerial tramway, monorail, ski
+ lift
+ 0205 Arbitrary line extension
+ 0206 Closure line
+__________________________________________________________________________________________________________________________________
+
+
+
+
+ APPENDIX D.--DLG Attribute Codes--continued
+__________________________________________________________________________________________________________________________________
+ MAJOR MINOR
+DATA CATEGORY TYPE OF CODE APPLICATION CODE CODE DESCRIPTION
+__________________________________________________________________________________________________________________________________
+Transportation, Feature identification Points 190 0300 Seaplane anchorage
+ Pipelines, Trans- (cont'd.) (degenerate lines)
+ mission Lines,
+ Miscellaneous Trans- Multiple element 190 0400 Power station
+ portation Features (cont'd.) types 0401 Substation
+ 0402 Hydroelectric Plant
+ 0403 Landing strip, airport,
+ perimeter of airport
+ 0404 Heliport, perimeter of heliport
+ 0405 Launch complex, perimeter of
+ launch complex
+ 0406 Pumping station (other than
+ water)
+ 0407 Seaplane ramp or landing area
+ 0408 Measuring station
+
+ Descriptive Multiple element 190 0600 Underground
+ types 0601 Under construction
+ 0602 Abandoned
+ 0603 Above ground
+ 0604 Labeled "closed"
+ 0605 Unimproved, loose surface
+ 0606 Submerged
+ 0607 Nuclear
+
+ 190 0000 Photorevised feature
+
+ Parameters Multiple element 193 0--- Angle of clockwise rotation
+ types (nearest whole degree)
+ 198 0000 Best estimate of position or
+ classification
+ 199 00-- Coincident feature
+__________________________________________________________________________________________________________________________________
+
+
+
+
+ APPENDIX D.--DLG Attribute Codes--continued
+__________________________________________________________________________________________________________________________________
+ MAJOR MINOR
+DATA CATEGORY TYPE OF CODE APPLICATION CODE CODE DESCRIPTION
+__________________________________________________________________________________________________________________________________
+U.S. Public Land Feature identification Nodes 300 0001 U.S. Public Land Survey System
+ Survey System section corner
+ 0002 Point on section line (no corner)
+ 0003 Closing corner
+ 0004 Meander corner
+ 0005 Auxiliary meander corner
+ 0006 Special meander corner
+ 0007 Witness corner
+ 0008 Witness point
+ 0009 Angle point
+ 0010 Location monument (includes amended
+ monument and mineral monument)
+ 0011 Reference mark
+ 0012 Quarter-section corner
+ 0013 Tract corner
+ 0014 Land grant corner
+ 0015 Arbitrary section corner
+
+ Nodes (identifi- 300 0040 Corner identified in field
+ cation procedures) 0041 Corner with horizontal coordinates
+ 0042 Corner with elevation value
+
+ Parameters Areas Select one parameter code from each of
+ the following A, B, C, and D lists
+ and/or consult list E.
+
+ A. Origin of Survey
+
+ 306 00-- Insert two-digit code from Appendix K.
+
+ B. Township number(s)
+
+ 30- ---- Insert 2 for north of the baseline or
+ 3 for south of the baseline in first
+ space. In the second space, insert
+ a 0 for full township, 2 for 1/4
+ township, 4 for « township, or 6
+ for 3/4 township. Insert township
+ number in the last three spaces,
+ right justified.
+
+
+
+
+ APPENDIX D.--DLG Attribute Codes--continued
+__________________________________________________________________________________________________________________________________
+ MAJOR MINOR
+DATA CATEGORY TYPE OF CODE APPLICATION CODE CODE DESCRIPTION
+__________________________________________________________________________________________________________________________________
+U.S. Public Land Parameters Areas (cont'd.) C. Range number(s)
+ Survey System (cont'd.)
+ (cont'd.) 30- ---- Insert 4 for east of the principal
+ meridian or 5 for west of the
+ principal meridian in the first
+ space. In the second space, insert
+ a 0 for a full range, 2 for 1/4
+ range, 4 for « range, 6 for 3/4
+ range, 8 for duplicate to the north
+ or east of the original township, or
+ 9 for triplicate to the north or
+ east of the original township.
+ Insert range number in last three
+ spaces, right justified.
+
+ D. Section number
+ 301 ---- In the first space, insert 0 for
+ numeric section identifier, 1 for
+ numeric portion of alphanumeric
+ identifier or 2 for alphabetic part
+ of alphanumeric identifier. In the
+ last three spaces, insert section
+ number or numeric representation of
+ alphabetic character (01-26), right
+ justified.
+
+ E. Land grant identifier
+ 307 ---- In the first space, insert the
+ appropriate number:
+
+ 0 for numeric grant identifier
+ 1 for numeric portion of alphanumeric
+ identifier
+ 2 for alphabetic portion of
+ alphanumeric identifier
+ 3 for alphabetic identifier
+ 4 for identifier of named grant in
+ Arizona
+
+
+
+
+ APPENDIX D.--DLG Attribute Codes--continued
+__________________________________________________________________________________________________________________________________
+ MAJOR MINOR
+DATA CATEGORY TYPE OF CODE APPLICATION CODE CODE DESCRIPTION
+__________________________________________________________________________________________________________________________________
+U.S. Public Land Parameters Areas (cont'd.) 5 for identifier of named grant in
+ Survey system (cont'd.) California
+ (cont'd.) 6 for identifier of named grant in
+ Colorado
+ 7 for identifier of named grant in New
+ Mexico
+ 8 For identifier of named grant in
+ other States
+ In the last three spaces after 0-3
+ above, insert the grant number or
+ numeric representation of the
+ alphabetic character (01-26),
+ right-justified. In the last three
+ spaces after 4-7 above, insert the
+ three-digit code of the named grant
+ as designated in Appendix L.
+
+ F. Excluded areas
+ 301 0100 Indian lands
+ 0101 Homestead entries
+ 0102 Donation land claims
+ 0103 Land grants; civil colonies
+ 0104 Private extension of public land
+ survey
+ 0105 Area of public and private survey
+ overlap
+ 0106 Overlapping land grants
+ 0107 Military reservation
+ 0198 Water
+ 0199 Unsurveyed area
+
+ Feature identification Lines 300 0201 Approximate position (within 200 feet)
+ 0202 Protracted position
+ 0203 Arbitrary closure line
+ 0204 Base line
+ 0205 Claim line, grant line
+
+ Points 0300 0300 Location monument
+ (degenerate lines) 0301 Isolated found section corner
+ 0302 Witness corner (off surveyed line)
+
+
+
+
+ APPENDIX D.--DLG Attribute Codes--continued
+__________________________________________________________________________________________________________________________________
+ MAJOR MINOR
+DATA CATEGORY TYPE OF CODE APPLICATION CODE CODE DESCRIPTION
+__________________________________________________________________________________________________________________________________
+U.S. Public Land Parameter Multiple element 308 0000 Best estimate of classification and/or
+ Survey System types position
+ (cont'd.) 309 00-- Coincident feature or symbol
+__________________________________________________________________________________________________________________________________
+* denotes a code which is no longer being used to encode features, but which may appear in older files.
+
+
+
+
+
+ APPENDIX G.--Sample DLG Data File
+ (Optional Distribution Format)
+
+
+
+CARTERSVILLE, GA 01 1981, 100000. S01
+RO4.RDS01
+ 3 1 16 2 0.25400000000D+01 4 0 4 1
+ -0.840560150000038D+08 0.340260150000010D+08 0.000000000000000D+00
+ 0.000000000000000D+00 0.000000000000000D+00 0.000000000000000D+00
+ 0.000000000000000D+00 0.000000000000000D+00 0.000000000000000D+00
+ 0.000000000000000D+00 0.000000000000000D+00 0.000000000000000D+00
+ 0.000000000000000D+00 0.000000000000000D+00 0.000000000000000D+00
+ 0.10000000000D+01 0.00000000000D+00 0.00000000000D+00 0.00000000000D+00
+SW 34.375000 -85.000000 683898.58 3805355.05
+NW 34.500000 -85.000000 683624.37 3819215.69
+NE 34.500000 -84.875000 695100.28 3819449.04
+SE 34.375000 -84.875000 695392.26 3805588.76
+ROADS AND TRAILS 0 551 551 010 198 198 011 747 747 1
+N 1 695392.26 3805588.76 2 0 0
+ -724 725
+N 2 685742.29 3819258.76 3 0 0
+ 1 -2 -87
+N 3 684845.86 3819240.53 3 0 0
+ -1 -23 -258
+N 4 687098.38 3819286.33 3 0 0
+ 2 -3 -34
+N 5 687347.30 3819288.85 3 0 0
+ 3 -4 -35
+N 6 687509.77 3819294.70 3 0 0
+ 4 -5 -42
+N 7 687735.78 3819299.29 3 0 0
+ 5 -6 -43
+N 8 687842.44 3819301.46 3 0 0
+ 6 -7 -45
+N 9 687969.42 3819304.04 3 0 0
+ 7 -8 -67
+N 10 688042.96 3819310.62 3 0 0
+ 8 -9 -66
+N 11 688129.40 3819307.29 3 0 0
+ 9 -10 -80
+N 12 688462.08 3819314.06 3 0 0
+ 10 -11 -31
+N 13 688632.22 3819317.52 3 0 0
+ 11 -12 -32
+N 14 688837.92 3819321.70 3 0 0
+ 12 -13 -24
+N 15 688947.12 3819323.92 3 0 0
+ 13 -14 -26
+N 16 689490.57 3819334.97 3 0 0
+ 14 -15 -154
+
+
+
+
+ APPENDIX G.--Sample DLG Data File
+ (Optional Distribution Format)--continued
+
+
+A 1 689504.51 3812402.15 61 65 1 0 0
+ -695 -701 -705 -706 -708 -710 -713 -714 -716 -718 -719 -722
+ -723 724 725 693 692 645 576 554 553 545 536 512
+ 483 407 244 218 146 113 94 21 20 19 18 17
+ 16 15 14 13 12 11 10 9 8 7 6 5
+ 4 3 2 1 -258 -399 -464 -509 -543 -547 -557 -620
+ -689
+ 0 0
+A 2 689504.51 3812402.15 3 4 0 0 0
+ 726 -725 -724
+A 3 689504.51 3812402.15 10 32 0 0 0
+ 87 -2 -34 -40 41 -49 -48 -74 -105 104
+A 4 689504.51 3812402.15 8 25 0 0 0
+ 136 23 -1 -87 -137 -139 -141 140
+A 5 689504.51 3812402.15 5 28 0 0 0
+ -259 258 -23 -136 -237
+A 6 689504.51 3812402.15 3 8 0 0 0
+ 34 -3 -35
+A 7 689504.51 3812402.15 5 9 0 0 0
+ 59 35 -4 -42 -58
+A 8 689504.51 3812402.15 4 6 0 0 0
+ 42 -5 -43 44
+A 9 689504.51 3812402.15 4 5 0 0 0
+ 43 -6 -45 46
+A 10 689504.51 3812402.15 4 8 0 0 0
+ 45 -7 -67 70
+A 11 689504.51 3812402.15 4 6 0 0 0
+ 67 -8 -66 -68
+A 12 689504.51 3812402.15 5 6 0 0 0
+ 66 -9 -80 79 78
+A 13 689504.51 3812402.15 17 34 0 0 1
+ 106 -79 80 -10 -31 -37 -111 -110 -115 -117 -119 -121
+ 122 0 84 85 -83
+A 14 689504.51 3812402.15 3 8 0 0 0
+ 31 -11 -32
+A 15 689504.51 3812402.15 5 9 0 0 0
+ 39 32 -12 -24 -38
+A 16 689504.51 3812402.15 4 6 0 0 0
+ 24 -13 -26 25
+L 1 2 3 4 1 2 0 0
+ 685742.29 3819258.76 684845.86 3819240.53
+L 2 4 2 3 1 2 0 0
+ 687098.38 3819286.33 685742.29 3819258.76
+L 3 5 4 6 1 2 0 0
+ 687347.30 3819288.85 687098.38 3819286.33
+L 4 6 5 7 1 2 0 0
+ 687509.77 3819294.70 687347.30 3819288.85
+L 5 7 6 8 1 2 0 0
+ 687735.78 3819299.29 687509.77 3819294.70
+
+
+
+
+ APPENDIX G.--Sample DLG Data File
+ (Optional Distribution Format)--continued
+
+
+L 6 8 7 9 1 2 0 0
+ 687842.44 3819301.46 687735.78 3819299.29
+L 7 9 8 10 1 2 0 0
+ 687969.42 3819304.04 687842.44 3819301.46
+L 8 10 9 11 1 2 0 0
+ 688042.96 3819310.62 687969.42 3819304.04
+L 9 11 10 12 1 2 0 0
+ 688129.40 3819307.29 688042.96 3819310.62
+L 10 12 11 13 1 2 0 0
+ 688462.08 3819314.06 688129.40 3819307.29
+L 11 13 12 14 1 2 0 0
+ 688632.22 3819317.52 688462.08 3819314.06
+L 12 14 13 15 1 2 0 0
+ 688837.92 3819321.70 688632.22 3819317.52
+L 13 15 14 16 1 2 0 0
+ 688947.12 3819323.92 688837.92 3819321.70
+L 14 16 15 17 1 2 0 0
+ 689490.57 3819334.97 688947.12 3819323.92
+L 15 17 16 18 1 2 0 0
+ 690620.63 3819357.95 689490.57 3819334.97
+L 16 18 17 18 1 2 0 0
+ 690925.37 3819364.15 690620.63 3819357.95
+L 17 19 18 19 1 2 0 0
+ 691189.48 3819369.52 690925.37 3819364.15
+L 18 20 19 20 1 2 0 0
+ 691605.95 3819377.98 691189.48 3819369.52
+L 19 21 20 21 1 2 0 0
+ 693447.02 3819417.96 691605.95 3819377.98
+L 20 22 21 21 1 2 0 0
+ 694107.34 3819428.85 693447.02 3819417.96
+L 21 23 22 22 1 2 0 0
+ 694914.90 3819445.27 694107.34 3819428.85
+L 22 24 22 21 22 3 1 0
+ 694205.18 3819364.78 694194.61 3819384.89 694107.34 3819428.85
+ 170 205
+L 23 25 3 5 4 3 1 0
+ 684825.58 3819113.09 684849.22 3819199.95 684845.86 3819240.53
+ 170 209
+L 24 26 14 15 16 2 1 0
+ 688848.53 3819174.57 688837.92 3819321.70
+ 170 210
+L 25 27 26 25 16 2 1 0
+ 688901.91 3819173.11 688848.53 3819174.57
+ 170 210
+L 26 27 15 16 17 3 1 0
+ 688901.91 3819173.11 688939.85 3819181.50 688947.12 3819323.92
+ 170 210
+L 27 28 17 18 18 3 1 0
+ 690593.10 3819212.58 690628.40 3819226.00 690620.63 3819357.95
+ 170 209
+
+
+
+
+ APPENDIX G.--Sample DLG Data File
+ (Optional Distribution Format)--continued
+
+
+L 28 29 25 4 4 3 1 0
+ 685461.28 3819085.37 685414.90 3819117.45 684825.58 3819113.09
+ 170 209
+L 29 30 24 24 22 2 1 0
+ 694605.90 3819273.85 694205.18 3819364.78
+ 170 205
+L 30 30 23 22 23 4 1 0
+ 694605.90 3819273.85 694615.85 3819284.21 694851.82 3819423.66
+ 694914.90 3819445.27
+ 170 205
+L 31 31 12 13 14 4 1 0
+ 688529.54 3819119.81 688480.67 3819149.30 688470.15 3819166.87
+ 688462.08 3819314.06
+ 170 210
+L 32 31 13 14 15 4 1 0
+ 688529.54 3819119.81 688611.12 3819230.71 688637.82 3819292.23
+ 688632.22 3819317.52
+ 170 210
+L 33 32 21 21 21 2 1 0
+ 693453.44 3819227.55 693447.02 3819417.96
+ 170 209
+L 34 33 4 3 6 4 1 0
+ 687148.37 3819076.48 687139.15 3819155.05 687123.40 3819180.14
+ 687098.38 3819286.33
+ 170 210
+L 35 33 5 6 7 4 1 0
+ 687148.37 3819076.48 687172.89 3819120.17 687342.68 3819265.89
+ 687347.30 3819288.85
+ 170 201
Added: packages/drawmap/branches/upstream/current/attributes
===================================================================
--- packages/drawmap/branches/upstream/current/attributes (rev 0)
+++ packages/drawmap/branches/upstream/current/attributes 2007-05-18 12:29:03 UTC (rev 834)
@@ -0,0 +1,700 @@
+# =========================================================================
+# attributes - A sample attribute file
+# Copyright (c) 1997,1998,1999,2000,2001 Fred M. Erickson
+#
+# 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 2, 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, write to the Free Software
+# Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
+# =========================================================================
+
+
+
+
+
+##################################################
+### Codes to select entire groups of features. ###
+##################################################
+# L 020 -1 all Hypsography
+L 050 -1 all Hydrography
+# L 090 -1 all Boundaries
+# L 170 -1 all Roads and Trails
+# L 180 -1 all Railroads
+# L 190 -1 all Pipelines, Transmission Lines, Miscellaneous Transportation Features
+# L 300 -1 all U.S. Public Land Survey System
+
+
+
+
+
+
+
+##################################################
+### Some useful codes for selecting common ###
+### features on an individual basis. ###
+##################################################
+#
+# Lines
+#
+L 170 201 primary route, class 1, symbol undivided
+L 170 202 primary route, class 1, symbol divided by centerline
+L 170 203 primary route, class 1, symbol divided, lanes separated
+L 170 204 primary route, class 1, symbol one way, other than divided highway
+# L 50 200 shoreline
+# L 50 201 manmade shoreline
+# L 50 202 closure line
+# L 50 406 dam or weir
+# L 50 412 stream
+# L 50 413 braided stream
+# L 50 414 ditch or canal
+# L 50 415 aqueduct
+# L 50 419 channel in water area
+# L 50 421 lake