Continuing the following article: The Geoserver
Explorer plugin QGis (1) installation and configuration, we will discuss
limitations of the plugin.
Limitations of the plugin
Here is a list
of limitations and problems likely
to come up.
Limitations related to the SRC.
problems when a custom SRC system
being used by QGIS. The SRC definition that works
rendering the QGIS layer, may not work when importing the layer
. Usually this results in a layer
that is published but that does not have a SRC set
and it is not activated. You can correct
the layer in the Explorer tree
Note that the layers are imported
the SRC defined in the original data source
the file prj if you
a different SRC by using the option Set Layer CRS
the QGIS table of contents will not have any effect when
importing the layer to GeoServer , except
the layer with this SRC so that the SRC definition is stored
with the data layer.
Limitations related to the
Explorer uses the GeoServer REST API to get the list of layers in the catalogue.
The REST API describes the layers without working space,
which means that if you have
layers with the same name and in different workspaces
(for example , ws1: macouche and ws2: macouche ),
they will be displayed just
as one ( macouche in this
When this is the case, the
situation is ambiguous and GeoServer
Explorer cannot differentiate the layers depicting the same name but
to different workspaces. The layer, as described by the
REST API, is added to the explorer tree,
but it represents only one of several layers that share the
same name. To denote this special situation, the layer is
with a warning icon, and a warning message appears
the layer description.
limitation is due to the different
versions of the SLD supported by QGIS and GeoServer .
allows to edit the style of a
from the QGIS interface. It can
a defined QGIS style into a downloaded from the GeoServer
catalogue and use GeoServer styles for the QGIS layers. This
two-way conversion is, however,
This is, mainly, due
to the different versions of SLD supported by QGIS and GeoServer , as well as
GeoServer and QGIS limitations. SLD is in use
a common format by GeoServer Explorer to describe the styles in the QGIS and
GeoServer layers, but some incompatibilities
exist. To increase the compatibility between them, specific
routines have been added
to the explorer GeoServer . However,
in some case, a defined style
QGIS may not be compatible with the elements supported
by GeoServer explorer , and the publication of a layer
will be executed with a modified style , or even
a default style.
This problem exists even
using the latest version of GeoServer, but older versions of GeoServer
more incompatibilities and do not validate
of the SLD produced by the GeoServer explorer.
As a general rule, the basic style
for vector layers should operate
without problems in both ways,
but a more complex symbology
inconsistent, leading to differences between, for example, the style you
QGIS and the style that the GeoServer layer will depict. Raster
layers have a more limited support.
Incidentally, I had to set a style for a QGis project and
load it into Geoserver with the plugin.
The style was correct for GeoServer (what
can be double checked with the option Layers Preview). But when
we tried to reload the layer into QGis, the style was not accepted
Here is a list
of acknowledged limitations for the LTC management:
The raster style is taken in
charge only from QGIS towards GeoServer . It
a raster style can be created
QGIS user interface and downloaded towards GeoServer,
but a raster style from GeoServer cannot be used
for a QGIS layer . When a GeoServer
is added to an ongoing QGIS project with the assistance of GeoServer Explorer,
its symbology will be used only
if it is
layer, but will be ignored in the case of a
layer and the default QGIS style will be used .
pseudo colour Single Band Gray and
Singleband are used.
the correct colour interpolation is not supported, but the
modes Linear and Discrete are employed.
When converting a GeoServer style into
QGIS style, the style is always defined
a style based on rules. This means
that even if the style is created using a different
type, such as graduated when it is downloaded into
a GeoServer catalogue and re-modified from QGIS it
not appear as a Graduate style. This is due to the way QGIS includes
the LTC styles, by, always, interpreting always as
labelling is employed, but all
labels (labels) will not be exported QGIS to LTC and downloaded GeoServer.
the advanced labelling is dependent on the
data is not used.
layer with a QGIS SVG style towards Geoserver generates
layer that respects this SVG symbol.
The same is not supported for the time being if the layer is
a WFS layer .
In the next article we will discuss how to use the Geoserver
Explorer plugin .