ZIP Codes and Zmanim – A Practical Approach

99557 ZIP code area (the largest in the USA)
99557 ZIP code area (the largest in the USA)
As mentioned in the ZIP Codes and Zmanim – Use With Care article, using ZIP codes to geolocate your position for zmanim can be problematic when the zip code is large. With large zip codes, zmanim on the west side of the zip code can be quite a bit later than zmanim on the east side of the zip. Recently, Lazer Guttman created an SMS based zmanim service at (914) 409-9394 that provides a warning when zmanim are requested for large zip codes. This approach is probably the best that can be done. I would recommend that any zmanim service that is zip code based (and does not have a map to allow zeroing in to a precise location), use this data to to provide a warning whenever the zip codes is wider than 0.5° of longitude. A degree of longitude spans 4 minutes (regardless of the latitude), so half of a zip code with half of a degree would span 2 minutes (one minute east or west of the center). It should be noted that Canadian postal codes are much smaller than zip codes (usually covering one side of a city block), and most likely do not face the same issue. A spreadsheet listing all zip codes with the maximum longitude and latitude distances (in degrees), was generated by Avraham David Gelbfish from OpenDataDE that is based on US Census data. His Python source code is below.

import json
import csv
jsonfile = open("tl_2019_us_zcta510/out2.geojson")
zipcodes = json.load(jsonfile)
def getop(geolist, operation, longitude = None, latitude = None):
    if isinstance(geolist[0], list):
        answers = [getop(geo, operation) for geo in geolist]
        for answer in answers:
            lat, lng = answer
            if latitude is None:
                latitude = lat
            if longitude is None:
                longitude = lng
            latitude = operation(latitude, lat)
            longitude = operation(longitude, lng)
        return latitude, longitude
        return geolist
with open("out2.csv", "w") as csvfile:
    zwriter = csv.writer(csvfile)
    zwriter.writerow(["Zip", "Latitude max distance", "Longitude max distance"])
    for zipcode in zipcodes["features"]:
        zip = zipcode["properties"]["ZCTA5CE10"]
        geometry = zipcode["geometry"]["coordinates"]
        maxlat, maxlng = getop(geometry, lambda x, y: x if x > y else y)
        minlat, minlng = getop(geometry, lambda x, y: x if x < y else y)
        dlat = abs(maxlat - minlat)
        dlng = abs(maxlng - minlng)
        zwriter.writerow([zip, dlat, dlng])

The Definition of Chatzos

Arctic Sun
This article was written לז״נ my close friend ר׳ מנחם מענדל בן יחיאל מיכל Menachem Halpert ז״ל. He was never without a smile, was always ready to listen and help, and was a true עניו. Menachem ז״ל was a regular reader of my posts, and in his self-deprecating way always claimed that the contents were over his head, but discussing the subject with him clearly showed a deep understanding. יהא זכרו ברוך.

Possible Definitions of Chatzos

The zmanim of chatzos / חצות are the solar midday and midnight points. The Radak in the ספר השרשים, שרש חצה defines the word chatzos / חצות as splitting the morning from the afternoon (or first half of the night from the second half).
I am aware of three possible definitions of chatzos.

  • When the sun is directly south (or north) of an observer. This is known astronomically as the solar meridian transit. This method is the only one that was measurable (not perfectly) in the time of chazal (and until relatively modern times) using a sundial or the shadow of a perfectly vertical pole with knowledge of the exact point of the cardinal directions. This is the generally accepted definition of solar noon in the astronomical world.
  • When the sun reaches its highest altitude of the day. This is known astronomically as the sun’s upper culmination.
  • Halfway between sunrise and sunset (or variations on this, such as halfway between alos and tzais).

Although these events happen in close proximity to each other, they do not happen at the same time as we will explain in this article. While they generally occur within the span of half of a minute and the difference is therefore halachically almost insignificant, the point of this article is to understand the exact definition of chatzos.

Is Calculating Chatzos As Half of the Day Close Enough?

Currently the KosherJava Zmanim library calculates chatzos as halfway between sunrise and sunset. This was done for simplicity and technical reasons. Rabbi Yehuda Burstein in his זמנים כהלכתם / Zmanim Kehilchasam 8th edition vol. 2 פ״ו ס״ד defines chatzos:

חצות היום הוא הרגע בו השמש נמצאת באמצע הרקיע ממש – בראש גובה קשת מהלכה היומי ממזרח למערב. … חישוב זמן זה הוא פשוט – דהוא במחצית הזמן שבין רגע הנץ המישורי לבין רגע השקיעה המישורית באותו מקום באותו יום.

Chatzos is the moment that the sun is positioned exactly in the center of the sky – at the highest point of its daily east/west path … Calculating this time is simple since it is halfway between the moment of sea-level sunrise and sea-level sunset.

He continues to explain that this half-of-the-day chatzos is not exactly accurate since the time from sunrise to astronomical midday is not equal to the time from astronomical midday to sunset. The difference is minor, and for this reason, most zmanim calendars do not bother calculating the astronomical chatzos.
In an effort to show the actual difference between meridian transit and half of the day chatzos, I graphed the difference between the two chatzos calculations at various latitudes.

Meridian Transit Versus Half of the Day
A chart showing the difference in seconds between meridian transit chatzos and half of the day at different latitudes.

This discrepancy is caused by changes in the length of the day. There are two factors that cause the length of the day to change, the EoT (we covered the equation of time in detail in the earlier FAQ: Chatzos Hayom Versus Chatzos Halayla article) and the change in the amount of daylight time from day-to-day. At the equator, the only change in the length of the day is the EoT, while as you move north of the equator (all examples in this article focus on the spring in the northern hemisphere, though you can mirror it to the other times of the year and southern hemisphere), the length of the day is impacted by the sun’s apparent lengthening path through the day as well (the sun sets farther north), and is above the horizon for more of its day arc. As we move away from the equinox and the day lengthens, the second half of the day is longer than the first half of the day, pushing the halfway point between sunrise and sunset past solar midday. However, even in Gateshead, England (55° N), the difference between the two calculations ranges from -47 to + 36 seconds, not a significant difference. As you get farther north into the Arctic Circle, things start to change more significantly, and that leads to a practical reason to use astronomical chatzos. In the Arctic Circle when the sun does not rise / set, chatzos can’t be calculated as half of the day. However calculating chatzos as the meridian transit can be done without issue because the meridian transit remains the same anywhere along a line of longitude (the algorithm does not factor in the latitude at all). While the impact of the accurate time of chatzos is not something that usually impacts people, in the Arctic Circle with periods of time where there is no day or night on a daily basis, chatzos may be used to define the boundaries of day and night. See the ביאור הגר״א או״ח ס׳ רס״א ב׳ where in the northern regions (including Vilna) chatzos is alos hashachar. In a future post I will discuss changes to the KosherJava Zmanim API to allow calculation of astronomical (local meridian transit) chatzos, and possibly more on the halachic impact of chatzos in the Arctic Circle.

Sun–Meridian Transit Time Versus The Sun’s highest Point (Transit Versus Culmination)

It is interesting to note that the sun is not exactly at its highest point (culmination) at its local meridian transit (when it is at an azimuth of 180° – directly south or 0° – directly north, depending on your location) on most days of the year. This was mentioned over 120 years ago in a paper by D.A. Pio published in the Monthly Notices of the Royal Astronomical Society, Vol. 59, May 1899; p. 513:

The Sun, the Moon, and all the planets culminate out of the meridian.

It is at its maximum difference near the equinoxes when the day arc is changing significantly from day to day. For example at Yerushalayim’s latitude of 31.778°, the sun reaches its highest point on February 20th 11.14 seconds after crossing the meridian. At 60° the difference on March 4th increases to 27.13 seconds.

Culmination Versus Transit
A chart showing how many seconds the culmination happens after the sun’s transit. Courtesy of J. Giesen.
While this seems like a large gap, the actual difference in the sun’s altitude between the transit and the culmination at latitude 31.778° is minimal, about 0.00002° (0.0826 arcseconds), something that can’t be measured without an observatory sized telescope. At 60° latitude, the altitude difference increases to 0.00006° (0.2148 arcseconds), again something almost imperceptible. In Longyearbyen, Norway, latitude 78.22°, the difference between transit and culmination peaks at 73 seconds on March 13. The difference increases significantly farther north. These calculations were done with the help of J. Giesen whose Transit and Culmination article discusses the phenomena in detail. The effect can also be seen using Stellarium.

The cause of the time difference between the two “flavors” of astronomical midday is due to the sun’s increasing declination that causes the sun’s altitude to increase faster than its movement along the day arc moves it down. The farther north you go, the flatter the day arc appears, meaning that it travels much farther horizontally for a small change in altitude. Around midday when the arc is flattest, the change in declination is increasing the altitude immediately after the meridian transit more than the drop caused by the day arc.
At this point you may wonder why chatzos is called chatzos if we define it as one of the astronomical midday definitions that is not exactly half of the day (a case can be made that neither is “half of the day” chatzos, since at the point of splitting it, you have not reached the lengthening full day…). The Radak’s definition of chatzos / chatzi quoted above concludes with:

… כלם ענין חלוקה, בין שיהיו החלקים בשוה או בלא שוה.

… they are all under the category of splitting, whether they are of equal parts or not.

The Radak on Shmuel II, 19:41 restates that chatzi is not always half as is clear from the “half” that is referred to there:

… ולשון חצי ומחצה ומחצית אינו אלא חלוק החלק מהכלל פעמים הוא חלק כחלק בשוה וזהו ברוב ופעמים אינו בשוה.

… the language of half (in its various forms) are only splits of the whole, sometimes it is an equal division, and that is the case most of the time, but sometimes it is not equal.

Note that this concept of chatzi not being half of the day would also seem to counter objections that some have about calculating chatzos from alos to tzais Geonim as an uneven split (regardless, it is very hard to fit such an uneven chatzos into any of the rishonim or achronim we mentioned earlier), though Rabbi Mordechai Kuber pointed out that it is half of the halachic day timewise, so it still fits the definition of chatzos.

Halachic Definition of Chatzos

Rashi in פסחים נח. ד״ה בין הערבים defines the afternoon (starting immediately after the 6th hour or chatzos) as:

משש שעות ולמעלה שהצל נוטה קרינן בין הערבים

From six hours and on, when the shadow leans [to the east], it is called the afternoon.

Rashi has the same definition in Brachos ט. ד״ה שם תזבח את הפסח and כו: ד״ה מנחה גדולה and Shabbos ט: ד״ה מנחה גדולה. Since Rashi defines after chatzos as when the shadows begin leaning, it would indicate that at chatzos shadows do not lean east or west, but point directly north. This seems to be a clear indication that chatzos is defined as when the sun is transiting its local meridian and is directly south at an azimuth of 180° (or directly north or an azimuth of 0° for locations south of the sun, or directly overhead on certain days for locations between the Tropic of Cancer and the Tropic of Capricorn), when there are no east or west shadows. The Tosafos Yom Tov in פסחים פ״ה מ״א expands and clarifies this:

כתב הר״ב דזמן שחיטת תמיד מכי ינטו צללי ערב וכו׳ ואין צל נוטה אלא צל כל אדם תחתיו. רוצה לומר ואין לו נטייה לא למזרח ולא למערב אבל שיהיה תחתיו ממש זהו דבר שהחוש מכחישו בכל אלו הארצות ואף בארץ ישראל. לפי שאין צל כל אדם תחתיו אף באמצע היום. אלא להשוכנים בין עגול סרטן לעגול גדי. ואחת בשנה *) תבא השמש נוכח הראש לקצתם קצתם איש איש ביומו לפי מספר עגולי השמש שתעשה מראשית השנה עד אחרית השנה אבל לשוכנים חוצה לעגולים האמורים לעולם השמש דרומית או צפונית להם ועושה צל בהכרח הנוטה לצפון או לדרום אפי׳ בצהרים והנה ארץ ישראל ידענו כי היא כמו שמנה מעלות לצפון עגול סרטן:

כתב המגיה *) הלשון אחת בשנה אינה מדויקת, כי רק לאלה השוכנים במקום קצות עגולי ההפך סרטן וגדי הרחוקות כל אחת מן קו המשוה כ״ג מעלות וחצי אם לצפון או לדרום רק לאלה תבא השמש נוכח הראש אחת בשנה; לשכנים בקצה גבול עגול ההפך סרטן יהיה זה ביום תקופת תמוז ולשוכנים בקצה גבול עגול ההפך גדי, ביום תקופת טבת. אך לאלה השוכנים בין שתי קצות העגולים האלה תבא השמש נכחם שתים בשנה:

The Raav wrote “The time of the Korban Tamid is from when the afternoon shadows lean etc. and there is no shadow, rather everyone’s shadow is directly underneath him.” Meaning, that the shadow does not project to the east or west, rather that it is directly under him. However, this is something that is not the case in any of our lands, including Eretz Yisrael. This is because a person’s shadow is not under him even in the middle of the day besides for those residing between the Tropic of Cancer and the Tropic of Capricorn … for those residing outside of the Tropics, the sun is always north or south of them [at solar noon] and casts a shadow to the north or south even in the afternoon. We know that Eretz Yisrael is about 8° north of the Tropic of Cancer.

Unlike the Tosafos Yom Tov, Rabbi Avraham Bar Chiyya Hanasi רבי אברהם בר חייא הנשיא in the Sefer Ha’ibur ספר העבור, מאמר אּ׳ שער ט׳ defines chatzos as:

והרגע השני הוא עת היות בחצי השמים מפני שהיא מגעת במקום ההוא אל סוף גבהה ועליותה על המקום אשר זרחה עליו, ומכאן ואילך היא נוטה לערוב

The second moment is the time that the sun is in the center of the sky since at that point it reaches its highest point and its climb from its rising point, and from here forward it begins to dip to the evening.

This definition refers to the sun’s highest point / culmination. Though it does mention the “center of the sky” which can be understood to mean meridian transit, from the ראב״ח’s general context it appears clear that he is referring to the culmination.

I would like to express my thanks to my son Shai for his insights, ideas and calculations, Pinny Markowitz for his debugging work in contrasting the old NOAA implementation of solar noon calculations versus the new implementation, and to members of the Frum software developers #zmanim Slack channel for reviewing and making suggestions that improved this article.

Parsha Code Restored to the KosherJava Zmanim Calendar API

Sunrise CalendarIn the Parsha Code Removed from KosherJava Zmanim Calendar API article posted two years ago, I documented the removal of the parsha code from the KosherJava Zmanim API due to licensing issues. I would like to announce that thanks to Yechiel Paricher, the zmanim library now supports a clean LGPL implementation. Yechiel’s Jan 17, 2019 pull request that was a port of his C libzmanim code, was finally merged on August 22nd, and over the past day, the old formatting code for parshiyos was restored after being changed to work with the new code. The new code not only restores the old functionality, but adds support for the special parshiyos of Shekalim, Zachor, Parah and Hachodesh. It also added support for Shabbos Mevorchim and Machar Chodesh.

Is the Year 5780 Spelled תש”פ or תש”ף?

Luach Davar Be'ito 5780 Showing both תש"פ and תש"ף
Luach Davar Be’ito 5780 Showing both תש”פ and תש”ף
With the start of the new year 5780, I have been asked the following question numerous times. What is the proper Hebrew spelling of the Jewish year 5780 (2019/2020). Is it spelled תש”פ or תש”ף? This is the first time in 30 years that we have this “burning” question, with the previous one being 5750 (1989/1990) תש”נ or תש”ן. The question arises when the Hebrew spelling of the Jewish year ends with a Hebrew final form (also known as end, “ende” or straight (versus bent)) letter of מנצפ”ך. This happens in years ending with a 20, 40, 50, 80 or 90. According to the Academy of the Hebrew Language’s article שנת תש”ף regarding the spelling of the year, the final form תש”ף is the correct spelling. However, things are not that simple. The excellent 1,700+ page calendar לוח דבר בעתו / Luach Davar Be’ito published annually by Rabbi Mordechai Genut, straddles this by showing one form on the front cover and the other on the spine. In the introduction, Rabbi Genut writes:

ישבנו על המדוכה כיצד לכתוב תש״ף או תש״פ. כדי לרצות בעלי 2 הדעות, נקטנו (כאשר נקטנו בלוח ה׳תש״ן) שבשער הכריכה יכתב ה׳תש״פ ואילו בכריכת הגב יכתב ה׳תש״ף.

In the calendar he published an 11 page essay on the subject by Rabbi Yaakov Matalon who provides the following reasons to use the תש”פ version:

  • ראשי תיבות or Hebrew abbreviations only end with a final form letter if the abbreviation is typically read as a word such as רמב״ם ,רמב״ן and רי״ף. Abbreviations such as יוה״כ that are read as יום הכיפורים are always spelled ending in a non-final form letter. The Academy of the Hebrew Language reads the year as the proper word תָּשָׁ״ף, while many (most) disagree and read it as תאו-שין-פא.
  • The abbreviated year is not an abbreviation at all, but a number in its Hebrew format, and final form letters do not belong at the end of a number. This has been the tradition in writing and publishing Jewish books, where the non-final form spelling of page and chapter numbers has traditionally been used. This can be seen in the Talmud, Shulchan Aruch, Tehilim and other sefarim. There have been exceptions to this rule, but they are indeed exceptions. The same tradition is in place on most Jewish monuments.
  • In some cases the final form מנצפ”ך letters are considered to have a different numerical value. See the Sefer Haaruch on the אטב״ח entry (the Atbach / אטב״ח cipher should not be confused with the אתב”ש / Atbash cipher) and the Maharsha’s explanation on Rashi in Sukka 52b.
  • For kabbalistic reasons the Sefer Chassidim in chapter 1154 mentions that the end form of the letter ף is avoided where possible in tefilah (מוסף is an unavoidable exception). The Sefer Harokeach mentions the same concept in chapter 337 regarding the lack of any ף in Birkas Hamazon. This would apply to this year that ends in an 80, but not the other 4 examples every century.

Rabbi Matalon ends with:

מסקנתנו היא, שמִּבֵּין שני האֳפנים, עדיף לכתוב באות רגילה, לא-סופית: תש״פ, תש״צ. מכּל השיקולים נמצא שזה האופן העדיף. מצד שני, נראה שאין מקום לטענה שהכותב באות-סופית, תש״ף, תש״ץ וכדומה, טועה הוא. אופן כתיבה זה, למרות חסרונותיו, מקובל אצל רבים, ואין מי שרואה בו טעות.

In short, neither is incorrect, but the better of the two is the non-final form תש”פ.

Formatting the Year in the KosherJava Zmanim API

The HebrewDateFormatter class in the KosherJava zmanim library coded years ago produced the final form of תש״ף (with the exception of single character years such as the year 5050). This logic was included in all ports that I am aware of. With a recent commit, the option for formatting years ending in מנצפ״ך was added, and the default changed to produce the non-final form version of תש”פ. Detailed information can be seen in the HebrewDateFormatter API documentation.

Inflight Zmanim Calculations – Why So Complex?

Airline ZmanimDetermining zmanim times while on an airline flight is rather complex compared to calculating it for a fixed location. Some of the complexity involves:

  • Where you are currently located
  • Your Speed
  • Direction of travel / flightpath

The above 3 variables impact the calculation of what the zmanim are in your current location and where you will likely be when various zmanim are met.

Surprisingly, the hardest part is figuring out your current location. The shortest point between 2 points on the globe is the great circle route. Though it is the shortest path, airliners rarely fly this way. To take advantage of prevailing winds such as the Gulf Stream, or to avoid bad weather, airlines often fly much longer routes and as a passenger you often do not know exactly where you are.
Yes, the airline shows you a nice location map, but getting your exact coordinates from the map is not something that they usually supply. From a practical perspective, many people on domestic and short international flights will manage to figure out davening times by themselves. As a general rule of thumb, it is time for Shacharis when the sun rises and time for Maariv when it gets dark. Please keep in mind that most poskim are of the opinion that we use zmanim at sea level elevation, or ground level, and not the 37,000 foot elevation of the flight. This elevation results in a difference of approximately 20 minutes in sunrise and sunset times. Not sure when Mincha time is? Wait until shortly before sunset. Just keep in mind that when flying due east (such as a flight from NY to Israel), you are flying in the opposite direction as the sun and the time for davening is compressed. While you may expect sof zman krias shema to be 1/4 of the way into the day, in this case the davening window is compressed into a much shorter time. The real complexity is in flights that cross the halachic dateline, polar flights and to a lesser degree, cross-Atlantic and Pacific flights. This article will not delve into the halacha of in-flight zmanim, but solely on the technical aspects of figuring out the zmanim times.


Using your phone’s GPS to identify your in-flight location, or even a standalone GPS device will usually not work once you are away from cell towers (where your GPS no longer has the assistance of A-GPS). GPS signals are very weak and your GPS receiver typically does not have an antenna strong enough to pick up the signals in an aluminum or even newer carbon fiber composite airplane like the Airbus A350 and Boeing 787. To receive a signal, an external GPS receiver is usually required and assuming that you can get a signal (it helps if the external receiver is placed by a window), we can proceed. Note that while you would expect that the CFRP body of a Boeing 787 would allow for a much stronger signal than aluminum airliners, the graphite (and probably other materials) in the 787 CFRP in conjunction with the electrochromic windows on the 787, completely block GPS signals. It is this shielding as opposed to GPS jamming that blocks signals on El-Al 787s. In my testing with an external GPS device designed for aviation such as the Dual XGPS 160, the composite A350 and 787 both do not allow enough GPS signal through for a GPS receiver to provide a location fix. It may be surprising that it is easier to receive the weak GPS signal in an aluminum fuselage than a composite one, but keep in mind that carbon fiber is an excellent electrical conductor. Carbon fiber was used as the filament in Thomas Edison’s early light bulbs and does not let RF signals through and effectively acts as a Faraday cage. If you are able to receive a GPS signal, you can accurately calculate zmanim for your current location using tools such as the KosherJava zmanim map. Just change the latitude and longitude to what you see in your GPS in the URL While not an ideal solution, it does work. The same works for the rare airlines whose maps do show accurate GPS coordinates. Please note that Wi-Fi based geolocation will not work on your flight (in my testing it gave the location of the service provider headquarters).

Precalculated Flight Paths

Another way to figure out where you are located when in the air is via a precalculated flight path. This allows programs such as the Chai Tables Chai Air Times program for Windows and Android to work. However, they just calculate a great circle route between the origination and destination locations, something that is not very accurate. Currently MyZmanim’s Inflight charts are the most practical. These charts calculate the average path of the 5 previous flights in an attempt to better estimate your flight path and provide precalculated charts based on the time you take off. While this solution is currently the best that I am aware of, there are a number of issues with it. For one, much of the flight path over the oceans and Arctic that are provided by services such as FlightAware and others (that are used by MyZmanim) are just educated guesses for cross oceanic or Polar flights, since there are no ADS-B receivers in much of this area. As a matter of fact, this terrestrial ADS-B receiver free area comprises 75% of the globe. Even if the previous flight paths were accurate, your current flight may be very different. Flights such as the Cathay Pacific flights from the NY area to Hong Kong fly either east or west depending on wind conditions. MyZmanim deals with this scenario by providing both east and west maps (based on the in-flight map you would use one or the other) and indicating the portion of a flight-path that is unknown, but this is a warning that does nothing to help you accurately calculate zmanim.

ADS-B Receivers

Every airliner broadcasts its position, heading, altitude and speed using ADS-B. A technical user can bring an ADS-B-receiver with him on the flight and use it to retrieve the current information on his flight. This would work even when there are no ground based ADS-B receivers. This is something costly and beyond the technical ability of the vast majority of flyers.

The future

Due to issues in tracking flights that came to light with the disappearance of Malaysia Airlines Flight 370, satellite based ADS-B tracking is rolling out and will be mandated. This will make it much easier for services such as MyZmanim to provide more accurate pre-flight estimates, since services such as Flight-Aware will be able to provide more exact historical flight paths. For users who do have in-flight Wi-Fi, services such as FlightAware will be able to provide almost real time location (note that many services have a 5 minute delay and are not really real-time), allowing future Wi-Fi connected zmanim apps to tap into this and provide accurate zmanim.