Using Brouter profiles for Locus navigation

How to use Brouter profiles for Locus navigation ( unfinished )

• Locus can interact with Brouter by one of these 3 ways..
  • It uses Brouter API, addressing Brouter navigation modes
    * bicycle_fast, bicycle_short, foot_fast(*), ( car_fast, car_short )
  • it calls Brouter interactively with the user one-time choice of Brouter profile, with the manual import of the generated GPX route * Brouter automatically chooses predefined waypoints of name from, to, optionally viaN * Brouter interactively chooses from the Locus waypoint list * The last way cannot be used if Locus waypoint count is higher than about 120-150.

Both direct profile choice ( if Brouter is launched from Locus ) and configuration of Navigation mode vs Profiles mapping start the same

• Launch Brouter application
• Select Brouter App in Brouter welcome menu
• Select chosen profile, e.g. Hiking
• Select respected ( check in ) or ignored ( checked out ) nogo areas

---

Now the procedures fork

Assigning Brouter Navigation mode to Brouter Profile

• Select Server mode
• Select foot_fast(*), or relevant bicycle or car modes, uncheck the rest.
• Review current mapping of 6 Brouter navigation modes on Brouter routing profiles
  

*** ###### Direct using of the Brouter Profile

• Select "Select From
• TO BE CONTINUED

***

(*) Locus does not use Foot_short Brouter navigation mode. I personally consider it as a pitiful drawback, as fear of fast/short confusion has probably overrun option to see the advantage to have both ones available. OSMAnd does not have this disadvantage, even if OSMAnd is otherwise a simpler, less skill demanding application than Locus.