<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE metadata SYSTEM "http://fgdc.gov/metadata/fgdc-std-001-1998.dtd">
<metadata>
	<idinfo>
		<citation>
			<citeinfo>
				<origin>Photo Science, Inc.</origin>
				<pubdate>20150123</pubdate>
				<title>
					Lidar data for North Carolina -  SANDY 2014
					USGS Contract: G10PC00026  Task Order Number: G14PD00182
					NC_Sandy_2014
				</title>
				<geoform>model</geoform>
			</citeinfo>
		</citation>
		<descript>
		<abstract>
			Geographic Extent: North Carolina Area of Interest for Sandy, covering approximately 9,396 square miles. 
			Dataset Description: The North Carolina - Sandy LiDAR project called for the Planning, Acquisition, processing and derivative products of LIDAR data to be collected  at a nominal pulse spacing (NPS) of 0.7 meter.  Project specifications are based on the U.S. Geological Survey National Geospatial Program Base LIDAR Specification, Version 1.  The data was developed based on a horizontal projection/datum of North Carolina State Plane Coordinate System, NAD83, survey feet and vertical datum of NAVD1988 (GEOID12A), survey feet.  LiDAR data was delivered in RAW flight line swath format, processed to create Classified LAS 1.3 Files formatted to 12138 individual 5000ft x 5000ft tiles, and corresponding Intensity Images and Bare Earth DEMs tiled to the same 5000ft x 5000ft schema, and Breaklines in ESRI File-Geodatabase format.
			
			Ground Conditions: LiDAR was collected in Spring 2014, while no snow was on the ground and rivers were at or below normal levels.  In order to post process the LiDAR data to meet task order specifications, Photo Science established a total of 282 QA control points and 161 Land Cover control points that were used to calibrate the LIDAR to known ground locations established throughout the North Carolina - Sandy project area. 
		</abstract>
		<purpose>
			Classified LAS files are used to show the manually reviewed bare earth surface.  This allows the user to create Intensity Images, Breaklines and Raster DEM. 
			The purpose of these lidar data was to produce high accuracy 3D hydro-flattened Digital Elevation Model (DEM) with a 5 feet cell size.
			These raw lidar point cloud data were used to create classified lidar LAS files, intensity images, 3D breaklines, hydro-flattened DEMs as necessary.
		</purpose>
		<supplinf>
			USGS Contract No. G10PC00026
			CONTRACTOR: Photo Science, Inc
			Ground Control Points were acquired and calibrated by Photo Science, Inc.
			All Lidar data acquisition, calibration, and follow-on processing were completed by the prime contractor.
			Please note the lrdinfo section has been repeated twice for the two different specifications used to acquire the data.
		</supplinf>
		<lidar>
			<ldrinfo>
				<ldrspec>USGS-NGP Base Lidar Specification v1.0</ldrspec>
				<ldrsens>Leica ALS 70</ldrsens>
				<ldrmaxnr>4</ldrmaxnr>
				<ldrnps>0.69</ldrnps>
				<ldrdens>1.35</ldrdens>
				<ldrfltht>1676</ldrfltht>
				<ldrfltsp>150</ldrfltsp>
				<ldrscana>17</ldrscana>
				<ldrscanr>31.7</ldrscanr>
				<ldrpulsr>165.6</ldrpulsr>
				<ldrpulsd>4</ldrpulsd>
				<ldrpulsw>0.38</ldrpulsw>
				<ldrwavel>1064</ldrwavel>
				<ldrmpia>0</ldrmpia >
				<ldrbmdiv>0.22</ldrbmdiv>
				<ldrswatw>1024.81</ldrswatw>
				<ldrswato>12.49%</ldrswato>
				<ldrcrs>NAD_1983_2011_StatePlane_North_Carolina_FIPS_3200_Feet</ldrcrs>
				<ldrgeoid>National Geodetic Survey (NGS) Geoid12A</ldrgeoid>
			</ldrinfo>
			<ldrinfoPAR>
				<ldrspec>USGS-NGP Base Lidar Specification v1.0</ldrspec>
				<ldrsens>Leica ALS 70</ldrsens>
				<ldrmaxnr>4</ldrmaxnr>
				<ldrnps>0.50</ldrnps>
				<ldrdens>2.62</ldrdens>
				<ldrfltht>1402</ldrfltht>
				<ldrfltsp>110</ldrfltsp>
				<ldrscana>17</ldrscana>
				<ldrscanr>324</ldrscanr>
				<ldrpulsr>197.0</ldrpulsr>
				<ldrpulsd>4</ldrpulsd>
				<ldrpulsw>0.32</ldrpulsw>
				<ldrwavel>1064</ldrwavel>
				<ldrmpia>0</ldrmpia >
				<ldrbmdiv>0.22</ldrbmdiv>
				<ldrswatw>857.27</ldrswatw>
				<ldrswato>13.71%</ldrswato>
				<ldrcrs>NAD_1983_2011_StatePlane_North_Carolina_FIPS_3200_Feet</ldrcrs>
				<ldrgeoid>National Geodetic Survey (NGS) Geoid12A</ldrgeoid>
			</ldrinfoPAR>
			<ldraccur>
				<ldrchacc>-9999</ldrchacc>
				<rawfva>0.118</rawfva><!--determined from the calibrated but unclassified point cloud and reported as a 95% confidence interval-->
				<clsfva>0.118</clsfva><!--determined from the derived DEM and reported as a 95% confidence interval-->
				<clscva>0.237</clscva><!--determined from the derived DEM and reported as a 95th percentile error-->
				<clssvas>
					<svalctyp>Forested, Fully Covered by Trees</svalctyp>
					<svavalue>0.248</svavalue><!--determined from the derived DEM and reported as a 95th percentile error-->
				</clssvas>
				<clssvas>
					<svalctyp>Mangrove</svalctyp>
					<svavalue>0.265</svavalue><!--determined from the derived DEM and reported as a 95th percentile error-->
				</clssvas>
				<clssvas>
					<svalctyp>High Grass, Weeds, and Crops</svalctyp><!--determined from the derived DEM and reported as a 95th percentile error-->
					<svavalue>0.207</svavalue>
				</clssvas>
				<clssvas>
					<svalctyp>Urban Areas</svalctyp><!--determined from the derived DEM and reported as a 95th percentile error-->
					<svavalue>0.089</svavalue>
				</clssvas>
			</ldraccur>
			<lasinfo>
				<lasver>1.3</lasver>
				<lasprf>3</lasprf>
				<laswheld>Withheld (ignore) points were identified in these files using the standard LAS Withheld bit.</laswheld>
				<lasolap>Swath "overage" points were identified in these files by adding 16 to the standard classification values.</lasolap>
				<lasintr>8</lasintr>
			</lasinfo>
		</lidar>
		</descript>
		<timeperd>
			<timeinfo>
				<rngdates>
					<begdate>20140126</begdate>
					<enddate>20140406</enddate>
				</rngdates>
			</timeinfo>
			<current>ground condition</current>
		</timeperd>
		<status>
			<progress>Complete</progress>
			<update>None planned</update>
		</status>
		<spdom>
			<bounding>
				<westbc>-77.7311406333641</westbc>
				<eastbc>-75.4480899025439</eastbc>
				<northbc>36.5701573858108</northbc>
				<southbc>34.4274005943767</southbc>
			</bounding>
			<lboundng>
				<leftbc>2380000</leftbc>
				<rightbc>3055000</rightbc>
				<topbc>1040000</topbc>
				<bottombc>250000</bottombc>
			</lboundng>
		</spdom>
		<keywords>
			<theme>
				<themekt>None</themekt>
				<themekey>model</themekey>
				<themekey>LAS Point Cloud</themekey>
				<themekey>remote sensing</themekey>
				<themekey>Elevation data</themekey>
				<themekey>Lidar</themekey>
				<themekey>Hydrology</themekey>
			</theme>
			<place>
				<placekt>None</placekt>
				<placekey>North Carolina</placekey>
				<placekey>Beaufort County</placekey>
				<placekey>Bertie County</placekey>
				<placekey>Camden County</placekey>
				<placekey>Carteret County</placekey>
				<placekey>Chowan County</placekey>
				<placekey>Craven County</placekey>
				<placekey>Currituck County</placekey>
				<placekey>Dare County</placekey>
				<placekey>Gates County</placekey>
				<placekey>Hertford County</placekey>
				<placekey>Hyde County</placekey>
				<placekey>Jones County</placekey>
				<placekey>Martin County</placekey>
				<placekey>Onslow County</placekey>
				<placekey>Pamlico County</placekey>
				<placekey>Pasquotank County</placekey>
				<placekey>Perquimans County</placekey>
				<placekey>Pitt County</placekey>
				<placekey>Tyrell County</placekey>
				<placekey>Washington County</placekey>
			</place>
		</keywords>
		<accconst>No restrictions apply to these data.</accconst>
		<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 it's limitations. Acknowledgement of the U.S. Geological Survey would be appreciated for products derived from these data.</useconst>
		<ptcontac>
			<cntinfo>
				<cntorgp>
					<cntorg>Photo Science, Inc., Data Acquisition Department</cntorg>
					<cntper>Michael Shillenn</cntper>
				</cntorgp>
				<cntaddr>
					<addrtype>mailing and physical</addrtype>
					<address>523 Wellington Way</address>
					<city>Lexington</city>
					<state>KY</state>
					<postal>40503</postal>
					<country>USA</country>
				</cntaddr>
				<cntvoice>859-277-8700</cntvoice>
				<cntfax>859-277-8901</cntfax>
				<cntemail>mshillenn@photoscience.com</cntemail>
				<hours>Monday through Friday 8:00 AM to 5:00 PM (Eastern Time)</hours>
				<cntinst>If unable to reach the contact by telephone, please send an email. You should get a response within 24 hours.</cntinst>
			</cntinfo>
		</ptcontac>
		<datacred>Photo Science, Inc. flew the LiDAR and processed the data.</datacred>
		<native>
			MicroStation Version 8; TerraScan Version 13; TerraModeler Version 13; GeoCue Version 2012.1.27.7; ESRI ArcGIS 10.1; Global Mapper 13; ALS Post Processor 2.75 Build #25; Windows 7 Operating System \\psihq_nx3200\\Projects\7505_089_NorthCarolina_2014LIDAR\ 2.2 TB and  \\Matrix\LIDAR\7505-089_NC_LiDAR_2014  15.8 TB
		</native>
	</idinfo>
	<dataqual>
		<logic>
			Classified LAS files were tested by Photo Science for both vertical and horizontal accuracy. All data is seamless from one tile to the next, no gaps or no data areas.
		</logic>
		<complete>
			Datasets contain complete coverage of tiles.
			No points have been removed or excluded.
			A visual qualitative assessment was performed to ensure data completeness.
			There are no void areas or missing data. The raw point cloud is of good quality and data passes Fundamental Vertical Accuracy specifications.
		</complete>
		<posacc>
			<vertacc>
				<vertaccr>
					The specifications require that only Fundamental Vertical Accuracy (FVA) be computed for raw lidar point cloud swath files.
						The vertical accuracy value is the AccuracyZ at 95 percent Confidence Interval in feet.  The FVA was tested using 282 independent survey located in open terrain. The survey checkpoints were distributed throughout the project area. The 282 independent check points were surveyed using GPS techniques.  See survey report for additional survey methodologies.  Elevations from the unclassified lidar surface were measured for the x,y location of each check point.  Elevations interpolated from the lidar surface were then compared to the elevation values of the surveyed control. AccuracyZ has been tested to meet 18.13 cm Fundamental Vertical Accuracy at 95 Percent confidence level using RMSE(z) x 1.9600 as defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASRPS Guidelines.
				</vertaccr>
				<qvertpa>
					<vertaccv>0.386 feet AccuracyZ at 95 percent Confidence Interval</vertaccv>
					<vertacce>
						The FVA was tested using 282 independent survey located in open terrain. The survey checkpoints were distributed throughout the project area. The 282 independent check points were surveyed using GPS techniques.  See survey report for additional survey methodologies.  Elevations from the unclassified lidar surface were measured for the x,y location of each check point.  Elevations interpolated from the lidar surface were then compared to the elevation values of the surveyed control. The RMSE was computed to be 0.197 feet. AccuracyZ has been tested to meet 18.13 cm Fundamental Vertical Accuracy at 95 Percent confidence level using RMSE(z) x 1.9600 as defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASRPS Guidelines.
					</vertacce>
				</qvertpa>
			</vertacc>
		</posacc>
		<lineage>
			<srcinfo>
				<srccite>
					<citeinfo>
						<origin>Photo Science, Inc.</origin>
						<pubdate>20140516</pubdate>
						<title>Survey Report of LiDAR Ground Control Points: North Carolina - SANDY 2014 LiDAR</title>
						<geoform>vector digital data and tabular data</geoform>
						<pubinfo>
							<pubplace>Lexington, KY</pubplace>
							<publish>Photo Science, Inc.</publish>
						</pubinfo>
					</citeinfo>
				</srccite>
				<typesrc>CD-ROM</typesrc>
				<srctime>
					<timeinfo>
						<sngdate>
							<caldate>2014</caldate>
						</sngdate>
					</timeinfo>
					<srccurr>ground condition</srccurr>
				</srctime>
				<srccitea>NC_Sandy_2014_LiDAR_gnd_ctrl</srccitea>
				<srccontr>This data source was used (along with the airborne GPS/IMU Data) to aid in the georeferencing of the lidar point cloud data.
				</srccontr>
			</srcinfo>
			<srcinfo>
				<srccite>
					<citeinfo>
						<origin>Photo Science, Inc.</origin>
						<pubdate>20140516</pubdate>
						<title>Survey Report of LiDAR Quality Control Points: North Carolina - SANDY 2014 LiDAR</title>
						<geoform>vector digital data and tabular data</geoform>
						<pubinfo>
							<pubplace>Lexington, KY</pubplace>
							<publish>Photo Science, Inc</publish>
						</pubinfo>
					</citeinfo>
				</srccite>
				<srcscale>50</srcscale>
				<typesrc>online</typesrc>
				<srctime>
					<timeinfo>
						<sngdate>
							<caldate>2014</caldate>
						</sngdate>
					</timeinfo>
					<srccurr>ground condition</srccurr>
				</srctime>
				<srccitea>NC_Sandy_2014_LiDAR_qc_ctrl</srccitea>
				<srccontr>This data source was used (along with the lidar intensity imagery) to QC and vertically adjust the lidar point cloud data.</srccontr>
			</srcinfo>
			<srcinfo>
				<srccite>
					<citeinfo>
						<origin>Photo Science, Inc.</origin>
						<pubdate>20140516</pubdate>
						<title>Lidar RAW Data for North Carolina - SANDY 2014</title>
						<geoform>lidar data</geoform>
						<pubinfo>
							<pubplace>Photo Science, Inc.</pubplace>
							<publish>20140516</publish>
						</pubinfo>
					</citeinfo>
				</srccite>
				<typesrc>online</typesrc>
				<srctime>
					<timeinfo>
						<rngdates>
							<begdate>20140126</begdate>
							<enddate>20140406</enddate>
						</rngdates>
					</timeinfo>
					<srccurr>ground condition</srccurr>
				</srctime>
				<srccitea>NC_Sandy_2014_LiDAR_Lidar_Data</srccitea>
				<srccontr>This data source was used to populate the lidar point cloud data.</srccontr>
			</srcinfo>
			<procstep>
				<procdesc>
					Hydro Flattening Breakline Processing: 
					Class 2 LiDAR was used to create a bare earth surface model.  The surface model was then used to heads-up digitize 2D breaklines of inland streams and rivers with a 100 foot nominal width and Inland Ponds and Lakes of 2 acres or greater surface area.
					Elevation values were assigned to all Inland Ponds and Lakes, Inland Pond and Lake Islands, Inland Stream and River Islands, using TerraModeler functionality.
					Elevation values were assigned to all Inland streams and rivers using Photo Science proprietary software.
					All ground (ASPRS Class 2) LiDAR data inside of the collected inland breaklines were then classified to water (ASPRS Class 9) using TerraScan macro functionality.  A buffer of 3 feet was also used around each hydro-flattened feature.  These points were moved from ground (ASPRS Class 2) to Ignored Ground (ASPRS Class 10).
					The breakline files were then translated to ESRI File-Geodatabase format using ESRI conversion tools.</procdesc>
				<srcused>NC_Sandy_2014_LiDAR_gnd_ctrl</srcused>
				<srcused>NC_Sandy_2014_LiDAR_Data</srcused>
				<procdate>2014</procdate>
				<srcprod>Hydro Flattened Breaklines</srcprod>
				<proccont>
					<cntinfo>
						<cntorgp>
							<cntorg>Photo Science, Inc.</cntorg>
						</cntorgp>
						<cntaddr>
							<addrtype>mailing and physical</addrtype>
							<address>523 Wellington Way</address>
							<city>Lexington</city>
							<state>KY</state>
							<postal>40503</postal>
							<country>USA</country>
						</cntaddr>
						<cntvoice>859-277-8700</cntvoice>
						<cntfax>859-277-8901</cntfax>
						<cntemail>apike@photoscience.com</cntemail>
						<hours>Monday through Friday 8:00 AM to 5:00 PM (Eastern Time)</hours>
						<cntinst>If unable to reach the contact by telephone, please send an email. You should get a response within 24 hours.</cntinst>
					</cntinfo>
				</proccont>
			</procstep>
		</lineage>
	</dataqual>
	<spdoinfo>
		<direct>Vector</direct>
		<ptvctinf>
			<sdtsterm>
				<sdtstype>String</sdtstype>
			</sdtsterm>
		</ptvctinf>
	</spdoinfo>
	<spref>
		<horizsys>
			<planar>
				<gridsys>
					<gridsysn>State Plane Coordinate System 1983</gridsysn>
					<spcs>
						<spcszone>3200</spcszone>
						<lambertc>
							<stdparll>34.33333333</stdparll>
							<stdparll>36.16666667</stdparll>
							<longcm>36.16666667</longcm>
							<latprjo>33.75000000</latprjo>
							<feast>2000000.00261667</feast>
							<fnorth>0.0</fnorth>
						</lambertc>
					</spcs>
				</gridsys>
				<planci>
					<plance>coordinate pair</plance>
					<coordrep>
					<absres>0.01</absres>
					<ordres>0.01</ordres>
					</coordrep>
					<plandu>feet</plandu>
				</planci>
			</planar>
			<geodetic>
				<horizdn>North American Datum of 1983 (2011)</horizdn>
				<ellips>Geodetic Reference System 80</ellips>
				<semiaxis>6378137</semiaxis>
				<denflat>298.257222101</denflat>
			</geodetic>
		</horizsys>
		<vertdef>
			<altsys>
				<altdatum>North American Vertical Datum of 1988 GEOID12a</altdatum>
				<altres>0.01</altres>
				<altunits>feet</altunits>
				<altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
			</altsys>
		</vertdef>
	</spref>
	<eainfo>
		<detailed>
			<enttyp>
				<enttypl>Breaklines</enttypl>
				<enttypd>A line in a surface that represents a distinct interruption in the slope of a surface, such as a ridge, road, or stream.</enttypd>
				<enttypds>Esri GIS Dictionary http://support.esri.com/en/knowledgebase/GISDictionary/term/breakline</enttypds>
			</enttyp>
			<attr>
				<attrlabl>OID</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>Feature geometry - PolylineZM</udom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>B_LINE_TY</attrlabl>
				<attrdef>Breakline Type</attrdef>
				<attrdefs>LiDAR Data</attrdefs>
				<attrdomv>
					<edom>
						<edomv>Lake Pond</edomv>
						<edomvd>LiDAR Data</edomvd>
						<edomvds>LAS version 1.3</edomvds>
					</edom>
					<edom>
						<edomv>Lake Pond Island</edomv>
						<edomvd>LiDAR Data</edomvd>
						<edomvds>LAS version 1.3</edomvds>
					</edom>
					<edom>
						<edomv>Double Line Drain</edomv>
						<edomvd>LiDAR Data</edomvd>
						<edomvds>LAS version 1.3</edomvds>
					</edom>
					<edom>
						<edomv>Double Line Drain Island</edomv>
						<edomvd>LiDAR Data</edomvd>
						<edomvds>LAS version 1.3</edomvds>
					</edom>
					<edom>
						<edomv>Ocean Shoreline</edomv>
						<edomvd>LiDAR Data</edomvd>
						<edomvds>LAS version 1.3</edomvds>
					</edom>
				</attrdomv>
			</attr>
		</detailed>
		<overview>
			<eaover>Breaklines with the types of Lake Pond, Lake Pond Island, Double Line Drain, Double Line Drain Island, and Ocean Shoreline.</eaover>
			<eadetcit>More detail about the attributes of this data set can be found in LAS 1.3 specifications and USGS LiDAR Base Specification Version 1.0.</eadetcit>
		</overview>
	</eainfo>
	<metainfo>
		<metd>20150123</metd>
		<metc>
			<cntinfo>
				<cntorgp>
					<cntorg>Photo Science, Inc.</cntorg>
					<cntper>Ryan Elizabeth Bowe, GISP</cntper>
				</cntorgp>
				<cntaddr>
					<addrtype>mailing and physical</addrtype>
					<address>523 Wellington Way</address>
					<city>Lexington</city>
					<state>KY</state>
					<postal>40503</postal>
					<country>USA</country>
				</cntaddr>
				<cntvoice>859-277-8700</cntvoice>
				<cntfax>859-277-8901</cntfax>
				<cntemail>rebowe@photoscience.com</cntemail>
				<hours>Monday through Friday 8:00 AM to 5:00 PM (Eastern Time)</hours>
				<cntinst>If unable to reach the contact by telephone, please send an email. You should get a response within 24 hours.</cntinst>
			</cntinfo>
		</metc>
		<metstdn>FGDC Content Standard for Digital Geospatial Metadata</metstdn>
		<metstdv>FGDC-STD-001-1998</metstdv>
		<metac>None.</metac>
		<metuc>None.</metuc>
		<metsi>
			<metscs>None.</metscs>
			<metsc>Unclassified</metsc>
			<metshd>NONE</metshd>
		</metsi>
	</metainfo>
</metadata>

