Hubbry Logo
Julian dayJulian dayMain
Open search
Julian day
Community hub
Julian day
logo
7 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
Julian day
Julian day
Julian day
View on Wikipedia
from Wikipedia

The Julian day is a continuous count of days from the beginning of the Julian period; it is used primarily by astronomers, and in software for easily calculating elapsed days between two events (e.g., food production date and sell by date).[1]

The Julian period is a chronological interval of 7980 years, derived from three multi-year cycles: the Indiction, Solar, and Lunar cycles. The last year that was simultaneously the beginning of all three cycles was 4713 BC (−4712),[2] so that is year 1 of the current Julian period, making AD 2025 year 6738 of that Period. The next Julian Period begins in the year AD 3268. Historians used the period to identify Julian calendar years within which an event occurred when no such year was given in the historical record, or when the year given by previous historians was incorrect.[3]

The Julian day number (JDN) has the same epoch as the Julian period, but counts the number of days since the epoch rather than the number of years since then. Specifically, Julian day number 0 is assigned to the day starting at noon Universal Time on Monday, January 1, 4713 BC, proleptic Julian calendar (November 24, 4714 BC, in the proleptic Gregorian calendar).[4][5][6][a] For example, the Julian day number for the day starting at 12:00 UT (noon) on January 1, 2000, was 2451545.[7]

The Julian date (JD) of any instant is the Julian day number plus the fraction of a day since the preceding noon in Universal Time. Julian dates are expressed as a Julian day number with a decimal fraction added.[8] For example, the Julian Date for 00:30:00.0 UT January 1, 2013, is 2456293.520833.[9] This article was loaded at 2025-11-02 10:43:17 (UTC) – expressed as a Julian date this is 2460981.9467245.

Terminology

[edit]

The term Julian date may also refer, outside of astronomy, to the day-of-year number (more properly, the ordinal date) in the Gregorian calendar, especially in computer programming, the military and the food industry,[10] or it may refer to dates in the Julian calendar. For example, if a given "Julian date" is "October 5, 1582", this means that date in the Julian calendar (which was October 15, 1582, in the Gregorian calendar – the date it was first established). Without an astronomical or historical context, a "Julian date" given as "36" most likely means the 36th day of a given Gregorian year, namely February 5. Other possible meanings of a "Julian date" of "36" include an astronomical Julian Day Number, or the year AD 36 in the Julian calendar, or a duration of 36 astronomical Julian years. This is why the terms "ordinal date" or "day-of-year" are preferred. In contexts where a "Julian date" means simply an ordinal date, calendars of a Gregorian year with formatting for ordinal dates are often called "Julian calendars",[10] but this could also mean that the calendars are of years in the Julian calendar system.

Historically, Julian dates were recorded relative to Greenwich Mean Time (GMT) (later, Ephemeris Time), but since 1997 the International Astronomical Union has recommended that Julian dates be specified in Terrestrial Time.[11] Seidelmann indicates that Julian dates may be used with International Atomic Time (TAI), Terrestrial Time (TT), Barycentric Coordinate Time (TCB), or Coordinated Universal Time (UTC) and that the scale should be indicated when the difference is significant.[12] The fraction of the day is found by converting the number of hours, minutes, and seconds after noon into the equivalent decimal fraction. Time intervals calculated from differences of Julian Dates specified in non-uniform time scales, such as UTC, may need to be corrected for changes in time scales (e.g. leap seconds).[8]

Variants

[edit]

Because the starting point or reference epoch is so long ago, numbers in the Julian day can be quite large and cumbersome. A more recent starting point is sometimes used, for instance by dropping the leading digits, in order to fit into limited computer memory with an adequate amount of precision. In the following table, times are given in 24-hour notation.

In the table below, Epoch refers to the point in time used to set the origin (usually zero, but (1) where explicitly indicated) of the alternative convention being discussed in that row. The date given is a Gregorian calendar date unless otherwise specified. JD stands for Julian Date. 0h is 00:00 midnight, 12h is 12:00 noon, UT unless otherwise specified. Current value is at 10:43, Sunday, November 2, 2025 (UTC) and may be cached. [refresh]

Name Epoch Calculation Current value Notes
Julian date 12:00 January 1, 4713 BC proleptic Julian calendar JD 2460981.94653
Reduced JD 12:00 November 16, 1858 JD − 2400000 60981.94653 [13][14]
Modified JD 0:00 November 17, 1858 JD − 2400000.5 60981.44653 Introduced by SAO in 1957
Truncated JD 0:00 May 24, 1968 floor(JD − 2440000.5) 20981 Introduced by NASA in 1979
Dublin JD 12:00 December 31, 1899 JD − 2415020 45961.94653 Introduced by the IAU in 1955
CNES JD 0:00 January 1, 1950 JD − 2433282.5 27699.44653 Introduced by the CNES[15]
CCSDS JD 0:00 January 1, 1958 JD − 2436204.5 24777.44653 Introduced by the CCSDS[15]
Modified JD2000 (MJD2000) 0:00 January 1, 2000 JD - 2451544.5 9437.44653 Introduced by ESA[16]
Lilian date day 1 = October 15, 1582[b] floor (JD − 2299159.5) 161822 Count of days of the Gregorian calendar
Rata Die day 1 = January 1, 1[b] proleptic Gregorian calendar floor (JD − 1721424.5) 739557 Count of days of the Common Era
Mars Sol Date 12:00 December 29, 1873 (JD − 2405522)/1.02749 53976.07671 Count of Martian days
Unix time 0:00 January 1, 1970 (JD − 2440587.5) × 86400 1762080197 Count of seconds,[17] excluding leap seconds
JavaScript Date 0:00 January 1, 1970 (JD − 2440587.5) × 86400000 1762080196997 Count of milliseconds,[18] excluding leap seconds
EXT4 File Timestamps 0:00 January 1, 1970 (JD − 2440587.5) × 86400000000000 1.7620801969968×10+18 Count of nanoseconds,[19] excluding leap seconds
.NET DateTime 0:00 January 1, 1 proleptic Gregorian calendar (JD − 1721425.5) × 864000000000 638976769969968000 Count of 100-nanosecond ticks, excluding ticks attributable to leap seconds[20]
  • The Modified Julian Date (MJD) was introduced by the Smithsonian Astrophysical Observatory in 1957 to record the orbit of Sputnik via an IBM 704 (36-bit machine) and using only 18 bits until August 7, 2576. MJD is the epoch of VAX/VMS and its successor OpenVMS, using 63-bit date/time, which allows times to be stored up to July 31, 31086, 02:48:05.47.[21] The MJD has a starting point of midnight on November 17, 1858, and is computed by MJD = JD − 2400000.5 [22]
  • The Truncated Julian Day (TJD) was introduced by NASA/Goddard in 1979 as part of a parallel grouped binary time code (PB-5) "designed specifically, although not exclusively, for spacecraft applications". TJD was a 4-digit day count from MJD 40000, which was May 24, 1968, represented as a 14-bit binary number. Since this code was limited to four digits, TJD recycled to zero on MJD 50000, or October 10, 1995, "which gives a long ambiguity period of 27.4 years". (NASA codes PB-1–PB-4 used a 3-digit day-of-year count.) Only whole days are represented. Time of day is expressed by a count of seconds of a day, plus optional milliseconds, microseconds and nanoseconds in separate fields. Later PB-5J was introduced which increased the TJD field to 16 bits, allowing values up to 65535, which will occur in the year 2147. There are five digits recorded after TJD 9999.[23][24]
  • The Dublin Julian Date (DJD) is the number of days that has elapsed since the epoch of the solar and lunar ephemerides used from 1900 through 1983, Newcomb's Tables of the Sun and Ernest W. Brown's Tables of the Motion of the Moon (1919). This epoch was noon UT on January 0, 1900, which is the same as noon UT on December 31, 1899. The DJD was defined by the International Astronomical Union at their meeting in Dublin, Ireland, in 1955.[25]
  • The Lilian day number is a count of days of the Gregorian calendar and not defined relative to the Julian Date. It is an integer applied to a whole day; day 1 was October 15, 1582, which was the day the Gregorian calendar went into effect. The original paper defining it makes no mention of the time zone, and no mention of time-of-day.[26] It was named for Aloysius Lilius, the principal author of the Gregorian calendar.[27]
  • Rata Die is a system used in Rexx, Go and Python.[28] Some implementations or options use Universal Time, others use local time. Day 1 is January 1, 1, that is, the first day of the Christian or Common Era in the proleptic Gregorian calendar.[29] In Rexx, January 1 is Day 0.[30]
  • The Heliocentric Julian Day (HJD) is the same as the Julian day, but adjusted to the frame of reference of the Sun, and thus can differ from the Julian day by as much as 8.3 minutes (498 seconds), that being the time it takes light to reach Earth from the Sun.[c]

History

[edit]

Julian Period

[edit]

The Julian day number is based on the Julian Period proposed by Joseph Scaliger, a classical scholar, in 1583 (one year after the Gregorian calendar reform) as it is the product of three calendar cycles used with the Julian calendar:

28 (solar cycle) × 19 (lunar cycle) × 15 (indiction cycle) = 7980 years

Its epoch occurs when all three cycles (if they are continued backward far enough) were in their first year together. Years of the Julian Period are counted from this year, 4713 BC, as year 1, which was chosen to be before any historical record.[31]

Scaliger corrected chronology by assigning each year a tricyclic "character", three numbers indicating that year's position in the 28-year solar cycle, the 19-year lunar cycle, and the 15-year indiction cycle. One or more of these numbers often appeared in the historical record alongside other pertinent facts without any mention of the Julian calendar year. The character of every year in the historical record was unique – it could only belong to one year in the 7980-year Julian Period. Scaliger determined that 1 BC or year 0 was Julian Period (JP) 4713. He knew that 1 BC or year 0 had the character 9 of the solar cycle, 1 of the lunar cycle, and 3 of the indiction cycle. By inspecting a 532-year Paschal cycle with 19 solar cycles (each of 28 years, each year numbered 1–28) and 28 lunar cycles (each of 19 years, each year numbered 1–19), he determined that the first two numbers, 9 and 1, occurred at its year 457. He then calculated via remainder division that he needed to add eight 532-year Paschal cycles totaling 4256 years before the cycle containing 1 BC or year 0 in order for its year 457 to be indiction 3. The sum 4256 + 457 was thus JP 4713.[32]

A formula for determining the year of the Julian Period given its character involving three four-digit numbers was published by Jacques de Billy in 1665 in the Philosophical Transactions of the Royal Society (its first year).[33] John F. W. Herschel gave the same formula using slightly different wording in his 1849 Outlines of Astronomy.[34]

Multiply the Solar Cycle by 4845, and the Lunar, by 4200, and that of the Indiction, by 6916. Then divide the Sum of the products by 7980, which is the Julian Period: The Remainder of the Division, without regard to the Quotient, shall be the year enquired after.

— Jacques de Billy

Carl Friedrich Gauss introduced the modulo operation in 1801, restating de Billy's formula as:

Julian Period year = (6916a + 4200b + 4845c) MOD 15×19×28

where a is the year of the indiction cycle, b of the lunar cycle, and c of the solar cycle.[35][36]

John Collins described the details of how these three numbers were calculated in 1666, using many trials.[37] A summary of Collin's description is in a footnote.[38] Reese, Everett and Craun reduced the dividends in the Try column from 285, 420, 532 to 5, 2, 7 and changed remainder to modulo, but apparently still required many trials.[39]

The specific cycles used by Scaliger to form his tricyclic Julian Period were, first, the indiction cycle with a first year of 313.[d][40] Then he chose the dominant 19-year Alexandrian lunar cycle with a first year of 285, the Era of Martyrs and the Diocletian Era epoch,[41] or a first year of 532 according to Dionysius Exiguus.[42] Finally, Scaliger chose the post-Bedan solar cycle with a first year of 776, when its first quadrennium of concurrents, 1 2 3 4, began in sequence.[e][43][44][45] Although not their intended use, the equations of de Billy or Gauss can be used to determined the first year of any 15-, 19-, and 28-year tricyclic period given any first years of their cycles. For those of the Julian Period, the result is AD 3268, because both remainder and modulo usually return the lowest positive result. Thus 7980 years must be subtracted from it to yield the first year of the present Julian Period, −4712 or 4713 BC, when all three of its sub-cycles are in their first years.

Scaliger got the idea of using a tricyclic period from "the Greeks of Constantinople" as Herschel stated in his quotation below in Julian day numbers.[46] Specifically, the monk and priest Georgios wrote in 638/39 that the Byzantine year 6149 AM (640/41) had indiction 14, lunar cycle 12, and solar cycle 17, which places the first year of the Byzantine Era in 5509/08 BC, the Byzantine Creation.[47] Dionysius Exiguus called the Byzantine lunar cycle his "lunar cycle" in argumentum 6, in contrast with the Alexandrian lunar cycle which he called his "nineteen-year cycle" in argumentum 5.[42]

Although many references say that the Julian in "Julian Period" refers to Scaliger's father, Julius Scaliger, at the beginning of Book V of his Opus de Emendatione Temporum ("Work on the Emendation of Time") he states, "Iulianam vocauimus: quia ad annum Iulianum accomodata",[48][49] which Reese, Everett and Craun translate as "We have termed it Julian because it fits the Julian year".[39] Thus Julian refers to the Julian calendar.

Julian day numbers

[edit]

Julian days were first used by Ludwig Ideler for the first days of the Nabonassar and Christian eras in his 1825 Handbuch der mathematischen und technischen Chronologie.[50][51] John F. W. Herschel then developed them for astronomical use in his 1849 Outlines of Astronomy, after acknowledging that Ideler was his guide.[52]

The period thus arising of 7980 Julian years, is called the Julian period, and it has been found so useful, that the most competent authorities have not hesitated to declare that, through its employment, light and order were first introduced into chronology.[53] We owe its invention or revival to Joseph Scaliger, who is said to have received it from the Greeks of Constantinople. The first year of the current Julian period, or that of which the number in each of the three subordinate cycles is 1, was the year 4713 BC, and the noon of January 1 of that year, for the meridian of Alexandria, is the chronological epoch, to which all historical eras are most readily and intelligibly referred, by computing the number of integer days intervening between that epoch and the noon (for Alexandria) of the day, which is reckoned to be the first of the particular era in question. The meridian of Alexandria is chosen as that to which Ptolemy refers the commencement of the era of Nabonassar, the basis of all his calculations.[46]

At least one mathematical astronomer adopted Herschel's "days of the Julian period" immediately. Benjamin Peirce of Harvard University used over 2,800 Julian days in his Tables of the Moon, begun in 1849 but not published until 1853, to calculate the lunar ephemerides in the new American Ephemeris and Nautical Almanac from 1855 to 1888. The days are specified for "Washington mean noon", with Greenwich defined as 18h 51m 48s west of Washington (282°57′W, or Washington 77°3′W of Greenwich). A table with 197 Julian days ("Date in Mean Solar Days", one per century mostly) was included for the years –4713 to 2000 with no year 0, thus "–" means BC, including decimal fractions for hours, minutes, and seconds.[54] The same table appears in Tables of Mercury by Joseph Winlock, without any other Julian days.[55]

The national ephemerides started to include a multi-year table of Julian days, under various names, for either every year or every leap year beginning with the French Connaissance des Temps in 1870 for 2,620 years, increasing in 1899 to 3,000 years.[56] The British Nautical Almanac began in 1879 with 2,000 years.[57] The Berliner Astronomisches Jahrbuch began in 1899 with 2,000 years.[58] The American Ephemeris was the last to add a multi-year table, in 1925 with 2,000 years.[59] However, it was the first to include any mention of Julian days with one for the year of issue beginning in 1855, as well as later scattered sections with many days in the year of issue. It was also the first to use the name "Julian day number" in 1918. The Nautical Almanac began in 1866 to include a Julian day for every day in the year of issue. The Connaissance des Temps began in 1871 to include a Julian day for every day in the year of issue.

The French mathematician and astronomer Pierre-Simon Laplace first expressed the time of day as a decimal fraction added to calendar dates in his book, Traité de Mécanique Céleste, in 1823.[60] Other astronomers added fractions of the day to the Julian day number to create Julian Dates, which are typically used by astronomers to date astronomical observations, thus eliminating the complications resulting from using standard calendar periods like eras, years, or months. They were first introduced into variable star work in 1860 by the English astronomer Norman Pogson, which he stated was at the suggestion of John Herschel.[61] They were popularized for variable stars by Edward Charles Pickering, of the Harvard College Observatory, in 1890.[62]

Julian days begin at noon because when Herschel recommended them, the astronomical day began at noon. The astronomical day had begun at noon ever since Ptolemy chose to begin the days for his astronomical observations at noon. He chose noon because the transit of the Sun across the observer's meridian occurs at the same apparent time every day of the year, unlike sunrise or sunset, which vary by several hours. Midnight was not even considered because it could not be accurately determined using water clocks. Nevertheless, he double-dated most nighttime observations with both Egyptian days beginning at sunrise and Babylonian days beginning at sunset.[63] Medieval Muslim astronomers used days beginning at sunset, so astronomical days beginning at noon did produce a single date for an entire night. Later medieval European astronomers used Roman days beginning at midnight so astronomical days beginning at noon also allow observations during an entire night to use a single date. When all astronomers decided to start their astronomical days at midnight to conform to the beginning of the civil day, on January 1, 1925, it was decided to keep Julian days continuous with previous practice, beginning at noon.

During this period, usage of Julian day numbers as a neutral intermediary when converting a date in one calendar into a date in another calendar also occurred. An isolated use was by Ebenezer Burgess in his 1860 translation of the Surya Siddhanta wherein he stated that the beginning of the Kali Yuga era occurred at midnight at the meridian of Ujjain at the end of the 588,465th day and the beginning of the 588,466th day (civil reckoning) of the Julian Period, or between February 17 and 18 JP 1612 or 3102 BC.[64][65] Robert Schram was notable beginning with his 1882 Hilfstafeln für Chronologie.[66] Here he used about 5,370 "days of the Julian Period". He greatly expanded his usage of Julian days in his 1908 Kalendariographische und Chronologische Tafeln containing over 530,000 Julian days, one for the zeroth day of every month over thousands of years in many calendars. He included over 25,000 negative Julian days, given in a positive form by adding 10,000,000 to each. He called them "day of the Julian Period", "Julian day", or simply "day" in his discussion, but no name was used in the tables.[67] Continuing this tradition, in his book "Mapping Time: The Calendar and Its History" British physics educator and programmer Edward Graham Richards uses Julian day numbers to convert dates from one calendar into another using algorithms rather than tables.[68]

Julian day number calculation

[edit]

The Julian day number can be calculated using the following formulas (integer division rounding towards zero is used exclusively, that is, positive values are rounded down and negative values are rounded up):[f]

The months January to December are numbered 1 to 12. For the year, astronomical year numbering is used, thus 1 BC is 0, 2 BC is −1, and 4713 BC is −4712. JDN is the Julian Day Number. Use the previous day of the month if trying to find the JDN of an instant before midday UT.

Converting Gregorian calendar date to Julian day number

[edit]

The algorithm is valid for all (possibly proleptic) Gregorian calendar dates after November 23, −4713. Divisions are integer divisions towards zero; fractional parts are ignored.[69]

Converting Julian calendar date to Julian day number

[edit]

The algorithm[70] is valid for all (possibly proleptic) Julian calendar years ≥ −4712, that is, for all JDN ≥ 0. Divisions are integer divisions, fractional parts are ignored.

Finding Julian date given Julian day number and time of day

[edit]

For the full Julian Date of a moment after 12:00 UT one can use the following. Divisions are real numbers.

So, for example, January 1, 2000, at 18:00:00 UT corresponds to JD = 2451545.25 and January 1, 2000, at 6:00:00 UT corresponds to JD = 2451544.75.

Finding day of week given Julian day number

[edit]

Because a Julian day starts at noon while a civil day starts at midnight, the Julian day number needs to be adjusted to find the day of week: for a point in time in a given Julian day after midnight UT and before 12:00 UT, add 1 or use the JDN of the next afternoon.

The US day of the week W1 (for an afternoon or evening UT) can be determined from the Julian Day Number J with the expression:

W1 = mod(J + 1, 7)[71]
W1 0 1 2 3 4 5 6
Day of the week Sun Mon Tue Wed Thu Fri Sat

If the moment in time is after midnight UT (and before 12:00 UT), then one is already in the next day of the week.

The ISO day of the week W0 can be determined from the Julian Day Number J with the expression:

W0 = mod (J, 7) + 1
W0 1 2 3 4 5 6 7
Day of the week Mon Tue Wed Thu Fri Sat Sun

Julian or Gregorian calendar from Julian day number

[edit]

This is an algorithm by Edward Graham Richards to convert a Julian Day Number, J, to a date in the Gregorian calendar (proleptic, when applicable). Richards states the algorithm is valid for Julian day numbers greater than or equal to 0.[72][73] All variables are integer values, and the notation "a div b" indicates integer division, and "mod(a,b)" denotes the modulus operator.

Algorithm parameters for Gregorian calendar
variable value variable value
y 4716 v 3
j 1401 u 5
m 2 s 153
n 12 w 2
r 4 B 274277
p 1461 C −38

For Julian calendar:

  1. f = J + j

For Gregorian calendar:

  1. f = J + j + (((4 × J + B) div 146097) × 3) div 4 + C

For Julian or Gregorian, continue:

  1. e = r × f + v
  2. g = mod(e, p) div r
  3. h = u × g + w
  4. D = (mod(h, s)) div u + 1
  5. M = mod(h div s + m, n) + 1
  6. Y = (e div p) - y + (n + m - M) div n

D, M, and Y are the numbers of the day, month, and year respectively for the afternoon at the beginning of the given Julian day.

Julian Period from indiction, Metonic and solar cycles

[edit]

Let Y be the year BC or AD and i, m, and s respectively its positions in the indiction, Metonic and solar cycles. Divide 6916i + 4200m + 4845s by 7980 and call the remainder r.

If r>4713, Y = (r − 4713) and is a year AD.
If r<4714, Y = (4714 − r) and is a year BC.

Example

i = 8, m = 2, s = 8. What is the year?

(6916 × 8) = 55328; (4200 × 2) = 8400: (4845 × 8) = 38760. 55328 + 8400 + 38760 = 102488.
102488/7980 = 12 remainder 6728.
Y = (6728 − 4713) = AD 2015.[74]

Julian date calculation

[edit]

As stated above, the Julian date (JD) of any instant is the Julian day number for the preceding noon in Universal Time plus the fraction of the day since that instant. Ordinarily calculating the fractional portion of the JD is straightforward; the number of seconds that have elapsed in the day divided by the number of seconds in a day, 86,400. But if the UTC timescale is being used, a day containing a positive leap second contains 86,401 seconds (or in the unlikely event of a negative leap second, 86,399 seconds). One authoritative source, the Standards of Fundamental Astronomy (SOFA), deals with this issue by treating days containing a leap second as having a different length (86,401 or 86,399 seconds, as required). SOFA refers to the result of such a calculation as "quasi-JD".[75]

See also

[edit]
  • Barycentric Julian Date – Julian date corrected for the barycenter of the Solar System
  • Dual dating – Date given in two different calendars
  • Decimal time – Representation of the time of day using decimally related units
  • Epoch (astronomy) – Moment in time used as a reference point in astronomy
  • Epoch (reference date) – Reference point from which time is measured
  • Era – Span of time defined for the purposes of chronology or historiography
  • J2000 – the epoch that starts on JD 2451545.0 (TT), the standard epoch used in astronomy since 1984
  • Julian year (astronomy) – Interval of exactly 365.25 Earth days
  • Julian year (calendar) – A year in the Julian calendar
  • Lunation Number – First lunar phase, the definition varies
  • Ordinal date – Date written as number of days since first day of year
  • Time – Continuous progression from past to future
  • Time standard – Specification for measuring time
  • Zeller's congruence – Algorithm to calculate the day of the week

Notes

[edit]

References

[edit]

Sources

[edit]
[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

Julian day

View on Grokipedia
from Grokipedia
The Julian day, more precisely termed the Julian Date (JD), is a continuous count of days and fractions thereof elapsed since noon on January 1, 4713 BC in the , providing a simple, unambiguous numerical timescale for chronological calculations. This system begins with Julian Day Number 0 at that epoch and increments by one for each subsequent day, allowing astronomers to express any date as a single without regard to months, years, or irregularities. The Julian Period of 7,980 years, aligning the 15-year Indiction cycle, the 28-year , and the 19-year Metonic lunar cycle, was introduced in 1583 by the French scholar to resolve ambiguities in historical and astronomical dating. Scaliger selected the starting as the last time these cycles coincided before the Christian era, ensuring a neutral reference point that avoids negative dates and facilitates computations across eras. In 1849, astronomer adapted this for the Julian Day Number system in his Outlines of Astronomy. In modern usage, the Julian day remains essential in astronomy for tasks such as , calculations, and observations, where precise timing over long intervals is required; it is often paired with the Modified Julian Date (MJD), which shifts the zero point to midnight on , 1858, by subtracting 2,400,000.5 from the JD for computational convenience. The system's adoption by institutions like underscores its reliability for space missions and geophysical applications, though it requires conversion algorithms to interface with civil calendars like the Gregorian.

Definition and Terminology

Julian Day Number

The Julian Day Number (JDN) is the integer assigned to each whole day in a continuous count of days, beginning with JDN 0 for the day starting at noon (UT) on January 1, 4713 BCE, according to the . This epoch marks the zero point from which all subsequent days are enumerated sequentially, providing a uniform timescale independent of month lengths, , or calendar transitions. Unlike traditional calendar systems that reset or adjust periodically, the JDN employs a straightforward, non-year-based progression to eliminate discontinuities, enabling seamless chronological calculations across eras and cultures. This continuous integer scale simplifies astronomical computations, historical dating, and software implementations by treating time as an unbroken sequence of days. The epoch was selected by in 1583 as the commencement of the Julian Period, a grand cycle of 7980 Julian years representing the of three key ancient cycles: the 28-year (governing weekday patterns), the 19-year Metonic lunar cycle (aligning lunar phases with solar years), and the 15-year indiction cycle (used for Roman taxation and administrative dating). By anchoring the count to this convergence point preceding , the system encompasses biblical events, , and prehistoric chronologies without requiring adjustments for cycle overlaps. An illustrative example is JDN 2451545, which denotes the day beginning at noon UT on , 2000 CE. The Julian Day Number serves as the foundational integer component of the broader Julian Date system.

Julian Date

The Julian Date (JD) is an extension of the Julian Day Number that incorporates a fractional component to precisely represent time within a day, expressed as JD = integer Julian Day Number + fraction of the day since noon Universal Time (UT). The fraction ranges from 0.0 at noon UT to 1.0 just before the next noon, with 0.5 corresponding to UT. This structure allows for continuous timekeeping in astronomical computations, where the day boundary at noon UT aligns with traditional practices rather than the midnight start of civil calendars. Standard notation places the decimal point between the day and the ; for example, JD 2451545.0 marks noon UT on January 1, 2000, while JD 2451545.5 indicates the midnight UT twelve hours later. The fractional part is derived by dividing the UT hours past noon by 24; local times require adjustment by the offset to UT first. For instance, 10:00 AM local time in a zone 5 hours behind UT (such as Eastern Standard Time) equates to 3:00 PM UT, or 3 hours after noon, giving a of 3/24 = 0.125.

History

The Julian Period

The Julian Period was devised by the French philologist and historian in 1583 as a tool for precise chronology. Named in honor of his father, the Italian scholar , it represented an innovative attempt to unify disparate historical dating systems prevalent in ancient records. The period encompasses a cycle of 7,980 years, calculated as the of three established calendrical cycles: the 28-year (accounting for the repetition of weekdays in the ), the 19-year Metonic lunar cycle (aligning solar and lunar calendars), and the 15-year indiction cycle (a Roman fiscal and administrative reckoning). This combination ensured that the full period would repeat without overlap, providing a robust framework for long-term dating. The cycles' yields exactly 7,980 years because 28, 19, and 15 share no common factors beyond 1 in pairwise combinations relevant to their periodicities. Scaliger set the commencement of the Julian Period at January 1, 4713 BCE, in the , precisely because this date coincided with the simultaneous start of all three cycles—a rare alignment that had not occurred since and would not again for . By anchoring the period to this epoch, Scaliger created a continuous, uninterrupted timeline extending backward and forward, free from the disruptions caused by intercalary adjustments, calendar reforms, or regional variations in ancient chronologies. The primary purpose of the Julian Period was to enable scholars to calculate exact intervals between historical events drawn from diverse sources, such as Roman annals, Greek histories, or biblical timelines, without the confounding effects of calendar irregularities like omitted or shifting year beginnings. This system facilitated comparative across civilizations, proving invaluable for reconstructing timelines in classical studies. In the , the Julian Period was adapted by astronomers into a day-counting scheme known as the Julian Day Number for precise celestial computations.

Development of Julian Day Numbers

In 1849, British astronomer Sir John F. W. Herschel proposed the use of a continuous count of days from the epoch of the Julian Period—a chronological cycle of 7980 years devised by Joseph Justus Scaliger in 1583—to streamline astronomical computations that spanned multiple calendars and eras. This innovation, detailed in Herschel's seminal work Outlines of Astronomy, extended Scaliger's cyclical framework into a practical linear numbering system starting from noon on January 1, 4713 BC (Julian calendar), allowing astronomers to reference dates as simple integers without regard to month or year boundaries. The gained traction among astronomers in the late , particularly through its integration into key publications that promoted standardization in ephemerides and observational records. Early applications focused on compiling ephemerides for solar bodies, where the uniform day count proved invaluable for interpolating orbits and predicting phenomena like eclipses or conjunctions without the complications of varying reforms. By the mid-20th century, the Julian Day Number had become a of astronomical practice. A significant milestone came in with its formal endorsement as a standard reference in the Explanatory Supplement to the Astronomical Almanac, published by the and Her Majesty's Nautical Almanac Office, which provided detailed algorithms and tables for its computation and application in modern observations. This adoption solidified its role in facilitating international collaboration and computational efficiency in astronomy.

Variants

Modified Julian Day

The Modified Julian Day (MJD) is a variant of the Julian Day designed for computational convenience in modern astronomy, defined by the formula MJD=JD−2400000.5\mathrm{MJD} = \mathrm{JD} - 2400000.5, where JD is the standard Julian Day. This adjustment shifts the reference epoch from noon on January 1, 4713 BCE (Julian calendar proleptic) to midnight on November 17, 1858, when MJD equals zero. By starting at midnight and subtracting a constant value, the MJD eliminates the integer part of the Julian Date that accumulates over millennia, resulting in a more compact numbering system. The primary purpose of the MJD is to simplify handling of dates in the 20th and 21st centuries, where standard Julian Days exceed 2,400,000, requiring six-digit prefixes that complicate data storage and processing in computing environments. This reduction in numerical magnitude facilitates easier arithmetic operations and reduces the risk of overflow in early computational systems, while maintaining the continuous day-count principle of the Julian Day. The MJD has been widely adopted in space science for timestamping observations and mission events, particularly by organizations such as NASA and the European Space Agency (ESA). For instance, NASA's Jet Propulsion Laboratory uses MJD in orbital mechanics calculations, and ESA employs it in satellite data processing for missions like XMM-Newton. A representative conversion is the J2000.0 epoch, which corresponds to JD 2451545.0 and thus MJD 51544.5 at noon on January 1, 2000.

Other Variants

The Truncated Julian Day (TJD) is a variant defined as TJD = JD - 2440000.5, with its at midnight UT on May 24, 1968, introduced by in 1979 for spacecraft operations and space tracking applications. The Reduced Julian Day (RJD) subtracts 2400000 from the standard JD, setting its at noon UT on November 16, 1858, and is employed in certain astronomical ephemerides and star catalogs to simplify numerical computations by reducing large day counts. The Darian Julian Day represents a non-standard of the Julian day system for Martian timekeeping in science fiction and contexts, where dates are computed from the standard JD relative to a defined (such as the 1609 Martian vernal ) and intercalation rules for sol-based years of 668 or 669 sols aligned with the Darian calendar's structure.
VariantOffset from JDEpochPrimary Use
Truncated Julian Day-2440000.51968 May 24, 00:00 UTSpace tracking ()
Reduced Julian Day-24000001858 November 16, 12:00 UTAstronomical ephemerides
Darian Julian DayEpoch-based1609 March 11 (vernal )Simulations and sci-fi

Calendar Conversions

From Gregorian Calendar to Julian Day Number

The conversion from a Gregorian calendar date to a Julian Day Number follows a standardized algorithm developed by astronomer Jean Meeus, which accounts for the Gregorian leap year rules and adjusts for the calendar's structure to compute the continuous day count since the Julian epoch. This method is applicable to dates in the proleptic Gregorian calendar, extending the rules backward before the calendar's official adoption in 1582 for consistency in astronomical computations. To perform the conversion for a given date (year yy, month mm, day dd), where the result is the Julian Date at noon UT, proceed with these steps:
  1. Adjust the month and year if necessary: If m>2m > 2, set y′=yy' = y and m′=mm' = m; otherwise, set y′=y−1y' = y - 1 and m′=m+12m' = m + 12. This treats January and February as the 13th and 14th months of the previous year, simplifying leap year handling.
  2. Compute the Gregorian correction factor: a=⌊y′/100⌋a = \lfloor y' / 100 \rfloor, then b=2−a+⌊a/4⌋b = 2 - a + \lfloor a / 4 \rfloor.
  3. Calculate the Julian Day: JD=⌊365.25(y′+4716)⌋+⌊30.6001(m′+1)⌋+d+b−1524\text{JD} = \lfloor 365.25 (y' + 4716) \rfloor + \lfloor 30.6001 (m' + 1) \rfloor + d + b - 1524 Here, ⌊⋅⌋\lfloor \cdot \rfloor denotes the floor function (integer part toward negative ). This incorporates the average length of a Julian year (365.25 days) and a monthly adjustment factor derived from the calendar's structure.
For example, the Gregorian date 2000 January 1 at noon UT corresponds to JD 2451545.0. This method is valid for all proleptic Gregorian dates after noon UT on November 24, −4713 (JD 0), ensuring no errors in day counting for positive Julian Days, though it assumes integer inputs and does not handle time fractions beyond the integer day. For dates before this , alternative extensions or validations are required to avoid discrepancies in extrapolations. To include time of day, add the fraction (UT hours / 24) to the JD value obtained.

From Julian Calendar to Julian Day Number

The conversion from dates in the to the Julian Day Number (JD) benefits from the calendar's regular leap year pattern, in which every fourth year is a with no exceptions for centuries. This allows for a simplified formula without the century-based corrections required for the : JD=⌊365.25×(y+4716)⌋+⌊30.6001×(m+1)⌋+d+b−1524\text{JD} = \left\lfloor 365.25 \times (y + 4716) \right\rfloor + \left\lfloor 30.6001 \times (m + 1) \right\rfloor + d + b - 1524 Here, yy is the year, mm the month (with and treated as months 13 and 14 of the preceding year if m<3m < 3, so adjust y=y−1y = y - 1 and m=m+12m = m + 12 accordingly), dd the day of the month, and b=0b = 0 for Julian calendar dates; the result gives the JD at noon UT, to which a time fraction past noon (UT hours / 24 - 0.5) is added for other times of day. The Julian Day Number system originates from noon Universal Time on January 1, 4713 BC, in the Julian calendar. For proleptic extensions of the Julian calendar before its historical introduction in 45 BC, the same formula applies directly, as it assumes consistent application of the leap year rule backward in time without additional modifications. As an example, the proleptic Julian date of January 1, 2000, at noon UT yields JD 2451558.0; this differs from the Gregorian January 1, 2000, at noon, which is JD 2451545.0, reflecting the calendars' divergence. In periods of overlap after the 1582 Gregorian reform, the same physical day (same JD) is labeled differently in the two calendars, with the Julian date lagging behind the Gregorian by an increasing number of days due to omitted leap years. The lag begins at 10 days in 1582 and reaches 13 days for dates in the 1900–2100 interval.

From Julian Day Number to Calendar Date

The conversion from a Julian Day Number (JD) to a calendar date in either the Julian or Gregorian calendar follows an algorithmic process that accounts for the historical transition between the two systems. This inverse calculation reverses the process of determining the JD from a given date, using integer arithmetic and floor functions to ensure precision. The standard algorithm from Jean Meeus begins by adjusting the JD and then branches based on whether the date falls before or after the adoption of the Gregorian calendar in 1582. For a JD (where the integer part represents noon UT), the steps for Gregorian (post-1582) or Julian (pre-1582) are as follows (adapted from Meeus, Astronomical Algorithms):
  1. Compute f=JD+0.5−⌊JD+0.5⌋f = \text{JD} + 0.5 - \lfloor \text{JD} + 0.5 \rfloor (fractional part, for time).
  2. Let Z=⌊JD+0.5⌋Z = \lfloor \text{JD} + 0.5 \rfloor.
  3. If Z<2299161Z < 2299161 (before 1582-10-15 proleptic Gregorian), use Julian branch:
    A=ZA = Z
    else (Gregorian):
    α=⌊(Z−1867216.25)/36524.25⌋\alpha = \lfloor (Z - 1867216.25) / 36524.25 \rfloor
    A=Z+1+α−⌊α/4⌋A = Z + 1 + \alpha - \lfloor \alpha / 4 \rfloor
  4. B=A+1524B = A + 1524
  5. C=⌊(B−122.1)/365.25⌋C = \lfloor (B - 122.1) / 365.25 \rfloor
  6. D=⌊365.25×C⌋D = \lfloor 365.25 \times C \rfloor
  7. E=⌊(B−D)/30.6001⌋E = \lfloor (B - D) / 30.6001 \rfloor
  8. Day d=B−D−⌊30.6001×E⌋+fd = B - D - \lfloor 30.6001 \times E \rfloor + f (f includes time adjustment)
  9. Month m=E−1m = E - 1 if E≤12E \leq 12, else m=E−13m = E - 13
  10. Year y=C−4716y = C - 4716 if m>2m > 2, else y=C−4715y = C - 4715
For the Julian branch, the Gregorian correction steps (3) are replaced with simpler adjustments without α\alpha. This ensures the date aligns with historical calendars: pre-1582 dates use the , while post-1582 use Gregorian. Floor functions throughout maintain integer precision, avoiding fractional errors for whole-day JDs. For fractional JDs, the integer part determines the date, with the fraction indicating time past noon UT. A representative example is JD 2451545.0, which converts to January 1, 2000, in the (noon UT). Applying the algorithm: Z=2451545Z = 2451545; since Z>2299161Z > 2299161, α=⌊(2451545−1867216.25)/36524.25⌋=16\alpha = \lfloor (2451545 - 1867216.25)/36524.25 \rfloor = 16, then A=2451545+1+16−4=2451558A = 2451545 + 1 + 16 - 4 = 2451558; proceeding yields y=2000y = 2000, m=1m = 1, d=1d = 1. This matches the J2000.0 reference in astronomical computations.

Additional Computations

Incorporating Time of Day

To incorporate the time of day into the Julian Day Number (JDN), which counts whole days starting at noon (UT), a decimal fraction representing the portion of the day elapsed since that noon is added, yielding the full Julian Date (JD). This fraction is calculated using the UT time as (hours + minutes/60 + seconds/3600)/24.0, where hours range from 0 to 23, ensuring the JD remains a continuous measure of time. For instance, on 2000 January 1 at 12:00 UT, the JDN is 2451545, and the fraction is 0.0, so the JD is 2451545.0; at 00:00 UT on the same calendar day, the fraction is 0.5 (since is 12 hours before noon), resulting in JD 2451544.5. When using , it must first be converted to UT by adding the appropriate offset (longitude-based or adjustment) before computing the fraction, as JD is defined relative to UT at Greenwich. Unlike UTC, which includes discontinuities from leap seconds, the JD system employs a continuous count based on a fixed 86400 seconds per day, ignoring insertions to maintain uniformity in astronomical computations. This approach ensures precise interval calculations without adjustments for irregular Earth rotation effects embedded in UT1. The formula for the time fraction can be expressed as: f=h+m60+s360024f = \frac{h + \frac{m}{60} + \frac{s}{3600}}{24} where hh is hours UT, mm is minutes, and ss is seconds, and the full JD is then JDN + ff (with f=0f = 0 at noon UT).

Day of the Week Determination

The day of the week corresponding to a Julian date (JD) is computed via modular arithmetic, leveraging the continuous integer sequence of days from the Julian epoch. This approach exploits the fact that there are exactly 7 days in a week, allowing the weekday to be found by taking the JD modulo 7 after appropriate adjustment for the epoch alignment. A standard formula is: Weekday=⌊JD+1.5⌋mod  7\text{Weekday} = \left\lfloor \text{JD} + 1.5 \right\rfloor \mod 7 where the result is 0 for Sunday, 1 for Monday, ..., and 6 for Saturday (offsets can be adjusted for alternative conventions, such as starting with Monday as 0). This derives from the Julian epoch at JD 0.0, which marks noon Universal Time on Monday, January 1, 4713 BC in the proleptic Julian calendar; the +1.5 offset accounts for the noon start and shifts the alignment to match common weekday numbering systems. For instance, JD 2451545.0 corresponds to noon UT on , 2000: ⌊2451545.0+1.5⌋=2451546,2451546mod  7=6\left\lfloor 2451545.0 + 1.5 \right\rfloor = 2451546, \quad 2451546 \mod 7 = 6 yielding , consistent with historical calendars. The method's validity stems from the unbroken continuity of the Julian day count, making it independent of calendar type (e.g., Julian or Gregorian) and applicable proleptically to any date, even before the .

Calendar Type Identification

The Julian Day Number (JDN) serves as a continuous count of days without regard to calendar discontinuities, but when converting a JDN back to a , it is necessary to identify whether the or the applies, as the two systems diverge after the historical transition in 1582. In standard astronomical practice, JDNs before 2299161 correspond to the , while those from 2299161 onward use the . This cutoff aligns with the Julian calendar's last day on October 4, 1582 (JDN 2299160), followed immediately by October 15, 1582, in the (JDN 2299161), skipping ten days to correct for accumulated errors in the Julian rule. Historically, the switch from the Julian to the did not occur uniformly worldwide; it depended on regional adoption, with Catholic countries implementing it in , Protestant regions like Britain and its colonies following in 1752 (skipping eleven days), and some Orthodox countries not adopting it until the or later. However, for computational consistency in astronomy and related fields, the convention fixes the transition at JDN 2299161, treating dates before this as proleptic Julian (extending the Julian rules indefinitely backward) and after as Gregorian. This approach avoids ambiguity in software and calculations, even though real-world historical dates may require adjustment based on local adoption. In reverse conversion algorithms from JDN to calendar date, such as those described in Jean Meeus's Astronomical Algorithms, the calendar type is determined by first computing an integer day count z=⌊JD+0.5⌋z = \lfloor \mathrm{JD} + 0.5 \rfloor (where JD is the full Julian Date including fractional day), then branching: if z<2299161z < 2299161, apply the Julian formula; otherwise, apply the Gregorian formula with an adjustment for the skipped days. Some implementations simplify this by checking if z+1524>2299160z + 1524 > 2299160, which effectively tests the same threshold after shifting the epoch for computational convenience in deriving year, month, and day components. For instance, JDN 2299160 yields October 4, 1582, in the Julian calendar, while JDN 2299161 yields October 15, 1582, in the Gregorian calendar, illustrating the seamless continuity of day numbering across the transition despite the date skip.

Calculating Decimal Years Between Dates

To calculate the decimal number of years between two dates, first compute the difference in their Julian Dates, ΔJD=JD2−JD1\Delta \mathrm{JD} = \mathrm{JD_2} - \mathrm{JD_1}. For intervals primarily within the Julian calendar, divide this difference by 365.25, the average length of a Julian year. For the Gregorian calendar, divide by 365.2425, which reflects the average year length over its 400-year cycle accounting for refined leap year rules. This provides a simple approximation for expressing time intervals in fractional years, useful in astronomical and chronological purposes.

Cycle Relations

Indiction, Metonic, and Solar Cycles

The indiction cycle is a 15-year period derived from the Byzantine administrative system for assessing taxes on land and property, instituted by Emperor Constantine in 312 CE and running from 1. In the Julian day system, this cycle is aligned to the chosen such that its starting point coincides with the overall period's beginning, facilitating chronological computations. The , or lunar cycle, spans 19 years, during which 235 synodic months (the time between consecutive new moons) approximate 19 tropical years with high accuracy, enabling the moon's phases to return to nearly identical positions relative to the dates. This alignment, totaling about 6,939.69 days, supports lunar-solar calendar synchronization. The consists of 28 years in the , reflecting the pattern of leap years every four years combined with the seven-day week, after which the sequence of weekdays for specific dates repeats exactly due to the total of 10,227 days (an integer multiple of seven). This cycle captures the calendar's internal repetition independent of astronomical solar motion. Since 15, 19, and 28 are pairwise coprime, their is simply their product: 15×19×28=798015 \times 19 \times 28 = 7980 years, forming the length of the Julian period, equivalent to 2,915,695 days in the . The independence of these cycles allows the position within each to be determined from the proleptic Julian year corresponding to the Julian day number, modulo the respective cycle length, with standard offsets for alignment (15 for indiction, 19 for Metonic, and 28 for solar).

Reconstructing the Julian Period

The reconstruction of the Julian Period determines the unique year position within its 7980-year cycle by combining the known positions from the indiction (15 years), Metonic (19 years), and solar (28 years) cycles, relying on their pairwise coprimality to apply the . This computational approach solves the simultaneous congruences defined by the cycle indices, yielding a position 7980 that aligns dates across historical records lacking direct Julian Day Numbers. The indiction index II (1–15), Metonic (golden number) index MM (1–19), and solar index SS (1–28) are typically obtained from the year using standard formulas, such as I=((y+3)mod  15)I = ((y + 3) \mod 15) or 15 if 0, M=((ymod  19)+1)M = ((y \mod 19) + 1), and S=((y+9)mod  28)+1S = ((y + 9) \mod 28) + 1 (offsets vary by convention to align with the epoch). These indices then feed into the reconstruction formula for the period year. The core formula for the period year yy (1-based) is the least residue of y=6916I+4200M+4845S(mod7980),y = 6916 I + 4200 M + 4845 S \pmod{7980}, derived from the Chinese Remainder Theorem with coefficients as modular inverses scaled by the products of the other moduli. This solves the system y≡I(mod15),y≡M(mod19),y≡S(mod28),y \equiv I \pmod{15}, \quad y \equiv M \pmod{19}, \quad y \equiv S \pmod{28}, (adjusted for 1-based indexing). The resulting yy gives the year offset from the (year 1 of the period at JD 0), corresponding to 4713 BC + (y - 1). This method, though rarely applied in modern computations due to direct JD-to-date algorithms, finds utility in historical for aligning pre- dates (before 4713 BC) recorded via cycle positions in ancient texts, enabling synchronization with the Julian Day scale. Its primary limitation is the assumption of exact cycle alignment at the epoch year -4712, which holds under the but may introduce minor discrepancies in non-astronomical historical contexts due to varying adoptions.

Applications

In Astronomy

The Julian Day (JD) system is integral to astronomical ephemerides, providing a continuous timescale for computing planetary and lunar positions over extended periods. The Laboratory's DE430 and DE431 ephemerides, covering dates from 1550 to 2650 CE, express positions and velocities of major solar system bodies as functions of JD in (TDB), with the reference epoch at JD 2440400.5 (June 28, 1969). Subsequent models, such as DE440 and DE441 (spanning 1550 to 2650 CE), maintain this convention, incorporating refined orbital fits to ground-based and observations while using JD for time parameterization to ensure interoperability with legacy data. In , JD standardizes timing for phenomena requiring precise synchronization, such as light-time corrections in and . For , observations from organizations like the American Association of Variable Star Observers (AAVSO) are recorded to 0.0001 day precision in JD, allowing corrections to heliocentric JD to account for Earth's orbital motion and the finite , which is crucial for aligning light curves across global sites. Similarly, for eclipsing binaries, JD facilitates barycentric corrections, minimizing errors in timing predictions that could otherwise accumulate due to effects over long baselines. Major astrometric catalogs rely on JD or its variants for timestamping observations, enabling consistent analysis of stellar motions. The European Space Agency's mission (1989–1993) converted onboard mission times to JD in (TCB) for processing over 118,000 stars, supporting high-precision parallax and proper motion measurements. The ongoing Gaia mission extends this approach, using Barycentric JD in TCB for timestamps in its data releases, as seen in photometric surveys where epochs are referenced to BJD 2455197.5 for billions of sources, facilitating variability studies and orbit determinations. The JD system's primary advantage in astronomy lies in its uniformity, which bypasses calendar leap day insertions and month-length variations, simplifying computations in long-term where irregularities could introduce cumulative errors over millennia. This continuity remains vital despite UTC's prevalence for civil and short-term timing, as reaffirmed in (IAU) resolutions; for instance, Resolution C7 (1994) defines the Julian ephemeris day in (TT), underscoring JD's foundational role in celestial reference systems.

In Computing and Software

In computing and software, the Julian day serves as a continuous temporal reference for date and time manipulations, particularly in scientific and astronomical applications where calendar discontinuities must be avoided. Libraries such as Python's Astropy provide robust support for Julian day conversions and representations. The Astropy time module internally stores times as a pair of double-precision floating-point numbers representing Julian days, enabling seamless handling of formats like TimeJD for standard Julian dates and TimeMJD for modified Julian dates (MJD = JD - 2400000.5). This design facilitates precise astronomical computations without reliance on calendar-specific rules. Similarly, Java's java.time.temporal package includes JulianFields, which offers access to Julian day numbers as a standard for expressing dates in scientific contexts, allowing conversions between calendar dates and continuous day counts. Standards like provide partial support for Julian day concepts through ordinal date representations (year and day-of-year), which align with business-oriented "Julian dates" but differ from the astronomical continuous count; full astronomical Julian days are not natively encoded, requiring custom conversions in compliant systems. NASA's toolkit, used for space mission analysis and planning, extensively employs both Julian days and MJDs as its primary time representation, enabling calculations and trajectory modeling across epochs. In GPS and systems, Julian days appear in files and modeling software for positioning satellites, though GPS weeks (since January 6, 1980) are more commonly preferred for operational timing; for instance, Yuma data uses Julian dates to compute positions valid from 1900 to 2100. Handling Julian days in databases presents challenges, particularly with proleptic dates—extensions of modern calendars backward before their historical adoption—which can lead to inconsistencies between proleptic Gregorian and hybrid Julian-Gregorian systems, as seen in frameworks like where shifting to proleptic modes required resolving discrepancies for accurate date arithmetic. Unlike the Y2K issue, which stemmed from two-digit year representations in discontinuous calendars, Julian days avoid such problems through their inherent continuity as a simple day count, ensuring reliable storage and querying across millennia without rollover errors. Post-2020 developments have integrated Julian days into pipelines for astronomy, especially in processing time-series data like light curves. For example, the StarEmbed benchmark (2025) uses modified Julian dates to timestamp observations from the , enabling foundation models to handle irregular sampling in tasks such as classification and on peta-scale datasets. This approach leverages the continuity of Julian days to train neural networks on temporal patterns without calendar-induced biases, enhancing predictions in transient event analysis.

References

  1. https://core2.gsfc.nasa.gov/time/
  2. https://caps.gsfc.nasa.gov/simpson/time/jd/julian-days.pdf
  3. https://adsabs.harvard.edu/full/1998JHA....29..327M
  4. https://templeton.eastern.edu/sites/default/files/inline-files/ephemerides_of_variable_stars.pdf
  5. http://web.mit.edu/jmorzins/www/iso8601/y2kdat.htm
  6. https://thonyc.wordpress.com/2013/08/07/counting-the-days/
  7. https://naif.jpl.nasa.gov/pub/naif/toolkit_docs/FORTRAN/req/time.html
  8. https://aa.usno.navy.mil/data/JulianDate
  9. https://jacobfilipp.com/DrDobbs/articles/SA/v12/i07/a2_s1.htm
  10. https://scienceworld.wolfram.com/astronomy/JulianDate.html
  11. https://pubs.aip.org/aapt/ajp/article/49/7/658/1051633/The-origin-of-the-Julian-Period-An-application-of
  12. https://aa.usno.navy.mil/faq/TT
  13. https://aa.usno.navy.mil/downloads/c15_usb_online.pdf
  14. https://aa.usno.navy.mil/faq/JD_formula
  15. https://castle.eiu.edu/~scienced/3290/science/sun/julianday.html
  16. https://www.academia.edu/37504747/Anthony_T_Grafton_Joseph_Scaliger_and_Historical_Chronology_The_Rise_and_Fall_of_a_Discipline_History_and_Theory_vol_14_no_2_May_1975_156_185
  17. https://archive.org/details/outlinesofastron00hersuoft
  18. https://aa.usno.navy.mil/faq/millennium
  19. https://www.hermetic.ch/cal_stud/jdn.htm
  20. https://aa.usno.navy.mil/publications/asa_history
  21. https://heasarc.gsfc.nasa.gov/docs/nicer/analysis_threads/time/
  22. https://gssc.esa.int/navipedia/index.php/Time_References
  23. https://heasarc.gsfc.nasa.gov/docs/xte/abc/time_tutorial.html
  24. https://xmm-tools.cosmos.esa.int/external/sas/current/doc/phasecalc.pdf
  25. https://ntrs.nasa.gov/api/citations/19800007830/downloads/19800007830.pdf
  26. https://www.astro.sunysb.edu/fwalter/PHY515/times.html
  27. https://www.researchgate.net/publication/290542846_The_Architecture_of_Time_Part_2_The_Darian_System_for_Mars
  28. https://ssd.jpl.nasa.gov/tools/jdc/
  29. https://quasar.as.utexas.edu/BillInfo/JulianDateCalc.html
  30. https://stjarnhimlen.se/comp/ppcomp.html
  31. https://irtfweb.ifa.hawaii.edu/~tcs3/tcs3/Misc/slalib_html/node219.html
  32. https://asd.gsfc.nasa.gov/Craig.Markwardt/doy2000.html
  33. https://www.naughter.com/aa.html
  34. https://orbital-mechanics.space/reference/julian-date.html
  35. https://www.skypoint.com/members/waltzmn/MSDating.html
  36. https://eclipse.gsfc.nasa.gov/SEhelp/calendars.html
  37. https://www.tondering.dk/claus/cal/chrweek.php
  38. https://www.calendarbede.com/book/indiction
  39. https://www.britannica.com/science/golden-number
  40. https://people.math.harvard.edu/~knill/crt/lib/Kangsheng.pdf
  41. https://naif.jpl.nasa.gov/pub/naif/generic_kernels/spk/planets/de430_and_de431.pdf
  42. https://ssd.jpl.nasa.gov/doc/Park.2021.AJ.DE440.pdf
  43. https://www.aavso.org/about-jd
  44. https://academic.oup.com/mnras/article/480/4/4557/5078965
  45. https://cdsarc.cds.unistra.fr/viz-bin/ReadMe/I/337?format=html&tex=true
  46. https://www.aanda.org/articles/aa/full_html/2023/06/aa44204-22/aa44204-22.html
  47. https://www.sciencedirect.com/topics/engineering/julian-day
  48. https://iopscience.iop.org/article/10.1086/378162/fulltext/202343.text.html
  49. https://docs.astropy.org/en/stable/time/index.html
  50. https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/time/temporal/JulianFields.html
  51. http://support.sas.com/kb/38/811.html
  52. https://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/req/time.html
  53. https://ntrs.nasa.gov/api/citations/20020078200/downloads/20020078200.pdf
  54. https://www.waitingforcode.com/apache-spark-sql/whats-new-apache-spark-3-proleptic-calendar-date-time-management/read
Add your contribution
Related Hubs
User Avatar
No comments yet.