Swiss Ephemeris Natal Chart Calculations

What Swiss Ephemeris is

The Swiss Ephemeris is a high-precision ephemeris computation library originally developed by Astrodienst (the makers of astro.com). It is built on the JPL Development Ephemeris (currently DE431) produced by NASA’s Jet Propulsion Laboratory, and it reproduces JPL planetary positions with arc-second accuracy — precise to 1/3600 of a degree. It is the calculation engine underneath most professional astrology software.

For NatalChart.AI it is the foundation: every chart, every aspect, every transit, every solar return is computed by Swiss Ephemeris before the AI sees a single byte of it.

Why this matters for AI astrology

Large language models are extraordinarily good at producing plausible-sounding text. They are not good at computing planetary positions. Ask a generic AI for a birth chart on a specific date and time and you may get a coherent-looking layout that does not match the actual sky — the AI is guessing at numbers that should be calculated, not predicted.

NatalChart.AI eliminates that risk by separating concerns:

Astronomy first. Swiss Ephemeris computes where each body actually was, with full geodetic and time-zone awareness.
Symbolism second. The language model receives that calculation as a structured payload and is constrained to only explain placements that exist in it (see Chart-Locked AI Reading).

What NatalChart.AI calculates

Ten classical bodies: Sun, Moon, Mercury, Venus, Mars, Jupiter, Saturn, Uranus, Neptune, Pluto.
Lunar Nodes: True Node (Rahu / North Node).
Major asteroids: Ceres, Pallas, Juno, Vesta.
Sensitive points: Chiron, Lilith (Black Moon), Part of Fortune, Vertex.
Angles: Ascendant, Midheaven (and their opposites IC and Descendant).
Houses: twelve cusps via the Placidus system by default.
Aspects: conjunction, sextile, square, trine, opposition (with mode-specific orbs in synastry).
Fixed stars: 73 named stars with 1.5° conjunction detection (Regulus, Algol, Spica, Sirius and others).

The full input pipeline

Birthplace coordinates are resolved via city search and stored in WGS 84 / EPSG:4326 (latitude / longitude in decimal degrees).
Time zone is determined by the geographic coordinates and the date of birth, using the IANA Time Zone Database — this correctly handles historical DST changes, Soviet-era time-zone shifts, and other one-off rules.
Local birth time is converted to UTC using those timezone rules.
Julian Day for that UTC instant is computed and passed to Swiss Ephemeris.
Swiss Ephemeris returns the longitudes and speeds of every body for that instant.
House cusps are computed from the latitude, local sidereal time and a chosen house system (Placidus by default).
Aspects are derived by comparing every pair of bodies’ longitudes against the canonical aspect angles within their orb.

Each step is open-source code running server-side; nothing is cached at runtime, nothing is approximated, nothing depends on the AI knowing astronomy.

What happens when birth time is unknown

Most chart factors come from the planet positions, which only depend on the date and (loosely) the time of day. Aspects and sphere scores are robust even at noon-fallback precision.

However, the Ascendant, Midheaven and house cusps move about one degree every four minutes — they require the exact birth time. NatalChart.AI marks these as time-sensitive in the reading and suggests rectification or birth-certificate verification when accuracy matters. See Unknown Birth Time Natal Chart.

Frequently asked questions

What is the Swiss Ephemeris?

The Swiss Ephemeris is a high-precision ephemeris computation library originally developed by Astrodienst. It's based on the JPL Development Ephemeris (DE431) from NASA's Jet Propulsion Laboratory and reproduces JPL planetary positions with arc-second accuracy. It's the calculation engine used by most professional astrology software.

Why does astrology software need an ephemeris?

An ephemeris is a table or computation of celestial body positions over time. Without one, software cannot know where the Sun, Moon, planets and asteroids actually were at the moment of someone's birth. Approximations and lookup tables produce small errors that compound for outer planets and historical dates; ephemeris-grade computation is the only reliable way to get correct positions.

Why shouldn't AI calculate planetary positions on its own?

Large language models are trained to predict text, not to compute astronomical positions. Asked for planetary longitudes on a specific date, an LLM will produce numbers that look correct but aren't grounded in any actual ephemeris computation. The result is a chart that looks plausible but doesn't match reality. NatalChart.AI calculates the chart with Swiss Ephemeris first and only then hands the structured data to the AI.

What does arc-second accuracy mean?

An arc-second is 1/3600 of a degree. Swiss Ephemeris reproduces JPL data with this level of precision for the Sun, Moon and planets across thousands of years. For the user, this means the planetary longitudes in your chart are accurate to a tiny fraction of one zodiac degree — well below the orb threshold any astrologer would use for aspects.

What if my birth time isn't exact?

Swiss Ephemeris itself is exact, but the inputs you give it matter. The Sun, Moon and planet aspects are usually robust to a few minutes of birth time error. The Ascendant, Midheaven and house cusps move about one degree every four minutes, so they're sensitive to the exact time. NatalChart.AI uses noon as a fallback if you don't know your exact time, and clearly marks which parts of the reading depend on the time.

What standards does NatalChart.AI use to calculate the chart?

Swiss Ephemeris (planetary positions, lunar nodes, asteroids, special points), the IANA Time Zone Database (historical local-time conversion to UTC), WGS 84 / EPSG:4326 (geodetic coordinates for birthplace), and Placidus house system by default.