[BaseCamp] Mieage mismatch in route detail v. ruler

[John O. Cooper]

This has happened to me many times.

You have to pay close attention to the route BC uses.  This weekend BC sent
me on a route to a bonus in a park that including a hiking trail because it
did not know about the driveway.

BC used to refused to route me through Barstow, CA, on I-15 and instead
sent me on a long detour.  I contacted Garmin and they said it is because
the road is reported as closed.  Garmin told me I-15 was CLOSED, the
connection between the most populous country in the USA to Las Vegas is
closed.  Not likely.

I confirm routes with Google Maps or S&T and when on the road I use WAZE



John Cooper

On Wed, Oct 5, 2016 at 8:50 AM, Dave Arkle <dave at expertfriend.com> wrote:

> Hi all
>
> Ok, so I'm planning a route for the Void, and I have discovered something
> that is making me not trust Basecamp for routing.
>
> The rally start happens to be near where I live, so I know the area. I know
> for a fact the first bonus I'm going to is X miles from that spot
> (roughly...I don't literally know the precise number), but when I
> double-click the route to get the detail/way point list view, it says the
> distance to that point is about 30% of X. If I use the ruler tool, I get a
> number that jibes with my guess as to how far it is (X).
>
> Curiously, if I look at the distance from bonus 1 to bonus 2 (half of which
> is back tracking) the mileage is correct.
>
> Is this common? I was using the distance between each bonus as the focal
> point of all of my route planning and timing, but if this is common, I'm
> screwed.
>
> I'm dreading the answer to this question, as this is my first rally, and if
> I can't plan it this way I'm not sure how I'll plan it...maybe just go
> ultra conservative so that I can't go over time I suppose. Ugh.
>
> --
> Dave Arkle
>
> To make _ANY_ changes, including unsubscribing from this list, click ----->
> http://micapeak.com/mailman/listinfo/basecamp
>
>