A TrafficBroadcast is expecting the RDS-TMC format and it can be used when there is no internet connection, so that the OfflineRoutingEngine can utilize traffic data coming over a radio channel. The TrafficBroadcast.activate(...) method needs to be called to receive traffic data events.

Note: In order to adopt the TrafficDataProvider interface special hardware is required. Talk to your HERE representative for more details. Only by adopting the TrafficDataProvider interface you can integrate radio station signals providing traffic broadcasts. Traffic broadcasts are meant to be used independently from the already included traffic on routes, on the map and from the HERE backends (when using the TrafficEngine).

This class continuously reacts to new locations provided from a location source and acts as a LocationDelegate. The location must be updated regardless of calling TrafficBroadcast.activate(...).

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.

Represents the parameters needed to request the traffic broadcast.

Represents the traffic events in RDS-TMC format.

Represents data used to request the list of preferred SIDs.

Represents the service prodiver info in RDS-TMC format.

Represents the parameters used to request the traffic broadcast.

Contains all outgoing dependencies to the client side.

Represents the RDS encryption key. Fields allocation information is described in CEN ISO/CD 14819-6.

Represents data to search for RDS encryption keys.