A routing profile is the set of travel-mode, vehicle, road-access, and preference rules a routing engine uses to calculate a path. This guide covers how car, truck, bike, and custom profiles differ, and how fleet teams can choose and validate the right one.
Key Takeaways
- A routing profile tells the engine what is traveling and which roads apply.
- The same two points can yield different car, truck, and bike routes.
- Truck profiles need height, weight, width, and length data.
- Custom profiles fit vehicles and service rules that default modes miss.
- Validate every profile against real trips before trusting it.
What Is a Routing Profile?
A routing profile is the rule set that tells a navigation or fleet engine which roads a vehicle may use and how to cost them. This guide covers digital maps, navigation, and fleet routing, not URL routing in web backends or network traffic routing.
In engines like Valhalla's API, each request names a costing model. auto follows automobile access and turn rules. truck adds truck access, dimension, and weight checks. The core point: car-accessible does not mean truck-suitable.
Main components of a profile
- Travel mode (car, truck, bike, motorcycle)
- Permitted road classes and access rules
- Vehicle height, width, length, weight, and axle load
- Turn rules, one-way rules, and closures
- Preferences such as toll, ferry, or highway avoidance
- Surface and grade preferences for bikes
Profile vs. map vs. optimization
The map represents the road network. The profile describes what a given vehicle can or should use on it. Optimization decides how to sequence multiple stops. Distance and ETA outputs from a profile-aware matrix feed the optimizer. A wrong profile corrupts everything downstream.
Why a generic car profile fails
Picture a 40-foot truck sent over a low-clearance bridge, down a truck-restricted street, or onto a private road. A cyclist might get routed up a steep, bike-hostile segment. Each looks like a fine route to a car profile.
Businesses usually need several profiles for mixed fleets: vans and box trucks of different sizes, field-service crews, cargo bikes, and paratransit vehicles. Regional restrictions vary too, so a single car default rarely fits the whole operation.
How Car, Truck, and Bike Profiles Differ
Car routing profile
A car profile prioritizes roads legally open to passenger vehicles and applies one-way rules, turn restrictions, and closures. Preferences like avoiding tolls, ferries, or highways sit on top.
Treat them as soft preferences. Google's Routes API applies avoid options only "where reasonable", so they are not hard exclusions.
Truck routing profile
Truck routing must respect physical limits and commercial access rules:
- Weight: federal Interstate limits are 80,000 lb gross, 20,000 lb single axle, and 34,000 lb tandem axle, with lower Bridge Formula limits and grandfathered exceptions
- Width: 102 inches on the National Network and reasonable-access routes
- Height: no federal limit; states set their own (California generally allows 14 ft)
- Hazmat: 49 CFR 397.67 requires compliance with state and tribal routing designations
Factor in truck-only roads, restricted bridges, urban limits, and local rules. Keep legal restrictions separate from business preferences, and verify current rules with official transportation agencies.
Clearance data still has gaps. Caltrans' list covers state routes, not local roads that pass beneath them.
Bike routing profile
Bike routing favors bike lanes, shared-use paths, low-stress streets, permitted trails, suitable surfaces, and gentler grades. It avoids roads where bicycles are prohibited.
Comfort and legality are different things. The Mineta Transportation Institute's Level of Traffic Stress framework rates streets from LTS 1 (tolerable to most children) to LTS 4 (strong and fearless riders).
Legal access is a separate question. California Vehicle Code 21960 lets authorities restrict bicycles on freeways, but that is not a nationwide ban.
Valhalla's bicycle costing adjusts speed by surface, bicycle type, and hilliness. Standard bikes, e-bikes, and cargo bikes may need separate profiles. California defines Class 1 and 2 e-bikes with a 20 mph assist cutoff and Class 3 with 28 mph.
Comparing one trip across three profiles
Say a delivery runs from a warehouse on an industrial edge to a downtown storefront:
- Car: takes the fastest legal path, perhaps a highway and a left-turn-heavy arterial.
- Truck: skips a low underpass and a weight-limited bridge, adding distance but staying legal.
- Bike: leaves the highway, uses a protected lane and a shared path, and avoids a steep hill.
Each difference traces to access rules, physical limits, or comfort. Selection rule: choose the profile from the vehicle's legal access and physical characteristics first, then apply preferences like toll avoidance.
When and How to Use Custom Vehicle Routing
What makes a profile custom?
Use a custom profile when car, truck, or bike defaults fail to capture a vehicle's dimensions, operating environment, permitted roads, or service needs. Examples include cargo vans, oversized delivery vehicles, refrigerated trucks, street sweepers, mobility vehicles, and cargo bikes.
Hard versus soft constraints
Hard constraints must never be violated: a height limit, a prohibited road, a weight restriction. Soft constraints are preferences the engine balances: avoiding tolls, minimizing highways, preferring bike infrastructure, limiting steep grades.
The distinction shows up in engine mechanics. In GraphHopper custom models, lower priority discourages a segment while an area priority of 0 blocks it entirely. Google's Route Optimization offers max_meters as a firm limit and soft_max_meters as a penalized one.
Road-network and map customization
Base maps miss private-road access, restricted entrances, temporary closures, and loading zones. Custom edits close that gap. Govern them like code:
- Name an owner for each edit
- Document why it exists
- Date it and set a review cycle
- Retire it when the condition ends
Otherwise a stale rule creates the same wrong route every day.
Validation and fallback
Test a custom profile on normal routes and edge cases: restricted roads, rural roads, dense downtowns, construction zones, and locations with incomplete addresses. Keep a documented fallback profile, plus an escalation path for when the engine can't confidently apply a rule.
Where NextBillion.ai fits
NextBillion.ai is built for vehicle-specific routing. Its Road Editor App sets road attributes, vehicle applicability, and activation times. Truck-compliant routing and 50+ hard and soft constraints let logistics software teams encode operational rules instead of forcing every vehicle into a generic car or truck mode.
How Routing Profiles Work in a Routing Request
Inputs that define the vehicle and trip
A request needs origin, destination, mode, and vehicle attributes. Completeness matters: HERE warns that omitted attributes default to 0 or none, which limits restriction checks. In NextBillion.ai's Directions API, mode defaults to car, and truck fields are optional.
Units also vary by provider:
- Height, width, length: centimeters in
truck_size - Loaded weight: kilograms
- Axle load: tonnes per axle in NextBillion.ai, kilograms in HERE
- Axle count: a separate field from axle load
How the engine applies the profile
The engine applies the profile in sequence:
- Loads the road network
- Filters or penalizes unsuitable roads
- Applies turn and access rules
- Weighs preferences
- Computes a route
A profile cannot reflect conditions the map or custom rules don't contain. HERE notes that where restriction data is missing, a truck route can still be calculated without considering dimensions, weight, or hazmat.
What to inspect in the result
- Route geometry, distance, and duration
- Turn-by-turn steps (
steps=true) - Warnings (HERE can return a critical
violatedVehicleRestrictionnotice) - Toll or ferry use
- Restricted endpoints: NextBillion.ai's
honor_restrictionsdefaults to false
With that default, a restricted origin or waypoint triggers a warning instead of blocking the route.
These outputs feed dispatch, driver apps, proof-of-delivery workflows, and customer ETAs. A returned route is not proof of a restriction-free path.
Best Practices for Choosing and Maintaining Profiles
Start with operational reality
Build each profile from actual legal limits, dimensions, equipment, service area, and driver workflow, not the vehicle's name. Then ask dispatchers and drivers where routes fail. They know the unofficial height limits and no-parking zones that map data misses.
Validate against real trips
Compare profile output with GPS traces, completed routes, and driver feedback. Include edge cases: low bridges, school zones, private roads, construction, seasonal closures, steep grades, and bad addresses.
Be careful with benchmarks. An Arkansas truck GPS study reported 87% average map-matching accuracy, but that measures GPS matching, not restriction compliance or routing quality.
Monitor, version, and revise
- Assign an owner for profile changes
- Keep version history and a reason for every restriction
- Track route exceptions, driver overrides, restricted-road incidents, on-time performance, and fuel use
When exceptions keep piling up in one configuration, split it into separate profiles.
Frequently Asked Questions
What is profile routing?
Profile routing applies vehicle, travel-mode, road-access, and preference rules to calculate a route suited to a specific type of traveler.
What is the difference between a car and truck routing profile?
A truck profile applies commercial access rules and limits on height, weight, width, and clearance. A car profile generally assumes passenger-vehicle access.
How does bike routing differ from car routing?
Bike routing favors bicycle infrastructure and suitable surfaces or grades. It avoids roads where bikes are prohibited or unsafe.
Can I create a custom vehicle routing profile?
Yes, when standard modes don't match your vehicle's dimensions, access rules, or operations. What you can customize depends on the platform's capabilities.
Do truck routing profiles account for vehicle restrictions?
They can account for low clearances, weight limits, and truck-prohibited roads, provided the map data and your vehicle inputs support those attributes.
Why do different vehicle profiles produce different routes?
Each profile applies its own access rules, physical limits, and preferences to the same road network.
