GeoRange IO
Reads remote cloud-optimised GeoTIFFs along a shape instead of a bounding box.
If what you want is a flight path, a transmission corridor, or a river, a bounding box is mostly bytes you paid for and threw away. This plans a request set for the actual geometry, coalesces it into HTTP byte ranges, and decodes DEFLATE partially from indexed mid-stream checkpoints.
Against tuned GDAL on live AWS Sentinel-2: 51% fewer bytes over the wire, 89% with precomputed indexes, 2.7× faster single-threaded and 15× in parallel — and byte-identical output across more than 15,000 reads, which was the part worth proving.
Trace a route to compare what each read fetches. A bounding box pulls — MB; the corridor needs — MB — — less over the wire.
Drag across the tiles. Amber is what a bounding-box read pulls down; white is what the corridor needs.Drag across the tiles. Amber is what a bounding-box read pulls; white is what the corridor needs.