Skip to content

Car profiles

Jump to bottom
Poutnik edited this page Jul 24, 2020 · 28 revisions

  • I have frozen further development of my car profiles until further notice. They are not bad, you may want to experiment with them, as they are more tunable than BRouter original car profiles. But it seems to me the latter have better production quality.

  • Fast profile takes motorways as the ideal ways, taking their real length. Length of the slower roads is considered effectively longer than the real one, and then there is evaluated shortest = fastest route.

  • Eco profile is based on the least estimated fuel consumption.

  • EcoFast profile (recommended) is a weighted average of Fast and Eco ones, balancing spent time and fuel cost. It gives 60% weight to Eco router evaluation and 40% to Fast one.

  • Short profile choosing the shortest possible route. This is not useful for the everyday car routing. It may find a use as a technical emergency, when a car is still operational, reaching the destination at limited speed ASAP.

  • There are several flag based modificators of profile behaviour:

    • avoid_tolls forbides usage of paid motorways and passing toll points.
    • avoid_motorways forbides usage of motorways( either free or not).
    • avoid_unpaved forbides usage of unpaved ways.
    • road_restriction with values 3-6 defines forbidden road to speed up long distance routing and to lower the resource consumption.

  • The prioritizing of ways according to the travel time or spent fuel is managed by Costfactor(CF). A 10 km long road that takes 50% more time than the fastest way is penalized with CF 1.5, so it is taken as if its length was 15 km. Similarly, a 10 km long road that is estimated to consume 20% more fuel than the ideal most economic road is penalized with CF 1.2, so it is taken as if its length was 12 km.

  • As an illustration, imagine 2 alternative roads from A to B.

    • Route1 is 110 km long, with cruising speed 120 km/h, lasting 55 minutes, consuming e.g. 8 L/100 km, i.e. 7.33 L.
    • Route2 is 90 km long, with cruising speed 90 km/h, lasting 60 minutes, consuming e.g. 6 L/100 km, i.e. 5.4 L.
    • Route1 is slightly faster, but consumes more fuel, by longer distance and higher specific consumption.
    • Fast mode chooses Route1 as faster, Eco mode chooses Route2 as cheaper.

  • Start/Stop points like crossroads and slowing down by curves affect traveling time in Fast profile and price in Eco profile. They are evaluated within abilities of Brouter scripts.

  • As car routes are usually longer than bicycle routes, you may notice time outs in Locus for routes longer than 50-100 km, if navigation is configured to use Brouter. The reason is Brouter is computation intensive and Locus may not be patient enough. There are 2 solutions>

    1. Generate GPX file and navigate along it.

    2. Use timeout free BRouter routing generation. When Locus raises timeout msg, switch BRouter and select <.....> item at the top of the BRouter profiles list. It will continue in the route calculation in the timeoutfree mode. if you use the same destination+profile later in Locus, it will be fast enough to fit the time out limits. It is like a kind of the Brouter training for a particular route. The data are volatile, so one must not use other Brouter routing in between.

Fuel consuption estimation for given steady speed is derived from mpgforspeed site.

See also Care profiles wiki

  • Turn restriction implemented in BRouter 1.4.8 ( with RD5 data 14-NOV-2016 or newer ). No change needed for car profiles. Bicycle profile need it turn on explicitly. Be aware of still marked as incomplete.
Clone this wiki locally