[MapProxy] Changing Tile Origin In mbtiles Caches

Oliver Tonnhofer olt at omniscale.de
Mon Jun 29 07:20:44 PDT 2015


you should set the grid of the mbtiles cache to a grid with the right origin.
See: http://mapproxy.org/docs/nightly/configuration.html#grids


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

> On 24.06.2015, at 02:59, Syrus Mesdaghi <syrusm at hotmail.com> wrote:
> Hi all, 
> we are creating a little django service that uses mapproxy to generate tilesets to then server them up for download. When we load the generated mbtiles through  geotools and openlayers,  the tile origins are different. The lower left tile shows up in the upper left corner and vice versa.  I see that services can be configured to change the tile origin by specifying:
> services:
>   tms:
>     origin: 'nw'
> but this would change the way the tiles are returned and not how they are stored in the mbtiles. looking at mbtiles.py I don't see a way to change the 'scheme' in the way mapbox's mbutils does. 
> https://github.com/mapproxy/mapproxy/blob/6d299f9e67cf62662a1cde74e4ae042cdd2d33ea/mapproxy/cache/mbtiles.py
> https://github.com/mapbox/mbutil/blob/master/mbutil/util.py
> I want to make sure 1) that I am not missing anything and 2) what concerns to keep in mind in the case we can get a pull request together. I suppose it can be expected behavior for origin change in mbtiles to be effectively 'cancelled out' by, say, tms service's origin change.  
> Thanks for any thoughts/suggestions. 
> - Syrus Mesdaghi
> _______________________________________________
> MapProxy mailing list
> MapProxy at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapproxy

More information about the MapProxy mailing list