[HSDK] Update OCM to the latest to resolve Routing issues

Routing Appears Off-Road at Intersections After Left Turns in HERE SDK Applications

Applies To

HERE SDK Navigate applications using custom OCM catalog configurations
Applications using custom OCM (Online Catalog Management) catalog configurations
Routing and map-matched route display functionality

Classification

Behavior Type: Data inconsistency

Symptoms

Customers may report one or more of the following:

Calculated routes appear off the road near intersections.
Left-turn maneuvers are displayed with incorrect route geometry.
Route guidance does not align with the visible road network.
The same routing issue occurs across multiple HERE SDK platforms.
Updating the HERE SDK version alone does not resolve the routing behavior.
Route results differ when using different OCM catalog versions.

Answer

If route geometry appears off-road at intersections and SDK upgrades do not resolve the behavior, verify the OCM catalog version used by the application. The issue can be caused by outdated map content in a previously configured OCM catalog version.

Updating the application to use the latest available OCM catalog version can resolve routing display and geometry inconsistencies caused by outdated map content.

Root Cause

The routing behavior is not caused by the HERE SDK software version itself. In affected implementations, the application is configured to use a specific OCM catalog version containing older map data. As a result, route calculations and displayed route geometry may reflect outdated road network information.

When a newer OCM catalog version is used, updated map content is applied and the route aligns correctly with the road network.

Impact

Incorrect route visualization near intersections.
Customer perception of inaccurate routing.
Inconsistent behavior between environments using different catalog versions.
Increased troubleshooting efforts when only SDK versions are reviewed.

Resolution

Configure the application to use the latest available OCM catalog version instead of an older fixed version.

<br /> private void initializeHERESDK() { // Set your credentials for the HERE SDK. String accessKeyID = "your_access_key_ID"; String accessKeySecret = "your_access_key_secret"; AuthenticationMode authenticationMode = AuthenticationMode.withKeySecret(accessKeyID, accessKeySecret); SDKOptions options = new SDKOptions(authenticationMode); // Specify one or more custom catalog configurations. options.catalogConfigurations = getCustomCatalogConfiguration(); try { Context context = this; SDKNativeEngine.makeSharedInstance(context, options); } catch (InstantiationErrorException e) { throw new RuntimeException("Initialization of HERE SDK failed: " + e.error.name()); } } private List getCustomCatalogConfiguration() { List catalogConfigurations = new ArrayList<>(); // OPTION 1: with the latest catalog version. boolean ignoreCachedData = true; CatalogVersionHint versionHint = CatalogVersionHint.latest(ignoreCachedData); // OPTION 2: with a previous catalog version CatalogVersionHint versionHint = CatalogVersionHint.specific(153); String customHRN = "hrn:here:data::olp-here:ocm"; DesiredCatalog customOCMCatalog = new DesiredCatalog(customHRN, versionHint); catalogConfigurations.add(new CatalogConfiguration(customOCMCatalog)); return catalogConfigurations; }<br />

Catalog Configuration Options

1. Latest Catalog Version (Recommended)
Uses the most recent OCM catalog content available for the application.
2. Specific Catalog Version
Uses a fixed catalog version for testing, validation, or issue reproduction scenarios.

CatalogVersionHint versionHint =

CatalogVersionHint.specific(153);

The following screenshots compare routing behavior when using different OCM catalog versions:



Older OCM catalog version showing route geometry misalignment near the intersection.



Updated OCM catalog version showing correct route geometry alignment.

Expected Behavior

When the application uses current OCM catalog data, route geometry should align with the road network and intersection maneuvers should follow the mapped roads correctly.

Unexpected Behavior

When the application uses outdated OCM catalog content, route geometry may appear off-road or misaligned at intersections despite running a supported HERE SDK version.

Additional Notes

Updating the HERE SDK alone may not update the OCM catalog version used by the application.
After changing the catalog configuration, cached map content may remain on the device.
If the updated catalog version is not applied, clear application data or reinstall the application before retesting.

References

* Upgrade from previous versions → Update automatically (HERE SDK documentation)

Keywords

HERE SDK, OCM, catalog version, route off road, intersection routing, left turn issue, route geometry, map data update, catalog configuration, Navigate SDK, routing accuracy, road alignment, map content, custom catalog, route display issue