Skip to main content Skip to complementary content

tGoogleMapLookup Standard properties

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

The Standard tGoogleMapLookup 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, Talend MDM Platform and in Talend Data Fabric.

Basic settings

Schema and Edit Schema

A schema is a row description, it defines the number of fields to be processed and passed on to the next component. The schema is either Built-in or stored remotely in the Repository.

Sync columns

Click this button to retrieve schema from the previous component connected in the Job.

Pause(in 1/10 seconds) Time break between http requests for geographic information record. By default, the value for this field is 1.
Latitude Column Select the schema column that holds the latitude information.
Longitude Column Select the schema column that holds the longitude information.

API key

To enter a key, click the […] button next to the field.

You must generate the API key from the Google Developer Console at

Information noteNote: Jobs migrated from releases older than 5.6 will need a key to run. Generate a key and set it in tGoogleMapLoopup basic settings before running the Job.

The component currently works with the Google Places API and not the Google Geocoding API as it was the case in releases older than 5.6. As a result, when you run the migrated Jobs in the current Talend Studio, you will have geographic information different from what you had in previous Talend Studio versions. For example, the Location_type column outputs ROOFTOP in older releases, while it outputs street_address now. You can find the list of location types at Place Types.

Advanced settings


Customize this field to import Java class for tGoogleMapLookup. By default, you do not have to modify this part.

tStatCatcher Statistics

Select this check box to collect log data at the component level.

Enable parallel execution
Select this check box to perform high-speed data processing, by treating multiple data flows simultaneously. Note that this feature depends on the database or the application ability to handle multiple inserts in parallel as well as the number of CPU affected. In the Number of parallel executions field, either:
  • Enter the number of parallel executions desired.
  • Press Ctrl + Space and select the appropriate context variable from the list. For further information about context variables, see Using contexts and variables.

Note that when parallel execution is enabled, it is not possible to use global variables to retrieve return values in a subJob.

  • The Action on table field is not available with the parallelization function. Therefore, you must use a tCreateTable component if you want to create a table.
  • When parallel execution is enabled, it is not possible to use global variables to retrieve return values in a subJob.

Global Variables

Global Variables

NB_LINE: the number of rows read by an input component or transferred to an output component. This is an After variable and it returns an integer.

ERROR_MESSAGE: the error message generated by the component when an error occurs. This is an After variable and it returns a string. This variable functions only if the Die on error check box is cleared, if the component has this check box.

A Flow variable functions during the execution of a component while an After variable functions after the execution of the component.

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 it.

For more information about variables, see Using contexts and variables.


Usage rule

This component is used as an in-between component. It requires an input component, an output component and row Main link.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!