This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Planning an out and back course

Do folks who use the course navigation for an out-and-back (not a loop) course recommend plotting a one-way course and then using the backtracking feature for the return leg? Or do you plot the return trip on Garmin Connect, making the course twice as long?

Is there any practical difference in how these will work?  I'm thinking about adding several long day hike destinations and not sure which method would be better.

  • I make out and return courses for this purpose.

  • Where I have runs like that I plot the entire route out and back.

  • Thanks for the replies. I can imagine for a run that you might not want to fiddle with these controls in the middle. In a hike, I normally have a lunch break at the destination. I'd be doing the stop/resume later function there, and it seems easy enough to do other navigation setup changes there as well.

    Do either of you have experience using the other methods to compare?  From the docs, it also seems possible to start the same course again in reverse direction all within the activity, instead of using the back-to-start on your own breadcrumbs. I'm not sure there is a difference here, except back-to-start could let me repeat any off-course excursions or navigate the extra bit from trailhead to my car... :-)

    With so many options, I can't figure out from documentation whether there is any relative advantage. Do course length/points limits come into play?  I imagine a one-way course is half as much data to store, but maybe that doesn't matter with a couple GB of storage on the FR255?

  • I would not worry about storage space for the routes. Most of mine are for cycling, where there are some minor differences going back and forth (one way streets). Also, I like to track how much of the climbing I have done on my trip. You are not necessarily half way on the climbing when you are at half distance.