My wife and I recently went on vacation to Ashville, North Carolina. On our way home, we planned to drop by and visit our daughter who lives in Waverly, Tennessee. Our daughter lives a little over an hour away from us. It had been a couple of weeks since we had seen her. We had talked about going with her to a new restaurant she had discovered in that area for some time. Stopping by to eat would be a good excuse stop and see her. The fact that it was just an excuse for visiting was made more obvious by the fact that the place we planned to eat was closed on that day, but we still stopped, finding another new local restaurant to try.
When we were done with the visit, we decided to try using the GPS on my wife’s phone to navigate home. We knew how to get home but there are several options available. We wanted to see which one the GPS recommended. Because of some major construction on the way we usually go, we were concerned about the possibility of construction related delays. Before we pulled away from our daughter’s house, my wife checked the GPS. It recommended that we go the way that we usually avoid. It also told us it would take us 22 hours to get home. We suspected that it was taking us out of the way, but it would have to be terribly wrong for it to take that long. Looking at the map, it appeared to be straightforward directions home. We chose to take our regular route. The GPS rerouted its directions, but it still said it was going to take an extremely long time to get home, much longer than normal. My wife stopped the GPS function, and we rode without any assistance for about 15 minutes. Then she decided to check it again just to make sure there weren’t any wrecks showing causing delays. That’s when she discovered that the GPS was set to give walking directions instead of driving. When we were on our trip, we had used that function to give us an idea of how long it would take to walk to destinations in downtown Ashville from our hotel. This why it take 22 hours to get from Waverly to Jackson, Tennessee.