Basecamp Calculations are Whack

Well without knowing exactly where you're talking about and which map you're using in BaseCamp it's impossible to comment. Could be numerous reasons. Can you post some screenshots and let us know which map you're using?

One of the easiest examples as mentioned above is Beatty to the end of Titus Canyon in Death Valley. Map is City Navigator North America NT 2018.3 - screen shot included. I have done this run at a moderate pace and goofing around in about an hour and a half. And to be clear, 8 miles is at 60 mph on pavement. This leaves 25 miles of dirt to do in just under 5 hours .. which is around 6 mph ... anyone that has been through Titus Canyon on a motorcycle, or in a car, knows that is just wrong. So when I see 5 hours, it makes everything Basecamp is telling me suspect now. I have another section in Canada that just seems off and wonky that I will post up as well.

ciq.forums.garmin.com/.../1384052.jpg

Second example - North Vancouver to D'Arcy is all pavement ... Basecamp and Google are close enough to believe it is around 3 hours with lower speed limits and many towns to pass through. From here on, is dirt roads, well traveled roads that people drive cars and trucks on daily. D'Arcy to Seton Portage Road way point is just over 14 miles in just under 3 hours ... 4.5 mph .. nope ... have seen video of guys that are mediocre riders do this in less than an hour. Then the next 3.7 miles to Highland Pub on my map is 40 minutes .. 10 mph? I mean I guess that is plausible, but doubtful based on the road images I have seen and people I have communicated with that have ridden it. Next way point is Terzaqhi Dam - 15 miles in 1 hour .. it could be completely plausible .. probably not since the road is a well traveled compact dirt road, but I won't argue that one yet... until you see the next section to Bridge River has it as 14 miles in 14 minutes ... so we go from 15 mph to 60 mph and the road does not change. Again, people I have talked to that have ridden this road tell me that MAYBE if we took those two sections as one big one and averaged the speed ... it might make sense, but not like this. The rest is still at 60 mph on dirt. It is very difficult to plan length of days and stopping points when the software is so completely inconsistent. Other sections or maps are fine in areas similar, but I am finding little pockets of insanity.ciq.forums.garmin.com/.../1384060.jpg

I don't think that is really the viable solution. The speed limit was set by someone probably driving a sedan through there, I go in and bump that speed up and it gets accepted and it will throw them off. A "set" speed limit makes sense, but the ability to CORRECT that speed in Basecamp, by segment, would be the best solution. I make the route, it tells me this crazy slow time, I do my due diligence and realize that my average speed will be closer to 20 mph instead of 5 mph and it calculates based on that. There is no setting or option in the PROFILES for this (there is no average speed for dirt roads as an option ... which may or may not solve the issue). So I don't know that it is a map error, or a limitation in Basecamp to customize routes. To me this is similar to when Microsoft Streets and Trips went from actual segment adjustable speeds to segment ranges (slow - medium - fast) - my slow was more like medium and so on.

Well for your solution to work HERE would need to designate those roads as 'dirt roads' or some other suitable description and BaseCamp would need to allow you to adjust the speed for those types of roads. Neither in my opinion are likely.

Or Basecamp allows you to set a speed between way points - that would be a third solution, best solution and easily doable solution. It is just an attribute that over-rides whatever the "designated" speed is.

Again unlikely I'm afraid.