<?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>64274</catalog-item-id>
      <title>2012 USACE Topobathy Lidar DEM: Post Sandy (NJ &amp; NY)</title>
      <short-name>2012_postsandy_usace_dem_m9012</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>49404</parent-catalog-item-id>
      <parent-title>DEMs - partner (no harvest)</parent-title>
      <parent-catalog-item-type>Project</parent-catalog-item-type>
      <status>Completed</status>
      <publication-date>2013-05</publication-date>
      <abstract>These files contain a digital elevation model derived from lidar data. The lidar data were collected on November 16, 2012 and cover
portions of the following counties:
New Jersey - Bergen, Essex, Hudson, Middlesex, Monmouth, Ocean, Union
New York - Bronx, Kings, Nassau, New York, Queens, Richmond, Suffolk, Westchester

These data were collected by the Coastal Zone Mapping and Imaging Lidar (CZMIL) system. CZMIL integrates a lidar sensor with
topographic and bathymetric capabilities, a digital camera and a hyperspectral imager on a single remote sensing platform
for use in coastal mapping and charting activities. Native lidar data is not generally in a format accessible to most Geographic
Information Systems (GIS). Specialized in-house and commercial software packages are used to process the native lidar data
into 3-dimensional positions that can be imported into GIS software for visualization and further analysis. Horizontal positions,
provided in decimal degrees of latitude and longitude, are referenced to the North American Datum of 1983 (NAD83). Vertical
positions are referenced to the NAD83 ellipsoid and provided in meters. The National Geodetic Survey's (NGS) GEOID12A model
is used to transform the vertical positions from ellipsoid to orthometric heights referenced to the North American Vertical
Datum of 1988 (NAVD88).

Original contact information: 
   Contact Org: JALBTCX
   Title: Data Production Manager
   Phone: 228-252-1121
   Email: JALBTCX@usace.army.mil</abstract>
      <purpose>These data were collected as a part of the Post Sandy effort to depict the elevations above and below the water in the NY coastal zone.</purpose>
      <supplemental-information>In areas of dense vegetation the points classified as ground might be incorrectly classified due to the inability of the laser to
penetrate the canopy and reach the bare ground.</supplemental-information>
   </item-identification>
   <keywords>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus>ISO 19115 Topic Category</thesaurus>
         <keyword>elevation</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>IWG-OCM</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>Light Detection and Ranging</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>National Coastal Mapping Program (NCMP)</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>U.S. Army Corps of Engineers (USACE)</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Temporal</keyword-type>
         <keyword>2012</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Temporal</keyword-type>
         <keyword>November</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>As Needed</maintenance-frequency>
      <distribution-liability>Any conclusions drawn from the analysis of this information are not the responsibility of USACE,
JALBTCX, the Office for Coastal Management or its partners.</distribution-liability>
      <data-set-credit>Acknowledgement of US Army Corps of Engineers (USACE) Joint Airborne Lidar Bathymetry Technical Center of Expertise (JALBTCX) would
be appreciated in products derived from these data.</data-set-credit>
   </data-set-information>
   <entity-attribute-information partial-listing="No" total-count="0"/>
   <support-roles>
      <support-role cc-id="1038694" in-effect="Yes">
         <support-role-type>Data Steward</support-role-type>
         <from-date>2013-05</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="1038696" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2013-05</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="1038697" in-effect="Yes">
         <support-role-type>Metadata Contact</support-role-type>
         <from-date>2013-05</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="1038695" in-effect="Yes">
         <support-role-type>Point of Contact</support-role-type>
         <from-date>2013-05</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="1293427">
         <geographic-areas>
            <geographic-area cc-id="1293429">
               <west-bound>-74.506526</west-bound>
               <east-bound>-73.172868</east-bound>
               <north-bound>41.009632</north-bound>
               <south-bound>40.022907</south-bound>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1293428">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2012-11-16</start-date-time>
            </time-frame>
         </time-frames>
      </extent>
   </extents>
   <spatial-information>
      <spatial-resolution>
         <horizontal-distance>1</horizontal-distance>
         <horizontal-distance-units>Meter</horizontal-distance-units>
      </spatial-resolution>
      <spatial-representation>
         <representations-used>
            <vector>Yes</vector>
         </representations-used>
         <grid-representations>
            <grid-representation cc-id="1038714">
               <dimension-count>2</dimension-count>
               <cell-geometry>Point</cell-geometry>
               <transformation-parameters-available>Yes</transformation-parameters-available>
               <axis-dimensions>
                  <axis-dimension cc-id="1293425">
                     <dimension-type>Row</dimension-type>
                     <size>6945</size>
                     <resolution-type>Length</resolution-type>
                     <resolution>1</resolution>
                     <resolution-units>Meter</resolution-units>
                  </axis-dimension>
               </axis-dimensions>
            </grid-representation>
         </grid-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-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=2478
;</data-access-procedure>
      <data-access-constraints>None</data-access-constraints>
      <data-use-constraints>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="1038698">
         <download-url>https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=9012</download-url>
         <distributor cc-id="1038696">
            <from-date>2013-05</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, map projection, file format, datum, etc.</description>
         <!--Note: file-type is deprecated-->
         <file-type>GeoTIFF</file-type>
         <distribution-format>GeoTIFF</distribution-format>
      </distribution>
      <distribution cc-id="1038699">
         <download-url>https://noaa-nos-coastal-lidar-pds.s3.us-east-1.amazonaws.com/dem/USACE_post-sandy_NY-NJ_2012_9012/index.html</download-url>
         <distributor cc-id="1038696">
            <from-date>2013-05</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>GeoTIFF</file-type>
         <distribution-format>GeoTIFF</distribution-format>
      </distribution>
   </distribution-information>
   <urls>
      <url cc-id="1038700">
         <url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2478/supplemental/2012_USACE_Post_Sandy_TopoBathy_Lidar_New_Jersey_and_New_York.kmz</url>
         <name>Browse Graphic</name>
         <url-type>Browse Graphic</url-type>
         <file-resource-format>kmz</file-resource-format>
         <description>This file shows the coverage of this data in New Jersey and New York.</description>
      </url>
   </urls>
   <activity-logs>
      <activity-log cc-id="1038702">
         <activity-date-time>2016-05-23</activity-date-time>
         <description>Date that the source FGDC record was last modified.</description>
      </activity-log>
      <activity-log cc-id="1038701">
         <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="1038703">
         <activity-date-time>2018-02-08</activity-date-time>
         <description>Partial upload of Positional Accuracy fields only.</description>
      </activity-log>
      <activity-log cc-id="1038704">
         <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>
   <technical-environment>
      <description>Microsoft Windows 2000 Version 5.2 (Build 3790) Service Pack 2; ESRI ArcCatalog 9.3.0.1770</description>
   </technical-environment>
   <data-quality>
      <accuracy>These data are not attributed. | Quantitative Value: N/A | Quantitative Test Explanation: These data are not attributed.</accuracy>
      <horizontal-positional-accuracy>The data positions were obtained using post processed KGPS methods. The horizontal accuracy of the data is better
than plus or minus 0.75 m.
; Quantitative Value: 0.75 meters, Test that produced the value: RMSE 95% Conf.</horizontal-positional-accuracy>
      <vertical-positional-accuracy>The data positions were obtained using post processed KGPS methods. The vertical
accuracy of the data is 0.125 m RMSE.
; Quantitative Value: 0.125 meters, Test that produced the value: RMSE 95% Conf.</vertical-positional-accuracy>
      <completeness-measure>Cloud Cover: Unknown</completeness-measure>
      <completeness-report>This data set covers the spatial extent of bathymetric and topographic lidar data obtained during this survey.</completeness-report>
      <conceptual-consistency>Differences between a DEM created from the lidar data representing bare ground and the ground truth
data is unbiased and measures 0.0396 m RMSE.</conceptual-consistency>
   </data-quality>
   <lineage>
      <lineage-process-steps>
         <lineage-process-step cc-id="1293423">
            <sequence-number>1</sequence-number>
            <description>These data were collected using the CZMIL system. It is owned and operated by the U.S. Army Corps of Engineers (USACE). The system collects lidar data at 10 kHz and RGB imagery at 2 Hz. A CASI-1500 hyperspectral line scanner is integrated with the  system as well. Aircraft position, velocity and acceleration information are collected through a combination of Novatel and POS A/V 510 equipment. All raw data streams are transferred to the office for downloading and processing in CZMILs Hydro Fusion software. Aircraft position data are processed using POSPac software and the results are combined with the lidar data to produce 3-D positions for each lidar shot. Upon inspection and QA/QC in the software packages Fledermaus and PFM_ABE, anomalous data are flagged as invalid. NOAAs VDatum software then converts all valid data from ellipsoid to orthometric heights based on the NGS' GEOID12A model and exports valid lidar data as a series of unclassified ascii xyz files.</description>
            <process-date-time>2012-12-23T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1293424">
            <sequence-number>2</sequence-number>
            <description>The flightline LAS files are imported into GeoCue [V2012], which is a geospatial workflow production and management software tool employed by JALBTCX to perform and monitor production of data products. Upon import into GeoCue, the flightline LAS files are divided into a series of boxes, each of which are 1500 meters in length and width. A customized classification macro, built upon the TerraScan [V12] module within Microstation V8i, classifies valid topographic data as ground points (2) and unclassified points (1). Upon completion the macro, the classification results undergo quality control and any misclassified points are manually edited. In areas of dense vegetation the bare earth ground points might be incorrectly classified due to the inability of the laser to penetrate the canopy and reach the bare ground. In these areas, JALBTCX defaults to the algorithms ground surface instead of manually reclassifying those points. The final classification results are comprised of individual lidar points with classifications of ground (2) or unclassified (1). They are partitioned into a series of USGS quarter quad delivery boxes, one Classified LAS file per box. The format of the file is LAS version [1.2]. Data are classified as 1 (valid non-ground topographic data), 2 (valid ground topographic data).</description>
            <process-date-time>2012-01-01T00:00:00</process-date-time>
         </lineage-process-step>
      </lineage-process-steps>
   </lineage>
   <related-items>
      <related-item>
         <catalog-item-id>50096</catalog-item-id>
         <catalog-item-type>Data Set</catalog-item-type>
         <title>2012 USACE Topobathy Lidar: Post Sandy (NJ &amp; NY)</title>
         <relationship-type>Cross Reference</relationship-type>
         <notes>point cloud used to derived this DEM</notes>
      </related-item>
   </related-items>
   <catalog-details>
      <guid>gov.noaa.nmfs.inport:64274</guid>
      <metadata-record-created-by pers-id="20140">Kirk Waters</metadata-record-created-by>
      <metadata-record-created>2021-02-09T16:14:01</metadata-record-created>
      <metadata-record-last-modified-by pers-id="20140">Kirk Waters</metadata-record-last-modified-by>
      <metadata-record-last-modified>2024-01-10T19:11:01</metadata-record-last-modified>
      <record-published>2024-01-10</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>
      <limited-metadata-available>No</limited-metadata-available>
      <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>
