[MapProxy] MapProxy Digest, Vol 105, Issue 2

Thu Dec 20 11:24:18 PST 2018

Hello,

Are there any examples of setting a WMS to TMS service with Mapproxy? I am
trying to do it, but I am not having success. I have read the
documentation. I have a GeoServer that has WMS services available.

Here are the lines on my mapproxy yml file:

services:
  demo:
  tms:
    origin: 'nw'

layers:
  - name: test_wms_cache
    title: Cached Test Layer
    sources: [test_wms_cache]

caches:
  test_wms_cache:
    sources: [ashgabat-14aug2017-2]

sources:
  ashgabat-14aug2017-2:
    type: wms
    req:
      url: http://xx.x.xxx.xx:8080/geoserver/nextview/wms?
      layers: ashgabat-14aug2017-2
      transparent: true

Here are some lines on the mapproxy console for the development server:
[info] 78.108.177.52 - - [20/Dec/2018 11:03:16] "GET / HTTP/1.0" 200 -
[info] 91.123.26.182 - - [20/Dec/2018 11:27:36] "GET / HTTP/1.1" 200 -
[info] 175.181.224.132 - - [20/Dec/2018 11:33:33] "GET / HTTP/1.0" 200 -
[info] 58.179.72.36 - - [20/Dec/2018 12:24:35] "GET / HTTP/1.1" 200 -
[info] 58.187.1.249 - - [20/Dec/2018 13:29:33] "POST /tmUnblock.cgi
HTTP/1.1" 404 -
[info] 46.174.191.28 - - [20/Dec/2018 14:30:26] "GET / HTTP/1.0" 200 -
[info] 78.108.177.53 - - [20/Dec/2018 15:51:51] "GET / HTTP/1.0" 200 -
[info] 180.251.241.7 - - [20/Dec/2018 16:05:12] "GET / HTTP/1.1" 200 -
[info] 203.160.57.227 - - [20/Dec/2018 16:35:02] "GET / HTTP/1.1" 200 -
[info] 46.174.191.29 - - [20/Dec/2018 16:41:02] "GET / HTTP/1.0" 200 -
[info] 12.4.223.4 - - [20/Dec/2018 17:58:20] "GET /demo/ HTTP/1.1" 200 -
[info] 12.4.223.4 - - [20/Dec/2018 17:58:29] "GET /demo/static/site.css
HTTP/1.1" 200 -
[info] 12.4.223.4 - - [20/Dec/2018 17:58:50] "GET /favicon.ico HTTP/1.1"
404 -
[2018-12-20 18:00:56,483] mapproxy.source.request - INFO - GET http://
xx.x.xxx.xx:8080/geoserver/nextview/wms?styles=&format=image%2Fpng&height=1184&bbox=-6771250.58767,-12308960.4129,-6759937.90748,-12297647.7327&transparent=True&layers=ashgabat-14aug2017-2&service=WMS&width=1184&request=GetMap&srs=EPSG%3A900913&version=1.1.1
200 - 104
[info] 12.4.223.4 - - [20/Dec/2018 18:00:56] "GET
/tms/1.0.0/test_wms_cache/EPSG900913/13/5425/3162.png HTTP/1.1" 200 -
[info] 18.234.66.101 - - [20/Dec/2018 18:03:03] "GET
/tms/1.0.0/test_wms_cache/EPSG900913 HTTP/1.1" 200 -
[info] 12.4.223.4 - - [20/Dec/2018 18:03:03] "GET
/demo/?tms_capabilities&layer=test_wms_cache&srs=EPSG900913 HTTP/1.1" 200 -
[info] 12.4.223.4 - - [20/Dec/2018 18:03:12] "GET /demo/static/site.css
HTTP/1.1" 200 -
[info] 12.4.223.4 - - [20/Dec/2018 18:03:12] "GET /demo/static/logo.png
HTTP/1.1" 200 -
[info] 78.108.177.53 - - [20/Dec/2018 18:37:18] "GET / HTTP/1.0" 200 -

The TMS is not working. Looking at the mapproxy.source.request the bounding
box seems way off. If I manually change the bounding box to one that my
GeoServer uses on a layer preview then the WMS call works. Maybe this is
why the mapproxy tile cache is not returning a good tiles? How can I fix
this?

Thanks,

Tom G.

On Fri, Nov 2, 2018 at 3:00 PM <mapproxy-request at lists.osgeo.org> wrote:

> Send MapProxy mailing list submissions to
>         mapproxy at lists.osgeo.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.osgeo.org/mailman/listinfo/mapproxy
> or, via email, send a message with subject or body 'help' to
>         mapproxy-request at lists.osgeo.org
>
> You can reach the person managing the list at
>         mapproxy-owner at lists.osgeo.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of MapProxy digest..."
>
>
> Today's Topics:
>
>    1. Re: WMS to TMS with mapproxy (Travis Kirstine)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 1 Nov 2018 15:20:06 -0400
> From: Travis Kirstine <traviskirstine at gmail.com>
> To: northswejohan at gmail.com
> Cc: mapproxy <mapproxy at lists.osgeo.org>
> Subject: Re: [MapProxy] WMS to TMS with mapproxy
> Message-ID:
>         <
> CALtm4h3oDXrtfwsyOOUtVyoFJc7hoG4m7rJRtZKN8GWf3rgQVA at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Yes it is possible to 'convert' a WMS to TMS.  MapProxy can be used to use
> WMS as a source to create TMS services.
>
> MapProxy requires no development expertise, but some knowledge of GIS would
> be helpful.  If you follow the docs and use the examples you should be fine
> setting it up in a test environment.
>
> On Thu, 1 Nov 2018 at 05:52, Johan Johansson <northswejohan at gmail.com>
> wrote:
>
> > Hi,
> >
> >
> >
> > Is it possible to convert a WMS url to a TMS url with your mapproxy.
> > How much work is it? If you’re not a developer.
> >
> > Best/
> > Johan
> > _______________________________________________
> > MapProxy mailing list
> > MapProxy at lists.osgeo.org
> > https://lists.osgeo.org/mailman/listinfo/mapproxy
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.osgeo.org/pipermail/mapproxy/attachments/20181101/55d5a97e/attachment-0001.html
> >
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> MapProxy mailing list
> MapProxy at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapproxy
>
> ------------------------------
>
> End of MapProxy Digest, Vol 105, Issue 2
> ****************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapproxy/attachments/20181220/fae43c95/attachment.html>