Meanwhile, T-Mobile in southern Illinois leaves a lot to be desired, and so dynamic routing was iffy at best unless I was near an interstate. I decided to head off on county blacktops and secondary state routes, sans data coverage, and made good time in spite of storms. I got on I-57 near Effingham, and traffic went smoothly until I approached Champaign-Urbana, where my ETA steadily racked upward as I got closer. A quick peek showed lots of trouble ahead around Rantoul.
So, I stopped for dinner in Champaign, then Google Maps sent me out on back roads until I got around the bad construction backup near Rantoul, after I "primed the pump" by heading north out of town on Mattis Avenue. From then on it was trouble-free.
On the other hand, one of my best experiences with Google Maps occurred one Thanksgiving Eve, on my way to Midland, Michigan. Near Kalamazoo, it informed me of a faster route, and when I took it, it quickly put me on surface streets. I was thinking "WTF?" until I passed another I-94 on-ramp, where the tag said "58 minutes slower." Apparently, there was a wreck near Battle Creek. The new route put me on the designated I-94 emergency bypass once I left Kalamazoo, and past the wreck it returned me to the interstate.
Oh yeah and we did get ahead of miles of stuck traffic.
Then, it was empty roads on US 26 as we went back at 90mph to 110mph till we hit Gresham and stopped off. Never seen my car driven that fast, but it sure did beat sitting in traffic!
I was using Waze when leaving Madras, Oregon, after the eclipse heading to the Puget Sound area of Washington. It suggested a route that would bypass a couple miles of slow traffic, but the road it sent me down was a dirt road with a periodic undulation in it that caused massive vibration, and my car and the two or three others that were on it were throwing up so much dust it was very hard to see. I turned around and went back to the main route and put up with the slow traffic.
A friend of mine was also leaving Madras, but heading to California. He was using Google. It also was giving some poor route advice. Here's what he told me when we compared notes of our trips home:
> Google kept sending us onto logging roads: we bailed on the first when we were told to turn onto a non-existent road; we bailed on the second when a van came out and told us that ~5 cars were stuck axle-deep in mud; we bailed on the third when we got to a sign informing us that we were about to enter an off-road-vehicle trail.
I'd also like to see a review of how the various cell phone companies handled it. Both me and my friend are on T-Mobile, and something like 90% of the text messages we tried to exchange were either lost or delivered hours late. I think we managed one or two short voice calls. Most voice calls either did not connect, or on occasion would connect but only one of us could hear the other.