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

User-Waypoints vs Turn-by-Turn navigation

Hi,

as far as I have researched and experimented, this is the state of waypoints and the 945 today:

- If you upload a Course (a predefined Route) manually via USB cable or via an app like the Strava Routes app, this route will not contain any waypoints at all. The map will show you only how far it is to the end of the course.

- If you upload a Course through Garmin Connect, it will be "enriched" with turn-by-turn navigation waypoints. This means that on a busy route, with lots of forks, you will have hundreds of artificially added waypoints, telling you to take a left or right. Garmin Connect also allows you to create your own "Custom" Waypoints, e.g. for Water or Aid-Station.

Problem Scenario:

Say I want to run this trail race, it is 30km long and has 4 aid-stations along the way. I add the course in garmin-connect, and mark each aid-station on it. I wish to get the information how far I have to go to reach the next aid-station during the race.

If I do the above, uploading the course via garmin connect will add in all the turn-by-turn waypoints, and my carefully setup datascreen containing Datafields like "Navigation->Distance to Next" and similar will **NOT** show the distance to the next aid-station, but rather it will show the distance until the next autogenerated turn-by-turn navigation turn is hit (which is every few hundred meters in path heavy places). My own custom waypoints still exists, but I cannot use them due to the added turn-by-turn information that I did not explicitly want!

Solution Suggestion:

- I would like to select if I want turn-by-turn navigation on the watch. If it bothers me, let me disable it - maybe even the other way around, let me enable it if I want it.

- Any waypoint specific datafields like "Distance to Next" etc. (there are a few in the Navigation category) should ignore any automatically added turn-by-turn waypoints, this is not what I want to know about!

  • Former Member
    0 Former Member over 5 years ago

    Same issue here. Here's my workaround:

    1) Create route in web tool with better mapping (Strava for me, but sometimes Suunto).

    2) Import to Garmin connect web tool and add waypoints (they must be added in garmin or they will not show).

    3) Export as FIT file (critical to getting waypoints to show on watch).

    4) Attach watch via USB to PC and copy FIT file to 'NewFiles' folder on watch. (this prevents the auto generated turn by turn waypoints)

    Wish Garmin would just add the option to truly disable turn by turn so I can sync via phone ....

  • I still looking for a way to enter waypoints and load maps on my FR945, frustrated

    I may be doing something wrong, but at this point I am using my old Suunto tool to load POI my new Garmin FR945

  • Thanks for the work-around, definetly will be using that method for my next race. Hoping very much Garmin can clean up this mess though, this requires quite some time, knowledge and a PC to work!

  • Hi 2251627,

    are you talking about the same thing as the OP is? We are talking about waypoints as parts of courses (like aid stations along a race course). We are not talking about POI or general points on the map that are not on a course.

    In case you are thinking of the same waypoints: You can create waypoints already both through the garmin connect app (on android at least) and on the connect garmin website. Simply go to "Courses", create a new one and then add your waypoints on it. This point of this post is that these custom waypoints are not usable properly when garmin "enriches" your courses with turn-by-turn navigation waypoints, which it will do if you try to upload it through garmin connect.

  • You could use any other tool offering better control over way points (for turn by turn or other annotations). E.g. "ride with gps" or a few others and then transfer the fit or tcx file to the watch with any other way then connect (which boils down to cable or 3rd party apps like gimporter)

  • Thank you all

    I will follow your advice, looks straight forward 

  • Yes - I use plotaroute.com and gimporter - best combo for this. For routes without specific waypoints I use ridewithgps as I prefer the UI.

  • Just to throw in another possibility that may work for some. I started playing around with AppBuilder - apps.garmin.com/.../fd690281-9c22-4fee-a81e-3b7f39aa67c5 - actually 3 versions available, by the developer Flowstate. Appbuilder allows you to "write" small chunks of code to run as a datafield. Although generally easy to use, it is capable of doing some really complex math. Flowstate has a decent set of instructions and examples at ciq-appbuilder.blogspot.com/.../overview.html

    First used it for a "Backyard Ultra" where I had a data field that tracked distance left on each trail loop and estimated time to completion based on a rolling average pace. When I arrived at the start/end and hit lap, it switched to show time left until the next lap started (on the hour). It actually worked really well (I even wrote it to adjust the lap distance based on the first lap as trail race distances are rarely accurately published).

    More for this use case, I did a trail marathon recently with aid stations and cut-off times. I didn't bother with a map in this case but I would have run into the same issue between turn directions and tracking aid stations being discussed here if I needed the navigation assistance.

    I used two datafields (could be combined into one or use Appbuilder 5+ if I needed more IQ fields):

    Distance to next Aid/Cutoff:
    format(findlte(distance,8.3,15.3,23.3,31.3,37.3,42.5)-distance,'%.1f')

    Time left to next aid/cutoff:
    setv(1,8100);setv(2,15300);setv(3,21600);setv(4,28800);setv(5,35100);setv(6,39600);getv(findlteindex(distance,8.3,15.3,23.3,31.3,37.3,42.5)+1)-timer

    Lots of other ways to do this (could base it off lap count if you want to hit the lap button each aid station - more accurate as it "re-syncs" each aid station so accumulative distance errors are reduced) but this was easiest and, as did not suspect I would be chasing cut-offs, it was accurate enough. No lap buttons or other things needed. At some point just before or after each aid station it would switch to the next one. Another option is to get really fancy and all a double press of lap to reset the distance - bit more complicated to write.

  • I'm also a plotaroute.com and gimporter user and love that combo.

    With another widget 'GRouteLoader', you can select a GC course by web url no, the number in web address of the course. No companion app needed on the mobile.

    I just tested it. Created a course with just a water and a food station. Downloaded it to watch with 'GRouteLoader' and my first waypoint when selecting the course on the watch is the water station. I also double-checked the course fit file in FItFileRepairTool and the only waypoints I get is my two stations, no tbt.

    Extremely simple if you're a GC course creator user. 

  • I had the same problem recently. Ultra trail run. I defined waypoints for each aid station and wanted to be able to see how much distance/time I had left to the next aid station/cut off limit. Had to go through all that fuss with exporting the fit file and importing it manually.

    Former Memberdo you think a modification of GC wyould be possible such that when waypoints are defined in GC route it would transfer the route just with user defined waypoints instead of turn-by-turn waypoints? Or if the turn-by-turn markers are a separate thing, the watch coud take into account just the user defined waypoints for ETA/distance to the next display?

    Seems there are more people struggling to get the same result....

    https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-945/169045/creating-a-course---with-way-points-for-eta-next---using-garmin-connect/913986#913986

    https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-945/193429/how-to-show-distance-to-the-next-course-point-instead-of-waypoint