Join Ride with GPS and discover even more new routes and riding buddies. Print turn-by-turn cue sheets so you know where you are heading. And then, log your rides and watch your progress.
A cool grey day and only a few riders. The rest must be baby sitting grand kids as its school holidays
By: | Pete Boult |
Started in: | Woodside, South Australia, AU |
Distance: | 47.7 km |
Selected: | 47.7 km |
Elevation: | + 581 / - 572 m |
Moving Time: | 02:53:00 |
Page Views: | 24 |
Departed: | Apr 20, 2023, 9:58 am |
Starts in: | Woodside, South Australia, AU |
Distance: | 47.7 km |
Selected distance: | 47.7 km |
Elevation: | + 581 / - 572 m |
Max Grade: | |
Avg Grade | |
Cat | |
FIETS | |
VAM | |
Ascent time | |
Descent time | |
Total Duration: | 04:22:52 |
Selection Duration: | 15772 |
Moving Time: | 02:53:00 |
Selection Moving Time: | 02:53:00 |
Stopped Time: | 01:29:52 |
Calories: | 1256 |
Max Watts: | |
Avg Watts: | 121 |
WR Power | |
Work | |
Max Speed: | 60.2 kph |
Avg Speed: | 16.6 kph |
Pace: | 00:05:30 |
Moving Pace: | 00:03:37 |
Best format for turn-by-turn directions on modern Garmin Edge Devices
Best format for turn by turn directions on Edge 500, 510. Will provide true turn by turn navigation on Edge 800, 810, 1000, Touring including custom cue entries. Great for training when we release those features. Not currently optimal for Virtual Partner.
Useful for uploading your activity to another service, keeping records on your own computer etc.
Useful for any GPS unit. Contains no cuesheet entries, only track information (breadcrumb trail). Will provide turn by turn directions (true navigation) on the Edge 705/800/810/1000/Touring, but will not have any custom cues. Works great for Mio Cyclo. Find GPS specific help in our help system.
Estimated Time shows a prediction of how long it would take you to ride a given route. This number is based on your recent riding history, and represents an estimate of moving time. Each time you upload a new ride, your Estimated Time profile will adjust to reflect your most recent riding. Only rides exceeding 10 miles (16 km) will affect these estimates.
Go BasicOur Basic members have unrestricted access to everything we offer in our mobile apps. Learn more by visiting our Compare Plans page.
Tell us a little about yourself
Rock solid GPS logging, helpful navigation, live logging and more are all available when you install our app.
Nice looking ride. As a mater of interest I was curious to see how accurate the elevation gain on your ride was so downloaded the GPX file and fed it into https://gpx.studio/ and it confirms that RWGPS exaggerates the gain. gpx studio says it was 1743
And does the site you fed it into resample to fewer points?
I dont think it reduces them, The the number of trackpoints showing in gpx.studio is 5392, not sure if you can determine number of trackpoints in RWGPS
OK Geoff, it sounds like gpx.studio imported the number of GPX points correctly . I had my sample rate at every 2* seconds and moving for 173mins = 5190 +/-60 points.
But that's not the point - its all about what you do with those points!! Is called signal processing and how you deal with unequally spaced data is something I dealt with in my profession.
I'll try and explain
Assuming X = eastings, Y = northings and Z = elevation above the geoid (shouldn't use sea level as this depends on gravity which is not spatially constant). Horizontal distance apart (we'll call it XY distance) of data points of course depends on your speed and global positioning data from satellite, which last time I looked (2 years ago) was no better than 3m on the flat if you pay for it and 9m if you don't, less accurate on slopes when satellite triangulation is compromised and non-existent in steep valleys. Elevation depends the accuracy of the barometer in your phone, changes in goid barometric pressure due to weather and I assume some crosschecking with the global digital elevation model (DEM, which as I said can be 3m at best).
So how do you deal with this somewhat imprecise data? You fit a grid (3D) / curve (2D) to the data and resample the grid / curve to a constant distance apart.** But fitting a grid (sometimes called a surface) or curve can be done in many different ways. In my experience there are 4 grid fitting algorithms that are commonly used with unequal spatial data: B-spline (https://en.wikipedia.org/wiki/B-spline), minimum curvature (have a look at this if you want a "simple" explanation of gridding methods - of which this is just one - https://www.petrosys.com.au/so-many-gridding-algorithms-ill-just-use-the-default/ ), least squares binomial and distance weighted average.
So depending on which method of signal processing the likes of RWGPS, Strava, Wahoo and gpx.studio use on input data you will get a different output for distance traveled, elevation gain speed and gradient etc.
At least with RWGPS you do have some control over the input data.
* Having the sampling interval set at 2 seconds is too short in my opinion, especialy where there are lots of steep hills being ridden by slow oldies like us, but 2 secs might for instance suit a faster road bike ride down country lanes on the flat. I had previously set mine in the App to 5 seconds - BUT having deleted the App and reinstalled it when having problems with my phone (due to the recent bank scam) I'd forgotten to set it to 5 seconds - 2 seconds must be the default.
** if this wasn't done then for one thing calculated gradients would be all over the place. They're not so this is what they must do.
Hope this helps / perhaps we could ask RWGPS exactly how they deal with their data - but I feel life is too short now.
See my latest NSC ride for a response