Messages

First, great work with the web-planner. I'm looking forward to further enhancements.

One question: is it intentional that the height-graph is only shown for tracks which are currently planned, but not for "old" tracks synced from the phone (although they have height-data)?

And are there plans to also make the synced POIs visible in the webplanner? Would be great to have e.g. POIs of trailheads available in the planner.

Hey,

first, congratulations for the new version! great (and much) work!
Immediately signed gold last week. Finally a way to give at least something back to you guys, you are doing great work! I tried to buy some locoins from time to time in the old version to support you a little bit, (and get new lomaps with the pois), but now with the subscription I feel better, because I cannot forget it :-)

I have a question regarding migration from pro to 4. I did a full Backup in pro and imported it to 4. What else exactly do I have to do to fully migrate?
- change default directories from "menion.android.locus.pro" to the "menion.android.locus" - subfolders
- copy over all those folders (maps?, mapsOnline?, Mapsvector?, srtm?, MapItems?, router?, config.cfg?). or are some of them included in the backup? I'm a little bit confused
- change all the package names for intentents in my tasker task from "menion.android.locus.pro" to "menion.android.locus"?
- what else did I miss?

Yes, my request is to do it like brouter-web and dynamically parse and display all parameters from brf file.

I don't have a specific request for confirmed parameters, despite maybe the kinematic model parameters (totalMass, Maxspeed etc.), which are brouter-builtin.

All other parameters I would like to use mostly exist in single profiles only and therefor I wouldn't recommend adding them as supported to Locus just because of this one profile.
For example, I created an enduro-motorcycle profile on user-request which has a "non-standard" parameter to switch the avoidance of paths, or I consider adding another parameter to influence uphill routing on paths to my mtb profile etc...). Without support for generic parameters, I would have to generate separate profiles of all permutations of profile parameters like libor does, but it gets confusing and it's not easily switcheable for example in a routeplanner session (if the profile-variants aren't already assigned to the (limited) slots in Locus).

As I wrote before, I think it's ok that the default setting only shows the whitelisted parameters (as is now).
But I would like to have the possibility to enable "full dynamic parameter" mode in expert settings for power-users (which you clearly embrace with locus (intens, url favourites, bt-buttons, dashboards, quick pois, presets...should I go on with the list?  )).
Maybe you could group the whitelisted parameters at the top of the settings dialog and show the other "non-standard" parameters below. Maybe with a caption "additional settings" and in a fainter color?

@zossebard
The set o profiles we currently work with is and will be available here:
https://github.com/asamm/brouter/tree/asamm/locus-routing-profiles
Some of them are default profiles from parent brouter repository and we rather want to keep them as they are validated by the previous usage in the app. Some of them are by Poutnik. We also consider your mtb profiles, of course. The modifications we made so far are rather minor. Feedback and improvement are welcome, just let us keep in mind that this set should be a safe set of defaults for all users. Regarding all profile parameters: I think we got your point, Menion will do that.

thanks for the information! nice to hear that you consider supporting more parameters. this way power users will e.g. also be able to tweak kinematic model parameters to optimize ETA (if supported by the profile).

Sent from my G8441 using Tapatalk

May I ask where the Lo* - profiles originate from? Clearly, they are not all from brouter default profiles? I assume some of them are based on poutniks profiles? Or did you create them all from scratch?

Do you plan to create issues and/or pullrequests in the corresponding source github repos for changes users suggest here? Or do you plan to maintain your own (proprietary) modified versions? Because if the former, other users could benefit as well from improved profiles.

And while you are at it: could you please reconsider (optionally) supporting ALL profile parameters instead of only your whitelist? I wrote this before: I think it's ok to use the whitelist as a default. But you could add a setting in expert settings to enable support for all parameters (for power users). I think it is ok to display the description texts from the profile instead of the translations Locus offers for the whitelisted parameters.
I recently enhanced my profile with yet another (non-whitelisted)parameter which significantly changes routing when altered. Without this parameter supported by Locus (unlike e.g. brouter-web), I'm forced to create even more variants of the profile with this parameter set to different values.

I hope you get my point.

regards,
zossebart

I like the online LoMaps as a starting point for new users. Nice hillshading also in lower mountain ranges (Germany) without much elevation difference compared to e.g. the alps.

Hiking/Biking route signs would be great but I understand that this might clutter the map view too much.

Rendering speed of supposedly not yet cached regions seems ok, but there are not many users as of now, of course. Will be interesting to see how your setup performs when this is the default map of new LM4...

Also, the online LoPoints feature is great!

I also have this problem on a Sony xz1 compact with Android 10 (lineageos). Recording is interrupted as soon as display is off. I also see "optimization not available" for locus map. however, for lm4 beta, "not optimized" is available (haven't checked if it helps with my problem, though). Is there a difference in implementation?
as a workaround, I disable battery optimization while using locus for now.

Gesendet von meinem G8441 mit Tapatalk

schau mal in dem Thread: https://forum.locusmap.eu/index.php?topic=4064.msg61379#msg61379

Locus verwendet seit einer der letzten Versionen keine Profile mehr, die beim Brouter installiert sind, sondern nur noch interne und welche die in dem entsprechenden Locus-Unterordner liegen.

Also, I do not see segment download in the route planner.

Try to create a route in an area where you not have routing data yet. Locus will detect this and offer routing data download (in the backround) for this area.

PS: noticed one thing with the surface display in route planner: the surface "grass_paver" is displayed as "grass". I would have expected this to be "paved", but maybe this has to be discussed further. I stumbled over this because an agricultural track I know showed "grass" surface, in reality it is paved with grass-pavers, but with gravel/earth instead of grass in the holes.

Die Hauptstraße wird dort u.a. benutzt, weil da ein Radweg- oder Radspur und eine lokale Radroute drauf getaggt ist. Das kann man beim Trekking-Profil teilweise mit dem Parameter "ignore_cycleroutes" verhindern.
Du möchtest also allgemein eher Wohngebietsstraßen und Feldwege nutzten und möglichst wenig "größere" Straßen, auch wenn diese einen Radweg haben?
Müßte man mal bei den mit seinem Script aus den Templates generierten Profilen von Poutnik schauen...die standardmäßig zum Download angebotenen decken soweit ich weiß nur eine Auswahl ab. Müsste ich mir aber auch erst nochmal anschauen.

Das geht in Locus nicht.

Mit Zwischenpunkten würde das ohnehin nicht funktionieren, da Locus hier jeweils eine Brouter-Berechnung pro Segment startet.

Dass dir immer die 2. Alternative besser gefällt deutet schon darauf hin, dass das Profil nicht passt. Was möchtest du denn fahren und welche Profile hast du schon probiert/modifiziert?

Wow, back from vacation and now two of my favourite pieces of software are joined together. Very nice!
Internal Brouter is very fast compared to external app
Surface and Way Type bars are a great enhancement! But I also have problems getting them displayed. Sometimes they only appear after switching from portrait to landscape display. After this, I can switch back to portrait and then the bars are also displayed there.

Gesendet von meinem D5503 mit Tapatalk

As it happens, another board user asked me if I could adept my mountainbike profile towards enduro motorcycle use some time ago.
He used the mountainbike profile because of it's major road avoidance/gravel road preference but didn't want the path/singletrail preference.

You can find the adepted profile here:
https://raw.githubusercontent.com/zossebart/brouter-misc/enduro-mc/enduro-mc.brf

You can paste it into the profile source box in brouter-web to test it (wrench symbol -> Profile-tab -> replace Text with content from enduro-mc.brf -> press Apply).

Maybe it's of use for you, also? Feedback would be appreciated!

Sounds like you downloaded the files in the wrong format from Github. You need to display the "raw" file and then save this.

Sorry falsche Sprache. Achte bitte beim Download von Github darauf, dass du die Datei zuerst als "raw" anzeigst und dann abspeicherst, dann sollte es hoffentlich funktionieren.

Same for me :-(

Gesendet von meinem D5503 mit Tapatalk