Unraveling a Mapmaker’s Dangerous Decision | Podcast | Overheard at National Geographic
So I told them that they didn't have a chance, and for the sake of their wives and children, they should vacate the area and go back. Both of them sunk, and at that time I heard the cocking of weapons. Once both of them cocked their weapons, I knew they meant business.
This is Brigadier Abdul Rahman Bilal, a retired Pakistani army officer. His son helped him set up a Skype call with me from his home in Rawalpindi, where I could hear small children and the Muslim call to prayer in the background. He's wearing a traditional wool pockle cap and a thick parka. He spoke through a long gray beard about events in 1989 that have made him famous in Pakistan.
I was nominated to personally lead this operation of assault on the enemy position and to dislodge him from height 21,158 feet. In just about any other part of the world, this peak would be a major tourist destination, a place ambitious climbers would flock to. It's taller than the tallest mountains in North America, Africa, Europe, and Antarctica. But in the Karakoram, home to some of the world's most colossal mountains, no one has bothered to even name it or dozens of other similar peaks around it. It's referred to on maps only by its height in feet.
Nevertheless, it holds the significant, if macabre, distinction: never in the history of mankind has there been ground combat at the altitude of 21,158 feet. So this is a record. Four miles above sea level is not an ideal place to fight a battle. Mountaineers know this altitude can be deadly because of the low level of oxygen and the subfreezing temperatures. And then there's the matter of getting up there. The air is so thin that helicopters can stall if they get too high, and peak 21,158 was covered in heavy layers of unstable snow.
Four men had already died in an avalanche attempting to reach it on foot. So Bilal explained that his forces had to be carried up one by one on ropes dangling beneath the struggling helicopters. This is called a sling load operation. We lifted people one at a time. Such an operation has never been planned in the history of mankind before. And this whole thing started in part because of an error on a map. A tiny line in this remote mountain wilderness pushed two powerful nations to fight on the highest battlefield on earth, and no one knew where the line came from until now.
[Music]
I'm Peter Guinn, editor-at-large at National Geographic magazine, and you're listening to Overheard, a show where we eavesdrop on the wild conversations we have here at NatGeo and follow them to the edges of our big weird beautiful world. This week we look at the imaginary lines we draw to divide up the world. As we'll see, those lines aren't always easy to draw, and the consequences of a tiny mistake could be deadly. More after this.
[Music]
There is a nearly 40-mile-long imaginary line that sits high in the Karakoram mountains, far away from civilization. The line is, or at least it was, a boundary between India and Pakistan, and it cuts right across one of the planet's longest glaciers, the Siachen. This ancient glacier is essentially a frozen river that for millennia has been winding its way between mountain peaks and flowing downhill inch by inch. It's like a big ice snake. I mean, I always think of it as a snake because it's got all these ripples and crevasses, and it kind of looks almost like a backbone or something; if you imagine a snake skeleton, it almost looks like that.
Martin Gamache is the director of cartography at National Geographic magazine. He and the other geographers here in the office have spent a lot of time looking at satellite images of the Siachen glacier, but not just because it's pretty. In that sprawling expanse of white, they were searching for something. If you're an astute observer, what you're going to see is you'll see little roads and the human footprint in that area. But from, you know, if you're zoomed out, you don't see a lot of that. The human presence in this area is still very, very low, as you might imagine. A glacier is not an easy place to travel, and before satellite images, it was largely unmapped.
Martin says that just a few years ago, state-of-the-art maps of this area were blank; unknown territory. The modern equivalent of the medieval "here be dragons" in this part of the world that we're talking about. Up until fairly recently, those base maps still had huge holes in them. They didn't even always understand the terrain. I mean, that's stunning to think about.
But you're telling me that as recently as 1999, you were working with maps that still had blank spaces?
Yeah, and that to me is the essence of why this is an exciting job. Because everybody will say, "Oh, well, everything's been mapped." Right? It's like, "Well, yeah, but to what level of detail?" What does that mean to be mapped? You know, yeah, we know that there's a mountain there, but no, we don't actually know how high it is, and we don't know how it relates to these other mountains necessarily.
Okay, well so this is gonna really show my map ineptitude potentially, but I've got a family atlas I'm gonna grab off the shelf here if I can actually find it. Okay, I wouldn't exactly call myself a hoarder, but things have piled up in my study over the years. It's a rock I found in the Himalayas that kind of looks like a snow leopard, a box of fungus from China that said to help you live longer—never thrown that away—and somewhere in the middle of all this is an old National Geographic atlas.
I can see Kashmir, but where is Hodgson's line? Where would I find it on a map like this?
Well, the thing about Hodgson's line is it’s literally like a straight line. If it's on there, you can't miss it.
Oh, I see it. I see it right here. I think actually, you know, if I'm looking at this, it's like half an inch long, you know, like basically the size of maybe two ants. That's Hodgson's line?
Yeah, it kind of makes a triangle there in the furthest northern part of India.
Martin is one of the first people in the world to call this boundary Hodgson's line. That's because before our team started researching the story, no one knew where the line came from. It's amazing that you could have such a seemingly inconsequential mistake that can, in part, lead countries to war. There are still thousands of soldiers who are up there bearing witness to this issue.
This is Freddy Wilkinson, the writer who worked with Martin to track down the mystery of this line. But before you can understand how this line led to combat, you need to know a little context about India and Pakistan. The seeds for the Siachen dispute were sown at the very birth of Pakistan and India after World War II. The British Empire was collapsing economically, and the British made the decision to get out of South Asia as quickly as possible.
Before World War II, Pakistan and India were both part of the same British colony. They decided very early on on a two-state solution, where there would be an India for the Hindu majority and a Pakistan for the Muslim people. In 1947, the British left South Asia. Within weeks of that independence, Pakistan and India were fighting over Kashmir. Violence broke out across the new border as the population reshuffled; Muslims tried to get into Pakistan, and Hindus tried to get into India. As many as 2 million people died in the chaos.
Things were especially complicated in the region of Kashmir. That's because India and Pakistan both believed, and still believe, that it should be part of their respective nations. When the dust settled from this initial war between India and Pakistan, Kashmir was divided. Representatives from the two new countries in the United Nations drew up a cease-fire agreement. Part of that agreement was a boundary that wound through Kashmir, and surveyors were dispatched to draw this line.
But a curious thing happens. After defining this line all the way through Kashmir, the survey team stopped about 40 miles before the Chinese border. Rather than actually finish their job at a certain coordinate point, they inserted this language that said the border was to run "thence north to the glaciers." It was a vague phrase, especially for something as sensitive as a national boundary line. But at the time, it was impractical to be more specific. For the survey team to actually succeed would have required elite mountaineers of that era to be guiding them.
So it makes sense that they would have looked at this terrain and figured, "Let's wrap it up and go home." Yeah, it must have seemed to them back in 1949 absurd that anybody would bother fighting over this territory. So the boundary stopped in a dead end, just short of completely dividing the two new countries.
According to the U.N. treaty, maps of the region should show a gap of roughly 40 miles in the official dividing line between Pakistan and India. That's a rare oddity for geopolitical maps, but an important one. And then quietly and inexplicably in the 1970s, maps began to appear all over the world showing the border completely connected. On a map like my home atlas, this tiny line was hard to notice. It's something of a geographic needle in a haystack and it took more than a decade for someone to come along with the right combination of knowledge about history, politics, and mountaineering to notice that the line didn't belong.
To understand how the line was discovered, I spoke with Indian journalist Nitin Gokulay. So maybe you could tell me a little bit about how that line was discovered, at least by the Indian side.
In 1978, a very famous military mountaineer, Colonel Kumar Narendra Bull Kumar, was seconded to accompany a German rafting expedition on the Indus River. As a military officer and an avid climber, Bull Kumar had a lot of experience in the mountains and knew the maps of the region by heart. He'd been asked to assist a pair of German adventurers who were planning an expedition in the region.
So after spending a couple of months with them, he saw some very fancy new maps that they were carrying. They were the U.S. maps. That's when he saw the line that closed the gap in the border and he knew it shouldn't have been there. Being a mountaineer and a military man, he got alarmed and he went straight to the Indian military, the army chief in Delhi. So they came there and they discovered that yes, the Pakistanis were coming in. Meanwhile, Pakistan had been treating the new line as fact and had been sending expeditions to the area.
Things slowly escalated between the two countries. The intelligence reports in December '82 onwards kept suggesting that Pakistan was planning some kind of an expedition or some kind of a deployment on the Siachen. India sent troops to occupy the area in 1984 and quickly took several peaks that gave them control over a huge swath of the Siachen. Pakistan sent troops to push them back. The fighting was brutal. The men struggled for breath in the thin air while trying to avoid avalanches and frostbite, all while shooting at each other.
And that brings us back to Bilal, the Pakistani army officer yelling at two Indian sentries atop peak 21,158. And I repeat it once again that they should go back. If they vacate the area, there's nothing between me and them. I don't want bloodshed. Then there was a yell: both of them, they murdered, and they fired at me. The two groups exchanged shots, and people on both sides were killed. But Bilal had the advantage; he had attacked during a blizzard and caught the Indian outpost off guard.
At somewhere around 9:15 in the night, they said that one officer and three of the soldiers had died. So they cut the ropes themselves, they burnt their tents, and they withdrew at nighttime. There was a big, a lot of cheering from the people on the other side in the rear, and we knew that we'd won. The Pakistani army succeeded in taking peak 21,158, but the Indians held on to many others.
Over the next 30 years, the two forces struggled for control of the strategic peaks around the Siachen, and after years of fighting, a ceasefire has taken hold. Thousands of soldiers have died over this remote piece of mountain and glacier. Most of those deaths have nothing to do with combat and are related to the extreme altitude and environment: hidden crevasses, avalanches, pulmonary edemas, and they were at least partially caused by this mysterious line on a map.
But no one knew where the line came from. Our writer, Freddy Wilkinson, spent more than six years investigating. He researched archives, traveled to India and Pakistan, and visited the U.S. State Department, where he met with an official named Dave Linthicum. It's a nondescript office suite in a government building. You have to go through a metal detector and security to get in. Dave ushered us into his room where he works at a cubicle, and taped above his desk is a photo of a man, Robert Hodgson. And I posted that right where I could see it all the time to remind myself not to f-up like he did.
This is the man who kept a black and white photograph of Robert Hodgson above his desk. Dave Linthicum, boundary analyst, retired U.S. State Department, Office of the Geographer. Dave has retired from the Office of the Geographer since meeting with Freddy, and he spoke with us on the condition that we say Dave's comments do not necessarily represent those of the U.S. State Department. Dave is like the Alex Trebek of geography: what is the Office of the Geographer? Since '53, it's had the authority to figure out exactly where U.S. government policy says boundaries between countries should be.
For example, the line between India and Pakistan. In the summer of 1968, the Office of the Geographer received a message from the U.S. Embassy in New Delhi. They asked how the U.S. should regard several border disputes India had with its neighbors, including Pakistan. The request fell to, you guessed it, Robert Hodgson, who was an assistant geographer in the office.
After a few months, Hodgson responded with a memo that stated going forward, U.S. maps would show a completed boundary through Kashmir, closing the 40-mile gap, rather than following the 1949 ceasefire agreement text, which says "thence north to the glaciers." Instead, Hodgson drew a line that was a whole lot more east than north, favoring Pakistan. Hodgson had closed the gap in the border, making the new line official on U.S. maps. But he also tried to keep it quiet.
Hodgson authored a memo where he said that this present memo is being used rather than our usual outlet to keep publicity to a minimum in changing the depiction of the boundary between India and Pakistan. That bit about keeping the publicity to a minimum didn't work. The U.S. government publishes thousands of maps every year, and commercial map publishers, including National Geographic, often took their cues from those government maps.
So this tiny line spread throughout the world, and it was just a matter of time before it sparked this conflict. So why did Hodgson do it? The answer is well, we don't know. First, we should note that Robert Hodgson died in 1979, so he didn't live to see the consequences of his line.
I've been Freddy's editor on this, and I've watched as he and Martin have researched the story for six years. The whole time, Robert Hodgson was like a ghost to us. We wanted to get a full picture of who he was, but many people who knew him had died. Freddy finally tracked down one of his former colleagues and two of his daughters. They filled in some of the details. For example, he was a funny dad who took the bus to work every day. He earned a purple heart as a World War II Marine and was well known for his straight shooting personality and his precision in marking borders all over the globe.
He was so well-respected as a geographer that an underwater mountain in the Atlantic was named in his honor. We don't know for sure, but based on everything we've learned about his life, it seems this line was simply a mistake. It's just a testament to if you do a thousand things right, you make one thing wrong, you might be known for the one thing.
Dave probably understands how Hodgson might have felt better than anyone because, in addition to being one of his successors in the Office of the Geographer, Dave also started a conflict with a misplaced border.
Well, thanks, Peter, for bringing up my biggest mistake. I appreciate that. In 2010, Nicaragua sent 50 troops into a small sliver of Costa Rica. They claimed the area was part of Nicaragua because that's how it was labeled on Google Maps. Costa Rica responded by sending troops of their own, and the two groups had a standoff in what has been called the first Google Maps war.
Dave's boss at the State Department found out the next day. He said, "You know, they're blaming this invasion of Costa Rica by Nicaragua on Google Maps. Didn't you draw that line, Dave?" And I said, "Yeah." I knew the next few weeks were going to be a bit tough. I drew the line incorrectly just for the last couple of kilometers. But that's all it takes.
David made a small mistake. Google worked quickly with the State Department to correct the border, and luckily, no one was hurt. Drawing borders is tricky because they mean a lot to the people who live there, and it's something our own geographers face here at National Geographic.
Even with all the benefits of modern satellite imagery, as Martin's team was making a map for this story, they had the same problem Hodgson had: where do you draw the line? As we were reporting our story, one of the things that we tried to do is look at a lot of satellite imagery—really detailed satellite imagery—and map where Indian positions and Pakistani positions were on the glacier.
At a certain point, like, you start going cross-eyed and thinking every little rock on the glacier is an Indian, you know, anti-aircraft or artillery position. And you kind of have to back up and say, "Okay, well, is this a speck of dust, or is it something real?" And then, you know, also like, "Oh, there's all these engine positions here in Pakistan that nobody's really described before. They're clearly, like, on the other side of the boundary. Does that mean we should redraw our line?"
Now we're faced with the dilemma: do we do what Hodgson did and kind of redraw the line? Do we change what is an agreed-upon line of control between India and Pakistan to reflect what is actually happening on the ground, which both sides have? Are they operating on each other's territory? Do we make that statement on our map, or do we wait and let somebody else decide when to do that?
I think one of the things about this story that hits me sort of in the gut every time I stop and think about it is that, you know, these imaginary lines, it’s a very academic sort of drawing room exercise until those lines turn into actions that lead to things like, you know, people being killed in this mountain range.
I mean, there's... do you ever think about that?
I don't think I'm doing a good job of it, like I do, and I think about it all the time. You never know fully what the consequences of your actions are going to be until you've triggered it. So I don't think Hodgson expected to—if he was to see or if he saw the outcome of this—I don't think he thought, "Oh, India and Pakistan are gonna be fighting a 30-year war on top of the world and people will die." I don't think he anticipated that at all. But once it happened, everybody said, "Oh, well, you know, you should have known," or like, "Of course."
Okay, so let me ask you this. This is 2016. Do we still show Hodgson's line now, like this?
No, no, we don't. We removed Hodgson's line and replaced it with a claim line by Pakistan to all of Jammu and Kashmir. We give them each equal treatment. To this day, the area where Hodgson's line used to be is occupied by Indian and Pakistani military forces. The official line no longer exists, but its shadow lingers on the highest battlefield on earth.
The theoretical line has been replaced by a very real line of opposing militaries. More after this.
[Music]
The Himalayas are home to all kinds of unusual geography. The most famous, of course, is the tallest mountain in the world, Mount Everest. But exactly how tall is it? A team from Nepal and China recently re-measured it and came up with a new official height you can read about the science behind it in our show notes. You can also read about a team of 10 Nepalis who completed the first winter ascent of K2, the world's second tallest mountain, which isn't far from the peak Bilal's men attacked.
Like many international conflicts, the history of Kashmir is complicated. Luckily, our culture team has put together an article explaining the history of the princely state of Jammu and Kashmir that helped me understand the basics of the conflict. Subscribers to the magazine can read Freddy's article, which includes more details about Robert Hodgson's life and the consequences of his line. You can also explore Martin's detailed maps of the Siachen. That's all in your show notes, right there in your podcast app.
Overheard at National Geographic is produced by Brian Gutierrez, Jacob Pinter, Laura Sim, Carla Wills, and Alana Strauss. Our senior editor is Eli Chen. Our executive producer of audio is D'Var Artelon. Our fact checker for this episode was Brad Scribner. Our copy editor is Amy Kolczak. Hansdale Sue sound designed this episode and composed our theme music.
Special thanks to members of Robert Hodgson's family: his daughters Amy Wilcox, Susan Summerfield, and Laura Johansen, who generously shared memories of their father.
[Music]
This podcast is a production of National Geographic Partners. Whitney Johnson is the director of visuals and immersive experiences. Susan Goldberg is National Geographic's editorial director, and I'm your host, Peter Guinn. Thanks for listening and see you all next time.
[Music]