Geocoding Workflow

The workflow for requesting geocoding jobs is as follows:

Decide which address information you wish to use to generate geocoder WGS-84 compliant latitude and longitude values.

Make a geocode request with a request body that defines the columns provide the source for the geocoded information and the names of the target columns. You can also add a list of strings that Geovisualization appends to the input columns. This is useful if you have a list of street addresses from the same town or country, but no column for that data. Appending the strings helps further specify the correct location for the geocoder service.

The processing of a geocode request may take some time, so the response to the request includes a unique ID that you can use to check the status of your request. Geocoder requests can have the following statuses:

pending

running

completed

failed

Make a geocode job status request to determine the status of your geocoding request. (You can also cancel a working geocode request.)

Once the geocode request job status is completed, you can use the new WGS-84 latitude and longitude in your dataset in visualizations.

If you prefer to use a GUI, you can use the GeovisualizationData Manager to geocode a dataset.

Requesting a Geocoding Job

To request a new geocoding job, you first need to have a dataset available. For more information on how to load data, see Managing your Data.

Once you have an appropriate dataset, you define a JSON request body that specifies the columns in the dataset to convert to geocoordinates and the names of the new target columns for the geocordinates:

Note: The value for the id field is a unique identifier for the submitted geocoding request. You can use this ID to determine the status of the request, as discussed in the following topic.

Checking the Status of a Geocoding Job

Once you have made a geocode request for a dataset, you can check the job's status with a GET to the following resource, replacing {GEOCODE_JOB_ID} with the job id returned in the response to the geocode request. (In the example above, that id is c0d0f18e3c184ffd9167e4ddc8bfe133) :