<?xml version="1.0" encoding="UTF-8"?>
<inport-metadata xmlns:xs="http://www.w3.org/2001/XMLSchema"
                 version="1.11"
                 source="https://www.fisheries.noaa.gov">
   <item-identification>
      <catalog-item-id>49628</catalog-item-id>
      <title>2013 City and Borough of Juneau, Alaska Lidar</title>
      <short-name>ak2013_cbj_juneau_m4813_metadata</short-name>
      <catalog-item-type>Data Set</catalog-item-type>
      <metadata-workflow-state ccs-id="9">Published / External</metadata-workflow-state>
      <parent-catalog-item-id>49401</parent-catalog-item-id>
      <parent-title>Lidar - partner (no harvest)</parent-title>
      <parent-catalog-item-type>Project</parent-catalog-item-type>
      <status>Completed</status>
      <publication-date>2015-03-10</publication-date>
      <abstract>This dataset is LiDAR point cloud data, which encompasses a 100 meter buffer around the Juneau,AK study area, approximately 121,313 acres. Dataset Description: This dataset consists of 1273 .LAS files delineated in 750 x 750 m tiles and named as specified by the client. Each .LAS file contains LiDAR point information, which has been calibrated, controlled, and classified. LAS points contain RGB values from orthoimagery mosaics. Normalized intensity values are represented in the intensity field in this version of the point cloud. Ground Conditions: LiDAR acquisition of near shore areas was prioritized to coincide with the lowest tides possible, within constraints of daily local weather patterns. Leaf-off, no snow conditions were targeted in all other areas given the diverse terrain represented in the study area.

The LAZ files have vertical georeferencing using the EPSG 5866 code for mean lower low water. However, this code is for depth while the data is in height. There was no appropriate code for MLLW height at the time.</abstract>
      <purpose>Data was collected to aid CBJ in assessing the topographic and geophysical properties of the study area to support municipal planning, habitat assessments, and general development in the region. The LiDAR point cloud data were used to create classified LiDAR LAS files, normalized intensity images, 3D breaklines, bare earth DEM, bare earth hydro-flattened DEM, High Hit DSM, Vegetation height model, bridge footprints, 0.5m contours, and a mean high water contour. Data were also used to rectify 4-band orthophotos. The contract for this project was funded by the Coastal Impact Assistance Program through the Alaska Department of Commerce, Community, and Economic Development as part of Grant # 10-CIAP-0009, titled 'Habitat Mapping and Analysis Project.'

All processing was completed by WSI.  In some areas of heavy vegetation or forest cover, there may be relatively few ground points in the LiDAR data. TINing the points produces large triangles and hence the elevations may be less accurate within such areas. Elevation values for open water surfaces are derived from waters edge breaklines. Triangles were created across water surfaces by interpolating from the nearest breakline elevation points. RandM Engineering Inc. (Mark A. Johnson - AKPLS#7570) provided the Mean Lower Low Water (MLLW) elevation adjustment for all monuments used for the project. These MLLW elevations were determined by running level loops from tidal benchmarks with published MLLW elevations to each monument. Differences between the orthometric elevations of each monument on Geoid 12A and the MLLW elevations can be found in Appendix B of the Juneau LiDAR data report. The average MLLW adjustment was approximately 1.045m with a standard deviation of 0.066m. As a result of being calibrated using the ellipsoidal MLLW elevations instead of the normal ellipsoidal elevations, the LiDAR data was adjusted to the MLLW vertical datum.</purpose>
      <notes>10272</notes>
   </item-identification>
   <keywords>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus>ISO 19115 Topic Category</thesaurus>
         <keyword>elevation</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Spatial</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Location Keywords</thesaurus>
         <keyword identifier="90761f8d-6abe-499c-b711-acec394daa59">VERTICAL LOCATION &gt; LAND SURFACE</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Instrument</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Instrument Keywords</thesaurus>
         <keyword identifier="7166c458-f935-4bd9-a322-d92830cf0c33">LIDAR &gt; Light Detection and Ranging</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Platform</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Platform Keywords</thesaurus>
         <keyword identifier="8b7834c1-2c66-414e-a655-2298e7dcc479">Airplane &gt; Airplane</keyword>
      </keyword>
   </keywords>
   <physical-location>
      <organization>Office for Coastal Management</organization>
      <city>Charleston</city>
      <state-province>SC</state-province>
   </physical-location>
   <data-set-information>
      <data-set-scope-code>Data Set</data-set-scope-code>
      <maintenance-frequency>None Planned</maintenance-frequency>
      <data-presentation-form>las</data-presentation-form>
      <entity-attribute-overview>LAS 1.2 format (classes 2,3,4,5,6,7,8,9,10,19,20,21,22,23,24,25,27)</entity-attribute-overview>
      <entity-attribute-detail-citation>none</entity-attribute-detail-citation>
      <distribution-liability>Any conclusions drawn from the analysis of this information are not the responsibility of RandM Engineering Inc., Watershed Sciences Inc (Quantum Spatial), Alaska DGGS, NOAA, the Office for Coastal Management or its partners.</distribution-liability>
   </data-set-information>
   <entity-attribute-information partial-listing="No" total-count="0"/>
   <support-roles>
      <support-role cc-id="670493" in-effect="Yes">
         <support-role-type>Data Steward</support-role-type>
         <from-date>2015-03-10</from-date>
         <contact-type>Organization</contact-type>
         <contact-name>NOAA Office for Coastal Management</contact-name>
         <contact-noaa-acronym>NOAA/OCM</contact-noaa-acronym>
         <contact-email>coastal.info@noaa.gov</contact-email>
         <contact-address>2234 South Hobson Ave</contact-address>
         <contact-address-city>Charleston</contact-address-city>
         <contact-address-state>SC</contact-address-state>
         <contact-address-zip>29405-2413</contact-address-zip>
         <contact-phone-number>(843) 740-1202</contact-phone-number>
         <contact-url>https://coast.noaa.gov</contact-url>
         <contact-url-description>NOAA Office for Coastal Management Home Page</contact-url-description>
         <contact-url-function>Online Resource</contact-url-function>
      </support-role>
      <support-role cc-id="670495" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2015-03-10</from-date>
         <contact-type>Organization</contact-type>
         <contact-name>NOAA Office for Coastal Management</contact-name>
         <contact-noaa-acronym>NOAA/OCM</contact-noaa-acronym>
         <contact-email>coastal.info@noaa.gov</contact-email>
         <contact-address>2234 South Hobson Ave</contact-address>
         <contact-address-city>Charleston</contact-address-city>
         <contact-address-state>SC</contact-address-state>
         <contact-address-zip>29405-2413</contact-address-zip>
         <contact-phone-number>(843) 740-1202</contact-phone-number>
         <contact-url>https://coast.noaa.gov</contact-url>
         <contact-url-description>NOAA Office for Coastal Management Home Page</contact-url-description>
         <contact-url-function>Online Resource</contact-url-function>
      </support-role>
      <support-role cc-id="670496" in-effect="Yes">
         <support-role-type>Metadata Contact</support-role-type>
         <from-date>2015-03-10</from-date>
         <contact-type>Organization</contact-type>
         <contact-name>NOAA Office for Coastal Management</contact-name>
         <contact-noaa-acronym>NOAA/OCM</contact-noaa-acronym>
         <contact-email>coastal.info@noaa.gov</contact-email>
         <contact-address>2234 South Hobson Ave</contact-address>
         <contact-address-city>Charleston</contact-address-city>
         <contact-address-state>SC</contact-address-state>
         <contact-address-zip>29405-2413</contact-address-zip>
         <contact-phone-number>(843) 740-1202</contact-phone-number>
         <contact-url>https://coast.noaa.gov</contact-url>
         <contact-url-description>NOAA Office for Coastal Management Home Page</contact-url-description>
         <contact-url-function>Online Resource</contact-url-function>
      </support-role>
      <support-role cc-id="670494" in-effect="Yes">
         <support-role-type>Point of Contact</support-role-type>
         <from-date>2015-03-10</from-date>
         <contact-type>Organization</contact-type>
         <contact-name>NOAA Office for Coastal Management</contact-name>
         <contact-noaa-acronym>NOAA/OCM</contact-noaa-acronym>
         <contact-email>coastal.info@noaa.gov</contact-email>
         <contact-address>2234 South Hobson Ave</contact-address>
         <contact-address-city>Charleston</contact-address-city>
         <contact-address-state>SC</contact-address-state>
         <contact-address-zip>29405-2413</contact-address-zip>
         <contact-phone-number>(843) 740-1202</contact-phone-number>
         <contact-url>https://coast.noaa.gov</contact-url>
         <contact-url-description>NOAA Office for Coastal Management Home Page</contact-url-description>
         <contact-url-function>Online Resource</contact-url-function>
      </support-role>
   </support-roles>
   <extents>
      <currentness-reference>Ground Condition</currentness-reference>
      <extent cc-id="1136597">
         <geographic-areas>
            <geographic-area cc-id="1136599">
               <west-bound>-135.155767</west-bound>
               <east-bound>-133.665411</east-bound>
               <north-bound>58.895525</north-bound>
               <south-bound>58.043303</south-bound>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1136598">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2013-05-08</start-date-time>
               <end-date-time>2013-06-11</end-date-time>
            </time-frame>
         </time-frames>
      </extent>
   </extents>
   <spatial-information>
      <spatial-representation>
         <representations-used>
            <vector>Yes</vector>
         </representations-used>
         <vector-representations>
            <vector-representation cc-id="1184175">
               <point-object>
                  <present>Yes</present>
                  <count>5279631270</count>
               </point-object>
            </vector-representation>
         </vector-representations>
      </spatial-representation>
      <reference-systems>
         <reference-system>
            <coordinate-reference-system>
               <crs-type>Geographic 2D</crs-type>
               <epsg-code>EPSG:6318</epsg-code>
               <epsg-name>NAD83(2011)</epsg-name>
               <datum-name>NAD83 (National Spatial Reference System 2011)</datum-name>
               <ellipsoid>GRS 1980</ellipsoid>
               <semimajor-axis>6378137</semimajor-axis>
               <flattening-ratio>298.257222101</flattening-ratio>
               <axes>
                  <axis>
                     <order>1</order>
                     <name>Geodetic Lattitude</name>
                     <abbreviation>Lat</abbreviation>
                     <units>degree</units>
                     <orientation>north</orientation>
                  </axis>
                  <axis>
                     <order>2</order>
                     <name>Geodetic Longitude</name>
                     <abbreviation>Lon</abbreviation>
                     <units>degree</units>
                     <orientation>east</orientation>
                  </axis>
               </axes>
            </coordinate-reference-system>
         </reference-system>
         <reference-system>
            <coordinate-reference-system>
               <crs-type>Vertical</crs-type>
               <epsg-code>EPSG:5866</epsg-code>
               <epsg-name>MLLW depth</epsg-name>
               <datum-name>Mean Lower Low Water</datum-name>
               <axes>
                  <axis>
                     <order>1</order>
                     <name>Depth</name>
                     <abbreviation>D</abbreviation>
                     <units>metre</units>
                     <orientation>down</orientation>
                  </axis>
               </axes>
            </coordinate-reference-system>
         </reference-system>
      </reference-systems>
   </spatial-information>
   <access-information>
      <security-class>Unclassified</security-class>
      <data-access-procedure>This data can be obtained on-line at the following URL: 
https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=4813

The data set is dynamically generated based on user-specified parameters.;</data-access-procedure>
      <data-access-constraints>No restrictions apply to this data.</data-access-constraints>
      <data-use-constraints>In some areas of heavy vegetation or forest cover, there may be relatively few ground points in the LiDAR data. TINing the points produces large triangles and hence the elevations may be less accurate within such areas. Elevation values for open water surfaces are derived from waters edge breaklines. Triangles were created across water surfaces by interpolating from the nearest breakline elevation points. RandM Engineering Inc. (Mark A. Johnson - AKPLS#7570) provided the Mean Lower Low Water (MLLW) elevation adjustment for all monuments used for the project. These MLLW elevations were determined by running level loops from tidal benchmarks with published MLLW elevations to each monument. Differences between the orthometric elevations of each monument on Geoid 12A and the MLLW elevations can be found in Appendix B of the Juneau LiDAR data report. The average MLLW adjustment was approximately 1.045m with a standard deviation of 0.066m. As a result of being calibrated using the ellipsoidal MLLW elevations instead of the normal ellipsoidal elevations, the LiDAR data was adjusted to the MLLW vertical datum.

Users should be aware that temporal changes may have occurred since this data set was collected and some parts of this data may no longer represent actual surface conditions. Users should not use this data for critical applications without a full awareness of its limitations. These data depict the heights at the time of the survey and are only accurate for that time.</data-use-constraints>
   </access-information>
   <distribution-information>
      <distribution cc-id="740422">
         <download-url>https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=4813</download-url>
         <distributor cc-id="670495">
            <from-date>2015-03-10</from-date>
            <contact-type>Organization</contact-type>
            <contact-name>NOAA Office for Coastal Management</contact-name>
         </distributor>
         <file-name>Customized Download</file-name>
         <description>Create custom data files by choosing data area, product type, map projection, file format, datum, etc.</description>
         <!--Note: file-type is deprecated-->
         <file-type>Zip</file-type>
         <compression>Zip</compression>
      </distribution>
      <distribution cc-id="1184174">
         <download-url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/entwine/mllw/4813/ept.json</download-url>
         <distributor cc-id="670495">
            <from-date>2015-03-10</from-date>
            <contact-type>Organization</contact-type>
            <contact-name>NOAA Office for Coastal Management</contact-name>
         </distributor>
         <file-name>ept.json</file-name>
         <description>Data in Entwine Point Tile format suitable for streaming.</description>
         <!--Note: file-type is deprecated-->
         <file-type>EPT</file-type>
      </distribution>
      <distribution cc-id="740423">
         <download-url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/mllw/4813/index.html</download-url>
         <distributor cc-id="670495">
            <from-date>2015-03-10</from-date>
            <contact-type>Organization</contact-type>
            <contact-name>NOAA Office for Coastal Management</contact-name>
         </distributor>
         <file-name>Bulk Download</file-name>
         <description>Simple download of data files.</description>
         <!--Note: file-type is deprecated-->
         <file-type>LAZ</file-type>
         <distribution-format>LAS/LAZ - LASer</distribution-format>
         <compression>Zip</compression>
      </distribution>
   </distribution-information>
   <urls>
      <url cc-id="740427">
         <url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/mllw/4813/supplemental/ak2013_cbj_juneau_m4813.kmz</url>
         <name>Browse Graphic</name>
         <url-type>Browse Graphic</url-type>
         <file-resource-format>kmz</file-resource-format>
         <description>This graphic shows the lidar coverage for the 2013 lidar project covering Juneau County, Alaska.</description>
      </url>
      <url cc-id="740425">
         <url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/mllw/4813/supplemental/ak2013_cbj_juneau_m4813_surveyreport.pdf</url>
         <name>Project report</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>pdf</file-resource-format>
         <description>Project report from the lidar contractor</description>
      </url>
   </urls>
   <activity-logs>
      <activity-log cc-id="670525">
         <activity-date-time>2017-04-04</activity-date-time>
         <description>Date that the source FGDC record was last modified.</description>
      </activity-log>
      <activity-log cc-id="670524">
         <activity-date-time>2017-11-14</activity-date-time>
         <description>Converted from FGDC Content Standards for Digital Geospatial Metadata (version FGDC-STD-001-1998) using 'fgdc_to_inport_xml.pl' script. Contact Tyler Christensen (NOS) for details.</description>
      </activity-log>
      <activity-log cc-id="718168">
         <activity-date-time>2018-02-08</activity-date-time>
         <description>Partial upload of Positional Accuracy fields only.</description>
      </activity-log>
      <activity-log cc-id="740424">
         <activity-date-time>2018-03-13</activity-date-time>
         <description>Partial upload to move data access links to Distribution Info.</description>
      </activity-log>
   </activity-logs>
   <data-quality>
      <horizontal-positional-accuracy>The cumulative orthophoto horizontal accuracy (RMSE) for the Juneau Priority Area 1 was 0.55 feet (0.17 meters) measured by ground control points and 0.30 feet (0.09 meters) measured by air targets, meeting our accuracy standard of &lt; 3 pixels (0.45 meters); Quantitative Value: 0.17 meters, Test that produced the value: The cumulative orthophoto horizontal accuracy (RMSE) for the Juneau Priority Area 1 was 0.55 feet (0.17 meters) measured by ground control points and 0.30 feet (0.09 meters) measured by air targets, meeting our accuracy standard of &lt; 3 pixels (0.45 meters)</horizontal-positional-accuracy>
      <vertical-positional-accuracy>Specifications for this project require that the FVA be 24.5 cm or better AccuracyZ at 95 percent confidence level.; Quantitative Value: 0.059  meters, Test that produced the value: 5.9 cm meters AccuracyZ at 95 percent Confidence Interval. Accuracy was assessed using 3095 ground survey RTK (real time kinematic) points. ; Quantitative Value: 0.072 meters, Test that produced the value: Bare Earth SVA; Quantitative Value: 0.236 meters, Test that produced the value: Brush SVA; Quantitative Value: 0.122 meters, Test that produced the value: Deciduous Forest SVA; Quantitative Value: 0.127 meters, Test that produced the value: Evergreen Forest SVA; Quantitative Value: 0.131 meters, Test that produced the value: Short Grass SVA; Quantitative Value: 0.106 meters, Test that produced the value: Wetland Grass SVA</vertical-positional-accuracy>
      <completeness-report>LAS files	include	all	data points collected. No points have been removed or excluded.  Shaded relief images have been visually inspected for data errors such as pits, border artifacts, and shifting.  LiDAR flight lines have been examined to ensure consistent elevation values across overlapping flight lines. The raw point cloud is of good quality and data passes Fundamental Vertical Accuracy specifications. Please see the LiDAR data report for a discussion of the statistics related to this dataset.</completeness-report>
      <conceptual-consistency>Data cover the entire area specified for this project.</conceptual-consistency>
   </data-quality>
   <lineage>
      <lineage-process-steps>
         <lineage-process-step cc-id="1136594">
            <sequence-number>1</sequence-number>
            <description>LiDAR Pre-Processing: 
				1. Flight lines and data were reviewed to ensure complete coverage of the study area and positional accuracy of the laser points. 
				2. Resolve kinematic corrections for aircraft position data using kinematic aircraft GPS and static ground GPS data.
				3. Develop a smoothed best estimate of trajectory (SBET) file that blends post-processed aircraft position with attitude data. Sensor head position and attitude are calculated throughout the survey. The SBET data are used extensively for laser point processing.
				4. Calculate laser point position by associating SBET position to each laser point return time, scan angle, intensity, etc. Create raw laser point cloud data for the entire survey in *.las (ASPRS v. 1.2) format. Data are converted to orthometric elevations (NAVD88) by applying a Geoid12a correction.
				5. Import raw laser points into manageable blocks (less than 500 MB) to perform manual relative accuracy calibration and filter erroneous points. Ground points are then classified for individual flight lines (to be used for relative accuracy testing and calibration).
				6. Using ground classified points per each flight line, the relative accuracy is tested. Automated line-to-line calibrations are then performed for system attitude parameters (pitch, roll, heading), mirror flex (scale) and GPS/IMU drift. Calibrations are calculated on ground classified points from paired flight lines and results are applied to all points in a flight line. Every flight line is used for relative accuracy calibration. 
				7. Assess statistical absolute accuracy via direct comparisons to ground RTK survey data.</description>
            <process-date-time>2013-09-30T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1136595">
            <sequence-number>2</sequence-number>
            <description>LiDAR Post-Processing: 
				1. Classify data to ground and other client designated classifications using proprietary classification algorithms.
				2. Manually QC data classification
				3. Normalize Intensity Values for receiver auto gain control, atmospheric effects, and angle of incidence.
				4.Apply RGB values from orthophotos to points.</description>
            <process-date-time>2013-09-30T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1136596">
            <sequence-number>3</sequence-number>
            <description>The NOAA Office for Coastal Management (OCM) received the files in laz format from USGS via an FTP online repository. The files contained lidar elevation and intensity measurements. The data were in UTM Zone 5, mean lower low water heights in meters. OCM performed the following processing for data storage and Digital Coast provisioning purposes:
1. The data were converted from UTM coordinates to geographic coordinates.
2. Duplicate points were removed
</description>
            <process-date-time>2022-09-13T00:00:00</process-date-time>
            <process-contact>
               <contact-type>Organization</contact-type>
               <contact-name>NOAA Office for Coastal Management</contact-name>
               <contact-noaa-acronym>NOAA/OCM</contact-noaa-acronym>
               <contact-email>coastal.info@noaa.gov</contact-email>
               <contact-address>2234 South Hobson Ave</contact-address>
               <contact-address-city>Charleston</contact-address-city>
               <contact-address-state>SC</contact-address-state>
               <contact-address-zip>29405-2413</contact-address-zip>
               <contact-phone-number>(843) 740-1202</contact-phone-number>
               <contact-url>https://coast.noaa.gov</contact-url>
               <contact-url-description>NOAA Office for Coastal Management Home Page</contact-url-description>
               <contact-url-function>Online Resource</contact-url-function>
            </process-contact>
         </lineage-process-step>
      </lineage-process-steps>
   </lineage>
   <catalog-details>
      <guid>gov.noaa.nmfs.inport:49628</guid>
      <metadata-record-created-by pers-id="19064">Anne Ball</metadata-record-created-by>
      <metadata-record-created>2017-11-15T15:21:17</metadata-record-created>
      <metadata-record-last-modified-by pers-id="0">SysAdmin InPortAdmin</metadata-record-last-modified-by>
      <metadata-record-last-modified>2023-10-17T16:12:16</metadata-record-last-modified>
      <record-published>2022-09-14</record-published>
      <owner-organization>OCM Partners</owner-organization>
      <owner-organization-acronym>OCMP</owner-organization-acronym>
      <owner-organization-address/>
      <owner-organization-address-city/>
      <owner-organization-address-state/>
      <owner-organization-address-zip/>
      <owner-organization-address-country/>
      <owner-organization-phone/>
      <owner-organization-url/>
      <owner-organization-business-hours/>
      <owner-organization-group-id>1002</owner-organization-group-id>
      <publication-status>Public</publication-status>
      <best-available-metadata>No</best-available-metadata>
      <is-do-not-publish>No</is-do-not-publish>
      <metadata-last-review-date>2022-03-16</metadata-last-review-date>
      <metadata-review-frequency>1 Year</metadata-review-frequency>
      <metadata-next-review-date>2023-03-16</metadata-next-review-date>
   </catalog-details>
</inport-metadata>
