I am running Cesium in sandbox, and trying to access wms layers from geoserver I am running locally on a virtual machine but having trouble returning the wms data.

The request hits the tile image, but I think nothing is being returned, or there is some issue with processing the data on the way back when trying to be processed in Cesium.

ex: the request url:

reaches an image/tile: enter image description here

  • the response headers: Access-Control-Allow-Origin:* Connection:keep-alive Content-Type:application/vnd.ogc.se_xml;charset=UTF-8 Date:Mon, 10 Aug 2015 19:46:08 GMT Server:nginx Strict-Transport-Security:max-age=31536000; includeSubdomains; Transfer-Encoding:chunked X-Frame-Options:SAMEORIGIN X-XSS-Protection:1; mode=block

how do i interpret the type: vnd.ogc.se_xml ?

  • the errors are: An error occurred in "WebMapServiceImageryProvider": Failed to obtain image tile X: N Y: N Level: N.

  • The relevant code is as follows:

    var viewer = new Cesium.Viewer('cesiumContainer');

    var provider = new Cesium.WebMapServiceImageryProvider({ url: 'url_to_wms_server', layers : 'layer_name' }); viewer.imageryLayers.addImageryProvider(provider);

any idea what's going wrong or what to change?

also, when i change the version to 1.3.0, the response type is text/xml but the url does not hit an image when i check.

  • 1
    About how to interpret the MIME type, it is written into WMS 1.1.0 standard as Service Exception Report XML shall be valid according to the Service Exception DTD in Annex A.3. In an HTTP environment, the MIME type of the returned XML shall be "application/vnd.ogc.se_xml".
    – user30184
    Aug 11, 2015 at 14:05
  • 1
    When you switch to version 1.3.0, you'll need to change srs=epsg:4326& to crs=CRS:84&, for your map to work in Cesium
    – nmtoken
    Feb 13, 2019 at 21:29

1 Answer 1


If you read the WMS Spec you will see how to set the format of the error messages that the server sends you.

In this case it is clearly saying that the number 256: is invalid. Somewhere you are sending a request with that number in it, check the URL. For more information turn up the logging verbosity in GeoServer and it will send you back more details, or you could look in the log file to see what is going wrong there.

  • 256 and 256 are the default parameters -set by cesium - of the height and width of the tile. those parameters and url provided go to the tile image, which is 256x256. I don't see what could be wrong with those numbers especially since the url goes to the tile image. see the documentation for WebMapServiceImageryProvider, which is the function that is being used and sets those parameters. cesiumjs.org/Cesium/Build/Documentation/… thoughts?
    – jf2qm
    Aug 11, 2015 at 14:20
  • but your 256 has a : on the end
    – Ian Turton
    Aug 11, 2015 at 14:32
  • is that not just the formatting of the error message?
    – jf2qm
    Aug 11, 2015 at 14:51
  • No that is the error message - that's why GeoServer put quotes around it
    – Ian Turton
    Aug 11, 2015 at 14:52
  • I've cleaned up your formatting to help clarify this
    – Ian Turton
    Aug 11, 2015 at 14:54

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.