Open vincentsarago opened 1 year ago
Thank you very much for the feedback @vincentsarago , I agree this would have been a good idea, and we should do this for later versions.
In truth, I don't think we really expected the TileMatrixSet standard to get much use before we (OGC) put out a standard (e.g., OGC API - Tiles) that referenced it, but I realized that projects like TiTiler actually used it :).
For reading both version 1.0 and 2.0, I think the easiest approach would be to support both the old and new name for the properties. The breaking changes between the two is detailed in https://docs.opengeospatial.org/is/17-083r4/21-066r1.html#Clause_Critical .
Hi, First thanks for the hard work put in defining the specificatio. It's true that I usually mostly complain about OGC specs because I find them hard to follow. Anyway I wanted to propose we add a
Version
into the TMS specification (maybe it exists but I didn't find it), because right now it's pretty hard to see in which version a TMS is based on. IMO having a simpleversion: 1.0
orversion: 2.0
will make it easier.I understand this comes late to the party but if this is something that could be considered for later version it will be great IMO.
Thank you