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

What is default speed for Virtual Partner on route generated from RWGPS

Hello

    What is default speed used by Virtual Partner for routes created in RWGPS? I am trying to understand that so I can set the adjustment factor on my Garmin Edge 1030, for the virtual partner to my expected speed

Thanks

Ted

  • From my experience of a decade of garmins (200, 510, 520, 530) and a decade of RWGPS the "speed" used for the Route/Course date/time stamps on the "Track Points" is completely random and thus the VP speed is random for following courses downloaded. I can download a course and the "speed" will be around 20kph and the next day I might download the same course and it will be 1kph. I have asked RWGPS "Support" about this several times but they don't understand the question and at best tell me about "estimated speed" which is a premium feature but nothing related to the VP speed (Track point date / time stamps)

    Some sites (including Garmin Connect) will allow you to set the speed related to the date / time stamps and therefore the VP speed but in the case of GC you lose all the custom cue entries in the imported courses and GCs cue entry user interface is tedious.

  • Maybe that helps:
    https://ridewithgps.com/help/estimated-time

    NOTE:
    Fitfile Repairtool ( https://www.fitfilerepairtool.info/ ) includes a tool to set the speed of the virtual partner. You chose an average speed and the program builds the time stamps.
    There are 2 options:
    -constant speed 
    -speed changes with slope

  • If you want to avoid the virtual partner altogether, use .fit files from rwgps for routes on your 1030

  • I get the "estimated-time" for my club rides. If a club has a "club membership" then rides in the club repository get "premium features" when members download them and I can confirm the estimated time feature has no relationship to the VP speed.

  • and I can confirm the estimated time feature has no relationship to the VP speed.

    Ok, I never tried that.

    I found no setting for VP speed. Do you know if there is any setting hidden somwhere on RWGPS...?

  • members download them and I can confirm the estimated time feature has no relationship to the VP speed.

    It may only work for routes in your account.

  • L.Rouge's post prompted me to export the same route several times and look at the timestamps within the TCX file and I found them to equate to the same speed although I do agree that it seems to be random between different routes. So I decided to ask RWGPS support as well and I got this reponse:-

    "When you export a TCX file, timestamps are added to the file that are used to create the virtual training partner. This is part of the TCX format that we have to adhere to in order to keep it compliant with the standard. If the TCX file is from a previously recorded activity, then those timestamps are based on your previous performance. But if the TCX file is from a route you've created or copied from another source, then the timestamps will be "fake" and won't be related to your performance on the route. 
     
    At this time, we do not have any tools to offer to change the timestamps in the TCX files prior to downloading. That may change in the future, as we have discussed creating a feature that will let users set time stamps for training while creating a course in our route planner. But I can't make any promises as to when something like that might be available."

    Unfortunately not an answer to the OP but the more people that contact RWGPS about this maybe the sooner they will add this functionality.

  • Noting also that the line in the TCX file

     <TotalTimeSeconds>1550</TotalTimeSecond

    is not the time but the number of Track Points in the file

    Garmin Connect Route Planner will allow setting the course Average Speed which will be used by the Virtual Partner and the Time Ahead/Behind data field but the user interface for creating courses with it is tedious and if you import a course created with another planner containing Course Points they are stripped out by Garmin Connect.

    RWGPS has to give each trackpoint a chronologically incrementing timestamp so how hard can it be to base this on the user entered duration or average speed, NOT VERY!

    Many of the Planners other than RwGPS permit a user entered course speed but RWGPS remains the best for almost everything else! (IMO), so I am stuck with it

  • That's very useful info about the number of trackpoints. Thanks. I'm doing a race where the route is on RWGPS and has 106,823 trackpoints which as you can imagine doesn't work too well on a Garmin with a limit of 10,000. Quite a few corners being cut which triggers Off-Course beeps. So when I'm splitting the route up that will give me a much easier way to check whether I'm within the limit than counting them :-).

    And as you say Garmin Connect strips out the course points which is very frustrating. I'm new to RWGPS (so thanks for the comment that it is the best) and like the function to advance the notification before turns. Which means I am also faced with the 200 course point limit that Garmin has. I'm not aware of a field that contains the number of coursepoints but there are only 649 in this full route so it's less of an issue.

    I can see the structure of the TCX in Excel - and agree it is not exactly hard to do a simple average speed calculation, and not that hard to do one taking into account the altidute as well. But I'm not sure my VBA skills are up to writing my own timestamp routine :-(.

  • I don't know but I will answer indirectly. When riding a course created with Garmin Connect the default speed is the one set in connect under the Pace Calculatr tab when you edit the course. That get sent to the Edge. Now it is very easy to take a route in RWGPS and import it in GC, just export a GPX from RWGPX, and in the Courses view in GC, select Import and import it. Once imported you can set the pace, add Course Points (that will work...) and all the rest, before sending to the Edge. Easy