John , you have put a lot of effort into understanding what is happening with the XT2 and the Tread app.
As described at the beginning with the example, the XT2 works with the route (more or less) clearly; the Tread app does not; and using the Tread app to send this route wirelessly to the Garmin does not work either.
I deactivate all avoidances in the XT2. All topic points are always deactivated, I have just checked this in the Tread app and also in the XT2.
Here it is again the topic that the profiles are very much missed in XT2. In the past, you could quickly switch between different profiles with older devices.
And about the current traffic information. With the exception of me, I use the motorcycle as a normal means of transport or i need it for direct go to and from destinations.
Because when I'm touring, current traffic information makes little sense in my eyes anyway. In my experience, no system in the world knows whether or not I can ride my motorcycle when the roads are blocked. Very, very often roads are disturbed but I can still ride my motorcycle without any problems.
Then, as you mentioned, traffic information is often not up to date. Conclusion: when I'm touring, and even more so when I'm planning, these are always deactivated. And if I have a lot of time just before the trip, I check online beforehand to see whether sections should be bypassed due to the current situation.
Then to the destination. The point is not really important to me, it is already my neighborhood. But the point is not a mistake and what makes the route planning so questionable is actually almost correct. Explanation, right there is the entrance of a gas station and right there for the intersection a left turn lane is allowed. But it has an exception, you can also turn left to the gas station, but Garmin probably doesn't know that. So Garmin first turns right, then turns around and drives back, only to arrive on the right-hand side. I can live with that if at least the route is calculated
The fact that the side of the road will play such an important role in cities in the future will present us with major planning challenges, especially if routes are sometimes driven the other way round.
I had already seen something similar because I didn't want to go west but east around a city. So I set a point on an eastern road and wondered why the route was making such arcs/circles. The reason was that there was a small green strip separating the lanes.
I've had the message “Shaping Point must be palced close to a road or trail” a few times in the past without a solution, I couldn't explain it. What sometimes helped in the Tread app was to make it a VIA point, but I don't really want that.
Anyway, this test route confirms that the Tread app shifts the sharpening points and makes my planning unusable. The Tread app is also capable of ensuring that routes imported with the Tread app cannot be used/calculated at all in the XT2.
And one more hint.
The route is for testing.
I will never, ever use the XT2 routing as it is.
Even if all XT2 tread app workarounds are known. When it really comes to planning routes, I won't spend hours in advance trying to please the Garmin. No, I'm not going to put myself through that, the XT2 will end up as trash in the garbage can first.
I am currently thinking about a good workflow for the future:
First planning with a practical route planner (which can also include satellite or terrain views), then checking in BaseCamp if necessary, then checking in XT2, then checking in the Tread app, then checking again in XT2, then correcting, then the whole work process again [...].
Honestly? Find the mistake why i even think about such procedures
PS
I still don't appreciate Garmin being so stubborn with different maps / versions. GPXs simply come from different sources and Garmin should handle this by now and work with it in a more error-tolerant way.