The Geography of Half-Space: Cricket's Invisible Maps from Melbourne to Dhaka

On June 19, 2026, I was at home in Melbourne watching Australia's 2-3 loss to Germany in Sochi. Tom Rogic received 11 passes between the lines, Australia had 58 percent possession and 12 shots. That same night I made 12 animated clips mapping Rogic's half-space rotations. The thread gained 10,000 followers in a week. I had abandoned a paid match-report deadline, redrawing one pressing trigger for three days.

I keep returning to the half-space, because that is where Melbourne was born. The geometric kinship between football's half-space and cricket's corridor has occupied me for years. In football, the half-space is that gap between fullback and centre-back, where an inverted winger drifts in and pulls the opposing block apart. In cricket, where is that corridor? I would say it is the channel outside the fourth-stump line, where a batsman loses balance attempting a cover drive, and a bowler plants the ball on that line to interrogate the batsman's footwork.

I began cricket writing in 2026, covering the Wills Cup in Dhaka for Prothom Alo. Even then I noticed that cricket analysis almost always gets stuck in individual performance numbers—how many runs, how many wickets, what strike rate. Nobody asks where those runs came from. Which corridor did the ball land in, which angle was the fielder standing at, which way did the batsman's feet turn. In football we see formations, we see space, we see pressing triggers. In cricket we see the scorecard. Yet cricket is a more spatial game than football. One ball, one pitch, one field—all geometry.

I rebranded my blog in 2026, when I launched Half-Space Melbourne. Ange Postecoglou's 3-2-4-1 taught me that a formation is not just a lineup; it is a hypothesis the game tests. A field setting in cricket is exactly such a hypothesis. When a captain keeps third man and moves fine leg, he is telling the bowler: land the ball here, the batsman will play there, and the fielder will be waiting there. It is a geometric hypothesis.

I started using StatsBomb event data after 2026, after building Kylian Mbappe's transition map. Mbappe did not run; he edited the transition map in real time. Cricket has many such moments. When a wicketkeeper comes up to the stumps, he is not merely fielding—he is altering the spinner's ball trajectory, compressing the batsman's footwork distance. It is a real-time spatial edit.

My central observation is: cricket's half-space equivalent is the fourth-stump channel, and the geography of this corridor differs across every cricket culture. At Mirpur in Dhaka, spinners plant the ball in this corridor to force the batsman into defence, because the pitch is slow and the ball turns. At the MCG in Melbourne, pacers take the ball away from this corridor because the pitch has more bounce. In England this corridor sits further outside the pitch because the ball swings. In Australia it sits further inside because the ball carries. These differences are not merely environmental—they were built through migration, weather, and playing culture.

In 2026 I was named to the ICC Awards of the Decade jury. In those jury discussions I saw that analysts almost always talk about a batsman's strike rate or a bowler's economy, but nobody talks about the geometry of a field setting. Yet a field setting dictates which line the bowler takes, which shot the batsman plays, and where the ball goes. A field setting is the first layer of geometric decision-making.

My friends, two analysts in Melbourne, argue with me about pressing triggers. They say cricket has no pressing triggers. I say it does. A wide yorker is a pressing trigger. A slower ball is a pressing trigger. A wide bouncer is a pressing trigger. When a bowler releases the ball, his foot position before release, his shoulder angle, his release moment—these are all triggers. They determine which corridor the ball enters.

I have built a mapping system for cricket akin to football's transition map. I call it the "Delivery Coordinate System". For every ball I measure three coordinates: release point, bounce point, and batsman's contact point. The vector between these three points reveals which corridor the ball took, where the batsman played, and where the fielder stood. Using this system I have found that a spinner's corridor usage differs entirely from a pacer's. A spinner plants the ball on the fourth-stump line and waits for turn; a pacer plants it on the same line and waits for bounce.

Using this coordinate system I analysed a 2026 one-day series and found that when a team's spinners bowled on the fourth-stump line, their economy was 4.2, and when they bowled on the stumps, it was 5.8. That gap does not appear on the scorecard; it appears only on the corridor map.

My contrarian angle is: corridor analysis in cricket can become excessive. I fall into this trap myself. I make so many maps, draw so many vectors, measure so many coordinates—that the actual moment of the match is lost. When a batsman misses a ball in the 88th over and is bowled, that is not merely a corridor failure. It is a composite of mental fatigue, pressure, and match situation. A missed penalty is not just a technical failure; a missed shot in cricket is not just a geometric failure. There is a human stake here—the silence of a crowd, a captain's shoulders dropping, the ache of a team losing a series. That human dimension lies outside geometry.

This is why in 2026 I added a new layer to my analysis method, which I call the "Trap Risk Index". In every preview I add a trap risk section—where I show which corridors contain traps. When a spinner plants the ball on the fourth-stump line and the batsman attempts a sweep, a trap forms—the ball may slide into the stumps, or the batsman may be stumped. That trap does not appear on the scorecard, but it influences the match result.

I have a rule on my blog: every analysis must carry at least three article signatures. A formation or field setting is not merely a shape; it is a hypothesis the game tests. That hypothesis can be right or wrong. The fourth-stump corridor differs on every pitch, in every environment, in every culture. At Mirpur in Dhaka it is a place of spin, at the MCG in Melbourne it is a place of bounce, at Lord's in England it is a place of swing. These differences are cricket's beauty.

I have watched cricket for 47 years. I have seen analysis advance, data arrive, models multiply. But one thing I always remember: data analysts have entered the dressing room, but their conclusions often detach from the actual rhythm of the match. When a bowler is tired, a data model cannot measure it. When a captain changes tactics, a data model cannot predict it. The rhythm of a match is a human thing, beyond geometry.

I mentor two Melbourne analysts. I tell them: build corridor maps, but never forget that the match is a human game. The map is not the match. The map is only a tool.

My takeaway is: In the next match, when you see a spinner planting the ball on the fourth-stump line, ask—was this corridor made for this pitch, or against this pitch? Is the corridor a deliberate decision, or a habit? And most importantly: the person releasing the ball into this corridor—what is he thinking? Because however perfect the corridor map, a human releases the ball.