reference.rst 21 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641
  1. .. _wms_reference:
  2. WMS reference
  3. =============
  4. Introduction
  5. ------------
  6. The OGC `Web Map Service <http://www.opengeospatial.org/standards/wms>`_ (WMS) specification
  7. defines an HTTP interface for requesting georeferenced map images from a server.
  8. GeoServer supports WMS 1.1.1, the most widely used version of WMS, as well as WMS 1.3.0.
  9. The relevant OGC WMS specifications are:
  10. - `OGC Web Map Service Implementation Specification, Version 1.1.1 <http://portal.opengeospatial.org/files/?artifact_id=1081&version=1&format=pdf>`_
  11. - `OGC Web Map Service Implementation Specification, Version 1.3.0 <http://portal.opengeospatial.org/files/?artifact_id=14416>`_
  12. GeoServer also supports some extensions to the WMS specification made by the Styled Layer Descriptor (SLD) standard to control the styling of the map output.
  13. These are defined in:
  14. - `OpenGIS Styled Layer Descriptor Profile of the Web Map Service Implementation Specification, Version 1.1.0 <http://portal.opengeospatial.org/files/?artifact_id=22364>`_
  15. Benefits of WMS
  16. ---------------
  17. WMS provides a standard interface for requesting a geospatial map image. The benefit of this is that WMS clients can request images from multiple WMS servers, and then combine them into a single view for the user. The standard guarantees that these images can all be overlaid on one another as they actually would be in reality. Numerous servers and clients support WMS.
  18. Operations
  19. ----------
  20. WMS requests can perform the following operations:
  21. .. list-table::
  22. :widths: 20 80
  23. * - **Operation**
  24. - **Description**
  25. * - `GetCapabilities`_
  26. - Retrieves metadata about the service, including supported operations and parameters, and a list of the available layers
  27. * - `GetMap`_
  28. - Retrieves a map image for a specified area and content
  29. * - `GetFeatureInfo`_
  30. - Retrieves the underlying data, including geometry and attribute values, for a pixel location on a map
  31. * - `DescribeLayer`_
  32. - Indicates the WFS or WCS to retrieve additional information about the layer.
  33. * - `GetLegendGraphic`_
  34. - Retrieves a generated legend for a map
  35. .. _wms_getcap:
  36. GetCapabilities
  37. ~~~~~~~~~~~~~~~
  38. The **GetCapabilities** operation requests metadata about the operations, services, and data ("capabilities") that are offered by a WMS server.
  39. The parameters for the GetCapabilities operation are:
  40. .. list-table::
  41. :widths: 20 10 70
  42. * - **Parameter**
  43. - **Required?**
  44. - **Description**
  45. * - ``service``
  46. - Yes
  47. - Service name. Value is ``WMS``.
  48. * - ``version``
  49. - Yes
  50. - Service version. Value is one of ``1.0.0``, ``1.1.0``, ``1.1.1``, ``1.3.0``.
  51. * - ``request``
  52. - Yes
  53. - Operation name. Value is ``GetCapabilities``.
  54. GeoServer provides the following vendor-specific parameters
  55. for the GetCapabilities operation.
  56. They are fully documented in the :ref:`wms_vendor_parameters` section.
  57. .. list-table::
  58. :widths: 20 10 70
  59. * - **Parameter**
  60. - **Required?**
  61. - **Description**
  62. * - ``namespace``
  63. - No
  64. - limits response to layers in a given namespace
  65. * - ``format``
  66. - No
  67. - request the capabilities document in a certain format
  68. * - ``rootLayer``
  69. - No
  70. - Flag to enable/disable the standard Root top level Layer element. Values are true or false. When false, the Root element will be included only if there are multiple top level layers, if there is only one, it will be the root layer itself.
  71. When specified, will override the global WMS setting or layer / group setting for the same behaviour.
  72. A example GetCapabilities request is: ::
  73. http://localhost:8080/geoserver/wms?
  74. service=wms&
  75. version=1.1.1&
  76. request=GetCapabilities
  77. There are three parameters being passed to the WMS server, ``service=wms``, ``version=1.1.1``, and ``request=GetCapabilities``.
  78. The ``service`` parameter tells the WMS server that a WMS request is forthcoming.
  79. The ``version`` parameter refers to which version of WMS is being requested.
  80. The ``request`` parameter specifies the GetCapabilities operation.
  81. The WMS standard requires that requests always includes these three parameters.
  82. GeoServer relaxes these requirements (by setting the default version if omitted),
  83. but for standard-compliance they should always be specified.
  84. The response is a Capabilities XML document that is a detailed description of the WMS service.
  85. It contains three main sections:
  86. .. list-table::
  87. :widths: 20 80
  88. * - **Service**
  89. - Contains service metadata such as the service name, keywords, and contact information for the organization operating the server.
  90. * - **Request**
  91. - Describes the operations the WMS service provides and the parameters and output formats for each operation.
  92. If desired GeoServer can be configured to disable support for certain WMS operations.
  93. * - **Layer**
  94. - Lists the available coordinate systems and layers.
  95. In GeoServer layers are named in the form "namespace:layer".
  96. Each layer provides service metadata such as title, abstract and keywords.
  97. .. _wms_getmap:
  98. GetMap
  99. ~~~~~~
  100. The **GetMap** operation requests that the server generate a map.
  101. The core parameters specify one or more layers and styles to appear on the map,
  102. a bounding box for the map extent,
  103. a target spatial reference system,
  104. and a width, height, and format for the output.
  105. The information needed to specify values for parameters such as ``layers``, ``styles`` and ``srs`` can be obtained from the Capabilities document.
  106. The response is a map image, or other map output artifact, depending on the format requested.
  107. GeoServer provides a wide variety of output formats, described in :ref:`wms_output_formats`.
  108. The standard parameters for the GetMap operation are:
  109. .. list-table::
  110. :widths: 20 10 70
  111. * - **Parameter**
  112. - **Required?**
  113. - **Description**
  114. * - ``service``
  115. - Yes
  116. - Service name. Value is ``WMS``.
  117. * - ``version``
  118. - Yes
  119. - Service version. Value is one of ``1.0.0``, ``1.1.0``, ``1.1.1``, ``1.3.0``.
  120. * - ``request``
  121. - Yes
  122. - Operation name. Value is ``GetMap``.
  123. * - ``layers``
  124. - Yes
  125. - Layers to display on map.
  126. Value is a comma-separated list of layer names.
  127. * - ``styles``
  128. - Yes
  129. - Styles in which layers are to be rendered.
  130. Value is a comma-separated list of style names,
  131. or empty if default styling is required.
  132. Style names may be empty in the list, to use default layer styling.
  133. * - ``srs`` *or* ``crs``
  134. - Yes
  135. - Spatial Reference System for map output.
  136. Value is in form ``EPSG:nnn``.
  137. ``crs`` is the parameter key used in WMS 1.3.0.
  138. * - ``bbox``
  139. - Yes
  140. - Bounding box for map extent.
  141. Value is ``minx,miny,maxx,maxy`` in units of the SRS.
  142. * - ``width``
  143. - Yes
  144. - Width of map output, in pixels.
  145. * - ``height``
  146. - Yes
  147. - Height of map output, in pixels.
  148. * - ``format``
  149. - Yes
  150. - Format for the map output.
  151. See :ref:`wms_output_formats` for supported values.
  152. * - ``transparent``
  153. - No
  154. - Whether the map background should be transparent.
  155. Values are ``true`` or ``false``.
  156. Default is ``false``
  157. * - ``bgcolor``
  158. - No
  159. - Background color for the map image.
  160. Value is in the form ``RRGGBB``.
  161. Default is ``FFFFFF`` (white).
  162. * - ``exceptions``
  163. - No
  164. - Format in which to report exceptions.
  165. Default value is ``application/vnd.ogc.se_xml``.
  166. * - ``time``
  167. - No
  168. - Time value or range for map data.
  169. See :ref:`wms_time` for more information.
  170. * - ``sld``
  171. - No
  172. - A URL referencing a :ref:`StyledLayerDescriptor <styling>` XML file
  173. which controls or enhances map layers and styling
  174. * - ``sld_body``
  175. - No
  176. - A URL-encoded :ref:`StyledLayerDescriptor <styling>` XML document
  177. which controls or enhances map layers and styling
  178. GeoServer provides a number of useful vendor-specific parameters for the GetMap operation.
  179. These are documented in the :ref:`wms_vendor_parameters` section.
  180. Example WMS request for ``topp:states`` layer to be output as a PNG map image in SRS EPGS:4326 and using default styling is: ::
  181. http://localhost:8080/geoserver/wms?
  182. request=GetMap
  183. &service=WMS
  184. &version=1.1.1
  185. &layers=topp%3Astates
  186. &styles=population
  187. &srs=EPSG%3A4326
  188. &bbox=-145.15104058007,21.731919794922,-57.154894212888,58.961058642578&
  189. &width=780
  190. &height=330
  191. &format=image%2Fpng
  192. The standard specifies many of the parameters as being mandatory,
  193. GeoServer provides the :ref:`tutorials_wmsreflector` to allow many of them to be optionally specified.
  194. Experimenting with this feature is a good way to get to know the GetMap parameters.
  195. Example WMS request using a GetMap XML document is:
  196. .. code-block:: xml
  197. <?xml version="1.0" encoding="UTF-8"?>
  198. <ogc:GetMap xmlns:ogc="http://www.opengis.net/ows"
  199. xmlns:gml="http://www.opengis.net/gml"
  200. version="1.1.1" service="WMS">
  201. <StyledLayerDescriptor version="1.0.0">
  202. <NamedLayer>
  203. <Name>topp:states</Name>
  204. <NamedStyle><Name>population</Name></NamedStyle>
  205. </NamedLayer>
  206. </StyledLayerDescriptor>
  207. <BoundingBox srsName="http://www.opengis.net/gml/srs/epsg.xml#4326">
  208. <gml:coord><gml:X>-130</gml:X><gml:Y>24</gml:Y></gml:coord>
  209. <gml:coord><gml:X>-55</gml:X><gml:Y>50</gml:Y></gml:coord>
  210. </BoundingBox>
  211. <Output>
  212. <Format>image/png</Format>
  213. <Size><Width>550</Width><Height>250</Height></Size>
  214. </Output>
  215. </ogc:GetMap>
  216. Time
  217. ....
  218. As of GeoServer 2.2.0, GeoServer supports a TIME attribute for WMS GetMap requests as described in version 1.3.0 of the WMS specification.
  219. This parameter allows filtering a dataset by temporal slices as well as spatial tiles for rendering.
  220. See :doc:`/services/wms/time` for information on its use.
  221. .. _wms_getfeatureinfo:
  222. GetFeatureInfo
  223. ~~~~~~~~~~~~~~
  224. The **GetFeatureInfo** operation requests the spatial and attribute data for the features
  225. at a given location on a map.
  226. It is similar to the WFS :ref:`wfs_getfeature` operation, but less flexible in both input and output.
  227. Since GeoServer provides a WFS service we recommend using it instead of ``GetFeatureInfo`` whenever possible.
  228. The one advantage of ``GetFeatureInfo`` is that the request uses an (x,y) pixel value from a returned WMS image.
  229. This is easier to use for a naive client that is not able to perform true geographic referencing.
  230. The standard parameters for the GetFeatureInfo operation are:
  231. .. list-table::
  232. :widths: 20 10 70
  233. * - **Parameter**
  234. - **Required?**
  235. - **Description**
  236. * - ``service``
  237. - Yes
  238. - Service name. Value is ``WMS``.
  239. * - ``version``
  240. - Yes
  241. - Service version. Value is one of ``1.0.0``, ``1.1.0``, ``1.1.1``, ``1.3.0``.
  242. * - ``request``
  243. - Yes
  244. - Operation name. Value is ``GetFeatureInfo``.
  245. * - ``layers``
  246. - Yes
  247. - See :ref:`wms_getmap`
  248. * - ``styles``
  249. - Yes
  250. - See :ref:`wms_getmap`
  251. * - ``srs`` *or* ``crs``
  252. - Yes
  253. - See :ref:`wms_getmap`
  254. * - ``bbox``
  255. - Yes
  256. - See :ref:`wms_getmap`
  257. * - ``width``
  258. - Yes
  259. - See :ref:`wms_getmap`
  260. * - ``height``
  261. - Yes
  262. - See :ref:`wms_getmap`
  263. * - ``query_layers``
  264. - Yes
  265. - Comma-separated list of one or more layers to query.
  266. * - ``info_format``
  267. - No
  268. - Format for the feature information response. See below for values.
  269. * - ``feature_count``
  270. - No
  271. - Maximum number of features to return.
  272. Default is 1.
  273. * - ``x`` or ``i``
  274. - Yes
  275. - X ordinate of query point on map, in pixels. 0 is left side.
  276. ``i`` is the parameter key used in WMS 1.3.0.
  277. * - ``y`` or ``j``
  278. - Yes
  279. - Y ordinate of query point on map, in pixels. 0 is the top.
  280. ``j`` is the parameter key used in WMS 1.3.0.
  281. * - ``exceptions``
  282. - No
  283. - Format in which to report exceptions.
  284. The default value is ``application/vnd.ogc.se_xml``.
  285. **Note:** If you are sending a GetFeatureInfo request against a layergroup, all the layers in that layergroup must be set as "Queryable" to get a result (See :ref:`WMS Settings on Layers page<data_webadmin_layers>`)
  286. GeoServer supports a number of output formats for the ``GetFeatureInfo`` response.
  287. Server-styled HTML is the most commonly-used format.
  288. For maximum control and customisation the client should use GML3 and style the raw data itself.
  289. The supported formats are:
  290. .. list-table::
  291. :widths: 15 35 50
  292. * - **Format**
  293. - **Syntax**
  294. - **Notes**
  295. * - TEXT
  296. - ``info_format=text/plain``
  297. - Simple text output. (The default format)
  298. * - GML 2
  299. - ``info_format=application/vnd.ogc.gml``
  300. - Works only for Simple Features (see :ref:`app-schema.complex-features`)
  301. * - GML 3
  302. - ``info_format=application/vnd.ogc.gml/3.1.1``
  303. - Works for both Simple and Complex Features (see :ref:`app-schema.complex-features`)
  304. * - HTML
  305. - ``info_format=text/html``
  306. - Uses HTML templates that are defined on the server. See :ref:`tutorials_getfeatureinfo_html` for information on how to template HTML output.
  307. * - JSON
  308. - ``info_format=application/json``
  309. - Simple JSON representation. See :ref:`tutorials_getfeatureinfo_geojson` for information on how to template JSON output.
  310. * - JSONP
  311. - ``info_format=text/javascript``
  312. - Returns JSONP in the form: ``parseResponse(...json...)``. See :ref:`wms_vendor_parameters` to change the callback name. Note that this format is disabled by default (See :ref:`wms_global_variables`).
  313. GeoServer provides the following vendor-specific parameters
  314. for the GetFeatureInfo operation.
  315. They are fully documented in the :ref:`wms_vendor_parameters` section.
  316. .. list-table::
  317. :widths: 20 10 70
  318. * - **Parameter**
  319. - **Required?**
  320. - **Description**
  321. * - ``buffer``
  322. - No
  323. - width of search radius around query point (in pixels).
  324. * - ``cql_filter``
  325. - No
  326. - Filter for returned data, in ECQL format
  327. * - ``filter``
  328. - No
  329. - Filter for returned data, in OGC Filter format
  330. * - ``propertyName``
  331. - No
  332. - Feature properties to be returned
  333. * - ``exclude_nodata_result``
  334. - No
  335. - When set to true, a *NaN* will be returned when the feature's queried pixel value is nodata.
  336. An example request for feature information from the ``topp:states`` layer in HTML format is: ::
  337. http://localhost:8080/geoserver/wms?
  338. request=GetFeatureInfo
  339. &service=WMS
  340. &version=1.1.1
  341. &layers=topp%3Astates
  342. &styles=
  343. &srs=EPSG%3A4326
  344. &format=image%2Fpng
  345. &bbox=-145.151041%2C21.73192%2C-57.154894%2C58.961059
  346. &width=780
  347. &height=330
  348. &query_layers=topp%3Astates
  349. &info_format=text%2Fhtml
  350. &feature_count=50
  351. &x=353
  352. &y=145
  353. &exceptions=application%2Fvnd.ogc.se_xml
  354. An example request for feature information in GeoJSON format is: ::
  355. http://localhost:8080/geoserver/wms?
  356. &INFO_FORMAT=application/json
  357. &REQUEST=GetFeatureInfo
  358. &EXCEPTIONS=application/vnd.ogc.se_xml
  359. &SERVICE=WMS
  360. &VERSION=1.1.1
  361. &WIDTH=970&HEIGHT=485&X=486&Y=165&BBOX=-180,-90,180,90
  362. &LAYERS=COUNTRYPROFILES:grp_administrative_map
  363. &QUERY_LAYERS=COUNTRYPROFILES:grp_administrative_map
  364. &TYPENAME=COUNTRYPROFILES:grp_administrative_map
  365. The result will be:
  366. .. code-block:: xml
  367. {
  368. "type":"FeatureCollection",
  369. "features":[
  370. {
  371. "type":"Feature",
  372. "id":"dt_gaul_geom.fid-138e3070879",
  373. "geometry":{
  374. "type":"MultiPolygon",
  375. "coordinates":[
  376. [
  377. [
  378. [
  379. XXXXXXXXXX,
  380. XXXXXXXXXX
  381. ],
  382. ...
  383. [
  384. XXXXXXXXXX,
  385. XXXXXXXXXX
  386. ]
  387. ]
  388. ]
  389. ]
  390. },
  391. "geometry_name":"at_geom",
  392. "properties":{
  393. "bk_gaul":X,
  394. "at_admlevel":0,
  395. "at_iso3":"XXX",
  396. "ia_name":"XXXX",
  397. "at_gaul_l0":X,
  398. "bbox":[
  399. XXXX,
  400. XXXX,
  401. XXXX,
  402. XXXX
  403. ]
  404. }
  405. }
  406. ],
  407. "crs":{
  408. "type":"EPSG",
  409. "properties":{
  410. "code":"4326"
  411. }
  412. },
  413. "bbox":[
  414. XXXX,
  415. XXXX,
  416. XXXX,
  417. XXXX
  418. ]
  419. }
  420. .. _wms_describelayer:
  421. DescribeLayer
  422. ~~~~~~~~~~~~~
  423. The **DescribeLayer** operation is used primarily by clients that understand SLD-based WMS.
  424. In order to make an SLD one needs to know the structure of the data.
  425. WMS and WFS both have operations to do this, so the **DescribeLayer** operation just routes the client to the appropriate service.
  426. The standard parameters for the DescribeLayer operation are:
  427. .. list-table::
  428. :widths: 20 10 70
  429. * - **Parameter**
  430. - **Required?**
  431. - **Description**
  432. * - ``service``
  433. - Yes
  434. - Service name. Value is ``WMS``.
  435. * - ``version``
  436. - Yes
  437. - Service version. Value is ``1.1.1``.
  438. * - ``request``
  439. - Yes
  440. - Operation name. Value is ``DescribeLayer``.
  441. * - ``layers``
  442. - Yes
  443. - See :ref:`wms_getmap`
  444. * - ``exceptions``
  445. - No
  446. - Format in which to report exceptions.
  447. The default value is ``application/vnd.ogc.se_xml``.
  448. GeoServer supports a number of output formats for the ``DescribeLayer`` response.
  449. Server-styled HTML is the most commonly-used format.
  450. The supported formats are:
  451. .. list-table::
  452. :widths: 15 35 50
  453. * - **Format**
  454. - **Syntax**
  455. - **Notes**
  456. * - TEXT
  457. - ``output_format=text/xml``
  458. - Same as default.
  459. * - GML 2
  460. - ``output_format=application/vnd.ogc.wms_xml``
  461. - The default format.
  462. * - JSON
  463. - ``output_format=application/json``
  464. - Simple JSON representation.
  465. * - JSONP
  466. - ``output_format=text/javascript``
  467. - Return JSONP in the form: paddingOutput(...jsonp...). See :ref:`wms_vendor_parameters` to change the callback name. Note that this format is disabled by default (See :ref:`wms_global_variables`).
  468. An example request in XML (default) format on a layer is: :
  469. http://localhost:8080/geoserver/topp/wms?service=WMS
  470. &version=1.1.1
  471. &request=DescribeLayer
  472. &layers=topp:coverage
  473. .. code-block:: xml
  474. <?xml version="1.0" encoding="UTF-8"?>
  475. <!DOCTYPE WMS_DescribeLayerResponse SYSTEM "http://localhost:8080/geoserver/schemas/wms/1.1.1/WMS_DescribeLayerResponse.dtd">
  476. <WMS_DescribeLayerResponse version="1.1.1">
  477. <LayerDescription name="topp:coverage" owsURL="http://localhost:8080/geoserver/topp/wcs?" owsType="WCS">
  478. <Query typeName="topp:coverage"/>
  479. </LayerDescription>
  480. </WMS_DescribeLayerResponse>
  481. An example request for feature description in JSON format on a layer group is: ::
  482. http://localhost:8080/geoserver/wms?service=WMS
  483. &version=1.1.1
  484. &request=DescribeLayer
  485. &layers=sf:roads,topp:tasmania_roads,nurc:mosaic
  486. &outputFormat=application/json
  487. The result will be: ::
  488. {
  489. version: "1.1.1",
  490. layerDescriptions: [
  491. {
  492. layerName: "sf:roads",
  493. owsURL: "http://localhost:8080/geoserver/wfs/WfsDispatcher?",
  494. owsType: "WFS",
  495. typeName: "sf:roads"
  496. },
  497. {
  498. layerName: "topp:tasmania_roads",
  499. owsURL: "http://localhost:8080/geoserver/wfs/WfsDispatcher?",
  500. owsType: "WFS",
  501. typeName: "topp:tasmania_roads"
  502. },
  503. {
  504. layerName: "nurc:mosaic",
  505. owsURL: "http://localhost:8080/geoserver/wcs?",
  506. owsType: "WCS",
  507. typeName: "nurc:mosaic"
  508. }
  509. ]
  510. .. _wms_getlegendgraphic:
  511. GetLegendGraphic
  512. ~~~~~~~~~~~~~~~~
  513. The **GetLegendGraphic** operation provides a mechanism for generating legend graphics as images, beyond the LegendURL reference of WMS Capabilities.
  514. It generates a legend based on the style defined on the server, or alternatively based on a user-supplied SLD.
  515. For more information on this operation and the various options that GeoServer supports see :ref:`get_legend_graphic`.
  516. Exceptions
  517. ----------
  518. Formats in which WMS can report exceptions. The supported values for exceptions are:
  519. .. list-table::
  520. :widths: 15 35 50
  521. * - **Format**
  522. - **Syntax**
  523. - **Notes**
  524. * - XML
  525. - ``EXCEPTIONS=application/vnd.ogc.se_xml``
  526. - XML output. (The default format)
  527. * - INIMAGE
  528. - ``EXCEPTIONS=application/vnd.ogc.se_inimage``
  529. - Generates an image
  530. * - BLANK
  531. - ``EXCEPTIONS=application/vnd.ogc.se_blank``
  532. - Generates a blank image
  533. * - PARTIALMAP
  534. - ``EXCEPTIONS=application/vnd.gs.wms_partial``
  535. - This is a GeoServer vendor parameter and only applicable for GetMap requests. Returns everything that was rendered at the time the rendering process threw an exception. Can be used with the :ref:`WMS Configuration Limits <wms_configuration_limits>` to return a partial image even if the request is terminated for exceeding one of these limits. It also works with the ``timeout`` :ref:`vendor parameter <wms_vendor_parameters>`.
  536. * - JSON
  537. - ``EXCEPTIONS=application/json``
  538. - Simple JSON representation.
  539. * - JSONP
  540. - ``EXCEPTIONS=text/javascript``
  541. - Return JSONP in the form: paddingOutput(...jsonp...). See :ref:`wms_vendor_parameters` to change the callback name. Note that this format is disabled by default (See :ref:`wms_global_variables`).