8000 Normalize when preparing intensity raster from multiple 3DEP projects · Issue #34 · uw-cryo/lidar_tools · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Normalize when preparing intensity raster from multiple 3DEP projects #34
Open
@dshean

Description

@dshean

Some vendors provide intensity as UInt8, others as UInt16, and it's not always clear how they've normalized the relative raster intensity values they deliver (in most cases, these are raw intensity/amplitude, not estimates of reflectance scaled by range, which would be nice). This is not an issue for elevation values, fortunately.

See attached example (note low contrast intensity for tiles near southern portion of AOI)

Image

I don't have a simple solution to this right now, but just something to be aware of. Likely need to use global point cloud statistics for intensity values of each 3DEP project within the AOI, and normalize each project accordingly.

I also noticed the output intensity raster is Float32. I think we can likely get away with scaled UInt16, maybe even UInt8. I remember some discussion on data types and filesize optimization with Karthik last year.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0