The aim of the project is to develop an application enabling the generation of SLD files, where a user has complete control over all aspects of the OGC SLD standard.
Main features include:
Vector (point, line and polygon) symbol editing
Raster symbol editing
Text symbol editing
Vector and raster legend image generation
Functions, filters, expressions, transformations all configurable via dialogs.
Inline feature support
GeoServer vendor options supported:
extshapes://, qgis:// marker shapes
Polygon random fills
Integration with GeoServer
YSLD import and export facility
Tools to improve workflow, including batch updates of fonts and rule scales.
Ability to convert Esri MXD files to SLD files (requires separate licensed components not supplied as part of this project) Build instructions here
A compiled single executable jar is available here, runs on macOS, Windows and Linux:
- SLDEditor Release 0.8.5 Released 22 Jan 2019
and can be started:
java -jar SLDEditor.jar
Due to the changes in Java, double clicking on the executable jar file does not work any more, specific OS installers/applications are available here:
An installer is available here: SLDEditor DMG Installer
An installer is available here: SLDEditor Windows Installer
A debian package installation has been created:
To add the Ubutnu PPA to your system
sudo add-apt-repository ppa:robward/sldeditorppa sudo apt-get update
sudo apt-get install sldeditor
I’ve been developing the application for about 18 months as a side project. The idea started when SciSys did some consultancy work and put together a proposal for an organisation to migrate from an Esri system to an OpenLayers/GeoServer stack. When it came to migrating ~1250 layers we didn’t know what number to put down for symbol conversion to SLD. When you looked at the numbers this was a large percentage of the overall cost and something needed to be done to reduce it if we were going to be competitive in doing migrations to open source GIS systems.
One of our long standing large enterprise GIS systems required a change to an SLD symbol which we used QGIS to edit. It turned out there was a known bug that caused the change to be forgotten. I looked to fix it, I’m very familiar with C++ and Qt but found it difficult to debug and realised the SLD styling data model was not completely implemented.
I looked at using GeoTools because I knew it could parse SLD files and render them. Another big advantage is that it supports all the GeoServer vendor options, in particular the labelling. I got something simple working quite quickly and it went from there.
Ideally all this functionality should be in QGIS, but QGIS would have to be rewritten to use a C++ version of GeoTools to be able to render the GeoServer vendor options, which will not happen overnight. I know of people that would love this capability and understand the reluctance for yet another application. I think as long as GeoServer is so heavily used, a Java desktop SLD Editor application is acceptable.
There have been discussions about developing a web-front end for the application, a possibility. However not all GIS systems we deliver are web based and some customer networks do not allow web access or a web server to be deployed without going through a lot of hoops. A standalone desktop application ensures there is no dependency on any other infrastructure.
One of the aims of the application is to work in a connected/disconnected environment.
The application is nearing a version 1.0.
There are some further GeoServer vendor options yet to be implemented.
Further testing is needed to ensure the application is rock solid.
There will be some work needed to understand why some symbols don’t display. I’m thinking windbarbs where I believe I’m passing the correct data but the symbol is not rendered.
The SLD Editor licensed under the GPLv3.
This application is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
The project documentation exists in the GitHub project wiki.