4 ms·
> coupled with http range queries on the static files hosted in S3 to bypass the need for tiling Did you look into Cloud Optimized GeoTIFF format? https://www
by jamessb 3y ago
> coupled with http range queries on the static files hosted in S3 to bypass the need for tiling
Did you look into Cloud Optimized GeoTIFF format?
https://www.cogeo.org/ https://www.cogeo.org/
It is supported by OpenLayers: https://openlayers.org/en/latest/examples/cog.html https://openlayers.org/en/latest/examples/cog.html
(I don't think that Maplibre or Leaflet have built-in support for it)
- Soupy 3y agoI did actually! For my particular source dataset it was far easier just to lean on the plain old GeoTiff format since that's what my source data was already formatted in and my testing of the client-side on-the-fly tiling using range queries and fast-png for encoding resulted in close to par performance with 0 increase in hosting costs and 0 headache in building custom pipelines to encode the cloud-optimized versions. Basically, I'm lazy, I'm sure it's the "correct" answer for other use-cases I also have been digging pretty extensively into protomaps though for some newer non-GeoTiff datasets I'm in the process of pulling in, in my opinion it's the future for this space - https://protomaps.com/ https://protomaps.com/