<div dir="ltr">Oliver:<div><br></div><div>I just updated (<a href="https://github.com/mapproxy/mapproxy/pull/130">https://github.com/mapproxy/mapproxy/pull/130</a>). Could you review it again?</div><div><br></div><div>Regards,</div><div>Aron</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 9, 2015 at 5:21 AM, Oliver Tonnhofer <span dir="ltr"><<a href="mailto:olt@omniscale.de" target="_blank">olt@omniscale.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<span class=""><br>
> On 09.06.2015, at 00:40, André Pirard <<a href="mailto:A.Pirard.Papou@gmail.com">A.Pirard.Papou@gmail.com</a>> wrote:<br>
> To support ArcGIS Rest, I made a tiny 1.6 patch that adds &size=<width>,< height> to a WMS requests.<br>
> By "manually" adding other ¶meters=as_below, the request becomes ArcGIS export compatible.<br>
> After installing 1.8, I noticed correct JOSM images despite the patch was absent.<br>
> Not receiving size information, ArcGIS returns 400×400 tiles and Mapproxy seems to cope with that.<br>
> I "manually" set &size=1184,1184 according to the size I saw Mapproxy use routinely.<br>
<br>
> <a href="http://geoservices.wallonie.be/arcgis/rest/services/TOPOGRAPHIE/PICC/MapServer/export?styles=&service=WMS&format=image%2Fpng&f=image&request=GetMap&dpi=90&height=1184&srs=EPSG%3A3857&version=1.1.1&bboxSR=3857&bbox=625842.501028,6539622.5054,626196.022284,6539976.02665&imageSR=3857&width=1184&transparent=True&size=1184,1184" target="_blank">http://geoservices.wallonie.be/arcgis/rest/services/TOPOGRAPHIE/PICC/MapServer/export?styles=&service=WMS&format=image%2Fpng&f=image&request=GetMap&dpi=90&height=1184&srs=EPSG%3A3857&version=1.1.1&bboxSR=3857&bbox=625842.501028,6539622.5054,626196.022284,6539976.02665&imageSR=3857&width=1184&transparent=True&size=1184,1184</a><br>
<br>
</span>Maybe it is easier to use a tile source (it supports bbox parameter since 1.1.0)? <a href="http://mapproxy.org/docs/nightly/sources.html#tiles" target="_blank">http://mapproxy.org/docs/nightly/sources.html#tiles</a><br>
<span class=""><br>
<br>
> Is Mapproxy designed to build a correct cache when the tiles are received with a non-requested size?<br>
> Does Mapproxy always use the same size (here 1184) for a given configuration?<br>
<br>
</span>1184 is 4 meta tiles plus 2x80 pixel meta buffer.<br>
<span class=""><br>
<br>
> Why isn't Aron Bierbaum's patch (authored on 16 Aug 2013) integrated?<br>
> It's essentially equivalent to my hack but needs not adding the other parameters "manually".<br>
> Isn't supporting ArcGIS great?<br>
<br>
</span>Do you mean <a href="https://github.com/mapproxy/mapproxy/pull/130" target="_blank">https://github.com/mapproxy/mapproxy/pull/130</a>?<br>
The pull request was not in a final state and it hasn’t got any updates since then.<br>
<br>
<br>
<br>
Regards,<br>
Oliver<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Oliver Tonnhofer | Omniscale GmbH & Co KG | <a href="http://omniscale.com" target="_blank">http://omniscale.com</a><br>
OpenStreetMap WMS and tile services | <a href="http://maps.omniscale.com" target="_blank">http://maps.omniscale.com</a><br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
MapProxy mailing list<br>
<a href="mailto:MapProxy@lists.osgeo.org">MapProxy@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/mapproxy" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapproxy</a></font></span></blockquote></div><br></div>