Create example reading from titiler backend

[kylebarron]

We should be able to use the new RasterTileLayer concept (#404) where we read in initial metadata, align the client TMS with whatever TMS titiler uses to provide tiles, and then it should be a pretty simple example.

cc @vincentsarago

[jo-chemla]

Quick question after commenting on stac-map web-map-links support here developmentseed/stac-map#314 (comment): after parsing quickly through the PR #469 body and especially this note,

First example in the repo that uses RasterTileLayer directly (not via COGLayer / ZarrLayer). Demonstrates the flow for any server that hands back per-tile binary arrays for an OGC tile matrix set.

Are you aiming at ingesting/rendering arbitrary 2d-raster-tiled datasets via deckgl-raster?

Titiler middleware beauty is that it can ingest arbitrary gdal-compatible inputs - I'm always blown away by this composability abstraction, be it

• COGs, the classic CNG raster format
• or alternative gdal drivers like GDAL_WMS, TMS,
• WMTS,
• eventually pmtiles container of raster-tiles now gdal can read/write it after PMTiles: add raster read and CreateCopy() support OSGeo/gdal#14504 etc

Below strings are samples extracted from this discussion that titiler/rasterio can ingest developmentseed/titiler#640

WMS: Similar than for a WMS compliant server: https://titiler.xyz/cog/crop/-110,-70,110,70/512x0.png?max_size=512&url=WMS:http://ows.terrestris.de/osm/service?layers=OSM-WMS-no-labels
TMS: https://titiler.xyz/cog/crop/-110,-70,110,70.png?url=<GDAL_WMS><Service name='TMS'><ServerUrl>http://example.com/tileset1/${z}/${x}/${y}</ServerUrl></Service><DataWindow><UpperLeftX>-20037508.34</UpperLeftX><UpperLeftY>20037508.34</UpperLeftY><LowerRightX>20037508.34</LowerRightX><LowerRightY>-20037508.34</LowerRightY><TileLevel>18</TileLevel><TileCountX>1</TileCountX><TileCountY>1</TileCountY><YOrigin>top</YOrigin></DataWindow><Projection>EPSG:3857</Projection><BlockSizeX>256</BlockSizeX><BlockSizeY>256</BlockSizeY><BandsCount>3</BandsCount><Cache /></GDAL_WMS>

Could be very helpful to make that abstraction of the client mapping library rendering abritrary raster-tiled datasets, WMS, WMTS, eventually TMS CRS other than 3857 (eg yandex) etc! Unifying all these would remove the need for custom, dedicated, interpration layers like current series of maplibre distinct protocols for pmtiles, wms, wmts listed in stac-map thread. And might be useful for stac-map to integrate such STAC items/assets as layers for viewing.

[kylebarron]

Are you aiming at ingesting/rendering arbitrary 2d-raster-tiled datasets via deckgl-raster?

That's possible with the RasterTileLayer. It's not tied to either Zarr or COG. It just needs:

• a tile layout description
• a function for how to load data for each tile
• a function for how to create a deck.gl layer for each tile