# tAddressRowCloud

Verifies and formats international addresses in the Cloud by using online services.

tAddressRowCloud enables you to parse address data and get formatted addresses quickly, accurately and without installing any software.

Address data is corrected against the latest online reference data from several providers including Loqate, MelissaData, Google or QAS. tAddressRowCloud proposes alternatives for missing address data such as country or postal code, and addresses are enriched with other elements such as latitude longitude.

For further information about the terms of services of Google Places API, see [Terms of Service](https://developers.google.com/maps/terms?hl=en).

This component is not shipped with your Talend Studio by default. You need to install it using the Feature Manager. For more information, see [Installing features using the Feature Manager](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/install-features-to-talend-studio).

## tAddressRowCloud Standard properties

These properties are used to configure tAddressRowCloud running in the Standard Job framework.

The Standard tAddressRowCloud component belongs to the Data Quality family.

This component is available in Talend Data Management Platform, Talend Big Data Platform, Talend Real-Time Big Data Platform, Talend Data Services Platform and in Talend Data Fabric.

## Basic settings

| Properties | Description |
| --- | --- |
| Schema | <ul> <li> <p>A schema is a row description. It defines the number of fields            (columns) to be processed and passed on to the next component. When you create a Spark            Job, avoid the reserved word <kbd>line</kbd> when naming the            fields.</p> </li> <li> <p> <span>Built-In</span>: You create and store the schema locally for this component                only.</p> </li> <li> <p> <span>Repository</span>: You have already created the schema and stored it in the                Repository. You can reuse it in various projects and Job designs.</p> </li> </ul> |
| Edit Schema | Click the [...] button and define the<br>input and output schema of the address data.<br><br>The output schema of tAddressRowCloud<br>proposes several read-only address columns including a VerificationLevel column which provides you<br>with a verification status of the processed address. The verification<br>levels in this column are defined by<br>Talend<br>.<br>For further information, see [Address verification levels in tAddressRowCloud](https://help.qlik.com/talend/en-US/components/8.0/address-standardization/taddressrowcloud-taddressrowcloud-address-verification-levels-in-taddressrowcloud-standard-component-enterprise-the).<br><br>As the output schema depends on the address provider, visit its website<br>for further information.<br><br>Also some of the output columns could be empty depending on what<br>address provider you select in the component basic settings when<br>executing the Job. |
| Address Provider | Select from the list the provider of the reference data against which<br>you want to validate and format input addresses.<br><br>The list of address providers includes Google, Loqate, QAS and<br>MelissaData. |
| License/API key | Enter the license or the API key provided by the address provider you<br>select from the list. You must visit the provider website, register and<br>get the license/API key.<br><br>To enter a key, click the […] button next to the field.<br><br>When you select Google as a provider, the component uses the Google<br>Places API. You must generate the key from the Google Developer Console<br>at https://developers.google.com/console/help/new/ and set the<br>key in this field. |
| Processing Mode | This option is applied only to the Loqate provider.<br><br>Select from the list the mode of address validation you<br>want to have:<br><br><ul> <li> <span>Verify and Geocode</span>                                    (selected by default): with this mode, the component                                    standardizes and corrects addresses and enriches them with                                    latitude and longitude information. <p>You must define the                                        address and country columns in the input schema and add them                                        to the <span>Mapping</span> table.</p> </li> <li> <p> <span>Verify                                            only</span>: with this mode, the component                                        standardizes and corrects addresses without enriching them                                        with latitude and longitude information.</p> <p>You must define the address column in the input schema and                                        add it to the <span>Mapping</span> table.</p> </li> </ul><br><br>Information noteNote: These processing modes cost extra credits. For further information, see<br>the [Loqate website](https://www.loqate.com/). |
| Country | This option is applied only to the QAS provider.<br><br>Select from the list the country corresponding to your input<br>addresses.<br><br>When you select QAS as a provider, the component uses the QAS Pro<br>OnDemand service. For further information about Experian address<br>verification, see the product sheet at https://www.edq.com/globalassets/product-sheets/address-verification.pdf. |
| QAS OnDemand username | This option is applied only to the QAS provider.<br><br>Enter the username you can find in the license provided by QAS.<br><br>You can check your username from the QAS OnDemand<br>portal. |
| Password | This option is applied only to the QAS provider.<br><br>Enter the password you can find in the license provided by QAS.<br><br>You can check your password from the QAS OnDemand<br>portal. |
| Use security mode to connect | Select this check box to connect to the Cloud in a secure mode. This<br>may have a slight impact on performance.<br><br>This check box is not available with all address providers. |
| Mapping | Address field: add lines to the table<br>and select from a predefined address list the fields that will hold<br>input addresses.<br><br>The address list includes the following columns for all address<br>providers: Address, PostalCode, Locality, AdministrativeArea and Country.<br><br><br>Input Column: add lines to the table<br>and select from the list the columns that hold addresses from input<br>schema. The input schema can have one or multiple columns and can have<br>columns that do not represent address data. |
| Use Additional Output | This option is not available for the QAS provider.<br><br>Select this check box and use the Output<br>Mapping table to add more address columns to the output<br>schema:<br><br><br>Address field: add<br>lines to the table and select from a predefined address list the fields<br>of the extra information you want to output.<br><br>These predefined address fields vary according to the provider you<br>select from the Address Provider list.<br>For further information about the additional address fields, check the<br>provider website.<br><br><br>Output Column:<br>select from the list the columns that will hold the additional addresses<br>information. You must first add these additional columns to the<br>tAddressRowCloud output<br>schema through the Edit Schema<br>button.<br><br><br>tAddressRowCloud<br>maps the values of the address fields to the output columns in the<br>Output Column.<br><br>If you select to have an output column in the Output Address table that has the exact name of an input<br>column, the input column value will be overwritten by the value given by<br>the component. |
| Die on error | Select the checkbox to stop the execution of the Job when an error<br>occurs.<br><br>Clear the checkbox to skip any rows on error and complete the process for<br>error-free rows. When errors are skipped, you can collect the rows on error using a Row &gt; Reject link. |

## Advanced settings

| Properties | Description |
| --- | --- |
| tStat<br>Catcher<br>Statistics | Select this check box to collect log data at the component<br>level. |

## Global Variables

| Variables | Description |
| --- | --- |
| Global Variables | ERROR\_MESSAGE: the error message generated by the<br>component when an error occurs. This is an After variable and it returns a string. This<br>variable functions only if the Die on error checkbox is<br>cleared, if the component has this checkbox.<br><br>A Flow variable functions during the execution of a component<br>while an After variable functions after the execution of the component.<br><br>To fill up a field or expression with a variable, press Ctrl+Space to access the variable list and choose the variable to use from<br>it.<br><br>For more information about variables, see [Using contexts and variables](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/contexts-and-variables). |

## Usage

| Usage guidance | Description |
| --- | --- |
| **Usage rule** | This component is usually used as an intermediate component, and it requires an<br>input component and an output component.<br><br>This component enables you to create a data flow, using a Row &gt; Main link, and to create a reject flow with a Row &gt; Reject link filtering the data in error. |

**Related concepts**

* [Parsing addresses against reference data in the Cloud](https://help.qlik.com/talend/en-US/components/8.0/address-standardization/taddressrowcloud-tfixedflowinput-tfileoutputexcel-tfileoutputexcel-parsing-addresses-against-reference-data-in-cloud-standard-component-enterprise-this)