Kyle Barron

https://github.com/SymbolixAU/flatgeobufr/issues/1#issuecomment-610289845 > 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...

> At least the javascript bindings appear to still be rough around the edges: The published npm module was not properly set up to be usable Yes, I opened an...

Yes, I agree the incremental loading is essential. I know you mentioned differences in "push/pull" [here](https://github.com/uber-web/loaders.gl/issues/701#issuecomment-601380788). I first need to read more about AsyncIterators, before attempting to add support for...

From a few minutes of reading, I think AsyncIterators are supported by default in flatgeobuf... `deserializeStream` returns an iterator, and each iteration is a promise. ([From here](https://github.com/bjornharrtell/flatgeobuf/blob/a6ed69fbfcbcd931b932fb346c5416c92ceb1b33/examples/leaflet/index.js#L12-L20)) ```js let it...

Ah I thought you were referring to _output_, not _input_. > One approach is to create a Stream wrapper over an async iterator (AsyncIteratorStream) and pass that in. I think...

I haven't personally worked the JS Parquet implementation at all, so I don't have any good information on this. My (possibly uniformed) impression is that the JS implementation can be...

I don't see that much of a dichotomy. To me, whether the metadata is within the same file or in a different file, it still has to be parsed before...

> multi-file loading I think that's part of what I'm getting at, but in my view as long as the server supports HTTP range requests, multiple files and multiple pages...

> Another layer of complexity on the loaders but certainly possible You're right it would be more complexity. At this point I just want to discuss the overall API, and...

I was thinking about this a little more today and one possibility that doesn't require any change in the global loaders API is to have _two_ loaders for some formats....