Ib Green

Thanks for investigating, this makes sense. It is not really a bug then, but nevertheless, it would be good to get a clean test run. There is a `test/utils/tape-assertions` that...

@kylebarron @NikolayActionEngine

Handling 429s with exponential backoff will require actually doing the fetch. If we are OK with this being part of this class, then we could add a `RequestScheduler.fetch()` style API....

We may want to: - make sure we can specify alternative versions of fetch. Should likely align with the [Fetch Option RFC](https://github.com/visgl/loaders.gl/blob/master/dev-docs/RFCs/v2.0/fetch-option-rfc.md) - bind this method so that `requestScheduler.fetch` can...

We perhaps also do an intermediate interface that doesn't require fetch overloading The schedule could return a `reschedule` callback: ```js let token = await requestScheduler.scheduleRequest(...); while (token) { const {done,...

Some time ago I did a test implementation of a `flatgeobuf` loader. The demo is awesome and the source repo is impressively ambitious and supports multiple language binding but I...

> you can fetch FlatGeobuf in the (modern) browser as binary and use as is without any conversion whatsoever if you can use the memory model directly (fx. access the...

> He suggested importing the untranspiled source, e.g. I am pretty sure I tried that and ran into other issues, but don't recall exactly (I think not everything I needed...

Regarding #718 That is very neat micro integration! I'm open for discussion. My initial take is that the primary justifications for including a flatgeobuf loader in loaders.gl are: 1. the...

Yes - unfortunately `deserializeStream` takes a stream as input. - `parseInBatches` takes an asyncIterator as input. We need a version of `deserializeStream()` that accepts an async iterator (an async iterator...