Messages

1

Locus Map / Re: [APP] - version 4.4.+ ( 23. 9. 2021+ )

« on: October 18, 2021, 10:21:56 »

In the route details. Can I move the "hide" button to the bottom bar?

+1

2

Locus Map / Re: [APP] - version 4.4.+ ( 23. 9. 2021+ )

« on: October 11, 2021, 12:05:23 »

The new separated center button is great, and so is the smooth animation!

Agreed, but: Do you like its position? I'm kind of uncomfortable with it, because it reaches into the top part. I'd prefer the compass button to be top left... maybe.

The top right is too far away. Those who switch on and off more often should have it downstairs. That only makes sense if you don't change anything. But it could be to the right of the center button. I think it's pretty good downstairs. Although that's probably just a matter of habit.
There we are again at the free place. So everyone can push it where they want it.

+1 down

Inviato dal mio SM-A520F utilizzando Tapatalk

3

Locus Map / Re: [APP] - version 4.4.+ ( 23. 9. 2021+ )

« on: September 27, 2021, 08:29:39 »

...
@lor74cas
Search system needs a big update > big plan on the Q1/Q2 of 2022. And in the route planner? You may partially use search over menu > Add point, or the long click on the "+" button.
...

Thank you for the tip, it's what I need, I did not remember the second function of + button, I think that a different icon is needed to remember this

4

Locus Map / Re: [APP] - version 4.4.+ ( 23. 9. 2021+ )

« on: September 24, 2021, 17:23:43 »

Hello
Is there anyone else who would like a search button in the planner?
Maybe with the results sorted by geographic proximity to the center of the screen / cursor

5

Troubles & Questions / Re: Route planer and estimated time problem

« on: September 07, 2021, 10:52:39 »

I agree, as some unnamed inhabitants of the unnamed continent may use Locus this way and some 15 page disclaimer should be used, like what you should not do with a  microwave oven.

I personally insert short comments in similar spirit for some my challenging (on demand) profiles for MTB, that following routes given by that profile may cause heavy fatique, injury or even death of inexperienced users.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

Don't use the microwave when hiking! 

6

Troubles & Questions / Re: Route planer and estimated time problem

« on: September 07, 2021, 10:18:41 »

If a tool fails because it was used, where it should not be, it is not the fault of the tool.

If there is a profile for hiking and the ETA is calculated, this is a tool that any inexperienced person can consider suitable. Not everyone who uses Locus is experienced hikers, some of them may be tricked into trusting the ETA and risk getting into trouble. I hope it never happens, but if someone gets hurt or needs to ask for help because they based their hike on the Locus ETA estimate, without any warning in the app, who would legally answer?
I think a warning is needed in the app, to protect developers from possible legal action, but even more so to clarify that ETA is not an exact science, but a rough estimate.

7

Troubles & Questions / Re: Route planer and estimated time problem

« on: September 06, 2021, 10:54:57 »

However, I think the ETA estimate is too optimistic, 1500 meters of positive difference in altitude in 2 hours, means 750 meters per hour. The estimate should be at least 3 hours, so there is a 1/3 excess. A mistake of this kind becomes dangerous on long journeys, especially in autumn with the hours of light that are decreasing. So be careful to plan with too much trust in the ETA, even the same planner should warn the user that the ETA is only an estimate and that travel times must be calculated based on their abilities, the type of terrain and weather conditions. This IMHO of a now old hiker.

8

Locus Map (4+) / Re: Web planner / portal

« on: August 13, 2021, 11:00:04 »

Good job, I like it.
The imported tracks do not have the timestamp, neither on the track itself in terms of statistics nor the points that compose it.
We need the undo button.

9

Troubles & Questions / Re: Recording the track---problem

« on: August 04, 2021, 15:54:01 »

Hello Michael. This option was in the app maybe two years ago ... for about an week. Then Google removed Locus Map from the Google Play and we had to remove this function. Reason? Locus Map does not belong into kind of apps that are able to request exclude from the battery optimization...

Sent from my Pixel 5 using Tapatalk

Hello,
a few months ago I used this app https://play.google.com/store/apps/details?id=com.redbull.wingsforlifeworldrun&gl=IT to participate in a virtual race. At the time of installation it proposes a verification system in order to avoid blocking caused by energy saving, maybe it can be an inspiration to you. The app is relevant to the same scope as Locus.

10

Locus Map (4+) / Re: Web planner / portal

« on: July 28, 2021, 15:39:16 »

Little bug.  Going cross-country (using the zig-zag icon) doesn't record any elevation gain.  On the Android, this works as expected.

+1
this is very annoying

11

Locus Map / Re: [APP] - version 4.2.+ ( 15. 6. 2021 )

« on: July 23, 2021, 17:45:34 »

Hello,
in the planner did you plan to insert a sort of search tool?
I think it'd be useful in the planner panel or as a icon

12

Locus Map / Re: [APP] - version 4.1.+ ( 4. 5. 2021 )

« on: May 30, 2021, 10:34:20 »

Upsidedown

Inviato dal mio SM-A520F utilizzando Tapatalk

13

Locus Map (4+) / Re: Web planner / portal

« on: May 28, 2021, 19:20:18 »

...

@lor74cas
Expanding and collapsing waypoints - is it still happening? I can not reproduce it (Chrome, Firefox, Safari)

now it works fine, but meanwhile there was an update of chrome browser on ubuntu lts 20.04

14

Locus Map (4+) / Re: Web planner / portal

« on: May 17, 2021, 18:50:54 »

Hello,
once the list of points has been expanded, I can no longer group it again.

15

Locus Map / Re: [APP] - version 4.1.+ ( 4. 5. 2021 )

« on: May 17, 2021, 18:23:53 »

@lor74cas
Yes, I am aware of this (temporary) limitation. Currently the term in the search bar is only matched against names of points in the local-unspecified language and the language of the client. Other tags are not taken into consideration. (Cannot be taken into consideration directly, as the OSM dataset is not the only possible source of data.) How this search is intended to work (and already works internally, with some minor performance issues):
Let us assume:
- Every point belongs to one or more categories.
- English is the language of client (mobile app or web planner user).
- "wate" is the term in the search bar.

1. A localized fulltext search matches "wate" against names (in local language and in english as specified). As you noticed exactly. Currently, this is the end.
2. Another fulltext search matches "wate" against small dictionaries of synonyms (thesaurus). "wate" could mean: waterfall, watermill, drinking_water, fountain, hot_spring. Why fountain, hot_spring? Because somebody has decided that water and hot_spring are semantically close enough. These little sets of synonyms, language specific,  are configurable on the fly, not stored in a hard manner.
So suggestions are proposed after points that match by their names. Are you searching for drinking_water, waterfall, watermill, fountain perhaps?
3. If we chose one of the suggestion, another search runs (Yes, I actually mean waterfall. Yes, i actually mean all accommodation possibilities combined by typing "room"). This time a localized search matches point by their category, not name. Only category is taken into consideration here, as a source of point can be e.g. Wikipedia, which is not tagged by OSM standards.
Hope this makes some sense, I attach some dictionaries (thesauruses), both specific and more generic to make it more clear.

It makes sense and it might work, but only by seeing it in action would I be able to tell you if it is correct or functional for research purposes.
Is it possible somehow to query locally on the db of the points to see the information relating to the categories? In this way in the areas I know I can check how much information is available and how it is grouped.