tGoogleMapLookup

Obtains detailed geographic information using geographic coordinates and address
information.

tGoogleMapLookup accesses the Google
Places API over HTTP request to obtain detailed geographic information according to the
geographic coordinates you provide.

For further information about Google Places API, see Google Places API.

Each data row needs one or several calls to the Places API. The
quota will depend on the license provided by Google. Make sure not
to run the component on a data set that exceeds your quota,
otherwise you will get error messages and addresses will not be
corrected.

For further information about the usage limits of Google Places
API, see Usage Limits and Billing.

For further information about the terms of services of Google
Places API, see Terms of Service.

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 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	Enter your API key. You must generate the API key from the Google Developer Console at https://developers.google.com/console/help/new/. Note: 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 studio, you will have geographic information different from what you had in older studios. 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

import	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, see Talend Studio User Guide. 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 further information about variables, see Talend Studio User Guide.

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 further information about variables, see
Talend Studio

User Guide.

Usage

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

Obtaining detailed geographic information using address and geographic
coordinates

This scenario applies only to Talend Data Management Platform, Talend Big Data Platform, Talend Real Time Big Data Platform, Talend Data Services Platform, Talend MDM Platform and Talend Data Fabric.

This scenario describes a three-component Job which send HTTP request to Google Places
API and obtain detailed geographic information based on the geographic coordinates we
provide.

Setting up the Job

Drop the following components from the Palette onto the design workspace: tFixedFlowInput, tGoogleMapLookup and tLogRow
Connect tFixedFlowInput to tGoogleMapLookup and tGoogleMapLookup to tLogRow
using Main links.

Configuring the components

Double-click tFixedFlowInput to display
its Basic settings view to define its
properties.
Click Edit schema to open a dialog box
that displays the data structure of input data and define the data you want
to pass to tGoogleMapLookup, two columns in
this scenario, lat and lng
respectively to hold the geographic coordinates.
Set the Type of column
lat and column lng to
Double. Leave rest of the settings as
they are. Then, click OK to close the
dialog box.
Click Use Single Table in the Mode area, fill the Value field of the lat column with
37.5300125 and that of the lng column
with -122.2624254.
Double-click tGoogleMapLookup to display
its Basic settings view and define its
properties.
Select the latitude and longitude columns defined in the input schema,
lat and lng respectively in this example, and leave the rest of
settings as they are.
Double-click tLogRow to display its
Basic settings view and define its
properties.
Select Vertical (each row is a key/value
list) in the Mode area and
Print unique name in the Title printing mode area.

Executing the Job

Save your Job and press F6 to execute
it.

Google Places API has query limits for applications that submit requests.
For further information about the usage limits of Google Places API, see
Usage Limits and
Billing.

The detailed geographic information of the given coordinates location is obtained
from the Google Map database and printed onto the console.

Document get from Talend https://help.talend.com

Thank you for watching.

Docs 7.x

0 Comments

Inline Feedbacks

View all comments

tGoogleMapLookup – Docs for ESB 7.x

tGoogleMapLookup