Pluto - Perigee and Apogee Calculator

Pluto Perigees and Apogees Calculator
For the 399-Year Span From 1700 AD to 2098 AD
Built Around the NASA/JPL Horizons API
PHP Program by Jay Tanner

Year Time Zone UTC

Optional Location Label

Double-Click Within Text Area to Select ALL Text

                   PLUTO PERIGEE AND APOGEE FOR THE YEAR 2024
               =================================================
               Time Zone UTC+00:00
               

               Dates refer to the modern Gregorian calendar.

========================================================================
 EVENT   Julian Date UTC   Calendar Date     Time UTC      Distance AU
------- ----------------- ---------------  -----------  ----------------
Apogee  2460332.616555305 2024-Jan-23-Tue  02:47:50 AM  35.9196795631788
Perigee 2460512.101283057 2024-Jul-20-Sat  02:25:51 PM  34.0456762558428
------- ----------------- ---------------  -----------  ----------------

Double-Click Within Text Area to Select ALL Text


NOTES:

[1] This Pluto perigee and apogee calculator spans the 399 year
    period from 1700 AD to 2098 AD.

    It was written in PHP v7.4.9 and makes internal calls to the
    NASA/JPL Horizons API v1.1

    Julian Dates (JD) and Calendar Dates:
    JD <  2299160.5 = Refers to Old-Style Julian Calendar Dates

    JD >= 2299160.5 = Refers to Modern Gregorian Calendar Dates

    Given JD = General Julian Date, then the Julian Day Number
               on the Calendar is JD Number = floor(JD + 0.5)

    Dates up to 1582-Oct-04-Thu refer to the Julian calendar.
    Dates from  1582-Oct-15-Fri refer to the Gregorian calendar.

    Technically speaking, there are no calendar dates in the range
    from 1582-Oct-05-Fri to 1582-Oct-14-Sun because those 10 dates
    were dropped from the calendar during the Julian to Gregorian
    calendar transition to bring dates of the seasons back into
    alignment with the sun and the rule for leap year was changed
    to prevent the previous calendar error from recurring.

    The date following 1582-Oct-04-Thu was 1582-Oct-15-Fri, the
    official first date on our modern Gregorian calendar system.



[2] Occasionally a time-out may occur if the JPL Horizons server
    is temporarily unavailable or too busy and an error occurs.

    If such a crash or hang-up does occur, simply refresh and try
    again.



[3] UT1 = Old Universal Time Scale - Solar based.
          Old previous UT time scale used for years up to 1961.

    UTC = Coordinated Universal Time Scale - Atomic based.
          Newer UT time scale used from 1962 to date.
          World times are now based on this standard.

    LT  = Local Time for the given time zone based on the
          given +/− HH:MM offset.

          Time Zone Offset Convention:
          West of Greenwich, time zone offsets are negative.
          East of Greenwich, time zone offsets are positive.



[4] Standard times are assumed. To adjust for Daylight Saving or
    Summer Time, add 1 hour to the standard times taking care to
    watch for any change of date -OR- subtract 1 hour from the
    time zone offset, which will automatically handle any date
    change.

    For example, the time zone offset for Eastern Standard Time
   (EST) is normally -5 hours. However, when Eastern Daylight Time
   (EDT) is in effect, use a time zone offset of -4 hours instead.
    The computed times will be in EDT and automatically handle any
    date changes.



[5] There is an optional location label that can be applied to the
    computed table for reference.  However, any label should match
    the indicated time zone so as to be accurate and make sense.

    For example, if using the time zone offset for India, putting
   'New York City, USA' as the location, would be rather absurd
    and an inaccurate match between location name and time zone.

    The label can consist of any printable plain-text string and
    defaults to 'Greenwich, England' at Time Zone Offset +00:00.



[6] This program implements a cookie to store and recall the year
    and other interface settings between calls. It does not track,
    monitor or perform any other activity. If you navigate away
    and come back later, the interface settings stored in the
    cookie will be recalled from your last visit.

    Each call will refresh the cookie for up to 7 days retention
    unless deleted sooner. There is no harm in deleting the cookie.
    The program will simply revert to the original default values.

Download PHP 7 Source Code For This Program
Program by Jay Tanner
Revised: Friday - March 03, 2023 at 01:48:18 UTC - PHP v7.4.9