Not negative feedback per se, just background. TMS common gridsets were conceived as a step along the path towards defining gridsets in a way that treats them like CRS: the definition of the grid is very much like a derived projected CRS, so why not have a register that encodes the relationship between the underlying projected CRS and the grid.
However, recent developments have made it clear that the maintainers of the standard don't see it this way, and they propose to allow flexibility in the underlying CRS [1]. Anyway, at some point I will likely try to prototype a more formal approach to this, but for the time being, what I have developed, and plan to stick with because of the flexibility aka instability of TMS definition, is Tiled CRS (TCRS) [2]. [1] https://github.com/opengeospatial/2D-Tile-Matrix-Set/issues/36#issuecomment-880918536 apologies that discussion is not coherent but it boils down to allowing different CRS in a TileSet instance vs the TMS registered definition. [2] https://maps4html.org/MapML/spec/#tiled-coordinate-reference-systems-0 Cheers Peter On Wed., Sep. 1, 2021, 5:15 a.m. Andrea Aime, < andrea.a...@geosolutionsgroup.com> wrote: > On Tue, Aug 31, 2021 at 7:14 PM Andrea Aime < > andrea.a...@geosolutionsgroup.com> wrote: > >> Release Candidate >> >> Scheduled for 2021-09-04, anything pending? >> >> - >> >> remove ingres datastore, etc… >> - >> >> https://github.com/geotools/geotools/pull/3619 >> - >> >> check: Update docs to reflect removing GTOPO30 etc... >> >> > I forgot yesterday, the OGC TileMatrixSet common gridsets PRs are still > pending: > - https://github.com/GeoWebCache/geowebcache/pull/980 > - https://github.com/geoserver/geoserver/pull/5242 > > All the feedback I got revolves around getting even more functionality, > but no negative about > this base addition. I'll merge it tomorrow unless I get some actual > pushback > > Cheers > Andrea > > == > > GeoServer Professional Services from the experts! > > Visit http://bit.ly/gs-services-us for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > GeoSolutions Group > phone: +39 0584 962313 > > fax: +39 0584 1660272 > > mob: +39 333 8128928 > > https://www.geosolutionsgroup.com/ > > http://twitter.com/geosolutions_it > > ------------------------------------------------------- > > Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE > 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si > precisa che ogni circostanza inerente alla presente email (il suo > contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è > riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il > messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra > operazione è illecita. Le sarei comunque grato se potesse darmene notizia. > > This email is intended only for the person or entity to which it is > addressed and may contain information that is privileged, confidential or > otherwise protected from disclosure. We remind that - as provided by > European Regulation 2016/679 “GDPR” - copying, dissemination or use of this > e-mail or the information herein by anyone other than the intended > recipient is prohibited. If you have received this email by mistake, please > notify us immediately by telephone or e-mail > _______________________________________________ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel >
_______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
