| 2017 Maryland Lidar: Anne Arundel County, MD | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:64273 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: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) pointOfContact dateStamp: DateTime: 2023-05-30T18:10:32 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: 24380292728 return to top referenceSystemInfo: return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) authority: (CI_Citation) title: NAD83(HARN) 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/4152/export/?format=gml role: (missing) code: urn:ogc:def:crs:EPSG:4152 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: 2017 Maryland Lidar: Anne Arundel County, MD alternateTitle: 2017_md_anne_arundel_m9234 date: (CI_Date) date: 2017 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 64273 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/64273 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: 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: This metadata record describes the lidar point cloud for the 2017 Anne Arundel LiDAR project covering approximately 450 square miles in Anne Arundel County in Maryland. This dataset meets QL1 accuracy and point density requirements. This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. purpose: To acquire detailed surface elevation data for use in conservation planning, design, research, floodplain mapping, dam safety assessments, and hydrologic modeling. The point clouds are suitable for 1 foot contour generation. USGS LiDAR Base Specification 1.2, QL1. credit: State of Maryland 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 Aug 01, 2023 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: 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) unknown graphicOverview: (MD_BrowseGraphic) fileName: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/9234/supplemental/anne_arundel2017_extent_m9234.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) edition: 12.3 descriptiveKeywords: (MD_Keywords) keyword: CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA keyword: VERTICAL LOCATION > LAND SURFACE type: (MD_KeywordTypeCode) place thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Location Keywords date: (missing) edition: 12.3 descriptiveKeywords: (MD_Keywords) keyword: LIDAR > Light Detection and Ranging type: (MD_KeywordTypeCode) instrument thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Instrument Keywords date: (missing) edition: 14.9 descriptiveKeywords: (MD_Keywords) keyword: Airplane > Airplane type: (MD_KeywordTypeCode) platform thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Platform Keywords date: (missing) edition: 14.9 descriptiveKeywords: (MD_Keywords) keyword: ALS70 keyword: Bare Earth keyword: Contour keyword: Grid keyword: Ground points keyword: LAS keyword: Lidar keyword: Topography keyword: Water points keyword: laser keyword: mapping keyword: point cloud keyword: Anne Arundel keyword: Maryland keyword: United States type: (MD_KeywordTypeCode) theme thesaurusName: (CI_Citation) title: MD date: (missing) 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]: 2017 Maryland Lidar: Anne Arundel County, MD [Data Date Range], https://www.fisheries.noaa.gov/inport/item/64273. 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: The digital data have been tested and their documentation carefully reviewed. However, the client and its representatives make no warranty or representation, either expressed or implied, with respect to the digital data and their documentation, their quality, performance, merchantability, or fitness for a particular purpose. The digital data are distributed on "as is" basis, and the user assumes all risk to their quality, the results obtained from their use, and the performance of the data. In no event will the client be liable for any direct, indirect, special, incidental or consequential damages resulting from and defect in the State of Maryland or in their documentation. This disclaimer of warranty is exclusive and in lieu of all others, oral or written, express or implied. No agent or employee is authorized to make any modification, extension, or addition to this 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: 64273 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/64273.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: .35 language: eng; US topicCategory: (MD_TopicCategoryCode) elevation environmentDescription: Microsoft Windows 7; ESRI ArcCatalog 9.3.1.1850 extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -76.843043 eastBoundLongitude: -76.395212 southBoundLatitude: 38.711239 northBoundLatitude: 39.237272 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2017-03-02 endPosition: 2017-03-05 return to top contentInfo: (MD_FeatureCatalogueDescription) complianceCode: false language: LanguageCode: eng includedWithDataset: false featureCatalogueCitation: (CI_Citation) title: USGA Base Specification 1.2, QL1 meeting 19.6 cm NVA 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: 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=9234/details/9234 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://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/9234/index.html 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: Horizontal positional accuracy for the Anne Arundel LiDAR project is dependent upon the quality of the GPS/INS solution, sensor calibration and ground conditions at the time of data capture. The data set was produced to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a 1.0 meter RMSEx/RMSEy. Quantitative value: 1.0, Test that produced the valued: This value is computed by comparing ground control to a DEM derived from the classified LiDAR data and represents the RMSE of residuals on controls within the project area. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: For the DEM data derived from the classified point cloud, the NVA and VVA were computed. The vertical accuracy was tested with independent survey check points located in various terrain types within the project area. These check points were not used in the calibration or post processing of the lidar point cloud data. The survey check points were distributed throughout the block area. Specifications for this project require that the NVA be 19.6 cm or better @ 95 percent confidence level. Quantitative value: 0.081m RMSE, or 0.16m NVA @ 95 percent Confidence Level 0.087m RMSE, or 0.14m VVA @ 95th Percentile, Test that produced the value: The NVA was tested using 41 independent survey check points located in bare earth terrain types within the project area. The 41 independent check points contained all NVA points and were surveyed using static GPS base stations collecting point location for 20 minute intervals. Elevations were measured for the x,y,z location of each check point. Elevations interpolated from the DEM surface were then compared to the elevation values of the surveyed control. This data set was tested to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a 10cm RMSEz Vertical Accuracy Class. Actual NVA accuracy was found to be RMSEz = 8.1cm, equating to +/- 16cm at 95% confidence level. The VVA was tested using 31 independent survey check points located in various vegetation terrain types within the project area. The 31 independent check points were surveyed using static GPS base stations collecting point location for 20 minute intervals. Elevations were measured for the x,y,z location of each check point. Elevations interpolated from the DEM surface were then compared to the elevation values of the surveyed control. This data set was tested to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a 10cm RMSEz Vertical Accuracy Class. Actual VVA accuracy was found to be +/- 14cm at the 95th percentile. result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: LiDAR data is collected for the project area. Post processing of the simultaneously acquired GPS/INS is performed and applied to the laser returns to output a point cloud in the specified project coordinate system and datums. The point cloud data is then subjected to automated classification routines to assign all points in the point cloud to ground, water, overlap and unclassified point classes. Anomalous laser returns that occur infrequently are removed entirely from the data set. Once clean bare earth points are established, all products are created. The products are then compared to the survey checkpoints. These accuracies must pass the NVA and VVA accuracy specifications. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: LiDAR data is collected within the project area and processed. After all of the deliverables were created, the dataset was verified against control. Well-distributed control was collected for the project area. result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: At selected locations throughout the site, accurate GPS coordinates and elevations are surveyed and the points are marked with targets. dateTime: DateTime: 2017-01-01T00:00:00 processStep: (LI_ProcessStep) description: New LiDAR data is captured for the project area using a Leica ALS70 w/MPiA LiDAR instrument an integrated IPAS20 GPS/INS system mounted within a Aero Commander twin engine airplane. dateTime: DateTime: 2017-01-01T00:00:00 processStep: (LI_ProcessStep) description: The airborne GPS data is post-processed in Intertial Explorer software and LEICA CloudPro software to determine the LiDAR sensor's angle and orientation in the terrain (project) coordinate system and datums during the survey. dateTime: DateTime: 2017-01-01T00:00:00 processStep: (LI_ProcessStep) description: The post processed GPS/INS solution is applied to the raw lidar data to orient and project the data points into the project area reference system as an unclassified point cloud. dateTime: DateTime: 2017-01-01T00:00:00 processStep: (LI_ProcessStep) description: The georeferenced lidar data is then classified and edited in Terrasolid Terrascan software. Data is classified to produce: Class 1: unclassified, Class 2: ground, Class 7: low point, Class 9: water, Class 10: ignored ground, Class 17: bridge deck, Class 18: high noise. dateTime: DateTime: 2017-01-01T00:00:00 processStep: (LI_ProcessStep) description: The data was downloaded from Maryland iMAP (https://imap.maryland.gov) in LAZ format with compatibility mode. The following operations were done on the data: 1) converted from NAD83(HARN) Maryland state plane feet to NAD83(HARN) geographic decimal degrees. 2) converted from NAVD88(GEOID12b) feet to NAD83(HARN) ellispoid meters. 3) LAZ 1.2 compatibility mode to LAZ 1.4 native mode. 4) Points below -30 feet were removed. Data was then ingested into the Digital Coast Data Access Viewer for distribution. dateTime: DateTime: 2021-02-09T00:00:00 processor: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor source: (LI_Source) description: Source Contribution: The classified lidar point cloud is used to derive various data products such as, but not limited to, bare earth gridded DEM, triangulated irregular networks (TIN), contours, digital surface models (DSM). The output format is fully compliant LAS v1.4, Point Record Format 6 scaleDenominator: (MD_RepresentativeFraction) denominator: 1200 sourceCitation: (CI_Citation) title: Classified lidar date: (missing) citedResponsibleParty: (CI_ResponsibleParty) organisationName: Sanborn Map Company Inc. role: (CI_RoleCode) originator sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2017 source: (LI_Source) description: Source Contribution: Targeted ground control is used to create a digital control file and control report as well as QC check of LiDAR accuracy. Predefined points (NGS when available) within the project area are targeted. sourceCitation: (CI_Citation) title: Ground control date: (CI_Date) date: 2010-01-01 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: Sanborn Map Company Inc. role: (CI_RoleCode) originator sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2017 source: (LI_Source) description: Source Contribution: Aerial LiDAR and GPS/IMU data are recorded for the defined project area at an altitude, flight speed, scanner swath width and scanner pulse frequency to achieve the design goals of the project. sourceCitation: (CI_Citation) title: LiDAR Data date: (missing) citedResponsibleParty: (CI_ResponsibleParty) organisationName: Sanborn Map Company Inc. role: (CI_RoleCode) originator sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2017 source: (LI_Source) description: Source Contribution: Post processed GPS/INS is applied to the lidar point data to georeference each point in the project coordinate system scaleDenominator: (MD_RepresentativeFraction) denominator: 1200 sourceCitation: (CI_Citation) title: Post processed GPS/INS date: (missing) citedResponsibleParty: (CI_ResponsibleParty) organisationName: Sanborn Map Company Inc. role: (CI_RoleCode) originator sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2017 source: (LI_Source) description: Source Contribution: The post processed lidar data has been projected and oriented in the specified coordinate system as an un-classified point cloud. scaleDenominator: (MD_RepresentativeFraction) denominator: 1200 sourceCitation: (CI_Citation) title: Post processed lidar date: (missing) citedResponsibleParty: (CI_ResponsibleParty) organisationName: Sanborn Map Company Inc. role: (CI_RoleCode) originator sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2017 source: (LI_Source) description: Source Contribution: The tile definition defines discreet non-overlapping rectangular areas used as cut lines to break up the large classified lidar dataset into smaller, more manageable data tiles. Each tile is 1800m by 1200m in dimension. scaleDenominator: (MD_RepresentativeFraction) denominator: 1200 sourceCitation: (CI_Citation) title: Tile Definition date: (missing) citedResponsibleParty: (CI_ResponsibleParty) organisationName: State of Mayland role: (CI_RoleCode) originator sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2017 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-08-01T07:27:56 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |