-
<% blocks.forEach(function(block, index) { %>
-
<% if (imageHeight) { %>
<% } %>
<% if (!block.description) { %> <%= block.name %> <% } else { %> <%= block.name %> <% } %>
<% if (block.description) { %> <% } %>
<% }) %>
Comments
6 comments
I agree 100% with OP. It's seldom that I am tracking that I don't take a side trip to investigate something, pause for lunch etc. If I want to record a track for a trail, without a pause feature the tracking feature is almost useless. Other GPS apps have this, but Caltopo does not. Will Caltopo add this feature?
Couldn’t agree more. Lack of this feature means (for me), that the mobile app has limited functionality. Which also means I need to use 2 app. CalTopo for all planning, export and import into Gaia and use Gaia mobile app for recording tracks. Would love to eliminate Gaia but cannot at this point. Have started to reconsider using 2 apps and ending CalTopo subscription. Don’t want to though. Please add this functionality
I dont think this would be a good addition. but I see what you are trying to accomplish.
question: when the track is started again, what should the behavior be? when the track is paused, there is no line being drawn. should it just draw a strait line from where it paised to your new location (good for trail breaks)? or should it start a new track?
the problem with the first one is that people (like my self) will pause the line and forget about it for too long (indefinitely?). or some may pause it while in a car and then restart a few miles later because they just want to track miles walked. but if it links the paused point to the restart point then the distance is still wrong because of the link. in Gaia, pausing is for the sake of human stats (like average speed, time traveling, etc), but caltopo does not do that like Gaia or OnX. (I prefer Backcountry Pro, personally, as I can track far more stats and customize the quick view and pause). The biggest reason I use CalTopo is planning trips and sharing live data (I am also in SAR). I don't think pausing is really helpful for CalTopo's aim, but I do think a "quick break" button on the screen would be a huge help. It would just start a new line with all the same name and sharing maybe append with a "-b" etc. when I have gloves on or I am in a tricky area, I would like to minimize button taps and typing. once home I can attach lines where appropriate. I know OP didn't want that, but I don't think the random strait line attaching the pause and restart points would be so good. it ends up cutting out part of the story of the trip and still alters the stats in an odd way. tapping a quick break button would allow you to layer combine the sctions you desire with ease. right now, splitting the tracks and recombining is a chore! especially when it us a cluttered mess like at rest areas and the gps goes crazy.
In response to CLMRG Cash, I understand why someone in SAR would not want to pause a track, but CalTopo is now used by many recreationists who would like to pause. Pausing would be an option entirely up to the user. Generally I use tracking for mapping linear features such as trails, or unmapped streams and such if I'm doing forestry work. If I do use Pause for a side trip with another app I return to my my point of diversion and restart there. A huge annoyance with no Pause is stopping for lunch or some other type of break - the result is a huge bird's nest of lines in the vicinity of the break point, which is useless for downloading to a trail track, and the elapsed time is also useless. Pause would be useful and optional tool for those who want it, but would not be required for those who don't.
Agree that pausing is a useful feature but merging tracks is pretty easy within Caltopo.
Also replying to CLMRG,
I understand the points being made - however, also from the SAR perspective, there are a number of reasons why we might break off from our assignment, only to return later (lunch, bathroom, helping a teammate, etc.). Leaving the track running full time adds significantly to the mess of larger maps and it also adds confusion for others as to what was happening and why (while off assignment). Creating additional tracks for the same assignment also further adds to the chaos of data on larger maps, as does having to take the extra steps to merge tracks. These things are logistical nightmares for those managing large amounts of data. It also further increases the likelihood of errors being introduced.
I do agree that connecting the points between the pauses presents an issue, but maybe the ends can be connected with a black dotted line, or something similar to clearly denote the pause.
Please sign in to leave a comment.