Question

ResolvedDomainPopulator

  • 18 May 2024
  • 0 replies
  • 35 views

Userlevel 4
Badge +13
FME Hub user geospatialize just uploaded a new transformer to the FME Hub.

Overview

Custom transformer designed to address a common issue when working with resolved domain columns in FME. When a reader is set to resolve domains, but the coded value is not found in the corresponding domain, the "_resolved" field is populated as null.

This can lead to inconsistencies and require manual intervention to handle the null values. The ResolvedDomainPopulator automatically populates these null values in the "_resolved" columns with the corresponding values from the original columns.

It ensures data consistency and eliminates the need for additional transformers or manual effort to handle the null values. However, it is important to note that this transformer assumes that all resolvable domains have been properly resolved before its application. It does not perform the actual resolution process itself. To maintain data integrity, ensure that the domain resolution process is completed using appropriate transformers or methods before applying the ResolvedDomainPopulator.

It's important to note that the ResolvedDomainPopulator transformer does not add or remove any attributes or features. It only modifies the existing "_resolved" columns based on the corresponding original column values.

Output

The ResolvedDomainPopulator transformer modifies the input features and outputs the modified features with the following changes:

Null values in the "_resolved" columns are populated with the corresponding values from the original columns.

If the original column value is not null or empty, it will be used to populate the null value in the corresponding "_resolved" column.

If the original column value is also null or empty, the "_resolved" column will remain null.

Features without "_resolved" columns or features where the "_resolved" columns already have non-null values are passed through unchanged.

The output features will have the same schema as the input features, with the updated values in the "_resolved" columns where applicable. All other attributes and geometry of the features remain unmodified.

Usage

Add the ResolvedDomainPopulator custom transformer to your FME workspace.

In the reader settings for the Esri ArcGIS Portal Feature Service data, make sure to enable the resolution of domain values. This can typically be done by setting the "Resolve Domains" or "Resolve Coded Values" option to "Yes" or checking the corresponding checkbox.

Connect the reader feature type containing the Esri ArcGIS Portal Feature Service data to a transformer that resolves the assetgroup and other important domain values.

For example: Use an AttributeRenamer transformer to rename the "arcgisonline_subtype_name" attribute to "assetgroup" to resolve the asset group domain values.

Connect the output of the transformer used in step 3 to the ResolvedDomainPopulator custom transformer.

Connect the output of the ResolvedDomainPopulator custom transformer to the desired writer (e.g., file geodatabase or ArcSDE geodatabase).

Run the workspace.



Would you like to know more? Click here to find out more details!

This post has been closed for comments