2 years ago I went on the (rocky & dirt) forest "roads" in the North Georgia mountains with my Jeep, and at the top of the dirt trail, I encountered a couple of

2 years ago I went on the (rocky & dirt) forest "roads" in the North Georgia mountains with my Jeep, and at the top of the dirt trail, I encountered a couple of hikers who drove their rental Nissan Versa into a mud pit. They had blindly followed their GPS and were completely stuck. I was too busy helping them get out of their predicament to notice exactly what they were using but I know that it wasn't Apple Maps (they were on Android). Actually, Apple Maps will refuse to route me though any of the forest service "roads" and shys away from unpaved ones (though I've found exceptions). Only if I set a intermediate destination in the middle of the forest will it route me through those trails. Back in city/suburbs, I've found the same as the author, in that Apple pads the time with a few extra minutes. I appreciate that realism because it only takes a few poorly timed traffic lights to add a few minutes to the estimate. I suspect there is some logic around building padding around lights at large intersections because I noticed that when the destination is right after a major intersection, that padding remains until I clear that intersection—and that doesn't seem to happen when the destination is much further after a big intersection.