Messages

[@lor74cas]

Hi,
@lor74cas
Elevation data for routing: we have altered brouter internals to use our company maintained dataset, which combines enhanced SRTM source (viewfinderpanorama) and some Lidar sources. However the resolution is 3'' only.

One of the most important things when you are outdoors is water. In the screens you can see that even if there are two fountains nearby, selecting the first search result which should theoretically be the closest sends me more than 50km away.

Thanks for reporting this. The problem here is: Currently the search only uses "names", so only the objects that have the term "water" or similar among their names in two languages ("local" language and "English" in this case) are found. The two nearby fountains are not named at all - "Drinking water" is the overall category of them. More complex search using keywords is needed here. It is already done internally. Sorting: we don't think sorting based on distance entirely is a way to go. More content (Wikipedia, user related) is coming, so "close calls in terms of distance" are resolved based on content.

Hi, regarding more generic qualities of places: there already are "attributes" - icons and short verbal description of features like WLAN access, wheelchair accessibility, smoking ... these are visible in the point detail, if present at all (in well mapped areas there are more of them). Diet is already somehow expressed by icons (veg. is "V", non veg. is "fork and knife"). Anyway being more specific about cuisine would be good, I agree. Probably a feature to do for next version of the database. 

The web planner doesn't work well set to walking, but does OK set to hiking. I screen recorded the issues which you can see in this video: https://www.dropbox.com/s/g88qnkugianhn1w/Locus%20Map%20web-based%20planner.mp4?dl=0

Thanks Geoff,
both walking and hiking profiles have been adjusted to accept all SAC difficulty levels. Walking profile puts high penalty on higher difficulties, so difficult (dangerous, exposed to fall) paths should be chosen as "last resort". This solution is not perfect, as difficult terrain may be unexpected to a "casual walker". We consider some sort of warnings for these scenarios. More detailed discussion on routing is here: https://forum.locusmap.eu/index.php?topic=7202.30
Regards

I think it would be good if the LoProfile modification has been explicitly listed in the profile comments.

It will help with eventual coordinated development of the profile/template, not to be just a one-time action. E.g. I can include generation of explicit Loxxxx profile into my profile generation script, that creates on demand all profiles from the current  template.

This is not limited to my profiles, as the script can take and modify any profile posted on GitHub.

Or, you can create a modified script version to generate LoProfiles from the current versions of the sources, unless you do not have it already.

Modifications: I will keep manual comments at the bottom of the files, that is an easy think to do, but we also encourage the usage of Git.(Tools like gitk do much better job in history bookkeeping than manual comments). Also changes via pull requests are encouraged. Currently all profiles include some minor changes (lifecycle tags awareness, turning instructions mode...), some of them are "hidden behind" the initial commit, sadly.
Generating profile variants from a template: Thanks, I wasn't aware of this script really. However we don't need to generate multiple files implementing ranges like "very easy - easy - medium - hard - very hard". What is going to happen more likely is: a single parameter ("difficulty level"), modifies a single profile (a temp. copy) in the time of request - some form of "request interceptor" inside brouter servlets. Multiple switch statements in this single profile can be seen as "difficulty presets", depending on a single variable, modified runtime. However your tool may be useful while generating those "presets". Hope this makes sense.       

Can the internal profiles be accessed from file system side? Didn't find them. Just curious.

No, internal profiles are hidden from user. Anyway we keep them in sync with above mentioned public repository. You can modify those publicly available profiles to your liking and place them in Locus/router/profiles2. Then in advanced settings the app recognizes them.

Hi all,
we have updated the set of routing profiles available here:
https://github.com/asamm/brouter/tree/asamm/locus-routing-profiles
Profiles are of course credited inside.
Now we want to ask for some feedback again: More specifically, In landscape (both flat and mountains) you are familiar with:
-Is the MTB profile in your opinion: Too easy, too hard, or just about right and safe for an average biker?
-There will be not much distinction between walking and hiking in flat landscape but  there should be some distinction in well mapped mountain areas. Do the results suit their activities?
-road cycling: roads too busy?
-any reason you would not use a particular profile for intended activity?
You can try them here:
https://web.locusmap.app/en/
And of course using brouter-web directly.
Thanks!

@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.   

@ Radim V
U- turn navigation instruction generation through Locus (B)Router missing command

Non-directional navigation instruction U-turn instruction delivered by the GraphHopper (-98) router has been nicely supported in most recent Kurviger.
After a non-directional U-turn you return over exactly the same out and return path and thus make a perfect 180 ° trackpoint turn.
In Kurviger you so do find the combination of a Shaping or Via Point together with the U-turn command sharing the same identical track point.

Notification Difference:
With a Shaping Point you only have a U-turn command message.
Example TTS: After 60m Return
With a Via Point you have a combined message: Via Point <name> followed by U-turn command.
Example TTS: After 60m Nice Viewpoint, Return.

Locus does not generate nor use, not even by using the online GraphHopper Router service.
And BRouter does not generate directional U-turns.
Question:
Is there a possibility in Locus LM4 with the internal Brouter to generate this as such and to use it?
In picture: See Icon difference. Non-directional U-turn is without arrow, directional U-turns with arrow.
On the left the Locus <sym> command, on the right the corresponding GraphHopper command.

Hi, this is something to look into, but currently, there are much more pressing issues to cope with, sadly.   

Please, block routing thru highway=construction in all profiles.

I see, will do also another lifecycle tags, thanks :-)

,,the app now fully integrates BRouter based solution"
I can't see an option to calculate alternative routes. I'm not going to use it without it. I don't remember how I've set BRouter in the Locus Pro, so I haven't tried it in the beta.

,,Both services use identical routing profiles, so you should get identical results."
I have 2 local BRouters 1 with map icon and second called inner. Both with different profiles, but without mine.
Inner and online have a different number of profiles
I've got timeout code 10102 when downloading routing segments for BRouter inner.

,,What do we want to do for now?"
Autorenaming profile according to the profile file name.
GUI to import custom profiles.
Too many taps to recalculate a route with a different profile, two confirmations are at least one too many.
In profile pop up a cogwheel next to ,,Settings" isn't obvious they are separated things. Put | at least.

Hi Pawel, thank you for your feedback. First of all we would like to sort the timeout problem. Does it happen always, even when connected to a reasonably fast network?

Hallo there,
In the recent version of FitSdk by Garmin(20.76.00), there is support for 27 coursepoints.
I am particularly interested in CoursePoint.SEGMENT_START and CoursePoint.SEGMENT_END.
If I generate myself a .fit file using these types and import it to Locus, I get both coursepoints/waypoints displayed.
Just their representation is very basic. This is fine, no problem. I just want to make sure there is no sophisticated mechanism for Garmin's (and Strava, of course :-)) segments in Locus. Do I need to expect any dedicated waypoints coming from Locus, representing them? If any related information has been made public please redirect me. Thanks, Radim.

Ahh, sorry, will write.

Hallo Locus team,
I am developing two add ons with Locus API. For both of them, I need to represent summits and valleys in the hierarchy of classes around Point. First I need to encode this generic SUMMIT / VALLEY enumeration and return it as a new Waypoint to Locus (using Locus API, not app import). (Many Garmin Edge devices have the ability to tell me "now you are going to be mostly climbing / descending for 5 km / 10 minutes"). I cannot figure out how to properly represent this summit valley classification.
Then I need to decode it from the data containers that Locus uses around Waypoints and map them together with all other enumerations from PointRteAction to a collection of types that Garmin's fitSDK understands. I have been previously working with .tcx files. Locus imports them ok, it assigns nice icons to both summits and valleys and also parses other data from <coursepoint> element like name and description and adds PASS_PLACE PointRteAction. Of course I could encode summits / valleys in the name e.t.c but having those two add ons related in such a tightly coupled way would be very bad. I can provide any details and data needed. Thanks, Radim.

Hallo, I am developing something with Locus API, and in one of my debug dumps I noticed some inconsistency regarding methods  location.hasSpeed(). If you check attached files, namely lines 26, 34, 39 in the .dump file you should see what I mean. GPX file that I imported in locus and consequently got via standard API mechanism (ActionTools.getLocusTrack()) also attached.
Only first "trackpoint" has speed false, all other have speed true, but 0 which is incorrect I think. (location and timestamp are available) 
This is not pressing issue to me as I use location and timestamps to recalculate speed or force constant speed if track is not fully timestamped.
Thanks, Radim