Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove trail feature #4886

Closed
Bananeweizen opened this issue Apr 15, 2015 · 9 comments
Closed

Remove trail feature #4886

Bananeweizen opened this issue Apr 15, 2015 · 9 comments
Labels
Feature Request A request for a new feature/function

Comments

@Bananeweizen
Copy link
Member

I suggest that we remove the trail feature due to severe limitations:

  • It doesn't work correctly, if the screen is off.
  • It has a restricted buffer size (so it cannot track multiple hours).
  • It looses the trail when reopening the map.

There are many more explicit tracking apps. E.g. I have Endomondo tracking my geocaching walkings through the forest.

@Bananeweizen Bananeweizen added the Feature Request A request for a new feature/function label Apr 15, 2015
@Lineflyer
Copy link
Member

Despite the limitations I would not remove that long existing feature. I personally deem it useful to see where I came from.
If we remove that I guess we will get many complaints (and loose a feature other geocaching apps have).

@rsudev
Copy link
Contributor

rsudev commented Apr 15, 2015

I am also in favour of keeping it. Of course is it no replacement for a real tracking app (luckily, so it doesn't require as much power), but still a helper for quicker orientation when doing multies or letterboxes (for me).

@mucek4
Copy link
Member

mucek4 commented Apr 17, 2015

I also suggest keep it. It's annoying but when you need it it's there. We could write into buffer even when it's off. So when you enable it it shows history already.
And maybe wiite it dotted when screen was off.

@yellowduck
Copy link

I also vote to keep it, as I find it very useful. Even better would be the ability to save it.

@SammysHP
Copy link
Member

An easy solution would be to store the track in a GPX in real time and read the last n points when starting the map activity. Also the user would be able to "export" the track (simply take the GPX) or clear it (delete the GPX).

@SammysHP
Copy link
Member

Please vote thumbs up or down on the first post.

@SammysHP SammysHP reopened this May 13, 2017
@Lineflyer
Copy link
Member

CrossCopy from #6558

My personal opinion on tracking features in c:geo:
Since a year I am out for geocaching more often by hiking a long trail or a bike tour.
For this I personally missed the possibilty of c:geo to basically support tracks. A significant number of hiking/biking (multi)caches provide users a GPX track as assistance.
I had to use another app for the track but in parallel contantly switch to c:geo to look for the next stage onroad or even for other caches along the track.

So in my case the trail feature is not so important but importing and showing a track would be.
However if we would support showing imported tracks (which I would really like) it may make sense also showing the way the user already made.

@yellowduck
Copy link

I stand by my original comment. I find this a useful feature.

@SammysHP
Copy link
Member

There is a majority who wants to keep this feature, thus closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request A request for a new feature/function
Projects
None yet
Development

No branches or pull requests

6 participants