• #LocalsOfMumbai

How do you draw a city that never stops building?

The design of the V9 Mumbai Suburban Rail Network map

A transit map is an argument. It says: here is the most useful way to understand this system. Not the most accurate, not the most complete — the most useful. Every line drawn at a deliberate angle, every station name placed above rather than below, every colour assigned to a corridor is a position taken. The V9 Mumbai Suburban Rail Network map is the result of more than a decade of taking those positions, revising them, and taking them again as the city around them kept changing.

Mumbai's rail network is not one system. It is three overlapping systems that grew up in different eras, follow different logics, and were never quite designed to talk to each other. The original suburban rail — Western, Central, and Harbour Lines — runs mostly north–south, built along the natural geography of the peninsula. The Metro network, expanding rapidly across the city since 2014, runs in every direction, cutting diagonally across that inherited geometry. The Monorail threads through a specific eastern corridor. The Bullet Train corridor arcs northeast toward Ahmedabad. Drawing a single map that holds all of this without collapsing into noise is the fundamental challenge the V9 is trying to answer.

The choice to go semi-geographic

The classical transit map tradition — Harry Beck's London Underground being its most famous expression — solves complexity by abandoning geography. Stations are evenly spaced. Lines run at 45° or 90° angles. The diagram becomes a system of relationships rather than a rendering of space. That approach works beautifully when a network has a clear hierarchy: a set of dominant corridors, a recognisable geometry, a manageable number of lines.

Mumbai's suburban network fits that description reasonably well on its own. Three parallel north–south corridors with a few cross-connections — a schematic can handle that. But as the Metro network has expanded, the purely schematic approach stops working. Metro Line 3 Aqua runs underground from Cuffe Parade in the south, surfaces near CSMT, continues through BKC, and terminates at Aarey Colony near the national park — a corridor that cuts diagonally across the city, intersecting the Western and Harbour Lines at multiple points. Metro Line 7 Red runs along a similar arc further north. These lines don't fit into a right-angle grid without severe distortion of the spatial relationships between them.

The V9 Hybrid addresses this by holding geography loosely rather than abandoning it. Lines follow their approximate compass direction — the Western Line tilts slightly because Virar is northwest of Churchgate, not due north; the Trans-Harbour Line curves east because Panvel sits east of Thane. The result isn't a road map. It can't tell you how far Dahanu Road is from Churchgate in kilometres. But it preserves enough geographic truth that you can read, at a glance, roughly where any station sits in the city — and that spatial sense makes multi-modal journeys far easier to plan.

The grammar of station markers

One of the map's quieter design achievements is its station marker system — the visual vocabulary it uses to distinguish between different kinds of stops. Mumbai has a problem that few transit maps face: the same location, or two locations metres apart, can simultaneously be a suburban rail junction, a Metro interchange, and an Indian Railways terminal. CSMT is all three. Dadar is both a Central and Western Line interchange with a Metro station nearby. Andheri is a Western Line station, a Metro Line 1 station, a Metro Line 7 station, and sits adjacent to the Aqua Line corridor.

The V9 uses a four-tier marker hierarchy. Major stations — the kind that function as terminals, interchanges, or key wayfinding anchors — get a double circle: a larger ring with a smaller filled circle at the centre. Mumbai Local stations use a smaller solid marker, consistent in weight with the line itself. Metro and Mono stations step down another level in visual weight — lighter, less demanding of the eye. Indian Railways stations carry a different marker shape entirely, signalling that you are entering a different system with different ticketing, different speeds, different logic.

This hierarchy teaches you how to read the map before you consciously realise it. The eye learns quickly that bigger markers mean decisions — interchanges, starting points, orientation anchors. Smaller markers are information for when you already know roughly where you're going.

The fast and slow problem

No other major transit map quite faces the problem that Mumbai's suburban network presents. Every line runs two distinct services: fast trains that skip intermediate stations, and slow trains that stop everywhere along the corridor. Whether a given station is served by fast trains matters enormously to commuters — the difference between a fast and slow train from Bandra to Virar is roughly twenty minutes.

The map handles this with a visual weight distinction applied directly to the line itself, with station markers indicating which platforms each service uses. This is a compact solution to what could otherwise require a second map entirely — it keeps the fast/slow information within the spatial layout of the network rather than pushing it into a separate table.

Notably, the original design logic for this distinction was arrived at through iteration and user testing. In the earliest versions of the Mumbai Rail Map, slow trains were shown as dotted lines — the visual convention that was floating on the internet at the time. The design through testing inverted this: continuous lines for fast, lighter weight for slow. The logic is more intuitive because continuous visual weight reads as primary, not as an exception.

Colour as a coding system — and one honest constraint

The suburban rail colours — orange for the Central Line, magenta-pink for the Western Line, green for the Harbour and Trans-Harbour Lines — were not chosen by convention or by committee. They emerged from the original 2013 design, were tested at real stations with real commuters at Dadar Central and CSMT, adjusted for colourblind accessibility (the map has always been tested against protanopia and deuteranopia), and arrived at their current form through that iterative, field-tested process. In that sense they are not just a palette — they are a validated communication system. The V9 carries them forward intact, and they should remain stable for as long as the suburban rail network itself does.

The Metro colours are a more complicated story, and one where the map sits under a constraint it did not choose. Mumbai's Metro lines are officially named after their colours: the Blue Line, the Yellow Line, the Aqua Line, the Red Line, and so on. The map has no choice but to honour those names — using a different colour for the Blue Line would create more confusion than it resolves. The result is a palette that was handed to the map by the naming authorities rather than arrived at through design. Multiple greens (Lines 4, 5, and 10), two reds (Lines 7 and 9), and a colour range that bunches in the cool spectrum in ways that create genuine differentiation challenges, particularly in the densely routed central section of the map — this is not the palette we would have chosen. It is the palette the city gave us, and the map works within it as carefully as it can, using line routing, spatial separation, and label placement to compensate where colour alone is insufficient.

As the Metro network grows and more lines open, this constraint will only become more acute. It is something we continue to negotiate version by version.

The stations that changed everything

No single development tested the map's design more rigorously than the expansion of Metro Line 3 Aqua. Running from Cuffe Parade in the south through Vidhan Bhavan, Churchgate Metro, Marine Lines, Girgaon, CSMT, Masjid Bunder, then north through Gundavali, Marol Naka, MIDC, SEEPZ, Aarey JVLR, and Aarey to Aarey Depot, the Aqua Line cuts through the most cartographically complex part of the entire map.

Each of these stations required label positions that didn't collide with existing suburban line labels placed years earlier. CSMT, already carrying one of the busiest label clusters on the map — it is simultaneously a major suburban station, an Indian Railways terminal, and a Metro station on two separate points of the Aqua Line — required particularly careful negotiation. The southern tip of the peninsula, where Cuffe Parade sits at the map's bottom edge, had been relatively quiet cartographic territory. It is now the origin of a major Metro corridor, which means labelling density at the bottom of the map increased substantially across the last year of updates.

These are not problems with neat solutions. They are negotiations between completeness and legibility, resolved differently at each iteration, always with the same constraint: the map has to be readable by someone standing on a platform with fifteen seconds before their train arrives.

The living map: embedding vs. downloading

The V9 Hybrid is available in two ways, and the distinction between them matters more than it might seem.

The map source files are maintained openly on the Locals of Mumbai GitHub repository at github.com/localsofmumbai. If you download the files from there, you get the map as it was at that moment — a static snapshot. When the next Metro station opens and the map is updated, your downloaded file does not know about it. For archival or print purposes, downloading is appropriate. For anything that needs to stay current — a website, an app, a digital display, a blog post — downloading is the wrong choice.
The right choice is embedding. The map is served live at maps.localsofmumbai.com/en/hybrid.jpg (JPG) and maps.localsofmumbai.com/en/hybrid.pdf (PDF). When you embed using those URLs, you always pull the current version. The embed code is straightforward:

---- <a href="https://localsofmumbai.com/"><img border="0" src="https://maps.localsofmumbai.com/en/hybrid.jpg" alt="Mumbai Rail Map" width="100% auto"></a> ----

Every website and application that uses this embed updated automatically when the Aqua Line's Cuffe Parade extension opened, when Vidhan Bhavan was added, when Girgaon joined the southern corridor. No file management, no re-upload, no stale maps. For a city where new Metro stations open every few months, that is not a minor convenience — it is the only approach that keeps a map honest.

A beginning, not a finished thing

The V9 is the most complete map this project has produced. It is also, in a real sense, only just beginning. Mumbai's Metro network is expanding on a timeline that will add dozens of stations and several entirely new lines over the next five years. Lines 4, 5, 6, and 12 are under construction. The Thane and Navi Mumbai Metro corridors are taking shape. The Trans-Harbour Sea Link will reshape how people think about the eastern side of the network.

Each new line that opens doesn't just add a few stations — it changes the spatial logic of everything around it. It creates new interchange points, makes previously distant areas adjacent, and shifts the weight of the map in ways that require every surrounding label to be reconsidered. The map will get more complex. It will also, with each iteration, become better at describing the city it covers — more truthful, more useful, more legible to the 7 million people who navigate this network every day.

That is what a living map is. Not a document that gets published and archived, but a design that keeps working as long as the city does.
The V9 Mumbai Suburban Rail Network map is available to view and embed at maps.localsofmumbai.com. For the full map library — all four styles, all five languages, print-quality files — visit localsofmumbai.com/downloads.