Who doesn’t love to get fully valid metadata?

The product team at wetransform has been working towards full compliance with version 2.0 of the Technical Guidance for the implementation of INSPIRE dataset and service metadata based on ISO/TS 19139:2007 over the past several months. A special thanks goes to Eleazar Araujo for his dedicated efforts in implementing the requirements.

We are pleased to announce that auto-generated hale»connect dataset and network service metadata is now fully compliant with that technical guidance.

wetransform helped develop the release planning process for the INSPIRE Reference Validator and as we look towards the last scheduled release of the year to include potentially breaking changes, we’d like to share some of the challenges that have kept us busy.

Adapting for Change

The migration from metadata version 1.3 to 2.0 involves a long list of removed requirements, new requirements, changed requirements and combined or altered requirements. For an exhaustive list of changes, review this document.

Important clarifications on the handling of conditions applying to access and use were introduced in metadata version 2.0, outlined in TG Requirement C.17 and TG Requirement C.18. The hale»connect metadata editor now enables users to make a selection from the INSPIRE Limitations on public access codelist. In the actual metadata, this codelist entry is encoded using gmx:Anchor. Users can now also select a codelist value from the INSPIRE Conditions applying to access and use codelist to set access and use conditions.

New requirements

The INSPIRE validator has added a new conformance class, Conformance Class 2b: INSPIRE data sets and data set series metadata for Monitoring to test INSPIRE monitoring and reporting requirements, including spatial scope and priority dataset keywords, that are not a part of the technical guidance.

The hale»connect metadata editor now enables users to tag metadata with a descriptive keyword from the Spatial scope controlled vocabulary in the INSPIRE Registry. The purpose of the codelist is to enable the monitoring of the distribution of regional and national level datasets supplied by Member States. Visit the [INSPIRE Maintenance and Implementation Group MIG for more information.

In addition to the Spatial scope keyword, the hale»connect metadata editor also supports tagging datasets with value(s) from to the Priority Dataset controlled vocabulary in the INSPIRE Registry. Priority dataset keywords serve to identify priority datasets provided by Member States and facilitate the discovery of datasets in the Thematic Viewer. For more information about the technical implementation of tagging priority datasets for the INSPIRE Thematic Viewer, visit the INSPIRE helpdesk wiki. Both Spatial scope and Priority dataset codelist values can be added directly to hale»connect metadata using dropdown menus in the dataset metadata editor.

Ever evolving

More changes are coming up, and we will monitor them and adapt our solutions to make sure your datasets, metadata and services remain compliant with the ever-changing demands of INSPIRE requirements.

Compliance is a complex topic which involves not only the technical requirements and the INSPIRE validator, but also tests run by third party solution providers OGC CITE, and new issues that can arise when testing new datasets in new conformance classes which contain elements that trigger the execution of additional tests.

Although all of our generated metadata is error free, hale»connect WMS view services currently receive a schema validation error because we include http://schemas.opengis.net/sld/1.1.0/sld_capabilities.xsd in the schema location of the GetCapabilities document. We do this to offer the GetLegendGraphic request and we are currently discussing the issue in the INSPIRE validator community as we are of the opinion that it should be permitted.

hale»connect WFS download services receive temporal filter validation errors for some datasets that contain temporal elements due to an error in the OGC CITE Team Engine, which has been fixed in the latest release. Once the updated Direct WFS conformance class is rolled out, the INSPIRE validator will use it and the issues will be resolved. hale»connect ATOM feeds continue to receive errors due to known bugs that we are working to solve.

We are testing continuously, and in doing so we hope to provide hale»connect users implementing automated metadata solutions a framework for metadata 2.0 compliancy and beyond.

Other hale connect updates

While compliance has been the number 1 priority, we’ve also added some new features.

Shapefile and attachments publishing

hale»connect now supports publishing shapefiles with referenced attachments. Relative file references added to fields within shapefile attribute tables are recognized as attachments and transferred to the target dataset if there is a transformation configured for the dataset. Attachments can include .PDF, .PNG, .PGW, .GeoTIFF or other file formats. Attachments provide users the option to serve additional, supportive documents in pre-defined download services. Learn more about attachments on hale»connect.

Copy Profiles

Profiles can now be copied on hale»connect. This functionality enables the use of existing profiles as a base for other profiles, which might be more restrictive. When copying a profile that belongs to an organisation other than the current user’s context, both the profile and the underlying schema must have the access permissions set to “Public”.

Who doesn’t love to get fully valid metadata?

The product team at wetransform has been working towards full compliance with version 2.0 of the Technical Guidance for the implementation of INSPIRE dataset and service metadata based on ISO/TS 19139:2007 over the past several months. A special thanks goes to Eleazar Araujo for his dedicated efforts in implementing the requirements.

We are pleased to announce that auto-generated hale»connect dataset and network service metadata is now fully compliant with that technical guidance.

wetransform helped develop the release planning process for the INSPIRE Reference Validator and as we look towards the last scheduled release of the year to include potentially breaking changes, we’d like to share some of the challenges that have kept us busy.

Adapting for Change

The migration from metadata version 1.3 to 2.0 involves a long list of removed requirements, new requirements, changed requirements and combined or altered requirements. For an exhaustive list of changes, review this document.

Important clarifications on the handling of conditions applying to access and use were introduced in metadata version 2.0, outlined in TG Requirement C.17 and TG Requirement C.18. The hale»connect metadata editor now enables users to make a selection from the INSPIRE Limitations on public access codelist. In the actual metadata, this codelist entry is encoded using gmx:Anchor. Users can now also select a codelist value from the INSPIRE Conditions applying to access and use codelist to set access and use conditions.

New requirements

The INSPIRE validator has added a new conformance class, Conformance Class 2b: INSPIRE data sets and data set series metadata for Monitoring to test INSPIRE monitoring and reporting requirements, including spatial scope and priority dataset keywords, that are not a part of the technical guidance.

The hale»connect metadata editor now enables users to tag metadata with a descriptive keyword from the Spatial scope controlled vocabulary in the INSPIRE Registry. The purpose of the codelist is to enable the monitoring of the distribution of regional and national level datasets supplied by Member States. Visit the [INSPIRE Maintenance and Implementation Group MIG for more information.

In addition to the Spatial scope keyword, the hale»connect metadata editor also supports tagging datasets with value(s) from to the Priority Dataset controlled vocabulary in the INSPIRE Registry. Priority dataset keywords serve to identify priority datasets provided by Member States and facilitate the discovery of datasets in the Thematic Viewer. For more information about the technical implementation of tagging priority datasets for the INSPIRE Thematic Viewer, visit the INSPIRE helpdesk wiki. Both Spatial scope and Priority dataset codelist values can be added directly to hale»connect metadata using dropdown menus in the dataset metadata editor.

Ever evolving

More changes are coming up, and we will monitor them and adapt our solutions to make sure your datasets, metadata and services remain compliant with the ever-changing demands of INSPIRE requirements.

Compliance is a complex topic which involves not only the technical requirements and the INSPIRE validator, but also tests run by third party solution providers OGC CITE, and new issues that can arise when testing new datasets in new conformance classes which contain elements that trigger the execution of additional tests.

Although all of our generated metadata is error free, hale»connect WMS view services currently receive a schema validation error because we include http://schemas.opengis.net/sld/1.1.0/sld_capabilities.xsd in the schema location of the GetCapabilities document. We do this to offer the GetLegendGraphic request and we are currently discussing the issue in the INSPIRE validator community as we are of the opinion that it should be permitted.

hale»connect WFS download services receive temporal filter validation errors for some datasets that contain temporal elements due to an error in the OGC CITE Team Engine, which has been fixed in the latest release. Once the updated Direct WFS conformance class is rolled out, the INSPIRE validator will use it and the issues will be resolved. hale»connect ATOM feeds continue to receive errors due to known bugs that we are working to solve.

We are testing continuously, and in doing so we hope to provide hale»connect users implementing automated metadata solutions a framework for metadata 2.0 compliancy and beyond.

Other hale connect updates

While compliance has been the number 1 priority, we’ve also added some new features.

Shapefile and attachments publishing

hale»connect now supports publishing shapefiles with referenced attachments. Relative file references added to fields within shapefile attribute tables are recognized as attachments and transferred to the target dataset if there is a transformation configured for the dataset. Attachments can include .PDF, .PNG, .PGW, .GeoTIFF or other file formats. Attachments provide users the option to serve additional, supportive documents in pre-defined download services. Learn more about attachments on hale»connect.

Copy Profiles

Profiles can now be copied on hale»connect. This functionality enables the use of existing profiles as a base for other profiles, which might be more restrictive. When copying a profile that belongs to an organisation other than the current user’s context, both the profile and the underlying schema must have the access permissions set to “Public”.

(more)

News entry thumbnail
hale»studio 4.0: Ready for the Future - and for XPlanung!
01.07.2020 by Thorsten Reitz, Christopher Hönn

Our main objective for this release has been to modernize hale studio from the ground up, by making it compliant with current OpenJDK versions, using the most recent eclipse RCP version, and by upgrading as many dependencies such as GeoTools as feasible. While we did not yet achieve full compliance with Java 11, we think that the current builds have accumulated so many updates that it is worth giving it to you as a new major release:

  • Major updates to the documentation and help
  • Reader and Writer for GeoPackage
  • A specific Writer for XPlanGML that supports partitioning by plan
  • Added presets for CEN/TS 17268 (TN-ITS), ISO 19139, XPlanGML 4.0/4.1/5.0/5.1/5.2/5.3beta and GeoInfoDok 6.0.1/7.0/7.1
  • Enhancements for GML Dictionary Codelist handling
  • Support for TLS 1.2
  • Various bug fixes and enhancements

The complete changelog is available here. To avoid any compatibility issues when using an existing workspace, we recommend starting with a fresh one when you install hale»studio 4.0. Furthermore, due to the GeoTools & JTS upgrade, the geometry bindings have changed. This breaks backwards compatibility of Groovy Scripts and Alignments created in 4.0. We will provide information on how you can manually backport your Groovy scripts if necessary.

If you are a user of the hale studio pro plugins, you need to upgrade these as well. Please reach out to the Servicedesk to get the new plug-ins.

If you would like to get some hale»studio training, check out our current webinar schedule.

Reader and Writer for GeoPackage

GeoPackage is the optimal, open format for delivering medium to large sized data sets to GIS users. It is a single file that can store tables, vector geometries and rasters. It is extensible and can deal with simple and more detailed data models well. There is even the option to add views and to store styles in a GeoPackage. It doesn’t have issues such as 11 character attribute limits, unknown encodings, missing or incomplete projection files, and is very fast to access.

For these reasons, there have been several requests to add GeoPackage to the list of supported formats for hale studio. We have now added a Reader and a Writer. The Writer can create GeoPackages from scratch, including the schema and metadata. This means you can even use an XML schema and then write your data to a GeoPackage. However, the required model transformations to make this work in complex cases are planned for the next release.

This work was funded by the Umweltbundesamt Austria and Rijkswaterstaat Netherlands, and supported by the European Environmental Agency.

XPlanGML writer and presets

XPlanung is a standard for all kinds of spatial plans that is currently implemented by thousands of agencies all across Germany. To make the work with XPlanGML in hale studio easier, we have added two features - Schema Presets for all releveant XPlanGML versions, and a writer that creates XPlanAuszug files without requiring manual configuration. This writer furthermore supports writing the data to one file per plan object - so you will get a file that has, for example the BP_Plan, the BP_Bereich and all directly or indirectly referenced objects.

This work was supported by the XLeitstelle.

Download hale studio

Download the latest version and send us your feedback:

Thanks to our customers for funding this work on the 27th release of hale studio!

Make it hot: hale studio pro

Learn how the hale studio pro packages can help you to

  • benefit from our INSPIRE knowledge transfer
  • validate data against the INSPIRE / ETF
  • connect with enterprise databases
  • and join in on the hale»studio community milestone meetings (e.g. on July 2nd, 2020 at 15:30 CEST).

Our main objective for this release has been to modernize hale studio from the ground up, by making it compliant with current OpenJDK versions, using the most recent eclipse RCP version, and by upgrading as many dependencies such as GeoTools as feasible. While we did not yet achieve full compliance with Java 11, we think that the current builds have accumulated so many updates that it is worth giving it to you as a new major release:

  • Major updates to the documentation and help
  • Reader and Writer for GeoPackage
  • A specific Writer for XPlanGML that supports partitioning by plan
  • Added presets for CEN/TS 17268 (TN-ITS), ISO 19139, XPlanGML 4.0/4.1/5.0/5.1/5.2/5.3beta and GeoInfoDok 6.0.1/7.0/7.1
  • Enhancements for GML Dictionary Codelist handling
  • Support for TLS 1.2
  • Various bug fixes and enhancements

The complete changelog is available here. To avoid any compatibility issues when using an existing workspace, we recommend starting with a fresh one when you install hale»studio 4.0. Furthermore, due to the GeoTools & JTS upgrade, the geometry bindings have changed. This breaks backwards compatibility of Groovy Scripts and Alignments created in 4.0. We will provide information on how you can manually backport your Groovy scripts if necessary.

If you are a user of the hale studio pro plugins, you need to upgrade these as well. Please reach out to the Servicedesk to get the new plug-ins.

If you would like to get some hale»studio training, check out our current webinar schedule.

Reader and Writer for GeoPackage

GeoPackage is the optimal, open format for delivering medium to large sized data sets to GIS users. It is a single file that can store tables, vector geometries and rasters. It is extensible and can deal with simple and more detailed data models well. There is even the option to add views and to store styles in a GeoPackage. It doesn’t have issues such as 11 character attribute limits, unknown encodings, missing or incomplete projection files, and is very fast to access.

For these reasons, there have been several requests to add GeoPackage to the list of supported formats for hale studio. We have now added a Reader and a Writer. The Writer can create GeoPackages from scratch, including the schema and metadata. This means you can even use an XML schema and then write your data to a GeoPackage. However, the required model transformations to make this work in complex cases are planned for the next release.

This work was funded by the Umweltbundesamt Austria and Rijkswaterstaat Netherlands, and supported by the European Environmental Agency.

XPlanGML writer and presets

XPlanung is a standard for all kinds of spatial plans that is currently implemented by thousands of agencies all across Germany. To make the work with XPlanGML in hale studio easier, we have added two features - Schema Presets for all releveant XPlanGML versions, and a writer that creates XPlanAuszug files without requiring manual configuration. This writer furthermore supports writing the data to one file per plan object - so you will get a file that has, for example the BP_Plan, the BP_Bereich and all directly or indirectly referenced objects.

This work was supported by the XLeitstelle.

Download hale studio

Download the latest version and send us your feedback:

Thanks to our customers for funding this work on the 27th release of hale studio!

Make it hot: hale studio pro

Learn how the hale studio pro packages can help you to

  • benefit from our INSPIRE knowledge transfer
  • validate data against the INSPIRE / ETF
  • connect with enterprise databases
  • and join in on the hale»studio community milestone meetings (e.g. on July 2nd, 2020 at 15:30 CEST).

(more)

From July until September 2020 we plan to offer a variety of new and free webinars on INSPIRE, data transformation, hale studio & hale connect. Three webinars will be in German – one of them of on XPlanung. Of course, the new release of hale»studio 4.0 will also play an important role:

  • 02.07.2020, 15:30 - 17:00 hale»studio Community Milestone Planning Meeting (English)
  • 09.07.2020, 15:00 - 15:45 AGIT 2020: Geodatenharmonisierung mit hale»studio (German) (AGIT requires participation fee)
  • 15.07.2020, 13:00 - 14:00 hale»connect: An introduction to managing INSPIRE data (English)
  • 23.07.2020, 13:00 - 14:00 hale»connect: Building an INSPIRE platform for municipalities (English)
  • 19.08.2020, 13:00 - 14:00 hale»connect: Installing hale»connect on premise (English)
  • 26.08.2020, 13:00 - 14:00 hale»studio 4: New functions (English)
  • 03.09.2020, 13:00 - 14:00 hale»connect: Metadata configurations (English)
  • 09.09.2020, 13:00 - 14:00 hale»studio: Neue Funktionen für XPlanung (German)
  • 16.09.2020, 13:00 - 14:00 hale»connect: Automated transformation workflows (English)
  • 23.09.2020, 13:00 - 14:00 hale»studio: Einführung in die Datentransformation nach INSPIRE (German)

If you want to learn more about it or register for any of the webinars, you just need to send an email at info@wetransform.to along with your name and your organization. All dates and webinar topics are planned and still subject to change or cancellation. In this case registrants will be informed automatically.

From July until September 2020 we plan to offer a variety of new and free webinars on INSPIRE, data transformation, hale studio & hale connect. Three webinars will be in German – one of them of on XPlanung. Of course, the new release of hale»studio 4.0 will also play an important role:

  • 02.07.2020, 15:30 - 17:00 hale»studio Community Milestone Planning Meeting (English)
  • 09.07.2020, 15:00 - 15:45 AGIT 2020: Geodatenharmonisierung mit hale»studio (German) (AGIT requires participation fee)
  • 15.07.2020, 13:00 - 14:00 hale»connect: An introduction to managing INSPIRE data (English)
  • 23.07.2020, 13:00 - 14:00 hale»connect: Building an INSPIRE platform for municipalities (English)
  • 19.08.2020, 13:00 - 14:00 hale»connect: Installing hale»connect on premise (English)
  • 26.08.2020, 13:00 - 14:00 hale»studio 4: New functions (English)
  • 03.09.2020, 13:00 - 14:00 hale»connect: Metadata configurations (English)
  • 09.09.2020, 13:00 - 14:00 hale»studio: Neue Funktionen für XPlanung (German)
  • 16.09.2020, 13:00 - 14:00 hale»connect: Automated transformation workflows (English)
  • 23.09.2020, 13:00 - 14:00 hale»studio: Einführung in die Datentransformation nach INSPIRE (German)

If you want to learn more about it or register for any of the webinars, you just need to send an email at info@wetransform.to along with your name and your organization. All dates and webinar topics are planned and still subject to change or cancellation. In this case registrants will be informed automatically.

(more)

Free hale»studioTraining on May 20th at 13:00 CEST (English)

Last month over a hundred users attended our introductory webinar to hale»studio. Now we offer a follow-up training – again, free of charge! The webinar on May 20th addresses hale»studio users with a beginner or intermediate level of expertise. We will therefore address aspects of data transformation that can be challenging for this user group.

To allow you an even better learning experience, you can look at the webinar topics in advance here. Just follow the links (more …) to the descriptions in the online help:

  1. Installing plug-ins for loading a FileGeodatabase
  2. Loading multiple WFS services that require a combined schema by creating a combined schema
  3. Loading multiple shapefiles and CSV files
  4. Using Join or Spatial join functions for multiple source datasets
  5. Using the Merge function
  6. Using the classification function with an Excel Mapping table
  7. Filtering attributes by setting condition contexts on source data attributes
  8. Mapping filtered data by using the Assign Bound function
  9. Visualizing data by filtering them in the views for source data and for transformed data and displaying them in the map view
  10. Selecting instances in the map view and displaying them in the views for source data and for transformed data

You can register for the webinar here…


…or register for the webinar by sending an email with your contact details to info@wetransform.to and enter Registration for TOP 10 Challenges as subject.

Happy transforming!

Free hale»studioTraining on May 20th at 13:00 CEST (English)

Last month over a hundred users attended our introductory webinar to hale»studio. Now we offer a follow-up training – again, free of charge! The webinar on May 20th addresses hale»studio users with a beginner or intermediate level of expertise. We will therefore address aspects of data transformation that can be challenging for this user group.

To allow you an even better learning experience, you can look at the webinar topics in advance here. Just follow the links (more …) to the descriptions in the online help:

  1. Installing plug-ins for loading a FileGeodatabase
  2. Loading multiple WFS services that require a combined schema by creating a combined schema
  3. Loading multiple shapefiles and CSV files
  4. Using Join or Spatial join functions for multiple source datasets
  5. Using the Merge function
  6. Using the classification function with an Excel Mapping table
  7. Filtering attributes by setting condition contexts on source data attributes
  8. Mapping filtered data by using the Assign Bound function
  9. Visualizing data by filtering them in the views for source data and for transformed data and displaying them in the map view
  10. Selecting instances in the map view and displaying them in the views for source data and for transformed data

You can register for the webinar here…


…or register for the webinar by sending an email with your contact details to info@wetransform.to and enter Registration for TOP 10 Challenges as subject.

Happy transforming!

(more)

After last week’s focus on Groovy, today we will take a closer look on other advanced functions and functionalities of hale studio that often get overlooked but provide great value. Making good use of these functionalities can help you on your way to becoming a more efficient hale studio power user.

For the remainder of this article it’s assumed that you have working knowledge of hale studio and are familiar with its terminology. For a primer on hale studio concepts, please refer to the online help.

Synchronize Schema Explorer and Alignment View

In large and complex source and/or target schemas, it can become difficult to find a specific source type or attribute. If you have the type or attribute relation open in the Alignment view, the button “Synchronise with cell selection” (highlighted in the screenshot below) can simplify navigation. When active, hale studio will jump to the source and target types or attributes of the selected mapping in the Schema Explorer.

Spatial Join

An advanced feature of hale studio is its ability to join objects of your source dataset based on the spatial relationship of their geometries with the Spatial Join transformation function. In contrast, the regular Join is limited to the equality of textual attributes. For the comparison of geometries, Spatial Join supports all modes of the Dimensionally Extended nine-Intersection Model: contains, covered by, covers, crosses, equals, intersects, overlaps, touches, and within.

Internally, Spatial Join is powered by a spatial index that is built when hale studio imports the source data. You can leverage the spatial index in your own Groovy scripts via the helper functions _.geom.spatialIndexQuery and _.geom.boundaryCovers. Make sure to check out our previous post on the subject if you would like to learn more about using the spatial index in Groovy scripts!

Filtering Data with Contexts

In hale studio, a context on a schema element can be used to restrict the element to certain instances or property values. After setting a context on a schema element, the effect of mapping cells defined on that element is limited to the instances or property values that match the context condition.

A special type of context is the index context that can be used in cases where the order of elements in the source instance conveys a special meaning. In the example below, the information on the language of a name is given implicitly through the order in which the names appear. The first name is in German, the second name is in English, and the third one is in Italian.

More information about contexts is available in the hale studio help. There you can also find a tutorial on how to create contexts.

Make the Most of the Map View

The Map view of hale studio provides you with a cartographic representation of both source and transformed data. Both can be displayed alongside each other, with different layouts to choose from. An often overlooked feature of the Map view is that you can select geometries by clicking on them and then inspect the properties of the corresponding object in the data view. You can also select multiple instances, just hold the Ctrl key when you click. Selected instances are highlighted in red, as can be seen in the screenshot below.

You can find the data views for source and transformed instances directly beneath the map. To show the properties of the objects selected in the map, activate the Use instances selected in the application mode in the upper left corner of the data view.

Vice versa you can also filter the data view and highlight the geometries of the filtered instances in the map. To do that, first activate the Random/filtered source data instances mode in the data view (upper left corner), then enter the desired filter expression and finally activate the globe button in the upper right corner of the data view. In the screenshot below, the source objects were filtered for a specific value of the bodenart property. The geometries of the filtered objects are highlighted in red in the map.

Happy transforming!

After last week’s focus on Groovy, today we will take a closer look on other advanced functions and functionalities of hale studio that often get overlooked but provide great value. Making good use of these functionalities can help you on your way to becoming a more efficient hale studio power user.

For the remainder of this article it’s assumed that you have working knowledge of hale studio and are familiar with its terminology. For a primer on hale studio concepts, please refer to the online help.

Synchronize Schema Explorer and Alignment View

In large and complex source and/or target schemas, it can become difficult to find a specific source type or attribute. If you have the type or attribute relation open in the Alignment view, the button “Synchronise with cell selection” (highlighted in the screenshot below) can simplify navigation. When active, hale studio will jump to the source and target types or attributes of the selected mapping in the Schema Explorer.

Spatial Join

An advanced feature of hale studio is its ability to join objects of your source dataset based on the spatial relationship of their geometries with the Spatial Join transformation function. In contrast, the regular Join is limited to the equality of textual attributes. For the comparison of geometries, Spatial Join supports all modes of the Dimensionally Extended nine-Intersection Model: contains, covered by, covers, crosses, equals, intersects, overlaps, touches, and within.

Internally, Spatial Join is powered by a spatial index that is built when hale studio imports the source data. You can leverage the spatial index in your own Groovy scripts via the helper functions _.geom.spatialIndexQuery and _.geom.boundaryCovers. Make sure to check out our previous post on the subject if you would like to learn more about using the spatial index in Groovy scripts!

Filtering Data with Contexts

In hale studio, a context on a schema element can be used to restrict the element to certain instances or property values. After setting a context on a schema element, the effect of mapping cells defined on that element is limited to the instances or property values that match the context condition.

A special type of context is the index context that can be used in cases where the order of elements in the source instance conveys a special meaning. In the example below, the information on the language of a name is given implicitly through the order in which the names appear. The first name is in German, the second name is in English, and the third one is in Italian.

More information about contexts is available in the hale studio help. There you can also find a tutorial on how to create contexts.

Make the Most of the Map View

The Map view of hale studio provides you with a cartographic representation of both source and transformed data. Both can be displayed alongside each other, with different layouts to choose from. An often overlooked feature of the Map view is that you can select geometries by clicking on them and then inspect the properties of the corresponding object in the data view. You can also select multiple instances, just hold the Ctrl key when you click. Selected instances are highlighted in red, as can be seen in the screenshot below.

You can find the data views for source and transformed instances directly beneath the map. To show the properties of the objects selected in the map, activate the Use instances selected in the application mode in the upper left corner of the data view.

Vice versa you can also filter the data view and highlight the geometries of the filtered instances in the map. To do that, first activate the Random/filtered source data instances mode in the data view (upper left corner), then enter the desired filter expression and finally activate the globe button in the upper right corner of the data view. In the screenshot below, the source objects were filtered for a specific value of the bodenart property. The geometries of the filtered objects are highlighted in red in the map.

Happy transforming!

(more)