Data prop for custom layer that doesn't attempt to fetch the full URL

[kylebarron]

I'm making a custom layer for GeoTIFF files. I'd like to use the name data for the input prop because that's most common for other deck.gl layers. In order to do this it looks like I must use a loaders.gl Loader.

However, it looks like it's impossible for loaders.gl Loaders to not try to fetch the entire input buffer. Is it possible to turn off the automatic deck.gl-loaders.gl integration for my layer, so that I can inject my own custom handling of the data prop? Or is there a way in loaders.gl to avoid having it always fetch the entire data input when a URL?

I see there's some work in loaders.gl about "sources". But based on type hints it looks like deck.gl doesn't allow those for the data prop.

[ibgreen]

Yes, the source support is not ready for upstreaming into deck.gl. However, I did some work on a TileSourceLayer.

• I started upstreaming it to deck.gl-community as a step towards grooming it for deck.gl inclusion.
• There is a precursor example here in loaders.gl https://github.com/visgl/loaders.gl/blob/master/examples/website/tiles/components/tile-source-layer.ts#L36
• Let me know if I can help, I am trying to get loaders.gl 4.4 wrapped up, still time at least for smaller changes.
• Geting a GeoTIFFSource in place would really round of the data sources even a partial collaboration on that would be great. I assume the tiling is not regular so it needs its own more advanced Source type?

Is it possible to turn off the automatic deck.gl-loaders.gl integration for my layer, so that I can inject my own custom handling of the data prop? Or is there a way in loaders.gl to avoid having it always fetch the entire data input when a URL?

You should be able to supply a custom fetch function via deck.gl loadOptions, would that help?

[kylebarron]

Thanks for the response.

I'll try a custom fetch function.

I have a tile layer that manages generic tile grids and I have deep connections into a geotiff loader, that I don't think would work in a more generic Source setup.

I plan to open source it soon, and then we can discuss more, but I just got selected for a 3-week jury duty, so the timeline will be delayed a bit.