The algorithm's for calculating zmanim are pretty standardized, and
most use the US Naval Observatory algorithm. The main reason that you
might see discrepancy is that
1) How do you know that the calendar that you are comparing to uses
the exact location? One end of a city to the other can be pretty far
apart. Some calendars do not enter the exact location, but rather
round off the longitude/latitude to the nearest minute, or just use
the general zip code location
2) some show seconds, some round the number (up or down), while other
calendars just truncate the seconds.
3) some use elevation, some do not. This can lead to a sizable
difference.
4) errors/variations on part of different calendar implementations.
These are very easy to creep into code, even when trying to follow an
exact algorithm. For an example of this, see
http://www.kosherjava.com/2008/04/13/fix-to-noaa-sunrisesunset-algorithm/
The bottom line is, that you have to compare apples and Apples
(capitalization intentional :) ), something very hard to do in this
case.
You can go to
http://www.kosherjava.com/zmanim-project/zmanim-calendar-generator/
and zoom into your exact location, generate a calendar and compare,
the 2 algorithms (USNO and NOAA), and try it with, and without
elevation. You will need the ability to open an Excel file to read
this data. To see the exact elevation, longitude and latitude used for
zmanim on the iPhone, click on "About These Times" at the bottom of
the zmanim list in the iPhone. It would be nice if the Siddur gave an
option to show seconds, since you would be able to better compare
them.
Keep in mind that atmospheric temperature, barometric pressure and
humidity all affect sunrise/set. This is the reason that most
calendars have disclaimers, and the time should never be relied on
exactly. The only value in seconds would be to be able to properly
compare one calendar to another.
KosherJava
On Sep 28, 10:58 am, "
Joseph.Mezr...@gmail.com"