| 2010 FEMA Lidar: Ozaukee County (WI) | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:50191 language: LanguageCode: eng characterSet: (MD_CharacterSetCode) UTF8 hierarchyLevel: (MD_ScopeCode) dataset contact: (CI_ResponsibleParty) organisationName: OCM Partners contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (missing) address: (CI_Address) role: (CI_RoleCode) resourceProvider contact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) pointOfContact dateStamp: DateTime: 2022-08-09T17:11:38 metadataStandardName: ISO 19115-2 Geographic Information - Metadata Part 2 Extensions for imagery and gridded data metadataStandardVersion: ISO 19115-2:2009(E) return to top spatialRepresentationInfo: return to top referenceSystemInfo: return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) authority: (CI_Citation) title: NAD83(2011) date: (CI_Date) date: 2008-11-12 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: European Petroleum Survey Group contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://apps.epsg.org/api/v1/CoordRefSystem/6318/export/?format=gml role: (missing) code: urn:ogc:def:crs:EPSG:6318 version: 6.18.3 return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) authority: (CI_Citation) title: North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters alternateTitle: North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters citedResponsibleParty: (CI_ResponsibleParty) organisationName: (withheld) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://apps.epsg.org/api/v1/VerticalCoordRefSystem/5703/?api_key=gml name: North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters description: Link to Geographic Markup Language (GML) description of reference system. function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) resourceProvider citedResponsibleParty: (CI_ResponsibleParty) organisationName: European Petroleum Survey Group contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.epsg.org/ name: European Petroleum Survey Group Geodetic Parameter Registry description: Registry that accesses the EPSG Geodetic Parameter Dataset, which is a structured dataset of Coordinate Reference Systems and Coordinate Transformations. function: (CI_OnLineFunctionCode) search role: (CI_RoleCode) publisher VerticalCS: metaDataProperty: CommonMetaData: type: vertical informationSource: OGP revisionDate: 2006-11-28 isDeprecated: false identifier: urn:ogc:def:cs:EPSG::6499 name: Vertical CS. Axis: height (H). Orientation: up. UoM: meter. remarks: Used in vertical coordinate reference systems. axis: CoordinateSystemAxis: descriptionReference: urn:ogc:def:axis-name:EPSG::9904 identifier: urn:ogc:def:axis:EPSG::114 axisAbbrev: H axisDirection: up code: urn:ogc:def:crs:EPSG::5703 return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2010 FEMA Lidar: Ozaukee County (WI) alternateTitle: wi2010_fema_ozaukee_m5042_metadata date: (CI_Date) date: 2011-01-31 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 50191 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/50191 protocol: WWW:LINK-1.0-http--link name: Full Metadata Record description: View the complete metadata record on InPort for more information about this dataset. function: (CI_OnLineFunctionCode) information role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/dataviewer protocol: WWW:LINK-1.0-http--link name: Citation URL description: Online Resource function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: Citation URL description: Online Resource function: (CI_OnLineFunctionCode) download role: (inapplicable) presentationForm: (unknown) abstract: The Ozaukee AOI consists of one area encompassing the entire county. Ground Control is collected throughout the AOI for use in the processing of LiDAR data to ensure data accurately represents the ground surface. QA/QC checkpoints, (FVA and CVA - see Ground Control process step for further information) also collected throughout the AOI, are used for independent quality checks of the processed LiDAR data. LiDAR acquisition products include Pre- and Post- flight reports which contain information on the flightlines, equipment parameters, and other pertinent acquisition details. The LiDAR Point Cloud product consists of tiles of LAS points which are partially classified such that the bare earth points can be calibrated to the ground surface and tested via the independent QC to ensure the ground surface is accurately represented. The LiDAR processing product consists of LAS points which are fully classified with the bare earth points tested via the independent QC to ensure the ground surface is accurately represented. This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. purpose: Provide high resolution terrain elevation and land cover elevation data. Terrain data is used to represent the topography of a watershed and/or floodplain environment and to extract useful information for hydraulic and hydrologic models. status: (MD_ProgressCode) completed pointOfContact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) pointOfContact pointOfContact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) custodian resourceMaintenance: (MD_MaintenanceInformation) maintenanceAndUpdateFrequency: (MD_MaintenanceFrequencyCode) notPlanned graphicOverview: (MD_BrowseGraphic) fileName: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/5042/supplemental/wi2010_fema_ozaukee_m5042.kmz fileDescription: This graphic shows the lidar coverage for the 2010 project for the coastal region of Wisconsin in Ozaukee County. fileType: kmz descriptiveKeywords: (MD_Keywords) keyword: Land Surface type: (MD_KeywordTypeCode) theme descriptiveKeywords: (MD_Keywords) keyword: Lidar - partner (no harvest) type: (MD_KeywordTypeCode) project thesaurusName: (CI_Citation) title: InPort date: (inapplicable) resourceConstraints: (MD_LegalConstraints) useConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: Cite As: OCM Partners, [Date of Access]: 2010 FEMA Lidar: Ozaukee County (WI) [Data Date Range], https://www.fisheries.noaa.gov/inport/item/50191. resourceConstraints: (MD_Constraints) useLimitation: NOAA provides no warranty, nor accepts any liability occurring from any incomplete, incorrect, or misleading data, or from any incorrect, incomplete, or misleading use of the data. It is the responsibility of the user to determine whether or not the data is suitable for the intended purpose. resourceConstraints: (MD_LegalConstraints) accessConstraints: (MD_RestrictionCode) otherRestrictions useConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: Access Constraints: None | 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. Acknowledgement of FEMA would be appreciated in products derived from these data. This digital data is produced for the purposes of updating/creating a DFIRM database. | Distribution Liability: Any conclusions drawn from the analysis of this information are not the responsibility of TerraPoint, RIGID, NOAA, the Office for Coastal Management or its partners. resourceConstraints: (MD_SecurityConstraints) classification: (MD_ClassificationCode) unclassified classificationSystem: (missing) handlingDescription: (missing) aggregationInfo: (MD_AggregateInformation) aggregateDataSetName: (CI_Citation) title: NOAA Data Management Plan (DMP) date: (unknown) identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: 50191 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/50191.pdf protocol: WWW:LINK-1.0-http--link name: NOAA Data Management Plan (DMP) description: NOAA Data Management Plan for this record on InPort. function: (CI_OnLineFunctionCode) information role: (inapplicable) associationType: (DS_AssociationTypeCode) crossReference spatialRepresentationType: (MD_SpatialRepresentationTypeCode) vector language: eng; US topicCategory: (MD_TopicCategoryCode) elevation extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -88.060711 eastBoundLongitude: -87.787129 southBoundLatitude: 43.190498 northBoundLatitude: 43.547961 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2010-10-31 endPosition: 2010-11-23 supplementalInformation: A footprint of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/5042/supplemental/wi2010_fema_ozaukee_m5042.kmz The preflight report of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/5042/supplemental/wi2010_fema_ozaukee_m5042_preflightreport.pdf The acquisition report of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/5042/supplemental/wi2010_fema_ozaukee_m5042_acquisitionreport.pdf The project report of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/5042/supplemental/wi2010_fema_ozaukee_m5042_lidarreport.pdf The survey report of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/5042/supplemental/wi2010_fema_ozaukee_m5042_surveyreport.pdf return to top contentInfo: (MD_FeatureCatalogueDescription) complianceCode: false language: LanguageCode: eng includedWithDataset: false featureCatalogueCitation: (CI_Citation) title: none date: (unavailable) return to top distributionInfo: (MD_Distribution) distributor: (MD_Distributor) distributorContact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) distributor transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=5042 protocol: WWW:LINK-1.0-http--link name: Customized Download description: Create custom data files by choosing data area, product type, map projection, file format, datum, etc. function: (CI_OnLineFunctionCode) download transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/5042/index.html protocol: WWW:LINK-1.0-http--link name: Bulk Download description: Simple download of data files. function: (CI_OnLineFunctionCode) download return to top dataQualityInfo: (DQ_DataQuality) scope: (DQ_Scope) level: (MD_ScopeCode) dataset report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: Deliverables were tested by for both vertical and horizontal accuracy. The vertical unit of the data file is in meters with 2-decimal point precision.; Quantitative Value: 0.051 meters, Test that produced the value: Calculated RMSEz from 21 RTK bare-earth points. See last page of the lidar report for clarity.; Quantitative Value: 0.223 meters, Test that produced the value: Consolidated Vertical Accuracy (CVA) equal to the 95th Percentile confidence level (RMSE[z] x 1.9600) calculated against the bare earth surface in all ground cover classes. Reported in meters. result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: Survey data have been checked for completeness, points have been collected in correct vegetation units, and distributed throughout the AOI. The terrain data have been checked for completeness against AOI polygons. No gaps as defined by FEMA Procedural Memo No. 61 are known to exist within the dataset. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: Survey data have been confirmed to be in proper units, coordinate systems and format. The terrain data have been confirmed as complete LAS format data files. Header files are in proper LAS format with content as specified by FEMA Procedural Memo No. 61. result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: GPS based surveys were utilized to support both processing and testing of LiDAR data within FEMA designated Areas of Interest (AOIs). Geographically distinct ground points were surveyed using GPS technology throughout the AOIs to provide support for three distinct tasks. Task 1 was to provide Vertical Ground Control to support the aerial acquisition and subsequent bare earth model processing. To accomplish this, survey-grade Trimble R-8 GPS receivers were used to collect a series of control points located on open areas, free of excessive or significant slope, and at least 5 meters away from any significant terrain break. Most if not all control points were collected at street/road intersections on bare level pavement. Task 2 was to collect Fundamental Vertical Accuracy (FVA) checkpoints to evaluate the initial quality of the collected point cloud and to ensure that the collected data was satisfactory for further processing to meet FEMA specifications. The FVA points were collected in identical fashion to the Vertical Ground Control Points, but segregated from the point pool to ensure independent quality testing without prior knowledge of FVA locations by the aerial vendors. Task 3 was to collect Consolidated Vertical Accuracy CVA) checkpoints to allow vertical testing of the bare-earth processed LiDAR data in different classes of land cover, including: Open (pavement, open dirt, short grass), High Grass and Crops, Brush and Low Trees, Forest, Urban. CVA points were collected in similar fashion as Control and FVA points with emphasis on establishing point locations within the predominant land cover classes within each AOI or Functional AOI Group. In order to successfully collect the Forest land cover class, it was necessary to establish a Backsight and Initial Point with the R8 receiver, and then employ a Nikon Total Station to observe a retroreflective prism stationed under tree canopy. This was necessary due to the reduced GPS performance and degradation of signal under tree canopy. dateTime: DateTime: 2010-01-01T00:00:00 processStep: (LI_ProcessStep) description: The R-8 receivers were equipped with cellular modems to receive real-time correction signals from the Keystone Precision Virtual Reference Station (VRS) network encompassing the Region 1 AOIs. Use of the VRS network allowed rapid collection times (~3 minutes/point) at 2.54 cm (1 inch) initial accuracy. All points collected were below the 8cm specification for testing 24cm, Highest category LiDAR data. To ensure valid in-field collections, an NGS monument with suitable vertical reporting was measured using the same equipment and procedures used for Control, FVA and CVA points on a daily basis. The measurement was compared to the NGS published values to ensure that the GPS collection schema was producing valid data and as a physical proof point of quality of collection. Those monument measurements are summarized in the Accuracy report included in the data delivered to FEMA. 20 FVA points and 15 additional CVA points across the group of AOIs were collected. 20 FVA points are necessary to allow testing to CE95 ? 1 point out of 20 may fail vertical testing and still allow the entire dataset to meet 95% accuracy requirements.In similar fashion, 20 CVA points are necessary to test to CE95 as discussed above. 15 CVA points were collected with the intention at the outset that 5 of the collected FVAs would perform double?duty as Open-class CVA points, to total 20 CVAs per AOI. The following software packages and utilities were used to control the GPS receiver in the field during data collection, and then ingest and export the collected GPS data for all points: Trimble Survey Controller, Trimble Pathfinder Office. The following software utilities were used to translate the collected Latitude/Longitude Decimal Degree HAE GPS data for all points into Latitude/Longitude Degrees/Minutes/Seconds for checking the collected monument data against the published NGS Datasheet Lat/Long DMS values and into UTM NAD83 Northings/Eastings: U.S. Army Corps of Engineers CorpsCon, National Geodetic Survey Geoid09 NAVD88. MSL values were determined using the most recent NGS-approved geoid model to generate geoid separation values for each Lat/Long coordinate pair. In this fashion, Orthometric heights were determined for each Control, FVA and CVA point by subtracting the generated Geoid Separation value from the Ellipsoidal Height (HAE) for publication and use as MSL NAVD88(09). dateTime: DateTime: 2010-01-01T00:00:00 processStep: (LI_ProcessStep) description: Using a Optech Gemini LiDAR system, 56 flight lines of highest density (Nominal Pulse Spacing of 1.0m) were collected over the Ozaukee area. A total of five missions were flown: November 11, 2010, November 15, 2010, 2 on November 16, 2010, November 23, 2010. Seven airborne global positioning system (GPS) base stations were used to support the LiDAR data acquisition: WIM5, SHAN, CHON, FOLA, WEBE, RASN, SIWI. Coordinates are available in the Post-Flight Aerial Acquisition Report. dateTime: DateTime: 2010-01-01T00:00:00 processStep: (LI_ProcessStep) description: Raw airborne GPS and IMU data were extracted from Applanix CARD. The GPS data was differentially processed in PosGPS and integrated with the IMU data in PosPAC. The GPS/IMU data is processed in Applanix to derive a smoothed best estimate of trajectory (SBET).The SBET was used to reduce the LiDAR slant range measurements to derive the Return measurement for each LiDAR pulse for all LiDAR pulses within for each flight line. The coverage was imported into TerraScan and tiled into 1500m x 1500m tiles. An initial accuracy assessment is done using the ground point survey data. The data then is classified to extract a bare earth digital elevation model (DEM). Once all project data was imported and classified, the survey ground control data was imported again and calculated against the LAS Class 2 (Ground) data for an accuracy assessment. As a QC measure, a routine was used to generate accuracy statistical reports by comparison among LiDAR points, ground control, and triangulated irregular networks (TIN). Any systematic bias in the data is removed to meet or exceed the vertical accuracy requirements. dateTime: DateTime: 2011-01-01T00:00:00 processStep: (LI_ProcessStep) description: The calibrated and filtered LiDAR point cloud was hand checked for accuracy. All points were placed in one of the following categories: 1 Unclassified, 2 Ground, 7 Noise, and 12 Overlap Points. Model Key points were then generated from the Ground points and placed in Category 8. Requested elevation values to were then provided to CompassData for their evaluation of the Consolidated Vertical Accuracy (CVA). dateTime: DateTime: 2011-01-01T00:00:00 processStep: (LI_ProcessStep) 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 16 N, NAVD88 (orthometric) 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. Erroneous elevations were removed. 3. The data were converted from NAVD88 (orthometric) heights in meters to GRS80 (ellipsoid) heights in meters using Geoid 09. 4. The LAS data were sorted by latitude and the headers were updated. dateTime: DateTime: 2016-05-24T00:00:00 processStep: (LI_ProcessStep) description: The vertical values in this data set have been converted to reference North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters, using the GEOID18 grids provided by the National Geodetic Survey. Any datum and projection transformations were then done with the Office for Coastal Management 'datum_shift' program. Compression to an LAZ file was done with the LAStools 'laszip' program and can be unzipped with the same free program (laszip.org) Processing notes: dateTime: DateTime: 2023-07-01T07:35:02 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |