{"id":1550,"date":"2020-05-07T11:35:11","date_gmt":"2020-05-07T11:35:11","guid":{"rendered":"https:\/\/wetransform.eu\/?post_type=news-and-events&p=1550"},"modified":"2022-07-28T08:03:54","modified_gmt":"2022-07-28T08:03:54","slug":"mapping-attributes-type-level","status":"publish","type":"news-and-events","link":"https:\/\/wetransform.to\/de\/news-and-events\/mapping-attributes-type-level\/","title":{"rendered":"Groovy Week 2020: Mapping Attributes on the Type Level to Split a Feature"},"content":{"rendered":"

In our fourth installment of the 2020 Groovy Week, we are going to take a look at how to map attributes in Groovy type transformation functions and how to use that to create multiple target objects for a single source object. Like in the previous Groovy Week posts, note that this article assumes you have working knowledge of hale\u00bbstudio and know the terminology.<\/p>\n

Thursday's Script: Mapping Attributes on the Type Level to Split a Feature (Florian)<\/h2>\n

The normal approach to map values of source attributes to the target is to invoke an attribute transformation function like Rename<\/code>, Classification<\/code> or Groovy Script<\/code>. These attribute-level functions let you create a target value based on the value(s) of the source attribute(s). Here is an example for a simple Rename<\/code> that maps the source description<\/code> attribute to the target attribute of the same name. The function is part of the Retype<\/code> of the source type River<\/code> to the target type Watercourse<\/code>.<\/p>\n

\"hale\u00bbstudio<\/p>\n

If we replace the type transformation function Retype<\/code> by a Groovy Retype<\/code>, we can achieve the same result as with the Rename<\/code> function by using the _target<\/code> instruction in the script:<\/p>\n