<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE metadata SYSTEM "http://thor-f5.er.usgs.gov/ngtoc/metadata/fgdc-std-001-1998.dtd">
<metadata>
 <idinfo>
 <!-- Identification Information - basic information about the data set. Type: compound. -->
  <citation>
   <!-- Citation - information to be used to reference the data set. Type: compound. -->
   <citeinfo>
    <!-- Citation Information - the recommended reference to be used for the data set. -->
    <origin>The Atlantic Group, LLC</origin>
        <!-- Originator - the name of an organization or individual that developed the data set. Type: text. Domain: "Unknown" free text. -->
        <pubdate>Unknown</pubdate>
    <!-- Publication Date - the date when the data set is published or otherwise made available for release. Type: date. Domain: "Unknown" "Unpublished material" free date. -->
    <title>2018 Kansas QL2 LiDAR - Digital Elevation Models (DEMs)</title>
    <!-- Title - the name by which the data set is known. Type: text. Domain: free text. -->
    <geoform>Raster</geoform>
    <!-- Geospatial Data Presentation Form. Type: text. Domain: "raster digital data" free text. -->
   </citeinfo>
  </citation>
  <descript>
   <!-- Description - a characterization of the data set, including its intended use and limitations. Type: compound. -->
   <abstract>Bare Earth DEM ERDAS .IMG format, Hydroflattened
   The State of Kansas Contract 0000000000000000000039891 required Leaf-off 2018 QL 2 LiDAR surveys to be collected over 54,663 square miles covering part or all of 86 counties in Kansas in support of the Kansas Department of Agriculture and Kansas Data Access and Support Center. Aerial LiDAR data for this task order was planned, acquired, processed and produced at an aggregate nominal pulse spacing (ANPS) of 0.71 meters and in compliance with USGS National Geospatial Program LiDAR Base Specification version 1.2.  Project Block 7A encompasses part or all of 7 counties in Southern Kansas and covers 1,940.2 square miles.</abstract>
   <!-- Abstract - a brief narrative descriptive summary of the data set. Type: text. Domain: free text. -->
   <purpose>The State of Kansas, on behalf of the Kansas Department of Agriculture and Kansas Data Access and Support Center, has contracted with Atlantic for professional services related to the development of Light Detection and Ranging (LiDAR). Additional partners include the USDA Natural Resource Conservation Service, the U.S. Geological Survey, the Kansas GIS Policy Board, the Kansas Department of Transportation and the Kansas Water Office. These LiDAR elevation data will be used for conservation planning, design, research, floodplain mapping, wetlands identification, dam safety assessments, hydrologic modeling, and subsidence monitoring.</purpose>
   <!-- Purpose - a summary of the intentions with which the data set was developed. Type: text. Domain: free text. -->
   <supplinf>
    	Raster File Type = ERDAS .IMG format
    	Bit Depth/Pixel Type = 32 bit floating point
    	Raster Cell Size = 1.0 meter
    	Interpolation or Resampling Technique = Bi-linear Interpolation
    	Required Vertical Accuracy = "24.5 cm nva" for 1.2 spec
  	
    <!-- Supplemental Information - other descriptive information about the data set. Type: text. Domain: free text. 
    Raster File Type = "IMG" "GRID" "TIFF"
    Bit Depth/Pixel Type = "32-bit float" "64 bit"
    Raster Cell Size. (Express the number as "0.5", "1.0", "2.0", "2.5", etc.) = "Meters" "United States Survey Feet" "International Feet" 
    Interpolation or Resampling Technique = "Triangulated Irregular Network (TIN)" "Inverse Distance Weighting (IDW)" "Radial Basis Functions" "Kriging" "Nearest Neighbor" "Bi-linear Interpolation" "Cubic Convolution" "Surface Fitting" "Adaptive" "Proprietary" "Unknown"
    Required Vertical Accuracy = (Depends on which Lidar Base Spec the project is adhering to. Example: "24.5 cm fva" for 1.0 spec, "24.5 cm nva" for 1.2 spec) -->
   </supplinf>
  </descript>
  <timeperd>
   <!-- Time Period of Content. Type: compound. -->
   <timeinfo>
    <!-- Time Period Information - information about the date and time of an event. Type: compound. -->
    <rngdates>
     <!-- Range of Dates/Times. Type: compound. -->
     <begdate>20180211</begdate>
     <!-- Beginning Date - the first year (and optionally month, or month and day) of the collection. Type: date. Domain: "Unknown" free date. -->
     <enddate>20180429</enddate>
     <!-- Ending Date - the last year (and optionally month, or month and day) for the collection. Type: date. Domain: "Unknown" free date. -->
    </rngdates>
   </timeinfo>
   <current>ground condition</current>
   <!-- Currentness Reference. Type: text. Domain: "ground condition"  free text. -->
  </timeperd>
   <status>
      <!-- Status - the state of the maintenance information for the data set. Type: compound. -->
      <progress>Complete</progress>
      <!-- Progress - the state of the data set. Type: text. Domain: "Complete" "In Work" "Planned" free text. -->
      <update>None Planned</update>
   <!-- Maintenance and Update Frequency - the frequency with which changes and additions are made to the data set after the initial data set is completed. Type: text. Domain: "Unknown" "As needed" "None planned" free text. -->
  </status>
  <spdom>
   <!-- Spatial Domain - the geographic areal domain of the data set. Type: compound. -->
   <bounding>
    <!-- Bounding Coordinates - the limits of coverage of a data set expressed by latitude and longitude values in the order western-most, eastern-most, northern-most, and southern-most. Type: compound. -->
    <westbc>-97.699172</westbc>
    <!-- West Bounding Coordinate - western-most coordinate of the limit of coverage expressed in longitude. Type: real. Domain: -180.0 <= West Bounding Coordinate < 180.0 -->
    <eastbc>-97.642612</eastbc>
    <!-- East Bounding Coordinate - eastern-most coordinate of the limit of coverage expressed in longitude. Type: real. Domain: -180.0 <= East Bounding Coordinate <= 180.0 -->
    <northbc>37.489761</northbc>
    <!-- North Bounding Coordinate - northern-most coordinate of the limit of coverage expressed in latitude. Type: real. Domain: -90.0 <= North Bounding Coordinate <= 90.0 -->
    <southbc>37.488214</southbc>
    <!-- South Bounding Coordinate - southern-most coordinate of the limit of coverage expressed in latitude. Type: real. Domain: -90.0 <= South Bounding Coordinate <= 90.0 -->
   </bounding>
  
  </spdom>
   <keywords>
      <!-- Keywords - words or phrases summarizing an aspect of the data set. Type: compound. -->
      <theme>
        <!-- Theme - subjects covered by the data set. Type: compound. -->
         <themekt>None</themekt>
    <!-- Theme Keyword Thesaurus. Type: text. Domain: "None" free text. -->
    <themekey>Elevation</themekey>
		<themekey>LiDAR</themekey>
		<themekey>Relief</themekey>
		<themekey>Digital Terrain Model</themekey>
		<themekey>Intensity Imagery</themekey>
		<themekey>LAS</themekey>
		<themekey>Breakline</themekey>
        <!-- Theme Keyword - common-use word or phrase used to describe the subject of the data set. Type: text. Domain: free text. -->
      </theme>
      <place>
        <!-- Place - geographic locations characterized by the data set. Type: compound. -->
        <placekt>None</placekt>
        <!-- Place Keyword Thesaurus. Type: text. Domain: "None" free text. -->
        <placekey>Kansas</placekey>

        <!-- Place Keyword - the geographic name of a location(s) covered by a data set. Type: text Domain: free text. -->
      </place>
    </keywords>
    <accconst>No restrictions apply to this data the data represented is the result of data collection and processing per contract specifications and indicates the general existing conditions at the time of the data collection. As such, it is only valid for its intended use, content, time, and accuracy specifications. The user is responsible for the results of any application of the data for other than its intended purpose.</accconst>
    <!-- Access Constraints - restrictions and legal prerequisites for accessing the data set. Type: text. Domain: "None" free text. -->
    <useconst>None. However, users should be aware that temporal changes may have occurred since this dataset was collected and that some parts of these data may no longer represent actual surface conditions. Users should not use these data for critical applications without a full awareness of the limitations of the data. Acknowledgment of owner would be appreciated for products derived from these data.The data represented is the result of data collection and processing per contract specifications and indicates the general existing conditions at the time of the data collection. As such, it is only valid for its intended use, content, time, and accuracy specifications. The user is responsible for the results of any application of the data for other than its intended purpose.</useconst>
    <!-- Use Constraints - restrictions and legal prerequisites for using the data set after access is granted. Type: text. Domain: "None" free text. -->
	
  </idinfo>
  <dataqual>
    <!-- Data Quality Information. Type: compound. -->
    <logic>All lidar data and lidar derived data covers the entire  area of interest. All lidar point cloud tiles show no edge artifacts or mismatches from tile to tile. Void areas (i.e. areas outside the project boundary but within the tiling scheme) are coded using a unique NODATA value. This value is identified in the appropriate location within the file header. Data cover the entire area specified for this project.</logic>
    <!-- Logical Consistency Report - an explanation of the fidelity of relationships in the data set and tests used. Type: text. Domain: free text. -->
    <complete>Area of interest covers project area.  A visual qualitative assessment was performed to ensure data completeness. No void areas or missing data exist. The raw point cloud is of good quality and data passes NVA specifications. Void areas (i.e., areas outside the project boundary but within the tiling scheme) are coded using a unique NODATA value. This value is identified in the appropriate location within the file header.</complete>
    <!-- Completeness Report - information about omissions, selection criteria, generalization, definitions used, and other rules used to derive the data set. Type: text. Domain: free text-->
<posacc>
      <!-- Positional Accuracy - an assessment of the accuracy of the positions of spatial objects. Type: compound. -->
      <vertacc>
        <!-- Vertical Positional Accuracy - an estimate of accuracy of the vertical positions in the data set. This set of tags is suggested for projects that include both classified and unclassified las files and required for projects that only include classified las files. Type: compound. -->
        <vertaccr>This data set was produced to meet ASPRS Positional Accuracy Standard for Digital Geospatial Data (2014) for a 10-cm RMSEz Vertical Accuracy Class.</vertaccr>
        <!-- Vertical Positional Accuracy Report - an explanation of the accuracy of the vertical coordinate measurements and a description of the tests used. Use statement, "This data set was produced to meet ASPRS Positional Accuracy Standard for Digital Geospatial Data (2014) for a 10-cm RMSEz Vertical Accuracy Class." Type: text. Domain: free text. -->
      </vertacc> 
    </posacc>
    <lineage>
      <!-- Lineage - information about the events, parameters, and source data which constructed the data set, and information about the responsible parties. Type: compound. -->
     
      <procstep>
        <!-- Process Step - information about a single processing step. Please provide information for each step of the data acquisition, calibration, processing, and analysis. Type: compound. -->
        <procdesc>Aircraft and Sensor Information and Flight Plan Execution
		Atlantic operated a Cessna (N732JE) outfitted with a Leica ALS70-HP LiDAR system during the collection of the project area. Atlantic acquired 79 passes of the AOI as a series of perpendicular and/or adjacent flight-lines executed in 7 flight missions conducted between February 11, 2018 and April 29, 2018.  Onboard differential Global Navigation Satellite System (GNSS) unit(s) recorded sample aircraft positions at 2 hertz (Hz) or more frequency. LiDAR data was only acquired when a minimum of six (6) satellites were in view.  
		</procdesc>
        <!-- Process Description - an explanation of the the processing step and parameters used. Include Flight, Imagery development, Analysis. Type: text. Domain: free text-->      
        <procdate>20180429</procdate>
        <!-- Process Date - the date when the processing step was completed. The field MUST be formatted YYYYMMDD. Type: text. Domain: "Unknown" "Not complete" free date. -->

      </procstep>
      <procstep>
        <!-- Process Step - information about a single processing step. Type: compound. -->
        <procdesc>Ground Control Survey
		A total of 72 ground survey points were collected in support of this project, including 19 LiDAR Control Points (LCP), 32 Non-vegetated Vertical Accuracy (NVA) and 21 Vegetated Vertical Accuracy (VVA). 

		Point cloud data accuracy was tested against a Triangulated Irregular Network (TIN) constructed from LiDAR points in clear and open areas.  A clear and open area can be characterized with respect to topographic and ground cover variation such that a minimum of five (5) times the Nominal Pulse Spacing (NPS) exists with less than 1/3 of the RMSEZ deviation from a low-slope plane. Slopes that exceed ten (10) percent were avoided.
 
		Each land cover type representing ten (10) percent or more of the total project area were tested and reported with a VVA. In land cover categories other than dense urban areas, the tested points did not have obstructions forty-five (45) degrees above the horizon to ensure a satisfactory TIN surface. The VVA value is provided as a target. It is understood that in areas of dense vegetation, swamps, or extremely difficult terrain, this value may be exceeded. 

		The NVA value is a requirement that must be met, regardless of any allowed “busts” in the VVA(s) for individual land cover types within the project. Checkpoints for each assessment (NVA and VVA) are required to be well-distributed throughout the land cover type, for the entire project area.  

		</procdesc>
        <!-- Process Description - an explanation of the the processing step and parameters used. Include Flight, Imagery development, Analysis. Type: text. Domain: free text-->
        <procdate>20190429</procdate>
        <!-- Process Date - the date when the processing step was completed. The field MUST be formatted YYYYMMDD. Type: text. Domain: "Unknown" "Not complete" free date. -->
      </procstep>
	  
	   <procstep>
        <!-- Process Step - information about a single processing step. Type: compound. -->
        <procdesc>LiDAR Point Cloud Generation
		Atlantic used Leica software products to download the IPAS ABGNSS/IMU data and raw laser scan files from the airborne system. Waypoint Inertial Explorer is used to extract the raw IPAS ABGNSS/IMU data, which is further processed in combination with controlled base stations to provide the final Smoothed Best Estimate Trajectory (SBET) for each mission. The SBETs are combined with the raw laser scan files to export the LiDAR ASCII Standard (*.las) formatted swath point clouds.
		</procdesc>
        <!-- Process Description - an explanation of the the processing step and parameters used. Include Flight, Imagery development, Analysis. Type: text. Domain: free text-->
        <procdate>20191121</procdate>
        <!-- Process Date - the date when the processing step was completed. The field MUST be formatted YYYYMMDD Type: text. Domain: "Unknown" "Not complete" free date. -->
      </procstep>
	  
	   <procstep>
        <!-- Process Step - information about a single processing step. Type: compound. -->
        <procdesc>LiDAR Calibration
		Using a combination of GeoCue, TerraScan and TerraMatch; overlapping swath point clouds are corrected for any orientation or linear deviations to obtain the best fit swath-to-swath calibration. Relative calibration was evaluated using advanced plane-matching analysis and parameter corrections derived. This process was repeated interactively until residual errors between overlapping swaths, across all project missions, was reduced to ≤2cm. A final analysis of the calibrated lidar is preformed using a TerraMatch tie line report for an overall statistical model of the project area.  Individual control point assessments for this project can be found in Section VI of this report. 
		Upon completion of the data calibration, a complete set of elevation difference intensity rasters (dZ Orthos) are produced. A user-defined color ramp is applied depicting the offsets between overlapping swaths based on project specifications. The dZ orthos provide an opportunity to review the data calibration in a qualitative manner. Atlantic assigns green to all offset values that fall below the required RMSDz requirement of the project.  A yellow color is assigned for offsets that fall between the RMSDz value and 1.5x of that value. Finally, red values are assigned to all values that fall beyond 1.5x of the RMSDz requirements of the project.
		</procdesc>
        <!-- Process Description - an explanation of the the processing step and parameters used. Include Flight, Imagery development, Analysis. Type: text. Domain: free text-->
        <procdate>20191121</procdate>
        <!-- Process Date - the date when the processing step was completed. The field MUST be formatted YYYYMMDD Type: text. Domain: "Unknown" "Not complete" free date. -->
      </procstep>

	   <procstep>
        <!-- Process Step - information about a single processing step. Type: compound. -->
        <procdesc>LiDAR Classification
			  Multiple automated filtering routines are applied to the calibrated LiDAR point cloud identifying and extracting bare-earth and above ground features. GeoCue, TerraScan, and TerraModeler software was used for the initial batch processing, visual inspection and any manual editing of the LiDAR point clouds. Atlantic utilized collected breakline data to preform classification for classes 9 (Water) and 10 (Ignored Ground). 
		Code	Description
		1	Unclassified
		2	Ground
		7	Low point (noise)
		9	Water
		10	Ignored ground (breakline proximity)
		`17	Bridge
		18	High point (noise)
		</procdesc>
        <!-- Process Description - an explanation of the the processing step and parameters used. Include Flight, Imagery development, Analysis. Type: text. Domain: free text-->
        <procdate>20191121</procdate>
        <!-- Process Date - the date when the processing step was completed. The field MUST be formatted YYYYMMDD Type: text. Domain: "Unknown" "Not complete" free date. -->
      </procstep>
	  
	    <procstep>
        <!-- Process Step - information about a single processing step. Type: compound. -->
        <procdesc>LiDAR Intensity Imagery
		LiDAR intensity imagery was created from the final calibrated and classified lidar point cloud. Intensity images were produced from all classified points and posted to a 0.5-meter cell size. Intensity images were cut to match the tile index and its corresponding tile names and delivered in .img format.
		</procdesc>
        <!-- Process Description - an explanation of the the processing step and parameters used. Include Flight, Imagery development, Analysis. Type: text. Domain: free text-->
        <procdate>20191121</procdate>
        <!-- Process Date - the date when the processing step was completed. The field MUST be formatted YYYYMMDD Type: text. Domain: "Unknown" "Not complete" free date. -->
      </procstep>
	     
	   <procstep>
        <!-- Process Step - information about a single processing step. Type: compound. -->
        <procdesc>Hydro-line Collection/Conflation
		Hydro breaklines were compiled using LiDAR intensity data and surface terrain models of the entire project area. After the collection, all delineated hydro features were validated for monotonicity and vertical variance.  This procedure ensures that no points were floating above ground. Hydro-lines were then encoded into the LiDAR surface and used to hydro-enforce/flatten all significant water bodies. These final hydro-lines were then used in the production of bare Earth digital models to hydro flatten significant water bodies.  This product was delivered as an ESRI geodatabase for the entire project area.
		</procdesc>
        <!-- Process Description - an explanation of the the processing step and parameters used. Include Flight, Imagery development, Analysis. Type: text. Domain: free text-->
        <procdate>20191121</procdate>
        <!-- Process Date - the date when the processing step was completed. The field MUST be formatted YYYYMMDD Type: text. Domain: "Unknown" "Not complete" free date. -->
      </procstep>
	  
	  <procstep>
        <!-- Process Step - information about a single processing step. Type: compound. -->
        <procdesc>Bare-Earth Surface – Digital Elevation Model (DEM)
		Bare earth Digital Elevation Models (DEMs) were derived using the hydro-lines and bare earth (ground) LiDAR points.  All DEMs were created with a grid spacing of 1 meter. DEMs for this project were cut to match the tile index and its corresponding tile names and delivered in 32-bit floating point .img format.
		</procdesc>
        <!-- Process Description - an explanation of the the processing step and parameters used. Include Flight, Imagery development, Analysis. Type: text. Domain: free text-->
        <procdate>20191121</procdate>
        <!-- Process Date - the date when the processing step was completed. The field MUST be formatted YYYYMMDD Type: text. Domain: "Unknown" "Not complete" free date. -->
      </procstep>

    </lineage>
  </dataqual>
  
  <spdoinfo>
  <!-- Spatial Data Organization Information. Type: compound. -->
  <direct>raster</direct>
  <!-- Direct Spatial Reference Method - the system of objects used to represent space in the data set. Type: text. Domain:  "Raster" -->
  <rastinfo>
      <rasttype>Pixel</rasttype>
      <rowcount>101</rowcount>
      <colcount>5000</colcount>
    </rastinfo>
  </spdoinfo>
 <spref>
    <!-- Spatial Reference Information. Type: compound. -->
        <horizsys>
      <planar>
        <mapproj>
          <mapprojn>NAD 1983 HARN UTM Zone 14N</mapprojn>
          <transmer>
            <sfctrmer>0.9996</sfctrmer>
            <longcm>-99.0</longcm>
            <latprjo>0.0</latprjo>
            <feast>500000.0</feast>
            <fnorth>0.0</fnorth>
          </transmer>
        </mapproj>
        <planci>
          <plance>coordinate pair</plance>
          <coordrep>
            <absres>0.0001</absres>
            <ordres>0.0001</ordres>
          </coordrep>
          <plandu>meter</plandu>
        </planci>
      </planar>
      <geodetic>
        <horizdn>D North American 1983 HARN</horizdn>
        <ellips>GRS 1980</ellips>
        <semiaxis>6378137.0</semiaxis>
        <denflat>298.257222101</denflat>
      </geodetic>
    </horizsys>
   <vertdef>
      <!-- Vertical Coordinate System Definition - the reference frame or system from which vertical distances (altitudes or depths) are measured. Type: compound. -->
      <altsys>
        <!-- Altitude System Definition - the reference frame or system from which altitudes (elevations) are measured. Type: compound. -->
        <altdatum>NAVD88</altdatum>
        <!-- Altitude Datum Name. Type: text. Domain: "National Geodetic Vertical Datum of 1929" "North American Vertical Datum of 1988" free text-->
        <altres>1200</altres>
        <!-- Altitude Resolution - the minimum distance possible between two adjacent altitude values, expressed in Altitude Distance Units of measure. Type: real. Domain: Altitude Resolution > 0.0 -->
        <altunits>meter</altunits>
        <!-- Altitude Distance Units - units in which altitudes (elevations) are recorded.  Type: text.  Domain: "meters" "international feet" "US survey feet" free text-->
        <altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
        <!-- Altitude Encoding Method - the means used to encode the altitudes. Type: text. Domain: "Explicit elevation coordinate included with horizontal coordinates" -->
      </altsys>
    </vertdef>
  </spref>


 <metainfo>
    <!-- Metadata Reference Information - information on the currentness of the metadata information, and the responsible party. Type: compound. -->
    <metd>20191219</metd>
    <!-- Metadata Date - the date that the metadata were created or last updated. Type: date. Domain: free date. -->
    <metrd>20191219</metrd>
    <!-- Metadata Review Date - if applicable, the date of the latest review of the metadata entry. Domain: free data; Metadata Review Date should be later than Metadata Date -->
    <metc>
      <!-- Metadata Contact - the party responsible for the metadata information. Type: compound. -->
      <cntinfo>
        <!-- Contact Information - Identity of, and means to communicate with, person(s) and organization(s) associated with the data set.Type: compound. -->
            <cntorgp>
			 <!-- The organization, and the member of the organization if desired, associated with the data set. THIS POINT OF CONTACT SHALL BE CONTACT INFORMATION FOR THE PRIMARY CONTRACTOR. Please DO NOT include contact information for the USGS. If desired, the primary contractor may add contact information to data sections where the data was obtained by a sub-contractor, however this is not required. More details can be found in the USGS LBS 1.3 under Appendix 4. Type: compound. -->
              <cntorg>Atlantic</cntorg>
              <cntper>Benjamin Litter</cntper>
            </cntorgp>
            <cntpos>Project Manager</cntpos>
            <cntaddr>
              <addrtype>mailing and physical</addrtype>
              <address>2223 Drake Ave. SW Suite 200</address>
              <city>Huntsville</city>
              <state>AL</state>
              <postal>35805</postal>
              <country>USA</country>
            </cntaddr>
            <cntvoice>256.971.9991</cntvoice>
            <cntfax>256.971.1154</cntfax>
            <cntemail>Benjamin.Litter@atlantic.tech</cntemail>
          </cntinfo>
   </metc>
    <metstdn>FGDC Content Standard for Digital Geospatial Metadata</metstdn>
    <!-- Metadata Standard Name - the name of the metadata standard used to document the data set. Type: text. Domain: "FGDC Content Standard for Digital Geospatial Metadata" free text -->
    <metstdv>FGDC-STD-001-1998</metstdv>
    <!-- Metadata Standard Version - identification of the version of the metadata standard used to document the data set. Type: text. Domain: free text. -->
    <metac>None.</metac>
    <!-- Metadata Access Constraints - restrictions and legal prerequisites for accessing the metadata. These include any access constraints applied to assure the protection of privacy or intellectual property, and any special restrictions or limitations on obtaining the metadata. Domain: free text -->
    <metuc>None.</metuc>
    <!-- Metadata Use Constraints - restrictions and legal prerequisites for using the metadata after access is granted. These include any metadata use constraints applied to assure the protection of privacy or intellectual property, and any special restrictions or limitations on using the metadata. Domain: free text. -->
    <metsi>
    	<!-- Metadata Security Information - handling restrictions imposed on the metadata because of national security, privacy, or other concerns. Type: compound. -->
    	<metscs>None.</metscs>
    	<!-- Metadata Security Classification System - name of the classification system for the metadata. Domain: free text -->
    	<metsc>Unclassified.</metsc>
    	<!-- Metadata Security Classification - name of the handling restrictions on the metadata. Domain: "Top secret" "Secret" "Confidential" "Restricted" "Unclassified" "Sensitive" free text -->
    	<metshd>None.</metshd>
    	<!-- Metadata Security Handling Description - additional information about the restrictions on handling the metadata. Domain: free text. -->
    </metsi>
    <metextns>
    	<!-- Metadata Extensions - a reference to extended elements to the standard which may be defined by a metadata producer or a user community. Extended elements are elements outside the Standard, but needed by the metadata producer. If extended elements are created, they must follow the guidelines in Appendix D, Guidelines for Creating Extended Elements to the Content Standard for Digital Geospatial Metadata. Type: Compound -->
      <onlink>None.</onlink>
      <!-- Online Linkage - the name of an online computer resource that contains the metadata extension information for the data set. Entries should follow the Uniform Resource Locator convention of the Internet. Domain: free text. -->
      <metprof>None.</metprof>
      <!-- Profile Name - the name given to a document that describes the application of the Standard to a specific user community. Domain: free text. -->
    </metextns>
  </metainfo>
</metadata>