Inaccurate display of traffic conditions during navigation and cruising

Nobody has claimed this yet.

Hi,

We observed inaccuracies on the traffic conditions returned from Mapbox, on the following events:

1. Traffic conditions when cruising and map initialization is not reflecting the actual traffic conditions on road. During our test drive, there are road segments which are not congested but are reflected as being congested on Mapbox display.
Refer to attached screenshot. Could we understand on how recent is the traffic condition and on what criteria would a road be considered congested (e.g. crowdsource feedback, travelling speed)?

2. Traffic conditions displayed during navigation is **different** from when cruising. We understood that the traffic conditions returned during navigation is based on Directions API while cruising is based on Mapbox traffic title as part of the core SDK. Could we understand on why the difference?


**Android API:** Directions API, Mapbox SDK
**Mapbox Navigation SDK version:** 2.20.2 (Android), 2.18.4(ios)

### Steps to trigger behavior

1. Call Directions API to start navigation with display on traffic conditions
2. Initialize map with traffic conditions for cruising and display of map

### Expected behavior
Traffic conditions returned from both Directions API and Mapbox SDK should be consistent and accurate to the real-time traffic conditions observed on ground.

### Actual behavior
As per description above.

Start with the listed reproduction steps using Directions API and the Mapbox SDK, comparing traffic during navigation with traffic during map initialization and cruising. Review the reported Android and iOS SDK versions and attached screenshot; done means determining whether the discrepancy and congestion display are expected, and documenting the relevant freshness and congestion criteria.

Written by the indexing model from the issue text.