New Topic

Locus Map - help desk Topic Idea Locus Map (Android)

This object is in archive!

Category Locus Map (Android)

Comments 11

Subscribers 6

Votes 5

Nearest points list shouldn't (by default) show a point 1,000km away

Andrew Heard shared this idea ago

Completed

I love the Nearest Points screen, but when most points are hidden there is possibility that a visible point half way around the world will make it into the list. This doesn't make sense. A point 1,000km away is not a Nearest Point. I suggest allowing a radius to be defined. Only points within a given distance, maybe default to 10km? will show in the list.

ba4ef7735e5aaf28a8d60cb8fd1fe0d0 d476e84a3199513be70814d4cb360a17

I like this idea 0

Replies (5)

Michael Bechtold ●

I also had rare cases when very distant points have been listed, but not those nearby - visible and invisible alike.

If that happens again, I need to report an error ...

URL

Andrew Heard ●

@Michael for me its not an error, just silly. If my settings have visible:on and nearest visible point is 10,000km away (say) then it will be at the top of the list. It just isn't logical.

URL

Michael Bechtold ●

I get you point and agree. But omitting NEARER points, while showing distant ones I still consider an error :-)

URL

Andrew Heard ●

Ahh yes. I missed your point. Did you have setting visible only and were the nearer points visible? Sorry, obvious, and I'm sure you have considered that.

URL

Michael Bechtold ●

"Only visible" I always leave off. And if I recall correctly, there were a few near points, and more remote points, but the score in between were ignored. If that happens again, I'll produce an accurate report.

URL

Menion ●

Hi guys,

@Michael, are you certain that some points were missing? This really should not happen.

And about this idea ... well, I may limit maximal distance for visible points, it's not a big problem. Anyway optional configuration for such settings looks for me like nonsense, so how to decide which value is optimal? Hard question.

So improvements here is mainly a cosmetic one right? It is not a real problem with usage ...

URL

Andrew Heard ●

> so how to decide which value is optimal

Not so hard, let the user decide, there is no optimal value as it will depend on the users circumstance, but I thought a default of 10km seemed reasonable.

>cosmetic

yes, but nearest point 1700km away is not near, it's silly

URL

Taras D ●

I haven't used Nearest Points yet but it does make sense that it should exclude excessively distant points.

I believe the concept of "Nearest" depends on the activity. 10 km radius for hiking is reasonable whereas 50 km is excessive. However, if one is driving, 10 km is rather close and 50 km isn't unreasonable. Therefore Andrew's suggestion makes sense: the user should have control over the "search radius" for "Nearest Points".

If one wants to get fancy, the search radius can be tied to the activity. For example, here are suggestions for default values:

Walking: 5 km
Hiking: 10 km
Biking: 25 km
Driving 50 km

However, I would be satisfied with a single, user-defined setting in the app (as shown in Andrew's example) or, at the very least, in the configuration file.

URL

Andrew Heard ●

@Taras also bear in mind there may not be an active "activity". No way for Locus to determine you are driving/ walking or just mapping.

URL

Taras D ●

The activity doesn't have to be active (i.e. recording a track). The "search radius" can simply be a value associated with an activity. In your example above, where it says "Distance 5km", it would display a drop-list of activities. If I want the search radius to be small, I set it to "Walking". If I want to cast a wider net, I set it to "Driving". The actual limits (5km, 50km, etc) are stored in the activity (i.e. recording) profiles (and can be edited there).

Anyhow, it's kind of moot now because Menion has indicated the search radius will be 100km.

URL

Menion ●

Hi guys,

thanks for a feedback. In next version will be nearest points limited to max. 100 km.

URL