Background Geo-Coding

Learn about jobs to retrieve and recalculate geocodes in the background.

Background geo-coding consists in the following tasks executed by CRM.server:

Both tasks are executed in one step by the BatchGeocodingJob job as defined in the settings.server.xml file:

<!--
Update missing or faulty geo-coordinates in records each night at 2 o'clock
You need a valid Bing license!
-->
<Job schedule="0 2 * * * " type="update.Crm.Server.Jobs.BatchGeocodingJob,update.Crm.Server">
The catalog value of the precision catalog: all records with a value equal or lower is recoded
<Precision>2</Precision>
The interval which should be checked: i.e. P1Y2M10DT2H30M
<Timespan>P2D</Timespan>
</Job>

Available parameters (for more details,see Re-Encoding Failed Geo-Codings):

Precision

Defines the precision of records which should be re-encoded. All records with a lower value is re-encoded.

Timespan

Defines the interval which is subtracted from the current date to re-encode all records with a value lower than this date in the Updated (Geo-coordinates) field.

Background geo-coding can only be executed on a Aurea CRM database containing a server license, see Aurea CRM License.

To enable server-side geo-coding, enable the Use Geo-coordinates configuration options (Geo-Coordinates category) in the Configuration info area (MC), see Geo-Coordinates.

In addition, at least the following configuration options must be defined:

  • License key
  • Geolocation handler

To restrict geo-encoding to batch-geocoding only, set the Active in the following modules option to "mmse".