Please excuse the length of this problem as I want to provide as much information as possible to see if I can take appropriate corrective action. I run BaseCamp v. 4.7.3 with City Navigator North America NT 2022.1 although the problem first arose using 2021.3. My Activity profile is Motorcycling with Routing set to Shorter Distance, Unpaved Roads to be avoided and all Feature Avoidances checked except Toll Roads and Roundabouts. I have been using the program for six years and it has helped me create hundreds of routes to download to my Zumo 590LM.
There is a road intersection SSW of Harrison, AR at N35o 50.894' W93o 21.673' that connects Hwy 16 with Hwy 21. These two roads, along with Hwy 43, are the shortest distance between Deer and Ponca, AR, respectively. The intersection is two lane paved country roads (pavement verified using Google Maps satellite view) with no direction restrictions. I routinely zoom in to the 80 ft. scale to ensure accuracy of my tick marks or waypoint creation. If I attempt to create a route from Deer to Ponca, or if those two towns are on a longer route I am creating when I attempt to make a right turn from Hwy 16 onto Hwy 21 BaseCamp will not allow me to do so and automatically creates a longer route south, then west, then NE to the intersection where it adds a left turn onto Hwy 21. It does not matter if I create the route by making successive tick marks on the roads I want to use or if I create a succession of Waypoints and then create the route by selecting all the Waypoints. In at attempt to trick the software into avoiding the longer distances I have split routes into two parts having the first part end just before the right turn intersection off Hwy 16 and begin the second part on Hwy 21 just after making the right turn onto Hwy 21. If I then use the function to connect the two routes BaseCamp does so and automatically creates the longer distance route(s). This has left me with the only option being to accept the fact that to keep the shorter distance route I must make it into two separate, sequential routes. I note also that several years ago I had a similar problem with a route in SW Tennessee with BaseCamp forcing me to take the wrong fork in a road and loop through a cemetery and then routed back to the correct fork. In this problem a helpful Garmin support representative replicated the same problem on her computer but could not find a way to correct the problem. I appreciate any assistance that can point out what I am doing wrong. Thank you.
