[MapProxy] Problems with TMS and grid _skip_first_level

[Oliver Tonnhofer]

Hi,

the TMS spec comes with its own definition of a mercator tile grid and this starts with four tiles in zoom level 0.

You need to use the /tile or /wmts endpoint. Please read https://mapproxy.org/docs/nightly/services.html#tiled-map-services-tms for more information

Regards,
Oliver

-- 
Oliver Tonnhofer  | Omniscale GmbH & Co KG  | https://omniscale.com
OpenStreetMap WMS and tile services         | https://maps.omniscale.com





> On 14.06.2017, at 09:46, G. Allegri <giohappy at gmail.com> wrote:
> 
> Hi,
> I'm using OL 3/4 for an application where a TMS layer is defined:
> 
> new ol.layer.Tile({
>    source: new ol.source.XYZ({
>       url: "http://localhost:8080/tms/1.0.0/mylayer/webmercator/{z}/{x}/{-y}.png",
>    })
> })
> 
> (the inverted "y" in a XYZ layer makes it behave as a TMS layer).
> 
> The map is EPSG:3857 and the layer source (WMS service) is also EPSG:3857
> 
> This OL app works perfectly with other cache tools, like mapcache, with a standard mercator grid.
> When I use it with MapProxy things get wrong becasue TileServiceGrid skips the first level for GLOBAL_(WEB)MERCATOR : https://github.com/mapproxy/mapproxy/blob/master/mapproxy/service/tile.py#L381
> 
> If self._skip_first_level is forced to False everything goes fine.
> 
> I noticed that even in you OpenLayers 2 Demo you start resolutions from 78271.516964, which is the second level of the the classical mercator grid.
> 
> My questions are: 
> 
>  - why is the first level skipped? 
>  - how could I define a GLOBAL_WEBMERCATOR grid without skipping the first level? I don't want to force it at level of (internal) code, obviusoly.
> 
> Thanks so much,
> Giovanni 
> 
> _______________________________________________
> MapProxy mailing list
> MapProxy at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapproxy