[gdal-dev] COG + javascript + openlayers

Javier Jimenez Shaw j1 at jimenezshaw.com
Tue Apr 6 13:40:38 PDT 2021


Hi

While I was reading about COG format, I thought it was great to replace
"gdal2tiles" if the COG was properly generated (I mean, using the option
TILING_SCHEME=GoogleMapsCompatible , and maybe something else I miss. I am
generating it, so I can optimize that).
Then I was expecting that geotiff.js (or any other client js library) will
be able to do the proper RANGE request to produce the tiling that libraries
like openlayers of leaflet is expecting. Yes, in Web Mercator projection
with aligned tiles, so no transformation is needed.

My initial target is just for RGBA uint8 images... plain vanilla. Storing
the COG file in S3, without any proxy in between doing any conversion. Just
relying on the RANGE request to get the needed area. My initial idea is to
keep the openlayers/leaflet 256x256 tiles. This allows parallel requests to
the server, and is very fast (and I do not have to refactor all my js
code). But maybe there is a better/faster solution (again, with S3 direct
access, no proxy in the server side. That would require deploying the
"proxy" on every geographical region).

However I have not found any proper solution (my search-fu is not the best,
to be honest). I would like something that performs *at least* as fast as
the tiles produced by gdal2tiles.

Do you know any solution/example?

Thanks
.___ ._ ..._ .. . ._.  .___ .. __ . _. . __..  ... .... ._ .__
Entre dos pensamientos racionales
hay infinitos pensamientos irracionales.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20210406/dad47029/attachment.html>


More information about the gdal-dev mailing list