Hi,
Currently I'm working on WMTS support. As some of you may know (and
those who do not, I refer to
http://www.opengeospatial.org/standards/wmts) uses notion of
scaleDenominator that's crucial to tile positioning. More less -
scaleDenominator tell how many meters are on the tile per pixel.
I
On 02.07.2015 21:47, Wiktor Niesiobedzki wrote:
Currently I'm working on WMTS support. As some of you may know (and
those who do not, I refer to
http://www.opengeospatial.org/standards/wmts) uses notion of
scaleDenominator that's crucial to tile positioning. More less -
scaleDenominator tell how
2015-07-02 23:12 GMT+02:00 Paul Hartmann phaau...@gmail.com:
On 02.07.2015 21:47, Wiktor Niesiobedzki wrote:
Currently I'm working on WMTS support. As some of you may know (and
those who do not, I refer to
http://www.opengeospatial.org/standards/wmts) uses notion of
scaleDenominator that's
On 02.07.2015 23:33, Wiktor Niesiobedzki wrote:
I understand, that how much real meters you get per unit of latitude
as well as per unit of longitude differs for different part of the
ellipsoid/sphere. But that's not what WMTS specification ask. The
crucial part of spec says:
pixelSpan =
