1

Having a strange issue consuming WMS services hosted on ArcGIS Server 10.3.

When the service is cached in ESRI's compact format, the request fails with HTTP 400. In exploded format, it works perfectly. I've tracked down the issue to the CRS parameter. For example:

`http://gis.example.org/arcgis/services/ServiceFolder/ServiceName/MapServer/WmsServer?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&CRS=CRS:84&BBOX=...'

will fail based on the CRS=CRS:84 parameter. If I change that to CRS=3857, it succeeds. Again, this only happens with compact format. I thought it might have something to do with the BBOX units, but the parameters for exploded are identical and it works.

The service was published as EPSG:3857. For what it's worth, the server was installed as 10.2.2 and upgraded to 10.3. I haven't tested through a fresh install of 10.3 or through an older version, but suspect it wouldn't matter. Have an open ticket with ESRI but have yet to hear back.

I've also tried editing the service's cfg with listCustomCRS and listSupportedCRS to no avail.

  • Is CRS:84 one of the listed CRS in the version 1.3.0 GetCapabilities response? Also I'm surprised that CRS=3857 succeeds what happens if you specify CRS=EPSG:3857? – nmtoken Mar 26 '15 at 13:00
  • @wchatx I am having the same problem! – a1234 Mar 26 '15 at 13:09
  • 1
    Yes, and as I understand it, CRS:84 is just 4326 for WMS 1.3.0 (per this help doc). And CRS=EPSG:3857 appears to succeed. Thanks, didn't notice that before. – wchatx Mar 26 '15 at 13:14

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.