The Prime Meridian & India
Greenwich, Ujjain & the Politics of 0°

What is a Prime Meridian?

A prime meridian is a line of longitude designated as 0°, from which all other longitudes are measured east or west. Unlike the equator — which is a natural geographic feature defined by Earth's rotation — a prime meridian is entirely arbitrary. Any line of longitude could be designated 0°. The choice of which line to call zero is a political and scientific decision, not a natural fact.

Before the 19th century, there was no agreement on a single prime meridian. Different countries, astronomers, and cartographers used different reference lines. France used the Paris Meridian. Britain used the Greenwich Meridian. The Dutch used Amsterdam. The Portuguese used Ferro (in the Canary Islands). The Spanish used Cádiz. And India used Ujjain — for over two thousand years.

The adoption of a single world prime meridian was not an inevitable scientific development. It was a political act — one that reflected the balance of naval and imperial power in the late 19th century. Understanding this is essential to understanding why India, with one of the world's most sophisticated astronomical traditions, finds its ancient meridian replaced by a line running through a London suburb.

Ujjain — India's Prime Meridian for 2,000 Years

The city of Ujjain (ancient Avantika or Ujjayini), located in present-day Madhya Pradesh at approximately 75°47'E, 23°11'N, served as India's astronomical prime meridian from at least the 4th century BCE until the adoption of the Greenwich Meridian in the late 19th century. This is not a marginal or obscure fact — it is the foundation of virtually all classical Indian astronomy.

Every major astronomical text of the ancient and medieval periods used Ujjain as their reference meridian. The Surya Siddhanta, the Aryabhatiya, the Brahmasphutasiddhanta, the Siddhanta Shiromani of Bhaskara II — all begin their longitude calculations from Ujjain. When Indian astronomers calculated planetary positions, eclipse predictions, or festival timings, they asked: "How far east or west is this location from Ujjain?" in exactly the way modern navigators ask: "How far east or west is this from Greenwich?"

The choice of Ujjain was not arbitrary. The city sits at a longitude (75°47'E) that, in the ancient Indian geographic worldview, was understood to be the central longitude of the Indian subcontinent. (The actual longitudinal centre of the subcontinent is closer to 80–82°E, but ancient cartographers' understanding of the subcontinent's extent was imprecise.) Ujjain was also a city of immense religious, commercial, and political significance — one of the four sites of the Kumbh Mela, the capital of the Avanti and later Gupta kingdoms, and home to the Mahakaaleshwar Jyotirlinga.

The 1884 International Meridian Conference

The International Meridian Conference was held in Washington, D.C. in October 1884. Twenty-five nations sent delegates. The purpose was explicit: to agree on a single prime meridian for worldwide use, to facilitate navigation, cartography, and the growing international telegraph and railway networks.

The outcome was almost predetermined. Britain, at the height of its imperial power, had the world's largest navy and merchant fleet. The majority of nautical charts and navigation tables already used Greenwich as their reference. Twenty-two nations voted in favour of Greenwich as the prime meridian; San Domingo voted against; Brazil and France abstained. (France would not officially adopt GMT until 1911, stubbornly maintaining Paris Mean Time for 27 years after the conference.)

"The adoption of the meridian of Greenwich as the initial meridian is hereby recommended to the governments here represented, from which longitudes shall be counted in two directions up to 180 degrees."
— Resolution I, International Meridian Conference, 1884

India — under British rule at the time — was represented by British delegates. There was no Indian voice at the conference. The ancient Ujjain meridian, which had served Indian astronomy for two millennia, was not mentioned. The decision that would define global timekeeping for the next 140+ years was made entirely by European and American powers, reflecting the geopolitical reality of 1884.

What India "Lost" — and What It Retained

The framing of "loss" is complicated. The adoption of Greenwich did not erase the Ujjain meridian — it simply made it irrelevant for international navigation and official timekeeping. Indian astronomical traditions did not change overnight. The Ujjain Jantar Mantar continued to function. Regional panchangs continued to use local solar time calculated from traditional references. The tradition of Kaal Nirnay (Marathi almanac), published annually from Pune and followed by millions across Maharashtra and Gujarat, still calculates its astronomical data with reference to the Ujjain tradition.

What India retained — and what is encoded in IST itself — is more subtle. The choice of UTC+5:30 for IST reflects the average longitude of British India (approximately 82°30'E = 5.5 hours east of Greenwich). But 82°30'E is not exactly the Ujjain meridian (75°47'E) — it is significantly further east, chosen because it is mathematically central to the subcontinent's extent. The Ujjain meridian produces a UTC offset of approximately +5:03 — which would have been an awkward timezone. The decision to use UTC+5:30 instead moved the effective reference east by about 7°, placing it near Mirzapur.

The Mirzapur Meridian — A Compromise No One Chose for Its Own Sake

The town of Mirzapur, Uttar Pradesh (82°30'E) has the distinction of being India's official timezone meridian without being particularly significant in any other respect. It is not a major city, not a historical centre, not an astronomical observatory. It is simply the town that happens to sit closest to the meridian of 82°30'E — the mathematical midpoint chosen for IST.

The contrast with Ujjain — a city of extraordinary historical depth, astronomical tradition, and religious significance — could not be more stark. Ujjain was the Mahakaal, the Lord of Time, because the city genuinely had an earned relationship with the measurement and study of time that extended for 2,000 years. Mirzapur is on IST's meridian because of arithmetic.

The Curious Case of Ujjain Solar Time Today

Here is the precise mathematical consequence of replacing the Ujjain meridian with the Mirzapur/IST meridian: Ujjain, sitting at 75°47'E, is 6°43' west of the IST meridian (82°30'E). Each degree of longitude corresponds to 4 minutes of solar time. Therefore, Ujjain's local solar noon occurs approximately 26 minutes 52 seconds after IST noon.

Put another way: when the IST clock reads 12:00:00 noon, the sun at Ujjain has not yet reached its highest point in the sky. The Mahakaaleshwar temple — the temple where Shiva as Lord of Time is worshipped — experiences solar noon at approximately 12:27 IST. The city that was once the centre of Indian time is now, by official measure, 27 minutes "behind" the country it once centred.

This creates an interesting spiritual irony. The Mahakaaleshwar temple's famous Bhasma Aarti — the 4 AM ritual that marks the transition between Brahma Muhurta and the regular day — is timed to IST, not Ujjain solar time. The city where India calculated time for 2,000 years now follows a clock calibrated to a meridian 650 kilometres to the east.

The GMT to UTC Transition — And What It Changed

In 1972, Greenwich Mean Time (GMT) was effectively replaced by Coordinated Universal Time (UTC) as the world's official time standard. The difference is subtle but important: GMT is based on astronomical observations (the mean solar time at the Greenwich meridian), while UTC is based on atomic clocks, adjusted by "leap seconds" to stay within 0.9 seconds of astronomical time.

IST is officially expressed as UTC+5:30 (not GMT+5:30), though for most practical purposes the distinction is invisible — the difference between GMT and UTC is always less than 1 second. India, as a member of the International Telecommunications Union and the International Bureau of Weights and Measures (BIPM), adopted UTC in the same transition. The Indian Naval Hydrographic Charts, Indian Railways, aviation, and financial markets all use UTC as the base reference.

Indian Standard Time is maintained and broadcast by the National Physical Laboratory (NPL) in New Delhi, which keeps a set of caesium atomic clocks — the most accurate timekeepers ever built. NPL broadcasts the IST signal via radio (All India Radio's time signal) and internet time servers (time.nic.in). NPL's atomic clocks are accurate to within a few nanoseconds per day — vastly more precise than anything Aryabhata or Brahmagupta could have imagined, yet built on the same fundamental question they dedicated their lives to answering: what time is it, precisely?

India's Time in a Connected World

The move from Ujjain to Mirzapur, from solar time to atomic time, from ancient panchangs to NPL caesium clocks — each transition reflects India's movement through historical epochs. The Vedic astronomers who first designated Ujjain as their reference meridian were not naive — they chose the city for a reason, embedded time in culture and mathematics with extraordinary precision, and built a tradition that survived for 2,000 years.

The adoption of GMT in 1884 and IST in 1906 were not erasures of that tradition — they were layers added on top of it. India's ancient time traditions did not disappear with colonialism. They persisted in the panchangs, in Rahu Kaal, in the Kumbh Mela's celestially-timed gatherings, in the Jantar Mantar's continued operation, in the cultural memory that makes millions of Indians consult an astrologer before a major decision rather than a clock.

What the prime meridian story ultimately reveals is this: time is never simply a scientific measurement. It is always also a cultural artefact, a political decision, and a marker of power. The line that runs through Greenwich, not Ujjain, is not a verdict on the quality of Indian astronomy — which was extraordinary. It is a consequence of 19th-century British naval supremacy. Understanding this does not require resentment. It simply requires accuracy — which, after all, is what timekeeping is for.