Stay organized with collections
Save and categorize content based on your preferences.
European Economic Area (EEA) developers
When you request a route, you can choose how the Routes API uses traffic
data when calculating your route. A traffic model is a way to factor
historical and live traffic conditions into your route generation, and can
affect both which routes you get and how long the estimated travel time is.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-26 UTC."],[[["\u003cp\u003eThe Routes API offers options to customize how traffic data is used for route calculation, impacting both route selection and estimated travel times.\u003c/p\u003e\n"],["\u003cp\u003eYou can choose to include or exclude traffic data, impacting the accuracy and speed of the results.\u003c/p\u003e\n"],["\u003cp\u003eTraffic-aware polylines provide detailed traffic conditions along the route but come with higher billing rates.\u003c/p\u003e\n"],["\u003cp\u003eDifferent traffic models can be selected to prioritize various factors like historical and live traffic conditions when estimating travel duration.\u003c/p\u003e\n"]]],["The Routes API allows users to incorporate traffic data into route calculations. Users can choose to include or exclude traffic data for varying accuracy and response times. They can also opt for traffic-aware polylines, which provide traffic condition details along the route, though this incurs a higher cost. Furthermore, users can specify which traffic model to use, prioritizing factors in calculating travel duration based on traffic conditions.\n"],null,["# Available traffic options\n\n**European Economic Area (EEA) developers** If your billing address is in the European Economic Area, effective on 8 July 2025, the [Google Maps Platform EEA Terms of Service](https://cloud.google.com/terms/maps-platform/eea) will apply to your use of the Services. Functionality varies by region. [Learn more](/maps/comms/eea/faq).\n\nWhen you request a route, you can choose how the Routes API uses traffic\ndata when calculating your route. A traffic model is a way to factor\nhistorical and live traffic conditions into your route generation, and can\naffect both which routes you get and how long the estimated travel time is.\n\nHere are the traffic options for a route:\n\n| Traffic Option | Description |\n|------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|\n| [Specify how and if to include traffic data](/maps/documentation/routes/config_trade_offs) | Include traffic data for more accurate results, or exclude it for a faster response. |\n| [Select whether polylines reflect traffic](/maps/documentation/routes/traffic_on_polylines#request_a_traffic-aware_polyline) | You can include information about the traffic conditions along the route in your returned polylines. This feature is billed at a higher rate. |\n| [Specify what traffic model to use](/maps/documentation/routes/traffic-model) | Specify which traffic model to use to prioritize different factors used in calculating duration in traffic. |"]]
