I’m working on an implementation of OGC API - Tiles and want to ensure that I’m using a valid and registry-backed TileMatrixSet. The existing WebMercatorQuad.json works well, but it’s defined for 256×256 tiles. My use case would benefit from a 512×512 variant to align with internal performance goals and simplify integration with other tooling that defaults to 512. I do not see anything that does this in https://defs.opengis.net/prez/catalogs/ogc-cat:register/col/ogc:tms/it1
The current spec clearly allows alternate tile sizes via tileWidth and tileHeight, but the registry only includes the 256 version of WebMercatorQuad. Before creating a variant, I wanted to ask: why is there no demonstrative 512×512 version of a TileMatrixSet? For us to implement, I would assume the TileMatrixSet would need to get an OGC URI.
I’m working on an implementation of OGC API - Tiles and want to ensure that I’m using a valid and registry-backed TileMatrixSet. The existing WebMercatorQuad.json works well, but it’s defined for 256×256 tiles. My use case would benefit from a 512×512 variant to align with internal performance goals and simplify integration with other tooling that defaults to 512. I do not see anything that does this in https://defs.opengis.net/prez/catalogs/ogc-cat:register/col/ogc:tms/it1
The current spec clearly allows alternate tile sizes via tileWidth and tileHeight, but the registry only includes the 256 version of WebMercatorQuad. Before creating a variant, I wanted to ask: why is there no demonstrative 512×512 version of a TileMatrixSet? For us to implement, I would assume the TileMatrixSet would need to get an OGC URI.