| 2011 FEMA Lidar: Modoc, California | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:61263 language: LanguageCode: eng characterSet: (MD_CharacterSetCode) UTF8 hierarchyLevel: (MD_ScopeCode) dataset hierarchyLevelName: Elevation 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: Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) pointOfContact dateStamp: DateTime: 2020-09-15T00:00:00 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: (MD_VectorSpatialRepresentation) topologyLevel: (MD_TopologyLevelCode) geometricObjects: (MD_GeometricObjects) geometricObjectType: (MD_GeometricObjectTypeCode) point geometricObjectCount: 355533786 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 (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: 2011 FEMA Lidar: Modoc, California date: (CI_Date) date: 2012-02-10 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 61263 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/htdata/lidar4_z/geoid18/data/9162/supplemental/Modoc_Final_Report.pdf protocol: WWW:LINK-1.0-http--link name: Dataset report description: Link to data set report. function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/htdata/lidar4_z/geoid18/data/9162/supplemental/BakerAECOM_LiDAR_Modoc_Final_QAQC_Report.pdf protocol: WWW:LINK-1.0-http--link name: Dataset report description: Link to data set report. function: (CI_OnLineFunctionCode) download 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: NOAA's Office for Coastal Management (OCM) Data Access Viewer (DAV) description: The Data Access Viewer (DAV) allows a user to search for and download elevation, imagery, and land cover data for the coastal U.S. and its territories. The data, hosted by the NOAA Office for Coastal Management, can be customized and requested for free download through a checkout interface. An email provides a link to the customized data, while the original data set is available through a link within the viewer. function: (CI_OnLineFunctionCode) download role: (inapplicable) presentationForm: (unknown) abstract: Digital Mapping Inc. collected lidar data for the Federal Emergency Management Agency (FEMA) in Region 9, Modoc, CA. The dataset encompasses 43 square miles, while the derived bare earth digital elevation model covers a 21 square mile subset of this area (linked in the Related Items section, below). Nominal pulse spacing of collection was <1 m. This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. purpose: 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. (Source: FEMA Guidelines and Specifications, Appendix N) credit: FEMA, Digital Mapping Inc. for the BakerAECOM, LLC The custom download may be cited as National Oceanic and Atmospheric Administration (NOAA) Digital Coast Data Access Viewer. Charleston, SC: NOAA Office for Coastal Management. Accessed Oct 20, 2020 at https://coast.noaa.gov/dataviewer. 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: 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: 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://coast.noaa.gov/htdata/lidar4_z/geoid18/data/9162/supplemental/extent_Modoc_CA_m9162.kmz fileDescription: This graphic displays the footprint for this lidar data set. fileType: KML descriptiveKeywords: (MD_Keywords) keyword: Earth Science > Land Surface > Topography > Terrain Elevation keyword: Earth Science > Oceans > Bathymetry/Seafloor Topography > Bathymetry > Coastal Bathymetry keyword: Earth Science > Oceans > Coastal Processes > Coastal Elevation type: (MD_KeywordTypeCode) theme thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Science Keywords date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Breaklines keyword: Digital Terrain Model keyword: Elevation Data keyword: Land Surface keyword: LIDAR keyword: Topography type: (MD_KeywordTypeCode) theme thesaurusName: (CI_Citation) title: FEMA NFIP Topic Category date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Continent > North America > United States Of America keyword: Vertical Location > Land Surface keyword: Vertical Location > Seafloor type: (MD_KeywordTypeCode) place thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Location Keywords date: (missing) descriptiveKeywords: (MD_Keywords) keyword: COMMUNITY Modoc County keyword: COUNT-FIPS 049 keyword: COUNTY Modoc keyword: FEMA-CID 060192 keyword: Region 09 keyword: STATE CA type: (MD_KeywordTypeCode) place thesaurusName: (CI_Citation) title: Geographic Names Information System date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Earth Remote Sensing Instruments > Active Remote Sensing > Profilers/Sounders > Lidar/Laser Sounders > LIDAR > Light Detection and Ranging type: (MD_KeywordTypeCode) instrument thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Instrument Keywords date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Aircraft > Aircraft type: (MD_KeywordTypeCode) platform thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Platform Keywords date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Lidar - partner (no harvest) type: (MD_KeywordTypeCode) project thesaurusName: (CI_Citation) title: InPort date: (inapplicable) 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. | Distribution Liability: No warranty expressed or implied is made by FEMA regarding the utility of the data on any other system nor shall the act of distribution constitute any such warranty. Any conclusions drawn from the analysis of this information are not the responsibility of 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: 61263 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/61263.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 spatialResolution: (MD_Resolution) distance: Distance: .5 language: eng; US topicCategory: (MD_TopicCategoryCode) elevation environmentDescription: GeoCue, TerraScan, TerraMatch, MicroStation, DashMap, Windows XP extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -120.58570417 eastBoundLongitude: -120.44318533 southBoundLatitude: 41.3914362 northBoundLatitude: 41.51813209 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2011-05-04 return to top contentInfo: (MD_FeatureCatalogueDescription) complianceCode: false language: LanguageCode: eng includedWithDataset: false featureCatalogueCitation: (CI_Citation) title: Appendix N of FEMA Guidelines and Specifications for FEMA Flood Hazard Mapping Partners contains a detailed description of the data themes and references to other relevant information. date: (unavailable) return to top distributionInfo: (MD_Distribution) distributionFormat: (MD_Format) name: Zip version: (missing) fileDecompressionTechnique: Zip distributionFormat: (MD_Format) name: LAZ version: (missing) 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: 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=9162/details/9162 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. A new metadata will be produced to reflect your request using this record as a base. Change to an orthometric vertical datum is one of the many options. function: (CI_OnLineFunctionCode) download transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://coast.noaa.gov/htdata/lidar3_z/geoid18/data/9162 protocol: WWW:LINK-1.0-http--link name: Bulk Download description: Bulk download of data files in LAZ format, geographic coordinates, orthometric heights. Note that the vertical datum (hence elevations) of the files here are different than described in this document. They will be in an orthometric datum. function: (CI_OnLineFunctionCode) download return to top dataQualityInfo: (DQ_DataQuality) scope: (DQ_Scope) level: (MD_ScopeCode) dataset report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Horizontal Positional Accuracy evaluationMethodDescription: Quantitative value: , Test that produced the valued: result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: Modoc tested 0.449 ft (13.69 centimeters) Fundamental Vertical Accuracy at 95% confidence level in open terrain using RMSEz x 1.9600. The Modoc FVA value passes the minimum requirement of 24.5 centimeters. Fundamental Vertical Accuracy (FVA) is defined as “The value by which vertical accuracy can be equitably assessed and compared among datasets. The FVA is determined with vertical checkpoints located only in open terrain, where there is a very high probability that the sensor will have detected the ground surface.” (FEMA Procedure Memorandum No. 61‐ Standards for LiDAR and Other High Quality Digital topography, September, 27, 2010, Page 6) The twenty‐five (25) points are to be evenly distributed throughout the project area. See QA/QC Report for more details. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: The Terrain data are consistent with the Elevation dataset. A comparison of profile plots with the flow vector data confirms that flow vectors are correctly drawn. Flood hazard boundaries do not extend beyond the ExternalBoundary, if exists. result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: 1-Acqusition: Modoc LIDAR acquisition consisted of 26 flight lines with 2 cross flights. Alturas Airport was flown for the airport calibration. Two base stations were used for the project. The LIDAR misson was flown in 05/04/2011. ALTM Gemini was used as the LIDAR scanner. LIDAR flight settings were: Altitude (m): 1200 System PRF (kHz): 70 Scan Freq (Hz): 39 Scan Angle +/-: 17 Desired Res (m): 0.804 PPM^2: 1.55 2-Processing: LIDAR data were processed and fit to the ground using DASHMap, GeoCue, TerraScan and TerraMatch softwares. All the data were calibrated to determine and eliminate systematic biases that might occur within the hardware of the ALTM Gemini system. A total of 11 aerial targets were surveyed and used to fit the LIDAR data to the ground. Ground point were removed from the top of bridges. LAS tiles that touch processing limit are classified however QA\QC of the ground points were done to the data which were within processing limit. LAS tiles are classified into 6 classes: 1 processed, but unclassified 2 bare-earth ground 7 noise 9 water 10 ignored 11 withheld 3-Breaklines: Breaklines were compiled for streams, lakes, ponds and man-made features -bridges, culverts- that constrict or control the flow of water in 3D data collection mode from LIDAR data. Breaklines were not collected for the areas outside the processing limit. Ponds and lakes are collected as polygons. They have constant elevation and they have elevation values less than the surrounding ground points. For dry streams and streams narrower than 50 feet single stream breaklines were collected. For streams wider than 50 feet edges of the streams were collected along with stream centerline. The project area was relatively flat which made it some of the streams having single elevation across. Stream breaklines were broken at culverts and not broken at bridges. Culvert breaklines snap to stream endpoints on both sides and have the same elevation as the stream breakline at the snapping location. Top and bottom of the bridge breaklines were collected. Breaklines are delivered as ESRI geodatabase file format. Topology rules were applied to the breaklines. Breaklines snap to each other, split at intersections, not self-intersect or overlap each other. 4-Low Confidence Areas: Areas that may not meet the data accuracy requirements due to heavy vegetation were compiled as 2D polygon. Special effort was given to minimize these areas. Ground points were tried to be classified from dense vegetation areas where possible using manual techniques. processStep: (LI_ProcessStep) description: NOAA Office for Coastal Management (OCM) received 92 lidar point cloud files in las format. The files contained lidar elevation and intensity measurements. The data were in California State Plane Zone 1 (NAD83), international feet coordinates and NAVD88 (Geoid03) elevations in international feet. The data were classified as: 1-Unclassified, 2-Ground, 7-Noise, 9-Water, 10-Ignored Ground & 11-Withheld. OCM processed all classifications of points to the Digital Coast Data Access Viewer (DAV). OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. An internal OCM script was run to check the number of points by classification and by flight ID and the gps and intensity ranges. 2. Internal OCM scripts were run on the laz files to convert from orthometric (NAVD88) elevations to ellipsoid elevations using the Geoid 03 model, to convert to geographic coordinates, to convert from vertical units feet to meters, to assign the geokeys, to sort the data by gps time, and zip the data to database and to http. processor: (CI_ResponsibleParty) organisationName: Office for Coastal Management role: (CI_RoleCode) processor source: (LI_Source) description: Source Contribution: Digital Mapping Inc. sourceCitation: (CI_Citation) title: LIDAR Data date: (CI_Date) date: 2012-02-10 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: Digital Mapping Inc role: (CI_RoleCode) originator sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2011-05-04 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: 2020-10-20T05:17:13 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |