Geocodes not being Calculated Correctly Due To Incorrect MATCH_MODE
Last updated on MAY 02, 2017
Applies to:Oracle Real-Time Scheduler - Version 2.1.0 and later
Oracle Utilities Mobile Workforce Management - Version 2.0 and later
Information in this document applies to any platform.
There is a high number of addresses that fail to geocode. The records are attempting to geocode through a Bulk Geocode process. The current configuration uses a match_mode= "RELAX_HOUSE_NUMBER".
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