geotiff.js is a small library to parse TIFF files for visualization or analysis. It is written in pure JavaScript, and is usable in both the browser and node.js applications.
Many times, we see that the exact same request is sent by geotiff.js: same URL, same Content-Range and Content-Length headers, resulting in a massive increase of the data to download. Depending on the compression used, and the bitness of the image, the increase can be catastrophic.
The displayed terrain is subdivided in a hierarchical grid, meaning that there will be some overlap between grid cells and COG tiles: the same COG tiles will be shared among neighbour cells. Now I expect that the BlockedSource deduplicate requests for the same slice of data, but it seems that it does not (or at least not always).
We are using geotiff.js to retrieve COG data in Giro3D, as seen in this example: https://giro3d.org/examples/cog_elevation.html
Many times, we see that the exact same request is sent by geotiff.js: same URL, same
Content-RangeandContent-Lengthheaders, resulting in a massive increase of the data to download. Depending on the compression used, and the bitness of the image, the increase can be catastrophic.The displayed terrain is subdivided in a hierarchical grid, meaning that there will be some overlap between grid cells and COG tiles: the same COG tiles will be shared among neighbour cells. Now I expect that the
BlockedSourcededuplicate requests for the same slice of data, but it seems that it does not (or at least not always).