Lost In Wisconsin
The Wife and I are cheap, and that means we don't have any sort of GPS-enabled unit. We won't buy one, fearing that if we do it would just get stolen (and yours truly would undoubtedly leave it in the car one too many times; it would just be easier for me to simply hand my cash to a criminal somewhere, because at least my car window wouldn't be smashed to bits). And we don't want to make extra monthly payments to put one on my phone because Verizon gets enough of my money.
So when we travel, we use the old fashioned way: we type our destination on Google Maps, then trust that our friends in Mountain View, or at least their algorithms, have picked the best possible route.
We used to use actual maps. But we discovered that keeping maps in our vehicles is impossible. Somehow, they all mysteriously escape their automotive holding cells and wander off, never to be seen again. Except, that is, for our map of South Carolina, which has never wandered off. Of course, we never need that map anymore. Maybe it just wants to rekindle old times.
At one point we had an atlas, and we used it a lot, and then it, too, got the wandering blues and we never heard from it again.
But who needs maps when you have Google?
I do, apparently.
I had to go to Wisconsin this week on "business." As Wisconsin, according to Google, is right next to Minnesota, I figured that I would drive -- anything less than 10 hours is drivable in my book; anything more and I take a plane, though now that I have multiple children who each require their own expensive plane seat, we've been breaking that rule a few times of late. That and I'd rather carve a jack o' lantern into my sternum than take children through airport security, but that's another post.
I had to go to Appleton, a modest-sized city south of Green Bay. I don't mind Green Bay, but I'd prefer not to go there during a year when the Vikings are 2-4 and we keep hearing stories about Brett Favre's genitalia.
In advance of said trip, I did all the requisite planning: I packed clothes, brought a jacket, took work-related information and a camera, made a hotel reservation and told everybody where I was going. I also scouted area amenities and looked to see whether my hotel had a fitness center and free breakfast. And I looked to see what was on TV the night I was going to get there because, to be honest, I usually just sit in my room and flip channels for several hours whenever I stay in a hotel (I have neither a TV in my bedroom, nor cable, so such mindless flipping is a thrill).
I also had a minor panic attack when my iPod froze -- I cannot, CANNOT, drive by myself without an iPod, because I can't think of anything worse than having to wade through small town radio. Your choices: country, gospel, a grainy classic rock station and 59 talk radio stations. If you're lucky, that is. Mostly your seek function just keeps going and going and going until you finally give up and start singing "99 Bottles of Beer on the Wall" to yourself.
And I checked my route on The Google. I looked it over. I consulted the map. I highlighted all the major route changes. I looked at the weather. Then I got going. (Thankfully, I was driving during the tail end of Windpolcalypse, so my wife's little Corolla that I was driving was not blown completely off the freeway).
Not surprisingly, the drive was boring -- really boring. There were few towns along the way, and the only excitement came when my door nearly blew off when I went to get gas. That, and my periodic consultation of Google's directions, which required me to risk my safety. But I followed them closely. And I kept heading west.
But, at some point, I realized that the freeway number didn't jive with what Google maps was telling me. And then I realized I was getting perilously close to Green Bay. I was supposed to turn toward the south.
I missed a turn. And I missed a turn because reading Google's directions requires a person to understand transportation jargon, which I don't. I usually look for the word "exit" when I have to change highways. These directions said "merge into," which I took to mean that the highway would merge into my existing route. It didn't.
Indeed, Google maps has done this to us before, getting routes wrong, providing poor directions, not making me read more clearly or force me to buy a GPS. In any event, I was lost in Nowhere, Wisconsin. And so, after I stopped cursing, I found a gas station and looked for a map, and bought about 50 of them, including a big atlas. And I read the map, and it told me to head due south from my location -- problem was, that route was closed, requiring a 30-minute detour.
But eventually, my good-old paper map got me to my destination. And, on the way home, I didn't even bother with The Google. And I'm glad to say that I didn't get lost in the process.
Now if somebody could just improve the restaurant selection along these freeways, I'd be thrilled.








