- From: Peter Rushforth via GitHub <sysbot+gh@w3.org>
- Date: Tue, 29 Jun 2021 13:51:23 +0000
- To: public-sdwig@w3.org
I'm happy to be able to report progress on this issue, thanks to all who commented. First, the good news is that there **is** [a registry for grid sets](https://defs.opengis.net/vocprez/object?uri=http://www.opengis.net/def/tms) that includes the origin, resolutions, tilesize and bounds, as well as the CRS associated to the grid set, based on the [TMS specification Annex D](https://docs.opengeospatial.org/is/17-083r2/17-083r2.html#annex_d). The not so good news is that [there is an emerging 'clarification' of TMS that allows the CRS underlying a grid set to be treated interchangeably in some circumstances](https://docs.opengeospatial.org/DRAFTS/17-083r3.html#TileMatrixSetCRSCompatibility). Unfortunately, this clarification goes right to the heart of why grid sets **should** be standardized as part of the / as though they are CRS: because of the resulting axis order (and other) confusion that will certainly result from such interchangeability. -- GitHub Notification of comment by prushforth Please view or discuss this issue at https://github.com/w3c/sdw/issues/1237#issuecomment-870619061 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 29 June 2021 13:51:25 UTC