Feature

Additional rendering details like buildings. Only used for the MapView. When not set, the data will be excluded when downloading offline regions or prefetching areas that contain such data. However, during online usage such data may still be downloaded into the cache and shown. Increase of 11-16% is to be expected for map size, in case of enabling this feature.

Feature enables following OCM layer groups:

• “detailed_rendering”

Map data that is used for map matching during navigation. When not set, navigation may not work properly when being used offline. Increase of 5-7% is to be expected for map size, but pay attention, that this feature is depended on other layer groups (e.g. routing), so, in total is takes about 21-29 % of map size.

Feature enables following OCM layer groups:

• “interop”
• “rendering”
• “navigation”
• “routing”

Map data that is used to search. When not set, the OfflineSearchEngine may not work properly when being used offline.

Feature enables following OCM layer groups:

• “rendering”
• “routing”
• “search”

Map data used for global search indexing. This feature enables searches across broader geographic areas and improves both performance and accuracy by leveraging global search indices. By default this feature is disabled.

Enables the HERE SDK to use the enhanced offline search algorithm for downloaded map regions when:

• OFFLINE_SEARCH_GLOBAL is included in LayerConfiguration.enabledFeatures and
• downloaded map regions contain the required OCM layer groups listed below.

Also enables the enhanced offline search algorithm for implicitly prefetched map content when:

• OFFLINE_SEARCH_GLOBAL is included in LayerConfiguration.implicitlyPrefetchedFeatures and
• downloaded map regions (if present) contain the required OCM layer groups.

Both options can be enabled together. However, if enabling the feature for implicitly prefetched content, it is recommended to also enable it for downloaded map regions to ensure consistent search behavior.

Important: After enabling this feature, make sure to update the cached offline maps. If the cached maps are not updated, the algorithm will either:

1. Fall back to the stable offline search if OFFLINE_SEARCH is still included in LayerConfiguration.enabledFeatures, or
2. Produce a LAYERS_NOT_DOWNLOADED error if the necessary layers are missing.

To prevent excessive map size growth, it is recommended to enable only one of OFFLINE_SEARCH_GLOBAL or OFFLINE_SEARCH at a time.

Enabling this feature increases storage requirements:

• Downloaded map region size by ~11–16% when enabled via LayerConfiguration.enabledFeatures.
• Map cache size by ~40–140% when enabled via LayerConfiguration.implicitlyPrefetchedFeatures (upper bound occurs for long routes, e.g., Paris → Rome).

Feature enables following OCM layer groups:

• “search_global”
• “search_data”

Note: This is a beta release of this feature, so there could be a few bugs and unexpected behaviors. Related APIs may change for new releases without a deprecation process.

Map data that is used to calculate routes. When not set, the OfflineRoutingEngine may not work properly when being used offline. Increase of 12-16.5% is to be expected for map size, but pay attention, that this feature is depended on other layer groups (e.g. navigation), so, in total is takes about 33-45 % of map size.

Feature enables following OCM layer groups:

• “rendering”
• “navigation”
• “routing”
• “interop”
• “car_offline_routing”

A basic set of rendering features such as carto POIs. Increase of 16-22% is to be expected for map size, but pay attention, that this feature is depended on other layer groups (e.g. navigation), so, in total is takes about 21-29 % of map size.

Feature enables following OCM layer groups:

• “rendering”

Map data that is used to calculate truck routes. When not set, the OfflineRoutingEngine may not work properly when being used to calculate truck routes. It is also used for map matching during truck navigation and for vehicle restriction visualization. When not set, truck navigation may not work properly when being used offline. Online truck navigation will still work when the device has an online connection. Increase of 0.7-1.1% is to be expected for map size, in case of enabling this feature. By default this feature is disabled.

Feature enables following OCM layer groups:

• “truck”
• “long_truck_offline_routing”
• “truck_offline_routing”

Map data that is used to render 3D landmarks. When not set, the data will be excluded when downloading offline regions or prefetching areas that contain such data. When the landmarks MapFeature is set to be visible for a MapScene, 3D landmarks will still be loaded and visible during online usage. Increase of 2-3% is to be expected for map size, in case of enabling this feature.

3D landmark rendering is enabled by default in grayscale on normal, logistics and topo schemes, and in textureless mode on lite schemes. However, when this map data feature is disabled, the 3D landmark rendering for the above schemes will not work in offline mode with the downloaded map packages. Feature enables following OCM layer groups:

• “landmarks”

Offline map data for EVChargingStation.

Feature enables following OCM layer groups:

• “ev_charging_station_rendering_premium”
• “ev_charging_station_search_premium”

Enables truck related attributes to be returned by Offline Search engine. Feature enables following OCM layer groups:

• “truck_service_premium”

Enables fuel attributes to be returned by Offline Search engine.

Feature enables following OCM layer groups:

• “fueling_station_premium”

Map data that is used to calculate bus routes. When not set, the OfflineRoutingEngine may not be able to calculate routes with BusOptions.

Feature enables following OCM layer groups:

• “bus_offline_routing”

Map data that provides junction view images and assets with aspect ratio 3x4. This will also provide common assets that do not depend on specific aspect ratio. By default this feature is disabled.

Feature enables following OCM layer groups:

• “junction_view_file_3x4”
• “junction_view_asset_3x4”
• “junction_view_asset_common”

Map data that provides junction view images and assets with aspect ratio 16x9. This will also provide common assets that do not depend on specific aspect ratio. By default this feature is disabled.

Feature enables following OCM layer groups:

• “junction_view_file_16x9”
• “junction_view_asset_16x9”
• “junction_view_asset_common”

Map data that provides junction sign images with aspect ratio 3x4. By default this feature is disabled.

Feature enables following OCM layer groups:

• “junction_sign_file_3x4”

Map data that provides junction sign images with aspect ratio 3x5. By default this feature is disabled.

Feature enables following OCM layer groups:

• “junction_sign_file_3x5”

Map data that provides junction sign images with aspect ratio 4x3. By default this feature is disabled.

Feature enables following OCM layer groups:

• “junction_sign_file_4x3”

Map data that provides junction sign images with aspect ratio 5x3. By default this feature is disabled. Feature enables following OCM layer groups:

• “junction_sign_file_5x3”

Map data that provides junction sign images with aspect ratio 16x9. By default this feature is disabled.

Feature enables following OCM layer groups:

• “junction_sign_file_16x9”

Map data that provides topography information. The related map feature terrain with mode hillshade is enabled by default on topo map schemes. It is disabled by default on all other schemes.

Note that this change has performance implications, with additional data consumption and impact on rendering frame rate. If performance is a concern, this feature can be disabled from the application side when loading the map scene. However, when this map data feature is disabled, the terrain rendering for the above schemes will not work in offline mode with the downloaded map packages. Feature enables following OCM layer groups:

• “terrain”

Map data that provides detailed topography information. By default this feature is disabled. Feature enables following OCM layer groups:

• “detailed_terrain”

Map data which provides ADAS information which includes slope, elevation and curvature information. By default this feature is disabled. Feature enables following OCM layer groups:

• “adas”

Map data which provides information about the parts of foreign segments in a tile, where a foreign segment is a segment that is stored in another tile but intersects the current tile. By default this feature is disabled. Feature enables following OCM layer groups:

• “ehorizon”

Map data that provides traffic broadcast functionality using RDS-TMC format. It should be used when there is no internet connection, so that the routing module can utilize traffic data coming over the radio channel to build a route in the offline mode. Feature enables following OCM layer groups:

• “traffic”