<?xml version="1.0" encoding="UTF-8"?>
<metadata>
  <idinfo>
    <citation>
      <citeinfo>
        <origin>Aero-Graphics</origin>
        <pubdate>20200226</pubdate>
        <title>Data Capture Terrain Submission for DAWSON COUNTY, MT</title>
	<edition>Version 2.3.3.2</edition>
        <geoform>FEMA-DCS-Terrain</geoform>
        <pubinfo>
          <pubplace>Washington, DC</pubplace>
          <publish>Federal Emergency Management Agency</publish>
        </pubinfo>
        <onlink>http://hazards.fema.gov</onlink>
        <lworkcit>
          <citeinfo>
            <origin>Federal Emergency Management Agency</origin>
            <pubdate>Unknown</pubdate>
            <title>FEMA CASE 19-08-0017S</title>
          </citeinfo>
        </lworkcit>
      </citeinfo>
    </citation>
    <descript>
      <abstract>Terrain data, as defined in FEMA's Guidelines and Standards for Flood Risk Analysis and Mapping, describe the digital topographic data that were used to create the elevation data representing the terrain environment of a watershed and/or floodplain. Terrain data requirements allow for flexibility in the types of information used to produce final terrain deliverables. Submission of the terrain data sources allows FEMA to account for the origins of the flood study elevation data. (Source: FEMA Guidelines and Standards for Flood Risk Analysis and Mapping.)</abstract>
      <purpose>Terrain data are used to represent the topography of a watershed and/or floodplain environment and to extract useful information for hydraulic and hydrologic models. (Source: FEMA Guidelines and Standards for Flood Risk Analysis and Mapping)</purpose>
    </descript>
    <timeperd>
      <timeinfo>
        <sngdate>
          <caldate>20200226</caldate>
        </sngdate>
      </timeinfo>
      <current>MIP Submission Date</current>
    </timeperd>
    <status>
      <progress>In work</progress>
      <update>Unknown</update>
    </status>
    <spdom>
      <bounding>
        <westbc>-105.124847</westbc>
        <eastbc>-104.320903</eastbc>
        <northbc>47.441002</northbc>
        <southbc>46.797146</southbc>
      </bounding>
    </spdom>
    <keywords>
      <theme>
        <themekt>ISO 19115 Topic Category</themekt>
        <themekey>elevation</themekey>
      </theme>
      <theme>
        <themekt>FEMA NFIP Topic Category</themekt>
        <themekey>Land Surface</themekey>
		<themekey>Relief</themekey>
        <themekey>Topography</themekey>
        <themekey>Digital Elevation Model</themekey>
        <themekey>Digital Surface Model</themekey>
        <themekey>Digital Terrain Model</themekey>		
        <themekey>Elevation Data</themekey>
        <themekey>Slope</themekey>
        <themekey>LIDAR</themekey>
        <themekey>Breaklines</themekey>
        <themekey>Contours</themekey>
        <themekey>DEM</themekey>
        <themekey>Flow Vectors</themekey>
        <themekey>Bare Earth</themekey>
      </theme>
      <place>
        <placekt>None</placekt>
        <placekey>REGION 08</placekey>
        <placekey>STATE MT</placekey>
        <placekey>COUNTY Treasure</placekey>
        <placekey>COUNTY-FIPS 30021</placekey>
        <placekey>COMMUNITY DAWSON COUNTY</placekey>
        <placekey>FEMA-CID 300140</placekey>
        <placekey>HYDROLOGIC UNIT 10100004</placekey>
      </place>
    </keywords>
    <accconst>None</accconst>
    <useconst>Acknowledgement of FEMA would be appreciated in products derived from these data.  These digital data are produced for the purposes of updating/creating a FIRM Database.</useconst>
    <ptcontac>
      <cntinfo>
        <cntorgp>
          <cntorg>Federal Emergency Management Agency</cntorg>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing</addrtype>
          <address>500 C Street, S.W.</address>
          <city>Washington</city>
          <state>District of Columbia</state>
          <postal>20472</postal>
          <country>USA</country>
        </cntaddr>
        <cntvoice>1-877-336-2627</cntvoice>
        <cntemail>miphelp@riskmapcds.com</cntemail>
      </cntinfo>
    </ptcontac>
    <native>Original data development environment may vary.  The classification and quality control (QC) of LiDAR data is carried out using  TerraScan software v. 8.003 by Terrasolid Limited of Helinski, Finland. 
The tiling and final LAS file creation was performed using LiDAR CuePac v5.0 from GeoCue Corporation of Madison, Alabama, USA. Finishing of the data is done using Esri's ArcGIS software.  The submitted geodatabase was created using ArcGIS version 10.0.</native>

  </idinfo>
  <dataqual>
    <attracc>
      <attraccr>1. Flight lines and data were reviewed to ensure complete coverage of the study area and positional accuracy of the laser points.
		2. Laser point return coordinates were computed using Waypoint Inertial Explorer based on independent data from the LiDAR system, IMU, and aircraft.
		3. The raw LiDAR file was assembled into flight lines per return with each point having an associated x, y, and z coordinate.
		4. Visual inspection of swath to swath laser point consistencies within the study area were used to perform manual refinements of system alignment.
		5. Custom algorithms were designed to evaluate points between adjacent flight lines. Automated system alignment was computed based upon randomly selected swath to swath accuracy measurements that consider elevation, slope, and intensities. Specifically, refinement in the combination of system pitch, roll and yaw offset parameters optimize internal consistency.
		6. Noise (e.g., pits and birds) was filtered using postprocessing software, based on known elevation ranges and included the removal of any cycle slips.
		7. Using TerraScan and Microstation, ground classifications utilized custom settings appropriate to the study area. 
		8. The corrected and filtered return points were compared to the RTK ground survey points collected to verify the vertical accuracy.

		The data are classified as follows:
		Class 1 = Unclassified.  This class includes vegetation, buildings, noise etc.
		Class 2 = Bare Earth
		Class 7 = Low Noise
		Class 9 = Water
		Class 17 = Bridge Decks
		Class 18 = High Noise
		Class 20 = Ignored Ground


		The LAS header information was verified to contain the following:
		Class (Integer)
		GPS Week Time (0.0001 seconds)
		Easting (0.01 intl. ft.)
		Northing (0.01 intl. ft.)
		Elevation (0.01 US Survey ft.)
		Echo Number (Integer 1 to 4)
		Echo (Integer 1 to 4)
		Intensity (8 bit integer)
		Flight Line (Integer)
		Scan Angle (Integer degree)</attraccr>
    </attracc>

    <logic>Checks were performed to ensure the data files can be opened, are georeferenced properly, and cover the geographic area completely. Additionally, field survey checkpoints area obtained to evaluate the accuracy of LiDAR products. As specified in the American Society for Photogrammetry and Remote Sensing (ASPRS) Positional Accuracy Standards for Digital Geospatial Data, checkpoints in non-vegetated areas are tested in a project area. A statistical analysis between the difference in elevations of the field survey checkpoints and LiDAR-derived, bare earth elevations at the same locations provides a quality assessment of the LiDAR data.</logic>
    <complete>The bare earth surface data is an estimation of the bare earth surface and does not include vegetative and built features.  Likewise, it contains estimates of water edges at the time of data collection, and may not reflect current conditions. The bare earth surface will contain voids where insufficient energy was reflected from the surface to generate a valid return from the terrain.  Voids in the bare earth surface tend to occur in heavily vegetated areas, water bodies, and beneath buildings, motor vehicles, bridges etc. Fresh or wet asphalt, wet sand and certain types of vegetation can also cause voids or anomalous elevations.  The data may have been further processed to remove points found to be within delineated water bodies. Low confidence areas are delineated and provided in a separate dataset.</complete>
    <posacc>
      <horizpa>
        <horizpar>The LiDAR data horizontal accuracy is in compliance with the National Standard for Spatial Data Accuracy (NSSDA) RMSE estimation of elevation data in support of 2ft. contour mapping products as it is referenced in the FEMA Guidelines and Standards for Flood Risk Analysis and Mapping.</horizpar>
      </horizpa>
      <vertacc>
        <vertaccr>Deliverables were tested by Aero-Graphics for both vertical and horizontal accuracy. All data is seamless from one tile to the next, no gaps or no data areas in the three project areas. The vertical unit of the data file is in decimal feet with 2-decimal point precision.</vertaccr>
        <qvertpa>
          <vertaccv>0.380</vertaccv>
          <vertacce>Final 1.96 RMSE in feet of non vegetated ground check points withheld from the calibration and post processing of the LiDAR point cloud within the Treasure County project site.</vertacce>
        </qvertpa>
      </vertacc>
    </posacc>
    <lineage>
<srcinfo> 
 <srccite> 
 <citeinfo> 
<origin>Aero-Graphics</origin> 
<pubdate>20200226</pubdate> 
<title>Raw Point Cloud Data</title> 
</citeinfo> 
</srccite> 
<typesrc>External Hard Drive</typesrc> 
 <srctime> 
 <timeinfo> 
 <sngdate> 
<caldate>20200226</caldate> 
</sngdate> 
</timeinfo> 
<srccurr>Publication Date</srccurr> 
</srctime> 
<srccitea>TOPO1</srccitea> 
<srccontr>The unedited LiDAR data were classified to facilitate the application of the appropriate feature extraction filters. A combination of proprietary filters is applied as appropriate for the production of bare earth digital terrain models (dtms). Interactive editing methods are applied to those areas where it is inappropriate or impossible to use the feature extraction filters, based upon the design criteria and/or limitations of the relevant filters. These same feature extraction filters are used to produce elevation height surfaces. The LiDAR mass points were delivered in American Society for Photogrammetry and Remote Sensing LAS 1.1 format. The LAS files do not include overlap. The data was classified as follows: Class 1 = Unclassified; Class 2 = Ground; Class 3 = Low Vegetation; Class 4 = Medium Vegetation; Class 5 = High Vegetation; Class 6 = Building; Class 7 = Low Point (noise) Class 9 = Water. The bare-earth files contain all ground (class 2) points.</srccontr> 
</srcinfo> 
<srcinfo> 
 <srccite> 
 <citeinfo> 
<origin>Aero-Graphics</origin> 
<pubdate>20200226</pubdate> 
<title>Classified Point Cloud Data</title> 
</citeinfo> 
</srccite> 
<typesrc>External Hard Drive</typesrc> 
 <srctime> 
 <timeinfo> 
 <sngdate> 
<caldate>20200226</caldate> 
</sngdate> 
</timeinfo> 
<srccurr>Publication Date</srccurr> 
</srctime> 
<srccitea>TOPO2</srccitea> 
<srccontr>The final processing and classification of LiDAR data to the required ASPRS LAS classes, per project specifications. This includes testing for Non-vegetated Vertical Accuracy (NVA).</srccontr> 
</srcinfo>
 <srcinfo> 
 <srccite> 
 <citeinfo> 
<origin>Aero-Graphics</origin> 
<pubdate>20200226</pubdate> 
<title>Bare Earth DEM</title> 
</citeinfo> 
</srccite> 
<typesrc>External Hard Drive</typesrc> 
 <srctime> 
 <timeinfo> 
 <sngdate> 
<caldate>20200226</caldate> 
</sngdate> 
</timeinfo> 
<srccurr>Publication Date</srccurr> 
</srctime> 
<srccitea>TOPO3</srccitea> 
<srccontr>An elevation model where bare-earth elevation values have regularly spaced intervals (x and y).</srccontr> 
</srcinfo> 
 <srcinfo> 
 <srccite> 
 <citeinfo> 
<origin>Aero-Graphics</origin> 
<pubdate>20200226</pubdate> 
<title>Contours</title> 
</citeinfo> 
</srccite> 
<typesrc>External Hard Drive</typesrc> 
 <srctime> 
 <timeinfo> 
 <sngdate> 
<caldate>20200226</caldate> 
</sngdate> 
</timeinfo> 
<srccurr>Publication Date</srccurr> 
</srctime> 
<srccitea>TOPO4</srccitea> 
<srccontr>Contour generation from LiDAR point data.</srccontr> 
</srcinfo> 
 <srcinfo> 
 <srccite> 
 <citeinfo> 
<origin>Aero-Graphics</origin> 
<pubdate>20200226</pubdate> 
<title>Breaklines</title> 
</citeinfo> 
</srccite> 
<typesrc>Digital</typesrc> 
 <srctime> 
 <timeinfo> 
 <sngdate> 
<caldate>20200226</caldate> 
</sngdate> 
</timeinfo> 
<srccurr>Publication date</srccurr> 
</srctime> 
<srccitea>TOPO5</srccitea> 
<srccontr>Water boundary polygons were developed using an algorithm which weights LiDAR-derived slopes, intensities, and return densities to detect the edge of water.</srccontr> 
</srcinfo> 
      <procstep>
        <procdesc>Terrain data used for flood risk analysis go through LiDAR preliminary processing and the unclassified point cloud data are tested as specified in the USGS National Geospatial Program Base LiDAR Specification Version 1.0.  Where the Mapping Activity Statement (MAS) requires bare earth post-processing of the floodplain area of interest (AOI), the elevation data are tested and comply with both the Fundamental Vertical Accuracy (FVA) and Consolidated Vertical Accuracy (CVA) requirements.  Where no bare earth post-processing is specified, only the FVA requirements apply for LiDAR preliminary processing.
</procdesc>
        <procdate>20200226</procdate>
      </procstep>
    </lineage>
  </dataqual>
 <spref>
		<horizsys>
			<planar>
				<gridsys>
					<gridsysn>State Plane Coordinate System 1983</gridsysn>
					<spcs>
						<spcszone>2500</spcszone>
						<lambertc>
							<stdparll>45.0</stdparll>
							<longcm>-109.5</longcm>
							<latprjo>44.25</latprjo>
							<feast>1968503.93700787</feast>
							<fnorth>0.0</fnorth>
						</lambertc>
					</spcs>
				</gridsys>
				<planci>
					<plance>coordinate pair</plance>
					<coordrep>
						<absres>0.01</absres>
						<ordres>0.01</ordres>
					</coordrep>
					<plandu>International feet</plandu>
				</planci>
			</planar>
			<geodetic>
				<horizdn>North American Datum of 1983 (2011)</horizdn>
				<ellips>Geodetic Reference System 80</ellips>
				<semiaxis>6378137.000000</semiaxis>
				<denflat>298.257222101</denflat>
			</geodetic>
		</horizsys>
		<vertdef>
			<altsys>
				<altdatum>North American Vertical Datum of 1988 Geoid 12B</altdatum>
				<altres>0.01</altres>
				<altunits>US feet</altunits>
				<altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
			</altsys>
		</vertdef>
	</spref>
  <eainfo>
    <detailed>
      <enttyp>
        <enttypl>S_Submittal_Info</enttypl>
        <enttypd>A spatial data set consisting of polygons depicting the extents of the studied area.</enttypd>
        <enttypds>FEMA FIRM Database Technical Reference (available at http://www.fema.gov/guidelines-and-standards-flood-risk-analysis-and-mapping and on the FEMA Risk MAP Knowledge Sharing Site).</enttypds>
      </enttyp>
    </detailed>
    <detailed>
      <enttyp>
        <enttypl>S_Topo_Confidence</enttypl>
        <enttypd>A spatial dataset consisting of polygons depicting areas of low confidence topographic data.</enttypd>
        <enttypds>FEMA FIRM Database Technical Reference (available at http://www.fema.gov/guidelines-and-standards-flood-risk-analysis-and-mapping and on the FEMA Risk MAP Knowledge Sharing Site).</enttypds>
      </enttyp>
    </detailed>
    <detailed>
      <enttyp>
        <enttypl>Bare Earth DEM</enttypl>
        <enttypd>An elevation model where bare-earth elevation values have regularly spaced intervals in latitude and longitude (x and y).</enttypd>
        <enttypds>FEMA Guidelines and Standards for Flood Risk Analysis and Mapping (available at http://www.fema.gov/guidelines-and-standards-flood-risk-analysis-and-mapping and on the FEMA Risk MAP Knowledge Sharing Site)</enttypds>
      </enttyp>
    </detailed>
    <detailed>
      <enttyp>
        <enttypl>Classified Point Cloud Data</enttypl>
        <enttypd>The final processing and classification of LiDAR data to the required ASPRS LAS classes, per project specifications. This includes testing for Consolidated Vertical Accuracy (CVA).</enttypd>
        <enttypds>FEMA Guidelines and Standards for Flood Risk Analysis and Mapping (available at http://www.fema.gov/guidelines-and-standards-flood-risk-analysis-and-mapping and on the FEMA Risk MAP Knowledge Sharing Site)</enttypds>
      </enttyp>
    </detailed>
    <detailed>
      <enttyp>
        <enttypl>Breakline</enttypl>
        <enttypd>A linear feature demarking a change in the smoothness or continuity of a surface such as abrupt elevation changes or a stream line.</enttypd>
        <enttypds>FEMA Guidelines and Standards for Flood Risk Analysis and Mapping (available at http://www.fema.gov/guidelines-and-standards-flood-risk-analysis-and-mapping and on the FEMA Risk MAP Knowledge Sharing Site)</enttypds>
      </enttyp>
    </detailed>
    <detailed>
      <enttyp>
        <enttypl>Tiling Index</enttypl>
        <enttypd>A spatial dataset that describes the tiling system used for multiple files of the same type.</enttypd>
        <enttypds>FEMA Guidelines and Standards for Flood Risk Analysis and Mapping (available at http://www.fema.gov/guidelines-and-standards-flood-risk-analysis-and-mapping and on the FEMA Risk MAP Knowledge Sharing Site)</enttypds>
      </enttyp>
    </detailed>
	<detailed>
	  <enttyp>
		<enttypl>Contours</enttypl>
		<enttypd>A line delineating equal interval elevations.</enttypd>
		<enttypds>FEMA Guidelines and Standards for Flood Risk Analysis and Mapping (available at http://www.fema.gov/guidelines-and-standards-flood-risk-analysis-and-mapping and on the FEMA Risk MAP Knowledge Sharing Site)</enttypds>
	  </enttyp>
	</detailed>
    <overview>
      <eaover>The Terrain data package is made up of several data themes containing primarily spatial information. These data supplement the elevation datasets by providing additional information to aid flood risk evaluation and flood hazard area delineations.</eaover>
      <eadetcit>FEMA's Guidelines and Standards for Flood Risk Analysis and Mapping contains a detailed description of the data themes and references to other relevant information.</eadetcit>
    </overview>
  </eainfo>
  <distinfo>
    <distrib>
      <cntinfo>
        <cntorgp>
          <cntorg>FEMA, Mapping Information Platform</cntorg>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing</addrtype>
          <address>500 C Street, S.W.</address>
          <city>Washington</city>
          <state>District of Columbia</state>
          <postal>20472</postal>
          <country>USA</country>
        </cntaddr>
        <cntvoice>1-877-336-2627</cntvoice>
        <cntemail>miphelp@riskmapcds.com</cntemail>
      </cntinfo>
    </distrib>
    <distliab>No warranty expressed or implied is made by FEMA regarding the utility of the data on any other system nor shall the act of distribution constitute any such warranty.</distliab>
    <stdorder>
      <digform>
        <digtinfo>
          <formname>FEMA-DCS-Terrain</formname>
        </digtinfo>
        <digtopt>
          <onlinopt>
            <computer>
              <networka>
                <networkr>http://hazards.fema.gov</networkr>
              </networka>
            </computer>
          </onlinopt>
        </digtopt>
      </digform>
      <fees>Contact Distributor</fees>
    </stdorder>
  </distinfo>
  <metainfo>
    <metd>20200226</metd>
    <metc>
      <cntinfo>
        <cntperp>
          <cntper>Kelly Francis</cntper>
          <cntorg>Aero-Graphics</cntorg>
        </cntperp>
        <cntpos>Project Manager</cntpos>
				<cntaddr>
					<addrtype>mailing and physical</addrtype>
					<address>40 W Oakland Ave</address>
					<city>Salt Lake City</city>
					<state>UT</state>
					<postal>84115</postal>
					<country>USA</country>
				</cntaddr>
				<cntvoice>801-487-3273</cntvoice>
				<cntemail>kfrancis@aero-graphics.com</cntemail>
			</cntinfo>
    </metc>
    <metstdn>FGDC Content Standards for Digital Geospatial Metadata</metstdn>
    <metstdv>FGDC-STD-001-1998</metstdv>
    <metextns>
      <onlink>http://hazards.fema.gov</onlink>
      <onlink>http://www.epsg.org</onlink>
      <metprof>FEMA NFIP Metadata Content and Format Standard</metprof>
    </metextns>
  </metainfo>
</metadata>

