Skip to main content
U.S. flag

An official website of the United States government

MSHR NoData value

By NGP Standards and Specifications

This revision stipulates a specific NoData value required for Maximum Surface Height Rasters (MSHRs). The current MSHR language in the LBS pertaining to Raster Creation, as well as file format and version control, do not specify how the NoData value is to be populated.

 

Return to Revision Status Page

Introduction

For LBS 2025 Rev. A, Maximum Surface Height Rasters (MSHRs) shall have the NoData value set to –999999, aligning with the required NoData value of the corresponding Digital Elevation Model (DEM) tiles. Having a NoData value in the MSHRs align with the NoData value in the DEMs ensures consistency across validation checks between the MSHRs and DEMs.  

Current requirement: 

in LBS 2022 Rev A: Appendix 1: Maximum Surface Height Rasters:

Maximum Surface Height Raster

  • Raster Creation:
    • Spatial resolution (pixel dimension) of the images shall be twice (2x) the bare-earth DEM deliverable cell size in the project’s linear unit (meters or feet).
    • The grid cell size shall be specified and described in the associated mapping report (see Deliverables for the Lidar Mapping Report requirements).
    • TIN methods shall not be used to create the rasters.
    • The MSHR shall be representative of the associated data delivery.
    • The raster shall be in the same coordinate reference system (CRS) as the point cloud data to ensure alignment with the point cloud.
    • All returns shall be used to create the raster.
    • Voids shall not be filled.
    • Points flagged as withheld shall be excluded.
    • The raster shall be built with the highest elevation point value from each pixel.
    • The raster shall be 32-bit, floating point.
    • Delivery shall be tiles in the same tiling scheme as the bare-earth deliverable.

Change to: 

(Modifications are in bold text.)

Maximum Surface Height Raster

  • Raster Creation:
    • Spatial resolution (pixel dimension) of the images shall be twice (2x) the bare-earth DEM deliverable cell size in the project’s linear unit (meters or feet).
    • The grid cell size shall be specified and described in the associated mapping report (see Deliverables for the Lidar Mapping Report requirements).
    • TIN methods shall not be used to create the rasters.
    • The MSHR shall be representative of the associated data delivery.
    • The raster shall be in the same coordinate reference system (CRS) as the point cloud data to ensure alignment with the point cloud.
    • All returns shall be used to create the raster.
    • Voids shall not be filled.
    • Points flagged as withheld shall be excluded.
    • The raster shall be built with the highest elevation point value from each pixel.
    • The raster shall be 32-bit, floating point.
    • Delivery shall be tiles in the same tiling scheme as the bare-earth deliverable.
    • The NODATA value of ‘-999999’ shall be defined in GDA ATA tag #4211 L_NOD3. 
Was this page helpful?