When selecting the Zodiac System, you are deciding how the 360° circle of the sky is anchored. This is crucial for matching calculations with different cultural traditions:

• Tropical (Scientific/Western): Anchored to the Earth's seasons. 0° Aries always begins at the exact moment of the Vernal (Spring) Equinox, regardless of where the actual stars are. This is the standard in modern astronomy and Western astrology.
• Sidereal (Vedic/Lahiri): Anchored to the fixed stars in the background sky. Because the Earth wobbles on its axis (Precession of the Equinoxes), the Sidereal zodiac slowly drifts away from the Tropical zodiac by about 1° every 72 years. This is the standard in ancient Indian (Vedic) astronomy and astrology.

Which should I use? If you are cross-referencing modern scientific data or Western dates, use Tropical. If you are reverse-engineering an ancient Indian manuscript or Vedic chart, select Sidereal.

While the Vector Array is highly precise, it is long and cumbersome to share. We compress this array into a compact, human-readable string using a Mixed-Radix method where each planet uses a specific mathematical base (radix):

• Fast-Moving Bodies (Sun, Mars, Mercury, Venus): Base 360. Their full 0-359° Ecliptic Longitude is mapped directly (no division).
• The Moon: Base 108. The 360° circle is divided into 108 sections (representing the 27 Nakshatras × 4 Padas). Each unit is exactly 3.333...° (3° 20').
• Slow-Moving Bodies (Jupiter, Saturn, Uranus, Neptune): Base 12. The 360° circle is divided into 12 sections (representing the 12 Zodiac signs). Each unit is exactly 30°.

Decoding the Tuple: The algorithm generates an array for the 9 bodies using these specific bases: [360, 108, 360, 360, 12, 12, 12, 12, 12] in the order [Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn, Uranus, Neptune].

This mixed tuple is mathematically transformed into a massive decimal integer and then encoded into NewBase60 (bx60) characters, creating a short ID like EDIhRA: 1wyn8-yFwDw-Lw4U8-wU2M7-9yzBe-j.

Base-36 Decoding Table (For Versioning)

NewBase60 Decoding Table

Important Decoder Note: Because the ID (like 1wyn8) is a NewBase60 compression of a single unified integer, the letters do NOT map 1-to-1 to specific planets. To decode it, you must convert the entire NewBase60 string back into a standard decimal integer, and then repeatedly apply modulo division using the radix array [360, 108, 360, 360, 12, 12, 12, 12, 12] in reverse order to extract each planet's position. The character after the last hyphen (e.g. -j) is a modulo-60 checksum.

EDI has vast potential across multiple sectors due to its absolute independence from human calendars:

• Historical & Archaeological Data: Standardizing timestamps across ancient texts (removing Julian/Gregorian calendar conversion errors and historical dating gaps).
• Space & Interplanetary Travel: Serving as a universal timestamp independent of Earth's rotation, seasons, or leap years, vital for coordinating planetary missions.
• Cryptography & Blockchain: Providing a verifiable, celestial hash-seed for decentralized systems, ensuring completely immutable timestamping.
• Astrological & Scientific Indexing: Allowing researchers to instantly catalog and search for exact celestial configurations without needing to convert dates.

EDI is designed not just as a web tool, but as a universal backend service. We expose a fully documented REST API so you can programmatically generate EDIs in your own software, historical databases, or blockchain projects.

View the live API Documentation (Swagger UI) to explore endpoints like /api/v1/calculate, /api/v1/find_date, and /api/v1/decode.