Cannot Geocode An Address With Floor And Apartment Using the MWM Latin American Spanish Laguage Pack Due To Missing Navteq Mapdata Profile in GC_PARSER_PROFILES
(Doc ID 1305059.1)
Last updated on AUGUST 03, 2015
Applies to:Oracle Utilities Mobile Workforce Management - Version: 2.0
Information in this document applies to any platform.
With the Navteq map data for an alternate country, the direction "<street street#>, <city>, <Country>" is positioned, but the direction "<street street#>,<apartment #>, <city>, <Country>" is not geocoded. In this case, the MWM Latin American Spanish Language Pack is being used such that something like 'Floor 3' is entered as "Piso 3".
Sending direct SQL such as:
SELECT SDO_GCDR.GEOCODE( 'NAVTEQ_UTIL', SDO_KEYWORDARRAY( '6828 HATHAWAY RD', '3rd Floor', '', '', '', '', 'CUYAHOGA', '', 'OH', '' ), 'USA', 'DEFAULT') GC FROM DUAL
Returns with a matchlevel=1 for the successful cases and matchlevel=4 for the last, failed example. Matchlevel=4 is not acceptable for routing in MWM.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document