FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION
VERSION 2004
TITLE: NATIONAL PARKS AND SEASHORES
Geodataset Name: NPS Geodataset Type: SHAPE Geodataset Feature: POLYGON
GENERAL DESCRIPTION:
This dataset contains National Park and Seashore Service boundaries in the State of Florida.
DATA SOURCE(S): NOAA Coastal Services Center OPIS SCALE OF ORIGINAL SOURCE MAPS: 1:24,000 DATE OF AUTOMATION OR SOURCE: 1998 GEODATASET EXTENT: State of Florida 
FEATURE ATTRIBUTE TABLES:
Datafile Name: NPS.DBF ITEM NAME WIDTH TYPE PRECISION SHAPE 8 Shapepoly 0 AREA 15 Decimal 3 PERIMETER 15 Decimal 3 SOURCE 64 Character 0 UNIT_NAME 47 Character 0 UNIT_TYPE 36 Character 0 PROGRAM 27 Character 0 STATE 70 Character 0 MNG_AGCY 28 Character 0 CONTACT 20 Character 0 PL_CITE 38 Character 0 USC_CITE 20 Character 0 CFR_CITE 20 Character 0 DESCRIPT 47 Character 0 
FEATURE ATTRIBUTE TABLES CODES AND VALUES:
ITEM ITEM DESCRIPTION SHAPE Data attribute inherent to the ESRI shapefile format, which defines the data as a point, polyline, or polygon. AREA Area of polygon PERIMETER Perimeter of polygon SOURCE Source of original data UNIT_NAME Name of National Park Service Unit UNIT_TYPE Type of Unit (National Seashore, Park, etc.) PROGRAM Designating Program STATE Unit headquarter location MNG_AGCY Managing Agency CONTACT Unit phone number PL_CITE Public Law Authority USC_CITE Codified Public Law CFR_CITE Code of Federal Regulations DESCRIPT FGDL added item based on UNIT_NAME 
USER NOTES:
NOT LEGALLY BINDING. These digital national park unit boundaries should not be used for any legal boundary disputes. To obtain the most accurate, current boundary, users should contact the specific park. The National Park Service shall not be held liable for improper or incorrect use of the park boundary data described and/or contained herein. These data are not legal documents and are not intended to be used as such. The information contained in these data is dynamic and may change over time. The data are no better than the original sources from which they were derived. In fact, the data are likely less accurate than the original sources as no attempt has been made to thoroughly error check the data. It is the responsibility of the data user to use the data appropriately and consistent within the limitations of geospatial data in general and these data in particular. The National Park Service gives no warranty, expressed or implied, as to the accuracy, reliability, or completeness of these data. It is strongly recommended that these data are directly acquired from an NPS server and not indirectly through other sources which may have changed the data in some way. Although these data have been processed successfully on a computer system at the National Park Service, no warranty expressed or implied is made regarding the utility of the data on another system or for general or scientific descriptions, nor aggregate use with other data. Acknowledgement of the NPS Water Resources Division would be appreciated in products derived from these data. Users must assume responsibility to determine the appropriate use of these data. NOT INTENDED FOR LEGAL PURPOSES. A note concerning data scale: Scale is an important factor in data usage. Certain scale datasets are not suitable for some project, analysis, or modelling purposes. Please be sure you are using the best available data. 1:24000 scale datasets are recommended for projects that are at the county level. 1:24000 data should NOT be used for high accuracy base mapping such as property parcel boundaries. 1:100000 scale datasets are recommended for projects that are at the multi-county or regional level. 1:250000 scale datasets are recommended for projects that are at the regional or state level or larger. Vector datasets with no defined scale or accuracy should be considered suspect. Make sure you are familiar with your data before using it for projects or analyses. Every effort has been made to supply the user with data documentation. For additional information, see the References section and the Data Source Contact section of this documentation. For more information regarding scale and accuracy, see our web pages at: http://www.geoplan.ufl.edu/education.html 
FGDL QUALITY ASSURANCE STATUS:
-Reprojected data to FGDL Albers HPGN (See "Map Projection Parameters" below) -Upcased all character records -Clipped to the State of Florida -DESCRIPT item was added based on the item PL_CITE -Dropped item: PL_LINK 
REFERENCES:
This dataset is part of the Southeast Ocean Planning and Governance GIS http://www.csc.noaa.gov/opis/ 
DATA LINEAGE SUMMARY:
This data was downloaded in shapefile format by the GeoPlan Center in 2002 from Ocean Planning and Governance Geographic Information System (Ocean GIS) website: http://www.csc.noaa.gov/opis/html/data.htm. When received, the geographic extent of the data was the Southeastern U.S. and the data was in the following projection: Geographic, Datum: NAD83, Spheroid: GRS1980, Units: Decimal degrees. The data was clipped to the State of Florida and projected to FGDL Albers HPGN. DESCRIPT item was added based on PL_CITE, and lowercase characters within the attribute table were upcased. 
MAP PROJECTION PARAMETERS:
Projection ALBERS Units METERS Datum HPGN Spheroid GRS1980 1st standard parallel 24 0 0.000 2nd standard parallel 31 30 0.000 central meridian -84 0 0.000 latitude of projection's origin 24 0 0.000 false easting (meters) 400000.00000 false northing (meters) 0.00000
DATA SOURCES CONTACT(S):
Name: NOAA Coastal Services Center Address: 2234 South Hobson Ave Charleston, South Carolina 29405 Phone: (843)740-1210 Fax: (843) 740-1224 Email: clearinghouse@csc.noaa.gov Contact Person: Clearinghouse Manager
FGDL CONTACT:
Name: Florida Geographic Data Library Abbr. Name: FGDL Address: Florida Geographic Data Library 431 Architecture PO Box 115706 Gainesville, FL 32611-5706 Web site: http://www.fgdl.org Contact FGDL: Technical Support: http://www.fgdl.org/fgdlfeed.html FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html FGDL Mailing Lists: http://www.fgdl.org/fgdl-l.html For FGDL Software: http://www.fgdl.org/software.html