Steve's Julian Date Calculator

This utility is based on a calculator that was originally published by the Astronomical Applications Department of the US Naval Observatory.  However, the contents of that site have since changed, principally to initialise the form to midnight on the date shown by their server clock, not that in your computer.  Since this server is located in the USA, the initialised date might be different from the local date by one day.  This calculator uses the original format to convert from calendar date and time to Julian Date, and vice versa.  The direction of conversion is selected by the Calculation Type.  This page and its associated JavaScript file have been extended by Steve Glennie-Smith to increase accuracy to the nearest 10ms, to show a 'ticking' UTC clock and the local timezone.  Bug fixes are listed at the end.

Current Universal Time:-

BCE 
CE 

year

  month

day

 

hr

min

sec

 

[weekday

 

local timezone]

 

Universal Time

 

 

 Julian Date

Calculation type:

 

to->   JD Date   Use Year Zero    

The form is initialised to the Universal Date and Time (to all intents and purposes, this is the same as Greenwich Mean Time, but not exactly the same - see differences), as determined by the clock in your computer at the time this page is entered (note: this is always to the nearest second).  A conversion from your local timezone is applied.  The clock above the form shows Current Universal time, and will keep 'ticking'.  The time shown in the form will not 'tick' - this and the date are free for you to alter as inputs to the Julian Date calculator.  The weekday field is read-only, as determined from the Julian Date.  The timezone field is also read-only; it is fixed according to the local date and time when your session was started.  This includes any correction for 'daylight saving' (or 'Summer Time').

CE and BCE designate "Common Era" and "Before Common Era", often known as "AD" and "BC" respectively.  See notes below for the Use Year Zero option.
 


Julian Dates (abbreviated JD) are simply a contiguous count of days and fractions since noon Universal Time on 1st January, 4713 BCE (on the Julian calendar).  Almost 2.5 million days have elapsed since that date.  Julian Dates are widely used as time variables in astronomical software.  Typically, a 64-bit floating point (double precision) variable can represent an epoch expressed as a Julian Date to about 1 millisecond precision.  Note that the time scale that is the basis for Julian Dates is Universal Time, and that 00:00h UTC always occurs at a Julian Date fraction of 0.5.  The distinction between Julian Date and Julian Day is that the former is the whole number, including the fractional part, whereas the latter is just the integer part, ie. the number of days since 'Day Zero'.

Calendar dates — year, month, and day — are more of a problem.  Various calendar systems have been in use at different times and places around the world.  This calculator deals with only two: the Gregorian calendar, now used universally for civil purposes, and the Julian calendar, its predecessor in most of the western world.  As used here, the two calendars have identical month names and number of days in each month; they differ only in the rule for leap years.  The Julian calendar has a leap year every fourth year, while the Gregorian calendar has a leap year every fourth year except centennial years that are not exactly divisible by 400.

Although JD zero was 1st January 4713 BCE, this calculator will allow negative Julian Dates, and years with up to six figures.

The following assumptions are made:

The changeover to the Gregorian calendar only occurred as described above in Roman Catholic countries, however.  Adoption of the Gregorian calendar in the rest of the world progressed slowly.  For example, Great Britain and its colonies did not implement the change until September 1752 (though there is some doubt as to when the change took place in Scotland).  [The UNIX CAL command reflects the 1752 changeover, when it became necessary to delete eleven days, since the year 1700 had also been taken as a leap year.]

The corrections applied by the Gregorian calendar give a close average approximation (365.2425 days) to the time it takes for the earth to orbit the sun.  However, the actual time taken (averaged over the last few centuries) is 365.242190 days, so a small error still accrues, though now it is now a gain of 1 day in about 3220 years.  Various extensions to the 100 and 400 year rules in the Gregorian calendar have been proposed, but none have officially been adopted:

In my view it would be churlish to impose changes that would take place so far ahead on future generations.  Who knows - some idiot might let off an atom bomb or the earth could be hit by a big meteorite, both of which could affect the length of the year, and so blow all this theory out of the water.  However, Julian Dates will keep plodding along regardless.  Since the aim of this calculator is to give an accurate correlation between Julian Dates and Calendar Dates way into the future, I have concurred with Herschel and UNIX, and altered the original JavaScript to include the 4000 year rule.

More information on when various countries changed can be found on the Calendar pages of this European History site.  For another list of when certain countries switched to the Gregorian calendar, see section 2.2.4 of Claus Tøndering's Calendar FAQ

More information on calendars and their histories can be found in L.E. Doggett's "Calendars" chapter of the Explanatory Supplement to the Astronomical Almanac (ed. P.K. Seidelmann, 1992, University Science Books).  Note: these are commercial booksellers' sites.
 

Note: there are a number of other Julian Date calculators on the web: a quick search on Google turned up this one, which has huge errors.  Quickly playing with it, it became apparent that it only gives correct answers between 1st March 1800 and 28th February 2100.  Apart from 1900, it makes no correction for the Gregorian calendar and, according to it, JD zero was BCE4712 January 13th.  Beware!


Bug fixes:

Steve Glennie-Smith   21st November 2007

Back