Maximizing Efficiency: Key Differences Between FCD and Hamar Architectures in Traffic Stats

In Traffic Stats, we offer data based on two architectures: FCD and HAMAR. While FCD map-matches data on the fly, HAMAR utilizes pre-matched data, resulting in reports being processed approximately twice as fast on average.

To benefit from the faster HAMAR architecture, please follow these simple steps:

A) Avoid using full traversal routes.
B) Avoid querying for the last four days.
C) Select the recommended map for your date range - more information can be found here: Available Maps
D) Do not include the map version value in your API requests.

💡

While options A) and B) may sometimes be unavoidable due to the requirements of specific reports, step C) is often misapplied, typically occurring when running multiple API queries and cloning reports without adjusting the map version to align with the relevant date range between analyses.

Incorrectly using the FCD architecture while scheduling a larger number of analyses may cause congestion in the reports queue and significantly increase the processing time of your reports.

A simple yet effective way to improve this situation is to use the appropriate map version recommended by our web application (indicated by a star icon) or to omit the map version parameter in your API queries. In this case, our system will automatically select the recommended map version.

The recommended map version to the date range you selected is marked by the star icon.

The "mapVersion" parameter, which you can define in your API requests, is optional; if you do not define this parameter, the best map version for your analysis will be automatically selected.