{"id":1756,"date":"2015-11-02T17:32:50","date_gmt":"2015-11-02T17:32:50","guid":{"rendered":"https:\/\/wetransform.eu\/?post_type=news-and-events&p=1756"},"modified":"2022-07-08T11:57:11","modified_gmt":"2022-07-08T11:57:11","slug":"hale-2-9-4","status":"publish","type":"news-and-events","link":"https:\/\/wetransform.to\/de\/neuigkeiten-veranstaltungen\/hale-2-9-4\/","title":{"rendered":"GeoServer App-Schema Integration: HALE 2.9.4 is out"},"content":{"rendered":"
\n

HALE has been supported well by the community in the past months with contributions, through support subscriptions<\/a> and projects. We have thus been able to create an additional feature and maintenance release. So, why should you upgrade?<\/p>\n<\/div>\n

<\/p>\n

\n

GeoServer App-Schema configuration<\/h2>\n

Publishing OGC services based on GML Application Schemas and Complex Features with GeoServer<\/a> is now easier than ever. Use HALE to define the mapping from your data store to an application schema, such as INSPIRE or NAS. Then, upload the resulting configuration for the GeoServer App-Schema plugin<\/a> directly to your GeoServer instance. This feature was developed together with GeoSolutions S.R.L, Italy<\/a>. More information on the new feature including future plans is available at the GeoSolutions Blog<\/a>.<\/p>\n

\n

Inline transformations<\/h2>\n

Declarative Mapping, as implemented in HALE, is about simplification and effective re-use of transformation projects. When you encounter complex structures in your data, the mapping can still get quite complicated. By using the Inline transformation function<\/em>, you tell HALE that it should transform objects in a complex feature the same way as it would standalone features. <\/p>\n

As an example, let\u2019s look at a mapping between two CityGML ADEs. In both source and target schemas, there are a Building and a BuildingPart type. BuildingParts can be features on their own, thus a mapping is defined based on a Retype between the corresponding source and target types. Buildings can also contain BuildingParts, and to transform these internal BuildingParts we use the Inline transformation<\/em>, with the additional step to include it in the respective target property. <\/p>\n

Namespace agnostic loading of XML\/GML<\/h2>\n

HALE relies on qualified names for the transformation and handling of data, which consist of local names and namespaces. In many cases, you still want to transform data where only the local name matches. This can be the case for instance when using data based on a previous version of a schema or for data that is published via an OGC Web Feature Service. We have added an option when loading XML or GML data that instances will be loaded even if the namespaces do not match the schemas exactly. <\/p>\n

HL Consulting BVBA<\/a> funded this work under a Professional Support Subscription for HALE<\/a>. They use this feature to define their alignments on a schema that allows them to make extensive use of relation inheritance in their alignment, to have one mapping that they can use to transform data from different services.<\/p>\n

Tweaks and Bug fixes<\/h2>\n

We\u2019ve added a lot of smaller improvements and fixed some issues:<\/p>\n