2018 still feels like a fresh year, so here’s a fresh hale studio release to go with this! Despite some large changes under the hood, we’ve decided to make this a bugfix release mostly, with some smaller enhancements:
The whole list is available in the changelog.
Get the latest version, and let us know what you think of it!
This release of hale studio improves the integration with the online collaboration platform hale connect. It is now possible to select which organisation should own an uploaded transformation project for cases where the currently logged-in user is member of more than one organisation. Furthermore, hale studio now supports a relogin with same or different credentials without having to clear the credentials stored in preferences.
(E)CQL doesn’t just contain simple operators, but also a large set of functions that can be applied to any operand in any place where hale studio enables the use of such filters:
Filter functions can be used to build expressions such as
strToLowerCase(VALUE) like '%m%'. They also simplify many expressions, e.g. through functions such as
IN(val1, val2, ...), which needed an OR chain of comparisons so far, or
between(val, low, high) statements. It is even possible to use spatial functions to filter by the spatial relationship -
contains(geomA, geomB) will return
The Geoserver Documentation includes a full reference of the available functions.
This work was funded by the Landesbetrieb Geoinformation und Vermessung Hamburg through a support contract.
When you load source data from shapefiles, and then export the transformed data later on to a different projection / coordinate reference system, you may have encountered an error message like
Missing Bursa-Wolf Parameters. More information on this specific issue is available with the GeoTools documentation. Furthermore, there were cases where the axes were swapped due to inconsistent CRS definitions across different systems. With some enhancements to how hale studio interprets and uses CRS definitions from various sources (Shapefiles, GML, internal EPSG database), hale now avoids most of the pitfalls of these two issues.
When loading source data, hale studio now provides the content of the srsName attribute (in case of a GML source) or the WKT definition found in the projection file (.prj) that accompanies a Shapefile. This allows the user to select the correct CRS without having to manually look up this information in the source files.
Importing a schema or source data from a Shapefile requires the user to select the encoding of the Shapefile. In cases where the Shapefile is accompanied by a Codepage file (.cpg), hale studio can now read the encoding from that file a prefill the character set selection dialog.