Skip to content

Allow working with larger-than-memory rasters  #58

Description

@tomalrussell

E.g. global ~90m map may be on the order of 100GBs if represented uncompressed in memory.

snail.intersection.get_raster_values_for_splits currently takes raster data as a 2D ndarray.

When attributing values from rasters to split and indexed geometries, find an approach which doesn't assume that the full raster array can be loaded in memory.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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