-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem with exportation of complex SLD #42348
Comments
@MaxDragonheart see https://github.com/qgis/QGIS/issues?q=is%3Aissue+label%3ABug+label%3ASymbology+is%3Aopen+SLD QGIS symbology export to SLD isn't and never was perfect, it works only for relatively simple styles. |
Thank you! |
@MaxDragonheart I would not have many hopes, it is a matter that raised only limited interest in the past years.
I guess, but you would need to define a plan first, and also of course have the plan backed by a developer. |
@MaxDragonheart You might have a look to qgis/QGIS-Enhancement-Proposals#187 |
It seems the issue is due to the field name that contains a space: this generates the Parser Error in the exported sld file. QGIS/src/core/symbology/qgsrendererrange.cpp Lines 147 to 151 in f3a81eb
i.e. enclosing the field name with quotes in the "filterFunc" in other parts of the code e.g.: QGIS/src/core/symbology/qgscategorizedsymbolrenderer.cpp Lines 143 to 155 in 08ca000
|
I agree with @agiudiceandrea -- this is a bug rather than a limitation in QGIS' sld export. |
@MaxDragonheart are you able to supply a sample project demonstrating this issue? |
(oops, clicked the wrong button!) |
If I remove the space, like @agiudiceandrea suggest, some problems are solved, but other complex symbolgies are ignored. @nyalldawson this is the project, hope it is useful :) |
I need to public a webmap using GeoServer 2.17; this represent a complex polygons symbology from QGIS 3.16.
I've exported an SLD file from QGIS and I've used it on GeoServer but the render is complete different.
So I've opened the SLD and I've seen some
Parser Error
:Anyone has my same problem?
From GIS Stackexcenge suggest me that this is a QGIS's bug.
The text was updated successfully, but these errors were encountered: