fix(deck.gl-geotiff): raise COG open failures through onError

[earlybard]

What I am changing

COGLayer and MultiCOGLayer kick off the GeoTIFF open from updateState and never look at the promise again. If the header fetch or CRS lookup fails you get an unhandled rejection in the console, onError stays silent, and the layer just sits there empty.

Both now catch that and hand it to Layer.raiseError, so props.onError fires, and Deck's onError after it unless you return true.

How you can test it

new MultiCOGLayer({
  id: "missing",
  sources: { red: { url: "https://example.com/missing.tif" } },
  composite: { r: "red" },
  onError: (error) => console.warn(error.message, error.cause),
});

On main: unhandled rejection, no callback. With this: one loading COG sources: … call. There's a unit test per layer too, and both fail on main.

Related Issues

Closes #205. Takes over from #206, which did the same for COGLayer only and has drifted out of date.

AI disclosure: written with Claude Code as a code assistant, reviewed by me.

[kylebarron]

Thanks @earlybard. Can I ask how you're using deck.gl-raster?

[earlybard]

Hey @kylebarron. I'm building a COG viewer for open Geoscience Australia data. I'm:

• Streaming 16 bit COGs to the browser, rendering with MapLibre + deck.gl
• Using MosaicLayer + MultiCOGLayer to render many scenes as a mosaic
• Rescaling to 8 bit dynamically, allowing histogram manipulation
• Supporting band selection and mixing.

There are some tricky mosaic-like issues I'll be tackling next, e.g. controlling z-index of scenes within the mosaic, and not rendering fully occluded scenes.

Thanks again!

[kylebarron]

Oh interesting is raiseError an upstream method in the base deck.gl Layer?

[earlybard]

Yep it is. Marked (Internal) in the docstring but the types are public. Not sure how you feel about that!

My use case is a display in my UI if a GeoTIFF fails to load.

The alternative is a new prop like onGeoTIFFError, but this seemed easier + hooks into Deck's error handling.

[kylebarron]

Thanks!