Skip to content

Handle GDALRasterIO errors #111

@ksshannon

Description

@ksshannon

The code base is peppered with un-caught CPLErrs from GDALRasterIO(). We assume these reads and writes always occur without error. We should probably either deal with these errors explicitly, or wrap the calls with a function that throws. There are a lot of these, and if something goes wrong in one, it will probably be impossible to find.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions