-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No moonrise when official almanac states there is (ditto sunrise) #88
Comments
Have a similar issue, a missing moonset in Salt Lake City. To reproduce:
Running this results in:
This seems incorrect, since there was a moonset reported by timeanddate.com and pyephem dawn, dusk, moonrise and moonset calculations for the rest of May look good, just this oddity. |
Similar problem, missing moonrise at Russia/Moscow 2024 January 5 Minimal repro:
Im using Python 3.11.7 Every other moonrise in this month looks correct according to timeanddate.com The following dates also produce this error: |
Similar problem, no sunset in a very specific location in Texas on Jan 10, 2025: now = datetime.datetime(2025, 1, 10, tzinfo=timezone.utc)
lat = 28.5 # and more specific
lon = -99.7 # and more specific
observer = LocationInfo("Example", "World", "UTC", lat, lon).observer
sun(observer, now)
# ValueError("Unable to find a sunset time on the date specified") It does not fail for any other dates in January, or for less specific coords (I tried 28, -99). It does fail for more specific coords. Seems to be about a ~100 square mile area that's problematic. |
NOTE: The above times are New Zealand Daylight Saving Time (New Zealand Standard Time +01:00) in operation at these lunar events.
In the absence of a moonrise or moonset, Astral.moon appears to returns None (when a moonrise (moonset) is found but is not for the required dat) - or a ValueError if no moonrise(moonset) is found.
Hope this is useful.
The text was updated successfully, but these errors were encountered: