(MI_Metadata)fileIdentifier: gov.noaa.csc.maps:2008_GL_Bathymetry_m518language: eng; USAcharacterSet: (MD_CharacterSetCode) utf8hierarchyLevel: (MD_ScopeCode) datasetcontact: (CI_ResponsibleParty)individualName: Mike SutherlandorganisationName: DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of CommercecontactInfo: (CI_Contact)phone: (CI_Telephone)voice: 303-497-6120facsimile: 303-497-6513address: (CI_Address)deliveryPoint: NOAA/NESDIS/NGDC E/GC1 325 Broadwaycity: BoulderadministrativeArea: COpostalCode: 80305-3328country: USAelectronicMailAddress: mike.sutherland@noaa.govhoursOfService: 7:30am-5:00pm Mountainrole: (CI_RoleCode) authordateStamp: 2013-06-05metadataStandardName: ISO 19115-2 Geographic Information - Metadata - Part 2: Extensions for Imagery and Gridded DatametadataStandardVersion: ISO 19115-2:2009(E)return to topspatialRepresentationInfo: (MD_VectorSpatialRepresentation)geometricObjects: (MD_GeometricObjects)geometricObjectType: (MD_GeometricObjectTypeCode) pointreturn to topreferenceSystemInfo: (MD_ReferenceSystem)referenceSystemIdentifier: (RS_Identifier)authority: (CI_Citation)title: North American Datum 1983alternateTitle: NAD83date: (CI_Date)date: 2007-01-19dateType: (CI_DateTypeCode) revisioncitedResponsibleParty: (CI_ResponsibleParty)organisationName: contactInfo: (CI_Contact)onlineResource: (CI_OnlineResource)linkage: http://www.epsg-registry.org/export.htm?gml=urn:ogc:def:crs:EPSG::4269name: NAD83description: Link to Geographic Markup Language (GML) description of reference system.function: (CI_OnLineFunctionCode) informationrole: (CI_RoleCode) resourceProvidercitedResponsibleParty: (CI_ResponsibleParty)organisationName: European Petroleum Survey GroupcontactInfo: (CI_Contact)onlineResource: (CI_OnlineResource)linkage: http://www.epsg-registry.org/name: European Petroleum Survey Group Geodetic Parameter Registrydescription: Registry that accesses the EPSG Geodetic Parameter Dataset, which is a structured dataset of Coordinate Reference Systems and Coordinate Transformations.function: (CI_OnLineFunctionCode) searchrole: (CI_RoleCode) publishercode: urn:ogc:def:crs:EPSG::4269return to topreferenceSystemInfo: (MD_ReferenceSystem)referenceSystemIdentifier: (RS_Identifier)code: Ellipsoid in MeterscodeSpace: Local Vertical Referencereturn to topidentificationInfo: (MD_DataIdentification)citation: (CI_Citation)title: 2008 US Army Corps of Engineers (USACE) National Coastal Mapping Program Topobathy Lidar: Lake Michigandate: (CI_Date)date: 2009-01-01dateType: (CI_DateTypeCode) publicationcitedResponsibleParty: (CI_ResponsibleParty)organisationName: DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of CommercecontactInfo: (CI_Contact)phone: (CI_Telephone)voice: 843-740-1200address: (CI_Address)deliveryPoint: 2234 South Hobson Ave.city: CharlestonadministrativeArea: SCpostalCode: 29405-2413electronicMailAddress: coastal.info@noaa.govonlineResource: (CI_OnlineResource)linkage: http://coast.noaa.govrole: (CI_RoleCode) originatorcitedResponsibleParty: (CI_ResponsibleParty)organisationName: US Army Corps of Engineers (USACE) Joint Airborne Lidar Bathymetry Technical Center of eXpertise (JALBTCX)positionName: Data Production ManagercontactInfo: (CI_Contact)phone: (CI_Telephone)voice: 228-252-1131voice: 228-252-1121facsimile: 228-252-1133address: (CI_Address)deliveryPoint: 7225 Stennis Airport Rd, STE 100city: KilnadministrativeArea: MSpostalCode: 39556country: USelectronicMailAddress: JALBTCX@usace.army.milhoursOfService: 8 am - 5 pm Monday through Fridayrole: (CI_RoleCode) originatorcitedResponsibleParty: (CI_ResponsibleParty)organisationName: DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of CommercecontactInfo: (CI_Contact)phone: (CI_Telephone)voice: 843-740-1200address: (CI_Address)deliveryPoint: 2234 South Hobson Ave.city: CharlestonadministrativeArea: SCpostalCode: 29405-2413electronicMailAddress: coastal.info@noaa.govonlineResource: (CI_OnlineResource)linkage: http://coast.noaa.govrole: (CI_RoleCode) publisherpresentationForm: (CI_PresentationFormCode) imageDigitalabstract: These files contain topographic and bathymetric lidar data collected by the Compact Hydrographic Airborne Rapid Total Survey (CHARTS) system along the west coast of Michigan from Berrien County to Leelanau County, along the Lake Michigan coastline from 28 July - 16 Sept 2008. Lidar intensity data was also collected. CHARTS integrates topographic and bathymetric lidar sensors, a digital camera and a hyperspectral scanner on a single remote sensing platform for use in coastal mapping and charting activities. Data coverage generally extends along the coastline from the waterline inland 500 meters (topography) and offshore 1,000 meters or to laser extinction (bathymetry). The topographic lidar sensor has a pulse repetition rate of 9 kHz at 1064 nm (near-infrared wavelength). The bathymetric lidar sensor has a pulse repetition rate of 1 kHz at 532 nm (green wavelength). Native lidar data is not generally in a format accessible to most Geographical 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.purpose: These data were collected as a part of the National Coastal Mapping Program to depict the elevations above the water for the First Return, Last Return, or Hydro in the Michigan coastal zone.credit: Acknowledgement of the Joint Airborne Lidar Bathymetry Technical Center of eXpertise (JALBTCX) would be appreciated in any publications or derived products.status: (MD_ProgressCode) completedpointOfContact: (CI_ResponsibleParty)organisationName: US Army Corps of Engineers (USACE) Joint Airborne Lidar Bathymetry Technical Center of eXpertise (JALBTCX)positionName: Data Production ManagercontactInfo: (CI_Contact)phone: (CI_Telephone)voice: 228-252-1131voice: 228-252-1121facsimile: 228-252-1133address: (CI_Address)deliveryPoint: 7225 Stennis Airport Rd, STE 100city: KilnadministrativeArea: MSpostalCode: 39556country: USelectronicMailAddress: JALBTCX@usace.army.milhoursOfService: 8 am - 5 pm Monday through Fridayrole: (CI_RoleCode) pointOfContactresourceMaintenance: (MD_MaintenanceInformation)maintenanceAndUpdateFrequency: (MD_MaintenanceFrequencyCode) asNeededdescriptiveKeywords: (MD_Keywords)keyword: Bathymetry/Topographykeyword: U.S. Army Corps of Engineers, Mobile Districtkeyword: JALBTCXkeyword: CHARTSkeyword: SHOALSkeyword: LiDARkeyword: Elevationkeyword: ASCII XYZkeyword: Intensitytype: (MD_KeywordTypeCode) themethesaurusName: (CI_Citation)title: Nonedate: descriptiveKeywords: (MD_Keywords)keyword: United Stateskeyword: Michigankeyword: Allegan Countykeyword: Benzie Countykeyword: Berrien Countykeyword: Lake Michigankeyword: Leelanau Countykeyword: Manistee Countykeyword: Mason Countykeyword: Muskegon Countykeyword: Oceana Countykeyword: Ottawa Countykeyword: Van Buren Countytype: (MD_KeywordTypeCode) placethesaurusName: (CI_Citation)title: Nonedate: descriptiveKeywords: (MD_Keywords)keyword: 2008keyword: Julykeyword: Augustkeyword: Septembertype: (MD_KeywordTypeCode) temporalthesaurusName: (CI_Citation)title: Nonedate: resourceConstraints: (MD_Constraints)useLimitation: These data depict the elevations at the time of the survey and are only accurate for that time. 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. Any conclusions drawn from analysis of this information are not the responsibility of NOAA or any of its partners. These data are NOT to be used for navigational purposes.resourceConstraints: (MD_LegalConstraints)useLimitation: While every effort has been made to ensure that these data are accurate and reliable within the limits of the current state of the art, NOAA cannot assume liability for any damages caused by any errors or omissions in the data, nor as a result of the failure of the data to function on a particular system. NOAA makes no warranty, expressed or implied, nor does the fact of distribution constitute such a warranty.spatialRepresentationType: (MD_SpatialRepresentationTypeCode) vectorlanguage: eng; USAtopicCategory: (MD_TopicCategoryCode) elevationextent: (EX_Extent)geographicElement: (EX_GeographicBoundingBox)westBoundLongitude: -86.838156eastBoundLongitude: -85.915215southBoundLatitude: 41.748285northBoundLatitude: 44.989667temporalElement: (EX_TemporalExtent)extent: TimePeriod: beginPosition: 2008-07-28endPosition: 2008-09-16return to topdistributionInfo: (MD_Distribution)distributionFormat: (MD_Format)name: LAZversion: distributor: (MD_Distributor)distributorContact: (CI_ResponsibleParty)organisationName: DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of CommercecontactInfo: (CI_Contact)phone: (CI_Telephone)voice: 843-740-1200address: (CI_Address)deliveryPoint: 2234 South Hobson Ave.city: CharlestonadministrativeArea: SCpostalCode: 29405-2413electronicMailAddress: coastal.info@noaa.govonlineResource: (CI_OnlineResource)linkage: http://coast.noaa.govrole: (CI_RoleCode) distributordistributionOrderProcess: (MD_StandardOrderProcess)orderingInstructions: The National Geophysical Data Center serves as the archive for this LIDAR data. NGDC should only be contacted for this data if it cannot be obtained from
NOAA Coastal Services Center.distributor: (MD_Distributor)distributorContact: (CI_ResponsibleParty)individualName: Mike SutherlandorganisationName: DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of CommercecontactInfo: (CI_Contact)phone: (CI_Telephone)voice: 303-497-6120facsimile: 303-497-6513address: (CI_Address)deliveryPoint: NOAA/NESDIS/NGDC E/GC1 325 Broadwaycity: BoulderadministrativeArea: COpostalCode: 80305-3328country: USAelectronicMailAddress: mike.sutherland@noaa.govhoursOfService: 7:30am-5:00pm Mountainrole: (CI_RoleCode) distributordistributionOrderProcess: (MD_StandardOrderProcess)orderingInstructions: The National Geophysical Data Center serves as the archive for this LIDAR dataset. NGDC should only be contacted for the data if it cannot be obtained from
NOAA Coastal Services Center.return to topdataQualityInfo: (DQ_DataQuality)scope: (DQ_Scope)level: (MD_ScopeCode) datasetreport: (DQ_AbsoluteExternalPositionalAccuracy)nameOfMeasure: Horizontal Positional Accuracy ReportevaluationMethodDescription: The data positions were obtained using post processed KGPS methods. The horizontal accuracy of the data is better than +/- 0.75m.result: report: (DQ_AbsoluteExternalPositionalAccuracy)nameOfMeasure: Horizontal Positional AccuracymeasureDescription: 1 Sigmaresult: (DQ_QuantitativeResult)valueUnit: BaseUnit: identifier: metersunitsSystem: value: Record: 0.75report: (DQ_AbsoluteExternalPositionalAccuracy)nameOfMeasure: Vertical Positional Accuracy ReportevaluationMethodDescription: The data positions were obtained using post processed KGPS methods. The vertical accuracy of the data is better than +/- 0.20m.result: report: (DQ_AbsoluteExternalPositionalAccuracy)nameOfMeasure: Vertical Positional AccuracymeasureDescription: 1 Sigmaresult: (DQ_QuantitativeResult)valueUnit: BaseUnit: identifier: metersunitsSystem: value: Record: 0.20report: (DQ_CompletenessCommission)evaluationMethodDescription: Not providedresult: report: (DQ_ConceptualConsistency)measureDescription: The data provided in this file were tested against ground truth data. At these locations the lidar data matched within 0.20 meters, and different flight line data agreed within 0.20 meters.result: report: (DQ_QuantitativeAttributeAccuracy)nameOfMeasure: Quantitative Attribute Accuracy AssessmentmeasureDescription: These data are not attributed.evaluationMethodDescription: These data are not attributed.result: (DQ_QuantitativeResult)valueUnit: BaseUnit: identifier: metersunitsSystem: value: Record: N/Alineage: (LI_Lineage)processStep: (LE_ProcessStep)description: These data were collected using the CHARTS system. It is owned by the Naval Oceanographic Office and operated through contract. The system collects topographic lidar data at 9kHz, bathymetric lidar data at 1kHz and RGB imagery at 1Hz. 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 410 equipment. All raw data streams are transferred to the office for downloading and processing in SHOALS GCS 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. PFM_ABE's chartsLAS module then converts all valid data from ellipsoid to orthometric heights based on the NGS' GEOID03 model and exports data as a series of first return topography (TF), last return topography (TL) and bathymetry (H) ASCII files. The bathymetry files contain all of the returns from the bathymetric sensor which include returns both above and below the water. The National Geodetic Survey's (NGS) GEOID03 model was used to transform the vertical positions from ellipsoid to orthometric heights referenced to the North American Vertical Datum of 1988 (NAVD88). The 3-D position data were sub-divided into a series of ASCII file products, with each covering approximately 5 kilometers of shoreline. The file index was provided by the shape file, "mi_michigan_boxes.shp", and the numbers used to identify files are in the "Box" field of the shape file. The data file naming convention is based on the year, project, area name, "Box" number and product type (topographic or bathymetric). An example file name is "2008_NCMP_MI_Michigan_07_ASCII", where 2008 is the year of data collection, NCMP is the project under which data were collected, MI_Michigan is the area of data collection, 07 is the "Box" number and ASCII is the product type. The ASCII columns are Longitude, Latitude, UTM Zone, Easting, Northing, Elevation (orthometric), Elevation (ellipsoid), Date, Time, and Intensity.dateTime: DateTime: 2009-01-01T00:00:00processor: (CI_ResponsibleParty)organisationName: US Army Corps of Engineers (USACE) Joint Airborne Lidar Bathymetry Technical Center of eXpertise (JALBTCX)positionName: Data Production ManagercontactInfo: (CI_Contact)phone: (CI_Telephone)voice: 228-252-1131voice: 228-252-1121facsimile: 228-252-1133address: (CI_Address)deliveryPoint: 7225 Stennis Airport Rd, STE 100city: KilnadministrativeArea: MSpostalCode: 39556country: USelectronicMailAddress: JALBTCX@usace.army.milhoursOfService: 8 am - 5 pm Monday through Fridayrole: (CI_RoleCode) processorprocessStep: (LE_ProcessStep)description: The NOAA Coastal Services Center (CSC) received topo and hydro files in ASCII format. The files contained LiDAR elevation and intensity measurements. The points were classed as 'never classified.' The data were provided in Geographic coordinates and ellipsoidal heights and in orthometric heights. CSC performed the following processing to the ellipsoidal height data to make it available within the Digital Coast: 1. LASEdit was used to convert the ASCII formatted files to las format. 2. The hydro points classification was changed from 'never classified' to class 11, 'bathymetry'. The topo points classification remains as class 0, 'never classified'. 3. The LAS data were sorted by latitude and the headers were updated.dateTime: DateTime: 2009-11-01T00:00:00processor: (CI_ResponsibleParty)organisationName: DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of CommercecontactInfo: (CI_Contact)phone: (CI_Telephone)voice: 843-740-1200address: (CI_Address)deliveryPoint: 2234 South Hobson Ave.city: CharlestonadministrativeArea: SCpostalCode: 29405-2413electronicMailAddress: coastal.info@noaa.govonlineResource: (CI_OnlineResource)linkage: http://coast.noaa.govrole: (CI_RoleCode) processorprocessStep: (LE_ProcessStep)description: The NOAA National Geophysical Data Center (NGDC) received lidar data files via ftp transfer from the NOAA Coastal Services Center. The data are
currently being served via NOAA CSC Digital Coast at http://www.csc.noaa.gov/digitalcoast/. The data can be used to re-populate the system. The data are archived in LAS
or LAZ format. The LAS format is an industry standard for LiDAR data developed by the American Society of Photogrammetry and Remote Sensing (ASPRS); LAZ is a loseless
compressed version of LAS developed by Martin Isenburg (http://www.laszip.org/). The data are exclusively in geographic coordinates (either NAD83 or ITRF94). The data
are referenced vertically to the ellipsoid (either GRS80 or ITRF94), allowing for the ability to apply the most up to date geoid model when transforming to orthometric
heights.dateTime: DateTime: 2011-05-03T00:00:00processor: (CI_ResponsibleParty)individualName: Pamela GrotheorganisationName: DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of CommercecontactInfo: (CI_Contact)contactInstructions: Contact Data Centerrole: (CI_RoleCode) processorreturn to topmetadataMaintenance: (MD_MaintenanceInformation)maintenanceAndUpdateFrequency: (MD_MaintenanceFrequencyCode) annuallydateOfNextUpdate: 2014-06-05maintenanceNote: This metadata was automatically generated from the FGDC Content Standards for Digital Geospatial Metadata standard (version FGDC-STD-001-1998) using the 2013-01-04 version of the FGDC RSE to ISO 19115-2 for LiDAR transform.maintenanceNote: Translated from FGDC 2013-06-05T15:37:59.466-06:00maintenanceNote: Last Metadata Review Date: 2011-11-19