[MapProxy] WMTS

[Jeff Konnen]

Hi Oliver
As it is a prerendered TileCache structure, I am not able to change the
origin.
So this means that there's no possibility to serve my existing tilecache
tiles as WMTS service with mapproxy?
Thanks
Jeff


On Thu, Jun 20, 2013 at 9:29 AM, Oliver Tonnhofer <olt at omniscale.de> wrote:

> Hi Jeff,
>
> On 19.06.2013, at 09:52, Jeff Konnen wrote:
> > WARNING - grid 'luxembourg1930' is not compatible with WMTS, skipping
> for layer 'ortho_2010'
> >
> >   luxembourg1930:
> >     tile_size: [256, 256]
> >     srs: 'EPSG:2169'
> >     res: [500,250,150,100,50,20,10,5,2.0,1.0,0.5]
> >     bbox: [48000,57000,107000,139000]
> >
> >
> > What's the exact reason? Is there anything I can change?
> > What I want to do is to use our current Tilecache structure and serve it
> as WMTS, which does not seem to work..
>
>
> WMTS and TMS have a different tile origins (north/west vs. south/west).
> MapProxy uses south/west by default, but it is able to transform between
> these two origins when it is possible. But that's not the case as soon as
> you have a resolution step that is not x2 (eg. between 150 and 100).
>
> You need to set the origin of that grid to 'nw' or 'ul' (upper/left) to
> get this working in WMTS.
>
> MapProxy 2 will switch to 'nw' by default.
>
> Regards,
> Oliver
>
> --
> Oliver Tonnhofer    | Omniscale GmbH & Co KG    | http://omniscale.com
> http://mapproxy.org | https://github.com/olt    | @oltonn
>
>


-- 
Jeff Konnen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapproxy/attachments/20130620/5f6b8948/attachment.html>