1. What the route line represents
Mapbox builds a path over its road network graph with turn-by-turn geometry. Display uses Web Mercator tiles; distances and times come from the API response. Data can lag real-world closures, new roads, or one-way changes. Always follow posted signs and local traffic rules.
The polyline is drawn for clarity; it is not a lane-level guide. Tight urban grids, roundabouts, and highway exits still deserve a slow, sign-first reading especially at night or in bad weather.
2. Geocoding limits
If a place is missing or wrong, add context (city, region, country) or pick a nearby point. Results depend on the geocoder’s database, not on-site human verification.
Ambiguous business names can snap to the wrong storefront; airports and large campuses may have multiple valid entrances. When precision matters, start or end the route from a coordinate you verified in Location Maps or Satellite.
3. Combining with weather or satellite
Use Weather and Radar for general context, and Map search for optional overlays—still not official forecasts or warnings. Satellite can help confirm complex junctions visually.
Winter travel, mountain passes, and flood-prone roads need chain laws, maintenance bulletins, and emergency notices from transportation agencies. Consumer routing cannot encode every seasonal restriction.
4. What we do not provide
No commercial fleet routing, HAZMAT rules, hours-of-service, or emergency dispatch. No guarantee of fastest or safest route in all conditions. For regulated work, use tools your jurisdiction approves.
We do not collect a continuous GPS trace or reroute you automatically as you move; anything that feels like a dedicated navigation app is outside the scope of this website.