The Eclipse Phase Timing Tool is a set of JavaScript files and an HTML page that allows the user to get data for a particular eclipse at different locations. The HTML page allows the user to select an eclipse date and upload a CSV file containing location data (either coordinates or zip codes) and it outputs a CSV file with the eclipse data for each location.
A software utility developed by Eclipse Soundscapes to generate accurate eclipse phase timing data (start of eclipse, maximum start, maximum end, end of total/annular/partial eclipse) for any latitude/longitude input. The tool ingests detailed NASA-generated path prediction datasets, translating them into structured, location-specific timing data. Originally developed to support the scientific research done on the effects of the eclipse on wildlife that is supported by ES. The EPTT takes a .csv spreadsheet as input (with either latitude and longitude, or ZIP code information) and calculates detailed information about the timings of each eclipse phase at the locations given in .csv spreadsheet format. This tool has been updated utilizing NASA datasets through the 2024 total solar eclipse. Additional, but minor work would be needed to utilize this for future eclipses.
The eclipse data that is returned includes the following:
- Eclipse type [Output] (Total, Partial, Annular, None)
- Eclipse coverage [Output](as a percentage)
- First contact date [Output](The day of the eclipse.)
- First contact time (UTC) [Output](The time the Moon first appears on the disk of the sun..)
- Second contact time (UTC) [Output](Totality start time, if a total eclipse. Annularity start time if an annular eclipse. If partial it is 0.)
- Third contact time (UTC) [Output](Totality end time, if a total eclipse. Annularity end time if an annular eclipse. If partial it is 0.)
- Fourth contact time (UTC) [Output] (Time that the Moon as moved completely off the the disk of the Sun.)
- Maximum eclipse time (UTC) [Output] (Time where the local eclipse hits its peak.)
- Latitude [Input] (Observation latitude which provides timings above.)
- Longitude [Input] (Observation latitude which provides timings above.)
- Zip Code [Input] (if the selected upload option is Zip Codes)
- Download or clone the repository locally from: https://github.com/ARISA-Lab-LLC/Eclipse-Data-Tool.
- If downloaded directly from GitHub, unzip the folder to the desired location on your system
- Open the convert.js file using a text editor and replace the API_KEY placeholder in the retrieveCoordinateFromZipCode function with an actual Google Geocoding API key (line 147). Without this change the option to get eclipse data from zip codes will always raise an error. (https://developers.google.com/maps/documentation/geolocation/overview)
- Open the index.html file in the Eclipse-Data-Tool folder with your favorite browser
- Select an eclipse date
- Select the type of location data that will be provided in the uploaded CSV (Coordinates or Zip Codes)
- Click the “Upload CSV File” button to choose a CSV file to upload from your local system
- Click “Download Processed CSV” to download the result
- Steps 1-3 only need to be done once when the project is copied locally.
- Make sure that you can run java scripts on the computer where this is running.
- If the uploaded CSV file does not contain the expected location data in its proper format, an error alert will be presented to the user indicating the issue.
- You will need to add your own Google Geocoding API key to line 147 in convert.js and replace the API_KEY placeholder to use the ZIP Code Function.
-
Eclipse Data Credit: Eclipse map/figure/table/predictions courtesy of Fred Espenak, NASA/Goddard Space Flight Center, from eclipse.gsfc.nasa.gov.
-
Eclipse Soundscapes is an enterprise of ARISA Lab, LLC and is supported by NASA award No. 80NSSC21M0008. Any opinions, findings, and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the National Aeronautics and Space Administration.