SLD Editor

BBox filter function issue Whilst working on another project I needed to check how GeoTools handled geometry in the BBox filter function. I got the SLD Editor to open an SLD file with a BBox filter and discovered that an error was reported. After ... [More] some investigation I’ve raised an issue on the GeoTools project here. I have a fix but a couple of queries need to be ironed out before submitting a pull request. [Less]

SLDEditor Release 0.8.3 Version 0.8.3 of the SLD Editor has been released and available here. The release ensures that UTF-8 is used throughout the application as per the SLD specification.

SLDEditor Release 0.8.1 Version 0.8.1 of the SLD Editor has been released and available here. The release updates the functionality of the parameters of temporal filters. The component providing the date picker has been changed to a more actively ... [More] maintained project. In addition the time zone offsets can now be specified via the ui for dates and time periods. Multiple monitors are now supported, dialogs are now displayed on top of the application window even when the application window has been moved to a different monitor. [Less]

Some thoughts on the roadmap for the SLD Editor. Java 11 Currently the application compiles with Java 8 but nothing later due to JAXB being deprecated. The application is closely coupled to GeoTools which is starting to be reworked for Java 11. ... [More] Once development is further advanced I will start to look at updating SLDEditor to work with Java 11. QGIS The application started out as an experiment to see if the GeoTools library could be used to provide the symbol rendering and as grown from there. But it is yet another application and really should be integrated into another application. The likely candidate is QGIS, there is quite a bit of common functionality, but QGIS is written in C++ and SLDEditor and GeoTools in Java. However I have started to develop the SLDEditor functionality in QGIS but have hit a stumbling block in that the macOS build is broken and has been for a long time. For all maven’s faults being able to type one command to install all dependencies and compile the application and knowing it is going work is priceless. Before the build broke I developed classes to read and write SLD files without filter support but with unit tests. When the build works again and I have time I may continue… [Less]

SLDEditor Release 0.8.0 Version 0.8.0 of the SLD Editor has been released and available here. The main area of improvement is the filter dialog where there were a number of issues. Collection_Count function The Collection_Count function in ... [More] GeoTools was returning the wrong parameter description so I created a pull request to fix the issue in GeoTools 20.0. GeoTools filter functions The following functions in GeoTools did not have a toString() method implemented which meant the Java class name was displayed in the filter dialog instead of the function name and parameters: RecodeFunction StringTemplateFunction JenksNaturalBreaksFunction CategorizeFunction UniqueIntervalFunction QuantileFunction StandardDeviationFunction EqualIntervalFunction ConstrastFunction LightenFunction GrayscaleFunction ModuloFunction I created a pull request to fix the issue in GeoTools 20.0. PropertyIsLike function In GeoTools the PropertyIsLike uses String parameters but the Filter specification states that they should be single characters. Updated the code to refelect this. RasterSymbolizer SelectedChannelType expression In GeoTools 20.0 the RasterSymbolizer SelectedChannelType changed from being a value (before GeoServer 2.14) to an expression (GeoServer 2.14 onwards), update the Vendor Option settings to get the benefit. Development internals A number of changes have been made internally including: JUnit 5 Upgraded unit testing to use JUnit 5, relatively painless. JAXB The most painful area has been the move to deprecate JAXB in forthcoming Java versions. JAXB is used to turn the XML schemas into Java objects which can then read the contents of XML files directly into the Java objects. Used to read the user interface field configuration into the application and saves maintaining the XSD and the Java objects. The project still compiles on Java 8 but later versions cause issues with JAXB. I’m hoping Java 11 development catches up and a solution can be found soon. Installers As a consequence of the JAXB issues my aim of creating a single executable JAR for all operating systems this is now not possible. Parameters have to be passed into the JVM which means either a separate script to start the application or installers for all the different operating systems. I’m hoping Java 11 will sort this out but currently there are now separate Windows, Mac OS and Ubuntu installers for the application. Code Coverage Code coverage has increased to 83% but I have created a GeoServer virtual machine using Vagrant to allow the GeoServer integration to be unit tested locally which can increase the code coverage statistics further. Haven’t found a way of hosting this VM in Travis yet to get the increased code coverage numbers. [Less]