ClockAstronomical guide
Tropical vs Sidereal Planetary Positions
Compare tropical and sidereal zodiac positions, understand ayanamsa, and learn why ClockAstronomical currently shows tropical results only.
Two zodiac calculators can use the same planet and the same instant yet report different signs or degrees. Often neither calculation is broken: the tools are using different zero points.
The central distinction in tropical versus sidereal planetary positions is the reference used for 0° Aries. ClockAstronomical currently uses the tropical system only. It does not calculate a sidereal result or offer an ayanamsa selector.
The short version
- The tropical zodiac fixes 0° Aries to the equinox-based vernal point and divides the ecliptic into twelve equal 30° signs.
- A sidereal zodiac defines its starting point relative to the stars. A chosen ayanamsa specifies the offset between that starting point and the tropical origin for a date.
- Earth’s axial precession causes the equinox-based origin to move relative to the stellar background, so the two systems no longer use the same zero.
- Different sidereal traditions can choose different ayanamsas, so “sidereal” alone is not a complete calculation setting.
The Swiss Ephemeris documentation describes the tropical origin, sidereal zero point, precession, and the range of supported ayanamsas. The International Astronomical Union’s 2006 Resolution B1 is a primary reference for modern precession theory and the astronomical definition of the ecliptic.
What “tropical” means
In the tropical convention, 0° Aries is tied to the March equinox point, not to the visible outline of the constellation Aries. The remaining eleven signs are equal 30° divisions measured from that origin.
That distinction matters because zodiac signs and astronomical constellations are not interchangeable regions. A tropical sign is an equal longitude sector. A constellation is a bounded area of the observed sky. ClockAstronomical shows the first kind.
ClockAstronomical’s tropical planetary positions are also of date: the library transforms the apparent geocentric vectors into true ecliptic/equinox-of-date coordinates before the application converts each longitude to a sign and degree. The result is a browser visualization of tropical zodiac planetary positions, not a catalogue of constellation membership.
What “sidereal” means
A sidereal zodiac aims to keep its origin related to the stellar background. To convert between tropical and sidereal zodiac longitude, software needs an ayanamsa: a dated angular relationship between the two origins. The commonly shown shorthand is:
sidereal longitude = tropical longitude − ayanamsa
That formula is useful for orientation, but production ephemeris software must also be precise about the ecliptic, epoch, precession model, and whether nutation is included. The Swiss Ephemeris programming documentation therefore recommends calculating a configured sidereal position directly instead of casually subtracting a displayed offset.
In Indian astrological terminology, Sayana planetary positions generally refer to tropical positions and Nirayana to sidereal positions. Those words identify a coordinate convention; they do not imply that every practitioner uses the same other settings. A comparison should name the exact ayanamsa, such as Lahiri or another configured choice, rather than saying only “Vedic” or “sidereal.”
Geocentric is a separate choice
Tropical versus sidereal describes the zodiac’s longitude origin. Geocentric versus heliocentric describes the observer or origin of the position vector. They are separate decisions.
ClockAstronomical displays geocentric planetary positions: the direction is calculated from Earth’s center. A Sun-centered orbit diagram instead uses a heliocentric view. As a result, geocentric planet positions can exhibit apparent retrograde motion even though a planet has not reversed direction in its orbit around the Sun.
A local sky map adds another distinction. It normally needs the observer’s latitude and longitude and calculates altitude and azimuth. ClockAstronomical requests no location, so it cannot report visibility, rise and set times, or compass direction. The JPL Horizons manual is a useful reference for how observer location and reference frame change ephemeris output.
What ClockAstronomical calculates today
For every supported UTC instant, ClockAstronomical’s current pipeline is:
- Calculate a light-time- and aberration-corrected geocentric vector for each displayed body with Astronomy Engine.
- Rotate that vector into true ecliptic-of-date coordinates.
- Normalize ecliptic longitude into the interval from 0° to less than 360°.
- Divide the circle into twelve tropical signs and show the sign, degree in sign, total longitude, and direct/retrograde status.
In search language, these results may be called tropical planet positions, western planetary positions, or western astrology planetary positions. The phrases astrology planetary positions and astrological planetary positions are also used for zodiac-labelled coordinates. In ClockAstronomical, all of those labels point to the same limited output: calculated positions only, without houses, aspects, a birth chart, or interpretation.
The word “western” describes the wheel and tropical convention in this release; it is not a claim that all Western astrology uses identical settings. ClockAstronomical has no sidereal/Nirayana mode and no North or South Indian chart renderer.
Why the reported sign can change
Suppose a tropical result lies near the beginning of a sign. Depending on the date and named ayanamsa, a sidereal result may fall in the preceding sign. That does not mean the planet moved between the two calculations. The two zodiacs labelled the same direction from different origins.
The exact difference is not a timeless constant. Precession changes it over long periods, and the chosen ayanamsa changes the sidereal zero. For that reason, this article does not publish a single “conversion number” to reuse for all dates or systems.
A fair comparison checklist
Before comparing ClockAstronomical with another ephemeris, match or record all of the following:
- Instant and time scale. Use the same complete date, time, and UTC conversion. A local civil time entered as UTC represents a different instant.
- Observer. Select the geocenter, not a city, the surface of Earth, or the center of the Sun.
- Zodiac. Select tropical for a direct comparison with ClockAstronomical. If testing a sidereal result, record the exact ayanamsa.
- Reference plane and epoch. Match an ecliptic-of-date output rather than silently comparing it with a fixed J2000 ecliptic.
- Apparent or geometric position. ClockAstronomical’s geocentric direction includes light-time and aberration through its calculation-library call.
- Rounding. ClockAstronomical displays longitude and degree in sign to two decimal places; that formatting is not a 0.01° accuracy claim.
Even with the settings aligned, treat ClockAstronomical’s 0.1° figure as its stated accuracy target for 1900–2100, not as a guarantee. Dates in the wider supported AD 1000–3000 range are labelled Extended / approximate when they fall outside that target interval.
Which guide should you use?
If you want to reproduce a ClockAstronomical result, start with How to Find Planetary Positions by Date and Time. For the meaning of longitude and degree-in-sign, read What Is a Planetary Ephemeris?. Use a separately configured, documented sidereal ephemeris if your question specifically requires Nirayana positions; ClockAstronomical cannot supply that second coordinate system today.
Primary sources and methodology
- Swiss Ephemeris: sidereal ephemerides for astrology for tropical and sidereal zero points, ayanamsa, and precession caveats.
- Swiss Ephemeris programming interface for configured sidereal calculations and ayanamsa handling.
- IAU resolutions, including 2006 Resolution B1 for the modern astronomical precession/ecliptic reference.
- JPL Horizons system manual for observer and reference-frame distinctions.
- Astronomy Engine project documentation for ClockAstronomical’s calculation dependency.