:tocdepth: 3

:py:mod:`gws.plugin.ows_client.wms.provider`
============================================

.. py:module:: gws.plugin.ows_client.wms.provider

.. autoapi-nested-parse::

   WMS provider.

   References.

       - OGC 01-068r3: WMS 1.1.1
       - OGC 06-042: WMS 1.3.0

   see also https://docs.geoserver.org/latest/en/user/services/wms/reference.html

   A note on layer order:

   Internally we always list source layers topmost layer first,
   which corresponds to the layer tree display.

   WMS capabilities are assumed to be top-first by default,
   for servers with bottom-first caps, set ``bottomFirst=True``,
   in which case the capabilities parser will revert all layer lists.

   The order of GetMap is always bottom first:

   > A WMS shall render the requested layers by drawing the leftmost in the list bottommost,
   > the next one over that, and so on. (OGC 06-042, 7.3.3.3)

   therefore when invoking GetMap, our layer lists should be reversed.



**Source code:** :source:`gws.plugin.ows_client.wms.provider<gws/plugin/ows_client/wms/provider.py>`



Module Contents
---------------



.. py:class:: Config


   Bases: :py:obj:`gws.base.ows.client.provider.Config`

   WMS provider configuration.

   .. py:attribute:: bottomFirst
      :type:  bool
      :value: False


      True if layers are listed from bottom to top.


.. py:class:: Object


   Bases: :py:obj:`gws.base.ows.client.provider.Object`

   .. py:attribute:: DEFAULT_GET_FEATURE_LIMIT
      :value: 100


   .. py:attribute:: protocol

   .. py:method:: configure()

   .. py:method:: get_features(search, source_layers)