[Qgis-developer] SLD export not compliant due to unit attribute in the root element
Andrea Aime
andrea.aime at geo-solutions.it
Sat Jul 23 05:53:32 PDT 2016
Hi,
I'm looking into improving the SLD export, and stumbled into a schema
violation
that, if fixed, may cause other regression.
In particular, the root element StyledLayerDescriptor contains a "units"
attribute that
is not part of the SLD/SE specification, and thus makes validation fail:
<?xml version="1.0" encoding="UTF-8"?>
<StyledLayerDescriptor xmlns="http://www.opengis.net/sld" xmlns:ogc="
http://www.opengis.net/ogc" xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance" version="1.1.0" xmlns:xlink="
http://www.w3.org/1999/xlink" *units="mm" *xsi:schemaLocation="
http://www.opengis.net/sld
http://schemas.opengis.net/sld/1.1.0/StyledLayerDescriptor.xsd" xmlns:se="
http://www.opengis.net/se">
...
</StyledLayerDescriptor>
It's in particular the units="mm" element. Checking the git history I found
it has been introduced by this commit:
---------------------
b54b159 - rldhont <rldhont at gmail.com> 23-ott-2015
[BUGFIX] Set default units to mm in exportSld
The default units in QgsMapRenderer is Millimeters. The default units in SLD
is Pixel but exportSld does not convert all millimeters in pixels.
We notes this bug by comparing default QGS Server rendering and rendering
with
the SLD generated by QGIS.
To resolve it, we just have to add units to the document element.
---------------------
The above comments seems to suggest something is actually using that
attribute, but I'm not sure what.
Mind, GeoServer can parse the file the same, but if users try to validate
it (there is a validation button in the style editor), they will get the
following error:
"ine 2: cvc-complex-type.3.2.2: Attribute 'units' is not allowed to appear
in element 'StyledLayerDescriptor'."
Also, the attribute per se does nothing in a compliant client, since SLD
1.1 lacks the very concept of "on screen unit", the uom allowed
are pixel (on screen), meter (on ground), feet (on ground).
A SLD export trying to be compliant should convert mm to pixels assuming
some DPI conversion factor (which means,
making many changes around... bummer). I see there is already a uomScale in
the conversion properties, but I see it's not
used for point symbol sizes (as the commit message says.. I actually don't
see it being used anywhere).
Would it be ok to remove that attribute and use uomScale to properly adapt
sizes from mm to px instead?
Cheers
Andrea
--
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.
==
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*
Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.
The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.
-------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20160723/32981066/attachment.html>
More information about the Qgis-developer
mailing list