Messages

route name > only recorded. Imported or planned has different names. Also, in the recent version, you may modify the pattern for the name of the recorded track, so ...

There's the timestamp there {t} - I was wondering - will you add more variables? Especially (next) city name is interesting.

I would love not to see "Best Interval".

Oh yes. Same, also the waypoints symbols aren't useful for me. Maybe at a later stage we can define which elements are shown, while the rest (their fullscreen windows) can be accessed via a submenu.

Perhaps you can also select other fields there. I would love not to see "Best Interval".

+1

One more point about this screen.
When I click on the track, this sub-screen opens.
When I select a track in the track manager, the full screen opens.
I don't like the full screen because it can't be swiped down (other users too).

But the question is: when you swipe coming from track manager, where do you want to go? Back in the track manager or on the map?
For me it's the track manager, but the swipe gesture with the map at the top suggests the map

With the new track details (latest beta), I like the behavior when you tap a track on the map.  You get a small panel with the ideal amount of detail: the four key numbers, and an elevation chart.  You can swipe up for more, down for less and to get rid of it.  To me this is ideal.

When you tap a track in the track list (sometimes, haven't quite figured out the logic), you get a large panel that takes most of the screen.  Here, you can't swipe to make it smaller or make it go away; swiping only scrolls if needed.  To me, this is much less ideal, and I'll be forever trying to swipe it down to shrink.  Any chance to make it consistent (like the first paragraph above)?

Also, in the second case (non-swipeable panel), I sometimes have trouble exiting by tapping the left-arrow in the title bar.  Even when aiming and tapping carefully, it doesn't react maybe 20% of the time.  I've seen some map behavior that suggests my tap is directed to the map behind the arrow instead.

Hi guys,
as Viajero wrote.
I consider this as a feature that should be implemented in the app (overview of what is download and option to delete un-needed segments), but is not critical for now.

Über das Alter, zu spielen, bin ich hinaus. Und jetzt sollten wir es lassen und lieber über Locus diskutieren.

Ich stimme Graf Geo voll zu. Habe neben LM Pro auch Gold gekauft. Die App ist den Preis voll wert. Wenn ich schaue, für was ich während des Jahres Geld ausgebe, kommt es darauf auch nicht an.

...
Danke, kannst du da mal ein Beispiel als Screenshot zeigen

Ich habe mir Cachebox im playstore angeschaut und bei den Screenshots Augenkrebs gekriegt. Quietschbunt und verspielt. Nix für mich.
LM kann sehr viel, aber zum Cachen nehme ich c:geo und LM nur ergänzend, z. B. um zu einem Cache zu navigieren. Und für die Navigation im Auto nehme ich auch was anderes. Das ist auch kein Problem, meine Emails schreibe ich ja auch nicht mit LM.

@Saturo: ob man das Abomodell akzeptiert oder nicht, muss natürlich jede/r für sich entscheiden. Ich sehe meine Goldmitgliedschaft erstmal als Spende, um die Entwickler für ihre Arbeit zu unterstützen. Momentan würde auch mir der Ist-Zustand von LMpro völlig ausreichen.
Ich nutze LMpro seit 7 Jahren (damals 7,50 €) und die App wurde seitdem gewaltig weiterentwickelt, ohne dass es mich einen Cent mehr gekostet hätte. Das kann auf Dauer nicht funktionieren. Also kann ich das Abomodell für LM4 absolut nachvollziehen, irgendwo von müssen und sollen die Entwickler ja leben. Besser als wenn LM irgendwann mangels Einnahmen eingestellt werden müsste.
Dass LMpro weiter gepflegt und genutzt werden kann, ist doch super fair. Und falls LM4 in Zukunft den (nun gestiegenen) Erwartungen nicht entsprechen sollte, kann man ja jederzeit kündigen.
Die Zweigleisigkeit ist somit schon ok. LMpro für Einmalzahlung, LM4 für Abo.

Find inspiration here. Has streetname info and multiple route select.
https://www.plotaroute.com/makemearoute
Registration is free and you already get 3 free test attempts.
Download as gpx track + waypoints > Select Directions. (Locus compatible)
https://www.plotaroute.com/makemearoute

Verstuurd vanaf mijn Mi A2 Lite met Tapatalk

Thank you for this link!
I like the way they calculate the ETA, it's something Locus (app and web) needs to improve.

ROUND TRIP:
I used to play with the "round trip" feature, but after the first wow effect I decided it was absolutely useless. Who would ever rely on a random rotation function around a point?
It is not possible to define preferences of any kind, be they historical, naturalistic or cultural, so rather than relying on a random function my choice at a crossroads would be that of the road I like best, at least it would be based on my choices.
Unless real utility can be found for this feature, integrating it with the options I wrote above (and all the complications of the case), it should be removed, useful and solid functionality better than things like this that do nothing but generate doubts in users.
Those who use a GPS and map device usually want to rely on certainties, not on a roll of the dice.
But this is just my thought, maybe someone else found it useful, but for now I haven't seen a single post.

Thanks guys. I've probably found the error. Will try to publish a new version today (in the worst case tomorrow).

In a tracks context, the possibility to create embedded waypoints is needed and expected here (by me at least).

I've also always been arguing for adding that to the Track Editor, but Menion doesn't seem to believe in adding waypoints to tracks once they finished recording
Would be happy to be wrong, though...

Do I understand correctly. You want to make a waypoint to a track point. I do not desert for what. Do you have an example?

Well, "Waypoints" tab is part of all tracks. I use them all the time to mark special points and events during a recording. Same could be "general" POIs like "Restaurant", but some like "took off crampons here" are specific to the track. So waypoints make a lot of sense. And sometimes you forget them during recording, but you would like to add them later. While you can do that in the waypoint tab, they now don't have a timestamp anymore, which in cases like my example above are of interest. So adding a waypoint directly to a (timestamped) trackpoint makes a lot of sense. And from reading the threads here, I'm not the only one wishing for this...

But what I think about the track point. I create many track points (per language). To maintain OSM later. After uploading, I delete them all again. But I always have to select and delete each one individually (delete also confirm). Please make all selectable.

Agreed.

Few more things about the new track details:



• Thx for making the description selectable & copyable, as I asked for! While you're at it, why not make the title selectable, too?
• As has been noted above, simply having the waypoint icons there is, well, not so helpful. Tapping them should at least show their name, or even center them on screen.
• Also as noted above, wouldn't mind the description below the title. To save space without the header "Description", and perhaps only max. 2 lines, with a clickable "<more>" to expand if longer
• Some customization would be nice - I for example would like to slim it down by removing "Best interval"
• The crossing lines for the "current point" are nice to better gues the values - but why not display the actual values directly, too: "432m / 6.1km".
• I know, the left-most button takes you directly to the current trackpoint - but there should be the opposite, taking you back to the track.
Just my 2 cents - probably you already have some of those things in mind...

Question:
what happen with installed
- PRO
and
- LOCUS MAP GOLD
if i install this BETA with apk???

[Austria]

There's a new version (v2) of DTM Austria, my oldest DTM. Therefor I downloaded the latest LiDAR source data of Austria's federal states.

Additionally I created 2 models with finer resolutions (10m and 0.5"). These fine gridded models will kept limited to Austria.

https://data.opendataportal.at/dataset/dtm-austria

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