Support other projection

[vincentsarago]

As of today, mosaicjson has been designed for WebMercator projection, but quadkey could represent tiles in other projections.

To keep it simple, the projection option should be the name of the TileMatrixSet (TMS) and default to WebMercatorQuad.

ref: https://github.com/developmentseed/morecantile

[kylebarron]

To keep it simple, the projection option should be the name of the TileMatrixSet (TMS) and default to WebMercatorQuad.

Does that mean you won't support custom grids?

[vincentsarago]

@kylebarron well there is not an official list of TileMatrixSet (just a spec) so IMO they are more or less all custom 😂 (in their content).

we could maybe allow either a string or a dict to define a grid but I'm affraid this will turn to be a 🕳️

[kylebarron]

Yes, but you're able to make a custom grid from a CRS and an extent, so there's no reason why you couldn't have:

projection: {
	"tile_matrix_set": "WebMercatorQuad"
}

but also

projection: {
	"crs": "wkt representation of crs",
	"extent": [a, b, c, d]
}

so that you could always encode any arbitrary grid

[drwelby]

Have any tilers supported this yet? I have piles of UTM quadkey tiles to prototype with.

[vincentsarago]

👋 we moved away from static files for mosaic and we are now mostly using DB (STAC + PgSTAC) dynamic mosaics https://github.com/stac-utils/titiler-pgstac

I'm not sure what we want to do with this issue. I do not have a lot of time right now to work on this :-(

[drwelby]

I have static STAC Collections that describe the source tiles so maybe that fits into what you're doing, I'll take a look.

[vincentsarago]

I've made https://github.com/developmentseed/eoAPI which combine STAC db + Tiler (still a WIP)