Open jerstlouis opened 1 year ago
Side note:
maybe it would be good to have the coalescence factor present in the tileset metadata (tilematrixsetlimits) (https://docs.ogc.org/is/17-083r4/17-083r4.html#table12), IMO, the client should have a way to easily construct a list of valid
tiles using the tileset metadata.
@vincentsarago but the coalescence factor varies between rows of each tile matrix, there is only one minimum / maximum column for every matrix (level) in the limits of the tileset metadata
🤦 that's true. So the Client application cannot know not to call
a tile without implementing the TileMatrixSet 👍 !
The following is included in normative Section 6.1.5:
The spec says they are the same tile. It might be good to clarify that the first one (
((int)(col / c)) * c
) should be the one that clients look for, and that servers SHOULD redirect to the first one, but MAY return a 4xx for the non-canonical tile.e.g., for GNOSIS Global Grid, the northernmost tiles always have a column index which is a power of two (2 ^ level) multiplied by 0, 1, 2 or 3.
Feedback from @vincentsarago (https://github.com/developmentseed/morecantile/issues/115)