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.

I therefore suggest you to update the data with the more detailed ones at 1 "where available. Your servers will not suffer from a few more gigs of space occupied and a few more seconds of CPU usage, but you will give a more accurate data to everyone.
In my experience of use, 3 "is sufficient for road use (car, bike), but in the mountains 1" is better if, for example, you walk on the edge of a mountain ridge.
After all, the app allows the use of 1 "srtm (for the user it is only a matter of space occupied) on the cloud / web instead we should always have the best option.

[@lor74cas]

@lor74cas
1) Altitude always in metres - thanks for opening this topic. I have already changed this so you can check it in web planner.
2) Profile icon - thanks for the clarification. I added this on my list
3) Srtm files - I am receiving elevation data from the routing server and I don't know what is used internally for the calculation. I have asked @Radim V so probably he can give you more accurate answer
4) Different elevation gain stats - there must be somehting really wrong. I have tried it to reproduce and I was not able to see more than 1 meter difference (rounding issue between browser and backend). Could you share particular example of track where this is happening? Thanks a lot

1) thank you it works
4) BEFORE 1033 POSITIVE GAIN
https://web.locusmap.app/en/?planner=KYOwPgzgbggg9gBwH4F8AaKDSB3OABYARwBEBzAVwDE4BbAOVKgHUIBvSgTwEM6JCAhFFACiEANb8aKMgBkAxgCcYNACYwA+lDzYZYAC7CEAJTA08pDgGFyYAOLqaAVQA2UALJ7SMAGYpLACz0AKXJCWzkIIIADAC8AeRAIGBioywAPACtLMXUYUiYM5zcogE0Yrjwwf2s9Sq0kAEsAXRAMgB1vOQA1fxpbDgzhdRQ8DhAAZRAGgElvf34QdX4ufxgwUgI4SwBumTgmLmcxBpBSAG49g6OT88vD49OL-fubp6uH2+frx7vvz-fXr8Pm8Xj8vsCgYDwVCAWDYZ8ABINCFwJEotFQjFgrGI5GYvHYgm49FEp44smk7ZAA

and after 1133 POSITIVE GAIN
https://web.locusmap.app/en/?shared_track=NGIxYWMwOGItNmQ5Ny00YjM4LThkYjEtNzcxNDBiM2E3MzczOmIyZjVlOGRlLTY1MTQtNDFjZS04MzdiLTA1MGU0ZGNhNmNkMA..

@Menion I know it's not your job, but where can I write to report that your sites are a mess?
it seems that everything is badly connected, there is a main page, one for live tracking, one for the help desk, one for the forum, one for documentation.
There are at least 3 different types of graphics, many pages once opened have no reference to the main site.
With the arrival of the new version 4 it would have been the right time to do some cleaning.

[@lor74cas]

@lor74cas

2) Use metres only for elevation gain/loss - We will consider it. Please, what is the motivation for you (precision, ..)?
3) Logged in but icon still anonymous - I do not understand. Please, could you give me more info: Thx
4) Elevation chart for saved tracks - sure, it is in progress and should be there soon.
5) Hiding top bar - Good idea, we will consider it but for now more important tasks are on the list
6) More accurate altimetetry calculation - this is more related to the routing itselft. Please, ask here: https://forum.locusmap.eu/index.php?topic=7202.0

2) The altitude is always expressed in meters, the height of the mountains for example is in meters the k2 measures 8611 meters I have never seen it described as the 8.6 km high mountain. It is a practice, for hikers, mountaineers, runners, cyclists ...

3) When I am logged in, in my case for example, the image / icon associated with my account on Google appears, the same one you see associated with my profile on this forum.

6) I was just asking, do you "use the 1" srtm files where available"?

• In the stats panel elevation gain/loss is in km, when over the 1000m, please use always meters
• even if correctly logged in, the icon remains anonymous
• the altimetry graph must also be displayed on the tracks opened in cluod, not only on those created with the planner
• top bar with "locus map beta, THE APP, PLANNER ..." is not necessary and steals space, it would be appropriate to hide it like the other panels
• for a more accurate altimetry calculation I hope you use the 1" srtm files where available

There are several things to fix, but overall it's very responsive and easy to use

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.

https://www.openstreetmap.org/#map=14/62.5564/7.7225&layers=Y
no holes

https://www.openstreetmap.org/#map=14/62.5564/7.7225&layers=C
with holes, and I think Locus uses this one

In the image the mystery unveiled.

[@lor74cas]

...
@lor74cas
1) Not editable filename -> Is it really issue? You can easily rename file once downloaded ... For sure I could add logic to generate name (current time, start and destination - can be tricky one) but I didn't see any big benefit doing so.

Hello,
It is useful for the messy ones like me who leave everything in the download folder. To give the created file a useful name to identify its contents, I always have to open the folder and rename the file, it is not very convenient. By pressing the export button it would be better to simply ask the user for the name, there is no need to take the information from the points, the track or the map to suggest one, you can leave "export" as default, but editable by the user.

Plain/Hill/Mountain makes sense as a triad, and has no rude obscene connotations that I am aware of (an important consideration when using a foreign language).
However, my first thought was actually that the proposed naming appears to tie the Locus tiers rather strongly to the intended usage. If I walk or ride mainly in the plain, do I want the Plain version? Maybe it has no contour lines? Maybe the Hill version stops working above 1000m and the maps disappear in mist?


Sent from my moto g(6) plus using Tapatalk

I totally agree.

I know that free, base, advanced are less fun names, but they better describe the version of locus.
sleeping bag, camping tent, resort, just kidding. 

Export Gpx -> filename not editable the name is fixed to "export"
The points I put on the map to generate the track are exported as waypoints, but they are not. I think that the generic points with just coords in panel does not have to be considered as waypoints, but if I use +add to route on a relevant point on the map or (in future) I edit the coords in the panel with a more human readble text, this are real waypoints also to be exported. 

As the number of points increased, I noticed that it would have been appropriate:
1) A dedicated scroll for the points panel with the last inserted always visible
2) The statistics panel always visible at the bottom

Now for me after 10 points (depends on the screen resolution) the stats and new points are progressively moved down becoming invisible without using the scroll.

I tried the new circular automatic track, yes it works but why should I use it for ?

What I need is something that connects last point to start point to create a circular track

Inviato dal mio SM-A520F utilizzando Tapatalk

Hello,
I do not understand why this option is the top voted "Long click on "Route type": toggle between "manual" and "selected" routing".
"Toggle" function is a shortcut to change the profile to manual and back, it does not to draw directly a manual point.
With the direct manual point (on the + or on the profile icon, does't matter) if you need to concatenate more points you have two options:
1) with few points, use the long touch for each point
2) with a lot of points just toggle to the manual mode as always

With one point, no contest, just one long touch

I think I do not understand because someone else has different needs than me, but I'm curious.

Hello,
In the route planner I agree with another user who wrote about insert the points in the graph.

When showing the detail of the points, there is no reason to see the the graph for each segment because every graph has its own scale and you can not compare the segments, so I disabled this function.

In the attached mockup, I suggest a better use of the point detail panel:

• When enabled the top should be hidden
• At the bottom show the whole altimetry graph with the reference of points
• Highlight in the graph the selected segment
• Highlight in the map the segment centering and zooming at the top

The REC button still overlaps.

Now, here in Italy we can just play with the planner waiting for the end of this nightmare.

First impression:
https://gph.is/g/ZPJNoDV

I use auto-hide for all panels, I like the full map, I do not like too much the button of menu visible while all is hided, see attachment.
For my case of use the menu button gives access to something I do not usually need while focusing on the map, It'd be more convenient if it show up with the double touch of the map as the other hided menus.