This example uses a seekable-Zstandard wrapper around the same indexed FlatGeobuf data. The compressed object is about 5.14 GB (4.79 GiB); its uncompressed FlatGeobuf stream is about 12.34 GB (11.49 GiB). The blue rectangle shows the current query. The client reads the seek table and FlatGeobuf spatial index, then fetches only the compressed frames needed for matching features.

This page loads FlatGeobuf 4.5.0 from unpkg. The data CDN must support HTTP byte ranges and expose Content-Range to browser JavaScript.

Though getting a small subset of features from a large dataset transfers relatively little data, it does so using multiple requests. There are some tips for optimizing remote hosted flatgeobufs, mostly oriented around minimizing round trip latency.