[MapProxy] Antwort: Re: problems with mbtiles via mapproxy

[Oliver Tonnhofer]

Hi Paul,

On 17.09.2012, at 12:18, Paul Norman wrote:
> If you intend to use mapproxy to serve tiles to consumers expecting the
> Google/OSM layout you need to use /tiles/ instead of /tms/ and call with
> ?origin=nw.
> 
> I strongly suggest using mod_rewrite with apache to make the URLs easier to
> handle. Your users will thank you for sane URLs.
> 
> I use something like
> 
> Alias /tiles /path/to/tiles
> <Directory /path/to/tiles>
>        Options Indexes FollowSymLinks
>        RewriteEngine on
>        RewriteBase /tiles
>        RewriteRule
> ^([^/]+)/([^/]+)/([^/]+)/([^/]+)\.(png|jpeg|jpg|tif|tiff)$
> /my_mapproxy/tiles/1.0.0/$1_EPSG900913/$2/$3/$4.$5?origin=nw [L]
> </Directory>
> 
> WSGIScriptAlias /my_mapproxy /path/to/mapproxy/config/config.py
> 
> And then I have some other tile-related files served up from /path/to/tiles/

Thanks for that configuration snippet. Might be useful to some users!


With MapProxy 1.5 you will be able to change the default origin of your tile services:
See: http://mapproxy.org/docs/nightly/services.html#google-maps

  services:
    tms:
      origin: 'nw'

Regards,
Oliver

-- 
Oliver Tonnhofer    | Omniscale GmbH & Co KG    | http://omniscale.de
http://mapproxy.org | https://github.com/olt    | @oltonn