[MapProxy] ArcGIS Rest export hack and patch status

[Oliver Tonnhofer]

Hi,

> On 09.06.2015, at 00:40, André Pirard <A.Pirard.Papou at gmail.com> wrote:
> To support ArcGIS Rest, I made a tiny 1.6 patch that adds &size=<width>,< height> to a WMS requests.
> By "manually" adding other &parameters=as_below, the request becomes ArcGIS export compatible.
> After installing 1.8, I noticed correct JOSM images despite the patch was absent.
> Not receiving size information, ArcGIS returns 400×400 tiles and Mapproxy seems to cope with that.
> I "manually" set &size=1184,1184 according to the size I saw Mapproxy use routinely.

> 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

Maybe it is easier to use a tile source (it supports bbox parameter since 1.1.0)? http://mapproxy.org/docs/nightly/sources.html#tiles


> Is Mapproxy designed to build a correct cache when the tiles are received with a non-requested size?
> Does Mapproxy always use the same size (here 1184) for a given configuration?

1184 is 4 meta tiles plus 2x80 pixel meta buffer.


> Why isn't Aron Bierbaum's patch (authored on 16 Aug 2013) integrated?
> It's essentially equivalent to my hack but needs not adding the other parameters "manually".
> Isn't supporting ArcGIS great?

Do you mean https://github.com/mapproxy/mapproxy/pull/130?
The pull request was not in a final state and it hasn’t got any updates since then.



Regards,
Oliver

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