Geocoding For Some Addresses Do Not Populate Latitude/Longitude On Field Activities Due To Minimum Geocode Quality Values (Doc ID 1509231.1)

Last updated on AUGUST 22, 2016

Applies to:

Oracle Utilities Mobile Workforce Management - Version 2.1.0 and later
Information in this document applies to any platform.

Goal

Geocoding for some addresses does not populate Latitude/Longitude on the Field Activities. Some of the field activities in MWM do not have the Latitude/Longitude populated. All these activities are in Issues Detected state and have "Geocode not found for the given address" (<messageCategory>11002</messageCategory><messageNumber>19401</messageNumber>). The data for geocoding these addresses is fairly accurate with some unusual abbreviations, apartment designations or single typographical error but, we expect that geocoding is possible for this data.

Algorithms M1-LOC-ADDR and M1-ACT-ADGEO were were recently modified by adding a new Minimum Geocode Quality parameter with a value of 11 and a newer effective date than the base parameter.
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms