Other Classes

The following classes are available globally.

  • Represents an elevation placement target.

    An ElevationTarget encodes where geometry should be placed vertically.

    Instances are created exclusively via ElevationTargetFactory.

    Note: This is a beta release of this feature and may contain bugs or exhibit unexpected behaviour. Related APIs are subject to change without a deprecation process.

    Declaration

    Swift

    public class ElevationTarget
    extension ElevationTarget: NativeBase
    extension ElevationTarget: Hashable
  • Factory for creating ElevationTarget instances.

    Note: This is a beta release of this feature and may contain bugs or exhibit unexpected behaviour. Related APIs are subject to change without a deprecation process.

    See more

    Declaration

    Swift

    public class ElevationTargetFactory
    extension ElevationTargetFactory: NativeBase
    extension ElevationTargetFactory: Hashable
  • A tile data source that exposes geometry data for map features.

    Note: This is a beta release of this feature and may contain bugs or exhibit unexpected behaviour. Related APIs are subject to change without a deprecation process.

    See more

    Declaration

    Swift

    public class MapTileDataSource : TileSource
    extension MapTileDataSource: NativeBase
    extension MapTileDataSource: Hashable
  • Holds map tile geometry data.

    Note: This is a beta release of this feature and may contain bugs or exhibit unexpected behaviour. Related APIs are subject to change without a deprecation process.

    See more

    Declaration

    Swift

    public class MapTileGeometryData
    extension MapTileGeometryData: NativeBase
    extension MapTileGeometryData: Hashable
  • Factory for creation of MapTileDataSource instances backed by OCM data.

    Note: This is a beta release of this feature and may contain bugs or exhibit unexpected behaviour. Related APIs are subject to change without a deprecation process.

    See more

    Declaration

    Swift

    public class MapOcmTileDataSourceFactory
    extension MapOcmTileDataSourceFactory: NativeBase
    extension MapOcmTileDataSourceFactory: Hashable
  • Provides a generic dynamic camera behavior that transitions between two pre-configured camera behaviors based on lane detection and data consistency. This allows for optimized camera positioning depending on whether high-definition lane data is available or not.

    The camera will automatically switch between two pre-configured camera behaviors (HD and SD) based on the current navigation context and data consistency. This is a generic base class that works with any CameraBehavior types, allowing transitions between different camera behavior implementations.

    Transition criteria:

    • SD -> HD: switches to HD when at least minimumHdLengthInMeters of consecutive HD lane data is available ahead AND the route carpet is currently being rendered.
    • HD -> SD: switches back to SD when HD lane data runs low AND a real non-HD boundary exists ahead AND the minimum HD duration has been traveled.
    • HD is forced off when the route carpet data is not shown (e.g. carpet generation failure or missing layers) to avoid presenting an HD camera without HD visuals.
    • HD stays on when approaching the end of the route with only HD data remaining (no non-HD boundary), regardless of remaining distance.

    Construction-zone awareness: Traffic incidents of type CONSTRUCTION are taken into account at span level. When the algorithm looks ahead for the next minimumHdLengthInMeters of HD data, any route span tagged with a CONSTRUCTION incident is treated as a non-HD boundary, because lane data is typically unreliable across construction zones. The effective HD coverage ahead is capped at the start of the nearest construction span, so the same minimumHdLengthInMeters threshold drives the resulting SD<->HD transition. HD mode therefore always guarantees at least minimumHdLengthInMeters of dependable HD data ahead: when a construction zone falls within that window, the camera switches back to SD immediately, bypassing the usual minimum HD travel distance even if HD was just entered. The lookahead is intentionally span-scoped (not section-scoped), so a single distant incident does not block HD over long stretches of the route.

    Note: TransitionCameraBehavior cannot be nested - the hd_camera_behavior and sd_camera_behavior parameters must not be instances of TransitionCameraBehavior.

    Note: This is a beta release of this feature and may contain bugs or exhibit unexpected behaviour. Related APIs are subject to change without a deprecation process.

    See more

    Declaration

    Swift

    public class TransitionCameraBehavior : CameraBehavior, CameraHdTransition
    extension TransitionCameraBehavior: NativeBase
    extension TransitionCameraBehavior: Hashable