Maybe it’s a little early for technological tools to rise up and slaughter the human race, but a potentially deadly side of Google Maps has been discovered, at least that’s what the claims are. A group of mountaineers living in Scotland called the Maps themselves. deadly, even direct routes down cliffs was criticized for suggesting it.
The John Muir Trust, a Scotland-based mountain conservation foundation, believes that Maps’ recommended routes to Ben Nevis extremely dangerous and deadly claims to be. The group says a proposed route to Mount An Teallach leads users directly down a cliff.
Google Maps guides hikers to detours
Nathan Berrie, a conservation officer at the John Muir Trust, said of the situation: The trouble is that Google Maps sometimes directs visitors to the Upper Falls parking lot, probably because it’s the closest parking lot. but this path is not the right one and we often encounter inexperienced hikers heading towards Steam Falls or the southern slopes of Ben Nevis; they believe this route leads to the top.” he said.
Experts say that even experienced climbers and mountaineers can have trouble with Google Maps routes. Mountain safety consultant Heather Morning said: Type Ben Nevis into Google Maps and click on the ‘car’ icon, and a map of the route opens and takes you to a parking lot at the head of Glen Nevis; from here on the road to the top is marked with dots.“
Challenges even the most experienced climbers
Morning continued his statement as follows: Even the most experienced mountaineers will have trouble following this route. Route marks a very steep, stony and roadless terrain where it can be difficult to find the correct walking line even with good visibility. Add to that the clouds and rain, and Google’s path is deadly.”
A Google spokesperson said in a statement on the matter: We built Google Maps with safety and reliability in mind, and what Ben Nevis encountered we are working to investigate the redirect issue.” he said. After this explanation, when re-creating the route in Google Maps was tried, the route was not created as mentioned; Google has probably fixed the problem.