Re-Encoding Failed Geo-Codings

After batch-geocoding is completed and if the limit of the daily quota is not yet exceeded, records with a low geo-coding precision are re-encoded.

The following records are updated:

• A configuration entry Geolocation Handler (MC) is defined for the record's info area.
• Mandatory address fields (Country, City, Street and ZipCode (default) or custom fields as defined by the Field Mapping configuration entry) are not empty.
• Records with Precision below acceptable (as defined by the <Precision> attribute, see below).

  Records with Precision = "Manual input" are not changed.

• The date of the last geo-encoding (Updated (Geo-coordinates) field) is older than the re-encoding timespan (as defined by the <Timespan> attribute, see below).
• The records to be re-encoded are ordered by Date ascendant (= oldest first) and Precision descendant (lowest first).

The amount of records to be re-encoded is limited by the maximum batch size and the daily quota that is left. The sum of the number of records geo-coded by batch-geocoding and re-encoded may not exceed the daily quota.

The precision and timespan defining which records are to re-encoded is defined in the settings.server.xml file:

<Job schedule="0 2 * * * " type="update.Crm.Server.Jobs.BatchGeocodingJob,update.Crm.Server">
<Precision>2</Precision>
<Timespan>P2D</Timespan>
</Job>

Enter the code of the desired value of catalog Precision (97), e.g. 2 for "High". In this case records with Precision = "Medium", "Low" and "failed" is re-encoded.

Enter the timespan using ISO 8601, see http://en.wikipedia.org/wiki/ISO_8601#Durations.

Examples:

P1Y2M10DT2H30M => 1 year, 2 months, 10 days, 2 hours and 30 minutes.

Values without a value can be omitted: P2D => 2 days.