Skip to content

Allow custom dtypes and fills in _zonal_stats_rasterize #95

@martinfleis

Description

@martinfleis

I suggest that instead of forcing a float32 dtype, it's better to check the input raster data type first. If the input data type is float64 or float32, the output should use the original data type. If integer, then the output can use float32.

Also, I think it's better to set fill and dtype as two input parameters for the _zonal_stats_rasterize function so that the user can be aware of that and may change it as needed for memory efficiency. Cheers.

Originally posted by @coolzhao in #85

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