<?xml version="1.0" encoding="UTF-8"?>
<metadata>
  <idinfo>
    <citation>
      <citeinfo>
        <origin>National Park Service,  Water  Resources</origin>
        <pubdate>199904</pubdate>
        <title>Fort Larned National Historic Site Vegetation Mapping Project - Park Boundary</title>
        <geoform>vector digital data</geoform>
        <pubinfo>
          <pubplace>Fort Collins, Colorado</pubplace>
          <publish>National Park Service, Water Resources</publish>
        </pubinfo>
        <onlink>http://www1.usgs.gov/vip/fols/folsbdy.zip</onlink>
        <onlink>doi:10.5066/F7VX0DGX</onlink>
      </citeinfo>
    </citation>
    <descript>
      <abstract>This dataset contains 340  National  Park System  unit boundaries.  Under the jurisdiction of the  National Park  Service (NPS), these park units are located throughout  the United  States (U.S.) and its territories.  Almost all the  parks are  located  north  of  the equator in the  western  hemisphere; although  a  couple  parks are south of the  equator  or  in  the eastern hemisphere.  The dataset was compiled (and edited) from a variety sources: park-based GIS databases; U.S. Geological Survey 7.5'  1:24,000  quadrangles; NPS Park  Land  Status  Maps;  legal descriptions;  etc.).   The boundaries are georeferenced  to  the Latitude-Longitude (NAD27-Clarke 1866) coordinate system.  The ID field contains the unique 4 character park code identifying  each park.   The  NAME field contains the full park name.   The  NAME2 field  contains information about the source, scale, and date  of the  boundary.   The  boundaries  are  generally  the  designated boundary.   Inholdings may or may not be shown depending  on  the park.   This  dataset  was  originally created  in  Environmental System's Research Institute's ATLAS*GIS software and is currently maintained  in  this software.  This dataset  was  created  using ATLAS*GIS'  Ver. 4.0 Export to ShapeFile command.  The  ShapeFile was  then  imported  into  PC ARC/INFO  (SHAPEARC)  to  create  a coverage.   The  coverage was then exported to NPSUNITS.E00.   To obtain  the most accurate, current boundary, users should contact the specific park.</abstract>
      <purpose>These digital park unit boundaries should not be used for any legal boundary disputes.  They are intended solely for use only in identifying the general locations of national  park  units  throughout  the  U.S. This dataset was compiled to assist the NPS Water Resources Division in determining the proximity of certain hydrographic  features  to national park units and whether national park units are contained in other management units.</purpose>
    </descript>
    <timeperd>
      <timeinfo>
        <sngdate>
          <caldate>Depends on source document used for</caldate>
        </sngdate>
      </timeinfo>
      <current>Source boundary dates</current>
    </timeperd>
    <status>
      <progress>Complete</progress>
      <update>Irregular</update>
    </status>
    <spdom>
      <descgeog>Fort Larned National Historic Site</descgeog>
      <bounding>
        <westbc>-99.241151</westbc>
        <eastbc>-99.205033</eastbc>
        <northbc>38.191756</northbc>
        <southbc>38.118087</southbc>
      </bounding>
    </spdom>
    <keywords>
      <theme>
        <themekt>none</themekt>
        <themekey>national park boundaries</themekey>
        <themekey>federal lands</themekey>
      </theme>
      <place>
        <placekt>None</placekt>
        <placekey>Range includes all  50  states,</placekey>
      </place>
    </keywords>
    <accconst>None</accconst>
    <useconst>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 purposes,
nor shall  the act of distribution constitute any such warranty.  This  disclaimer applies both to individual use of the  data  and aggregate use with other data.  Acknowledgement of the NPS  Water Resources Division would be appreciated in products derived  from these data.</useconst>
    <ptcontac>
      <cntinfo>
        <cntorgp>
          <cntorg>National Park Service, Water Resources Division</cntorg>
        </cntorgp>
        <cntpos>GIS Specialist</cntpos>
        <cntaddr>
          <addrtype>mailing and physical address</addrtype>
          <address>1201 Oak Ridge Drive, Suite 250</address>
          <city>Fort Collins</city>
          <state>Colorado</state>
          <postal>80525</postal>
          <country>USA</country>
        </cntaddr>
        <cntvoice>Unknown</cntvoice>
      </cntinfo>
    </ptcontac>
    <native>Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.2.0.1324</native>
  </idinfo>
  <dataqual>
    <attracc>
      <attraccr>Attribute accuracy was tested  by manual comparison o  the source with hard  copy printouts.  Attributes were further verified by visual inspection.</attraccr>
    </attracc>
    <logic>Tests for logical consistency are performed by digitizing software (ATLAS*GIS).</logic>
    <complete>Dataset contains boundaries for only 340 of 375  park units.  The missing units are typically very small (an  acre  or less) and don't show up on  U.S.  Geological Survey  7.5'  quadrangles.   Park boundaries are generally the legislative boundary only.  No attempt has been made to include or exclude inholdings within the designated boundary.  For some
parks they are shown; others they are not shown.</complete>
    <lineage>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>National Park Service, Water Resources Division.</origin>
            <pubdate>various</pubdate>
            <title>National Park System Boundary Dataset</title>
            <geoform>map</geoform>
            <othercit>Information for this element varies for each  park included  in  the dataset.  See the boundary-specific WordPerfect file: MAPSTATS.DOC.</othercit>
          </citeinfo>
        </srccite>
        <srcscale>varies</srcscale>
        <typesrc>Unknown</typesrc>
        <srctime>
          <timeinfo>
            <sngdate>
              <caldate>Unknown</caldate>
            </sngdate>
          </timeinfo>
          <srccurr>Unknown</srccurr>
        </srctime>
        <srccitea>NPSWRDPARKBDYSVer.2</srccitea>
        <srccontr>National park unit designated boundaries</srccontr>
      </srcinfo>
      <procstep>
        <procdesc>This national park boundaries dataset was compiled by combining park boundaries from a  variety  of sources: extant digital park-based GIS  databases; analog  U.S. Geological Survey 7.5' 1:24,000 quadrangles;  analog NPS  Park  Land Status Maps; legal descriptions; etc.).   Digital boundaries  from  existing park GIS databases were  converted  to ATLAS*GIS format and thinned as necessary to reduce the number of points  describing the boundary to a maximum  of  4,096.   Analog boundaries   from  the  U.S.  Geological  Survey  7.5'   1:24,000 quadrangles and from NPS Park Land Status Maps were digitized  in ATLAS*GIS and directly incorporated into the master dataset.</procdesc>
        <srcused>NPSWRDPARKBDYSVer.2</srcused>
        <procdate>Ranges from 1992 to 1999</procdate>
      </procstep>
      <procstep>
        <procdesc>The boundary for Fort Larned NHS was selected and exported into shapefile format.</procdesc>
        <procdate>Unknown</procdate>
      </procstep>
      <procstep>
        <procdesc>Metadata imported.</procdesc>
        <srcused>c:\Temp\xml51.tmp</srcused>
        <procdate>Unknown</procdate>
      </procstep>
    </lineage>
  </dataqual>
  <spdoinfo>
    <direct>Vector</direct>
    <ptvctinf>
      <sdtsterm>
        <sdtstype>G-polygon</sdtstype>
        <ptvctcnt>2</ptvctcnt>
      </sdtsterm>
    </ptvctinf>
  </spdoinfo>
  <spref>
    <horizsys>
      <planar>
        <gridsys>
          <gridsysn>Universal Transverse Mercator</gridsysn>
          <utm>
            <utmzone>14</utmzone>
            <transmer>
              <sfctrmer>0.999600</sfctrmer>
              <longcm>-99.000000</longcm>
              <latprjo>0.000000</latprjo>
              <feast>500000.000000</feast>
              <fnorth>0.000000</fnorth>
            </transmer>
          </utm>
        </gridsys>
        <planci>
          <plance>coordinate pair</plance>
          <coordrep>
            <absres>0.000004</absres>
            <ordres>0.000004</ordres>
          </coordrep>
          <plandu>meters</plandu>
        </planci>
      </planar>
      <geodetic>
        <horizdn>North American Datum of 1983</horizdn>
        <ellips>Geodetic Reference System 80</ellips>
        <semiaxis>6378137.000000</semiaxis>
        <denflat>298.257222</denflat>
      </geodetic>
    </horizsys>
  </spref>
  <eainfo>
    <detailed>
      <enttyp>
        <enttypl>fols_bndry</enttypl>
        <enttypd>Shapefile Attribute Table</enttypd>
        <enttypds>National Park Service</enttypds>
      </enttyp>
      <attr>
        <attrlabl>FID</attrlabl>
        <attrdef>Internal feature number.</attrdef>
        <attrdefs>ESRI</attrdefs>
        <attrdomv>
          <udom>Sequential unique whole numbers that are automatically generated.</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>Shape</attrlabl>
        <attrdef>Feature geometry.</attrdef>
        <attrdefs>ESRI</attrdefs>
        <attrdomv>
          <udom>Coordinates defining the features.</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>AREA</attrlabl>
        <attrdef>Area of the polygon in square meters</attrdef>
        <attrdefs>NPS</attrdefs>
        <attrdomv>
          <rdom>
            <rdommin>180952.09</rdommin>
            <rdommax>2670254</rdommax>
            <attrunit>unknown</attrunit>
          </rdom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>PERIMETER</attrlabl>
        <attrdef>software computed value</attrdef>
        <attrdefs>NPS</attrdefs>
        <attrdomv>
          <rdom>
            <rdommin>1797.278</rdommin>
            <rdommax>7959.652</rdommax>
            <attrunit>unknown</attrunit>
          </rdom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>PARKPOLC_</attrlabl>
        <attrdef>User-defined feature number.</attrdef>
        <attrdefs>NPS</attrdefs>
        <attrdomv>
          <udom>Unique whole numbers.</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>PARKPOLC_I</attrlabl>
        <attrdef>User-defined feature number.</attrdef>
        <attrdefs>NPS</attrdefs>
        <attrdomv>
          <udom>Unique whole numbers.</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>ID</attrlabl>
        <attrdef>NPS Park Code</attrdef>
        <attrdefs>NPS</attrdefs>
        <attrdomv>
          <udom>Park acronym name.</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>NAME</attrlabl>
        <attrdef>Name of the National Park.</attrdef>
        <attrdefs>NPS</attrdefs>
        <attrdomv>
          <udom>Park name.</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>NAME2</attrlabl>
        <attrdef>Data source used for original product generation</attrdef>
        <attrdefs>NPS</attrdefs>
        <attrdomv>
          <udom>Information about the source, scale, and date  of the  boundary.</udom>
        </attrdomv>
      </attr>
    </detailed>
    <overview>
      <eaover>Three basic attributes are  assigned to each park boundary: (1) a unique four  character code;  (2) a full park name; and (3) boundary source information.  The  four character code is generally a combination of the  first two letters of the first two words in a park's name (or the first four  letters  if  the park has a one word name).   For  example, Yosemite National Park is YOSE while Rocky Mountain National Park is  ROMO.  The park's full name is the actual given name  of  the
park.   The boundary source information provides the date, scale, and originator of the particular park boundary.</eaover>
      <eadetcit>Unknown.</eadetcit>
    </overview>
  </eainfo>
  <distinfo>
    <distrib>
      <cntinfo>
        <cntorgp>
          <cntorg>USGS/CSS/Core Science Analytics and Synthesis</cntorg>
          <cntper>USGS-NPS Vegetation Characterization Program Coordinator</cntper>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing and physical address</addrtype>
          <address>Denver Federal Center, Building 810, MS 302</address>
          <city>Denver</city>
          <state>Colorado</state>
          <postal>80225</postal>
        </cntaddr>
        <cntvoice>(303) 202-4220</cntvoice>
        <cntfax>303-202-4219</cntfax>
        <cntemail>gs-b-npsveg@usgs.gov</cntemail>
      </cntinfo>
    </distrib>
    <resdesc>Downloadable Data</resdesc>
    <distliab>The U.S. Geological Survey and the National Park Service shall not be held liable for improper or incorrect use of the data described and/or contained herein.  These data and related graphics (if available) 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 not better than the original sources from which they were derived.  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.  Any related graphics (if available) are intended to aid the data user in acquiring relevant data; it is not approriate to use the related graphics as data.

The U.S. Geological Survey and 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 U.S. Geological Survey and National Park Service servers 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 U.S. Geological Survey, no warranty expressed or implied is made regarding the utility of the data on another system or for general or scientific purposes, nor shall the act of distribution constitute any such warranty. This disclaimer applies both to individual use of the data and aggregate use with other data. It is also strongly recommended that careful attention be paid to the contents of the metadata file associated with these data. Mention of trade names or commercial products in this metadata report does not constitute endorsement or recommendation for use by the U. S. Department of the Interior, U. S. Geological Survey and National Park Service.</distliab>
    <stdorder>
      <digform>
        <digtinfo>
          <formname>HTML</formname>
        </digtinfo>
        <digtopt>
          <onlinopt>
            <computer>
              <networka>
                <networkr>http://www.usgs.gov/core_science_systems/csas/vip/parks/fols.html</networkr>
              </networka>
            </computer>
            <accinstr>Internet Access</accinstr>
          </onlinopt>
        </digtopt>
      </digform>
      <fees>None</fees>
    </stdorder>
    <stdorder>
      <digform>
        <digtinfo>
          <formname>ARC/INFO</formname>
          <transize>0.134</transize>
        </digtinfo>
        <digtopt>
          <onlinopt>
            <computer>
              <networka>
                <networkr>National Park Service GIS Web Site; http://www.nps.gov/gis</networkr>
              </networka>
            </computer>
            <accinstr>Internet Access</accinstr>
          </onlinopt>
        </digtopt>
      </digform>
      <fees>None</fees>
    </stdorder>
  </distinfo>
  <metainfo>
    <metd>20080312</metd>
    <metrd>20100524</metrd>
    <metc>
      <cntinfo>
        <cntorgp>
          <cntorg>USGS/CSS/Core Science Analytics and Synthesis</cntorg>
          <cntper>USGS-NPS Vegetation Characterization Program Coordinator</cntper>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing and physical address</addrtype>
          <address>Denver Federal Center, Building 810, MS 302</address>
          <city>Denver</city>
          <state>Colorado</state>
          <postal>80225</postal>
        </cntaddr>
        <cntvoice>(303) 202-4220</cntvoice>
        <cntfax>303-202-4219</cntfax>
        <cntemail>gs-b-npsveg@usgs.gov</cntemail>
      </cntinfo>
    </metc>
    <metstdn>FGDC Biological Data Profile of the Content Standard for Digital Geospatial Metadata</metstdn>
    <metstdv>FGDC-STD-001.1-1999</metstdv>
    <metextns>
      <onlink>http://www.usgs.gov/core_science_systems/csas/metadata/index.html</onlink>
    </metextns>
  </metainfo>
</metadata>

