Look at the profile. The gradient is spiky, between 0 and 20%, for example. This indicates the altitude needs to be smoothed.
there’s two sharp corner warnings. These are a big problem. Loop warnings can generally be ignored, but sharp corners are always a problem. If you look at the corners, they have relatively few points. They would be improved by having more points, and with the curve occurring smoother, in an arc.
one of the corners is a turnaround. GPXMagic (or processGPX if you’re more of a command line person) can add a turnaround loop there. RGT cannot handle abrupt 180’s.
Fortunately, you can fix at least the first two of these by loading the GPX into GPXMagic (google for URL), load the GPX, click “one-click fix”, then save the new GPX. The loop can also be added (I’m not sure if one-click fix will do it but one of the tabs does this). With more experience you can learn how to refine it more. One thing I like to do is switch to satellite view and make sure the MR tracks the real road. If it doesn’t, you can use “nudge” with “smooth transition” (set transition length) to adjust groups of points. Then do “one click fix” after to make sure there’s no ugliness.
processGPX requires Perl and three CPAN modules: Geo::Gpx, XML::Descent, and Date::Parse. I run it on a Mac and Linux. Others have run it on Windows but I don’t know how to do that.
In addition to the usual set of bug and documentation fixes, this version has two significant new options, in addition to (too) many other options from previous versions:
-circuitFromPosition : this goes to the specified position in meters from the route start, checks for the original route to loop around and return to that point, and if such a loop is found, it is repeated the specified number of times. So this is useful for routes which contain circuits, but are not pure circuits which can be handled with the RGT lap option. An optional, rarely used option allows for the circuit to return to the original point more than once before the end of the lap (for example, an out-and-back circuit would use “2” here).
-circuitToPosition <repeats.> : this is similar, but the circuit ends at the specified position, and the position is counted from the end rather than start of the route. This allows defining circuits at the end of the GPX track using -circuitToPosition 0 4, for example, which would have 4 finishing circuits.
Doing circuits this way is much better than doing circuits by repeating the circuits in Strava, for example, since it assures that the circuits perfectly align.