LMlmm·Jun 4, 2025
https://github.com/RomanIakovlev/timeshape . It's glorious.
In Mapping latitude and longitude to country, state, or cityRomanIakovlev
timeshape
Java2024–2025
RomanIakovlev / timeshape
timeshape
Java library to find timezone based on geo coordinates
2Distinct people
2Mentions
0Explicit recommenders
208GitHub stars
What to know before exploring
What it is
Java library to find timezone based on geo coordinates
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by week2 dated mentions
Observed mentions: 2024-10-30 11:06:24 UTC to 2025-06-04 03:25:59 UTC. Weeks start Monday, UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Oct 28 | 2024-10-28 00:00:00 UTC | 2024-11-04 00:00:00 UTC | 1 | 0 | 1 |
| Nov 4 | 2024-11-04 00:00:00 UTC | 2024-11-11 00:00:00 UTC | 0 | 0 | 0 |
| Nov 11 | 2024-11-11 00:00:00 UTC | 2024-11-18 00:00:00 UTC | 0 | 0 | 0 |
| Nov 18 | 2024-11-18 00:00:00 UTC | 2024-11-25 00:00:00 UTC | 0 | 0 | 0 |
| Nov 25 | 2024-11-25 00:00:00 UTC | 2024-12-02 00:00:00 UTC | 0 | 0 | 0 |
| Dec 2 | 2024-12-02 00:00:00 UTC | 2024-12-09 00:00:00 UTC | 0 | 0 | 0 |
| Dec 9 | 2024-12-09 00:00:00 UTC | 2024-12-16 00:00:00 UTC | 0 | 0 | 0 |
| Dec 16 | 2024-12-16 00:00:00 UTC | 2024-12-23 00:00:00 UTC | 0 | 0 | 0 |
| Dec 23 | 2024-12-23 00:00:00 UTC | 2024-12-30 00:00:00 UTC | 0 | 0 | 0 |
| Dec 30 | 2024-12-30 00:00:00 UTC | 2025-01-06 00:00:00 UTC | 0 | 0 | 0 |
| Jan 6 | 2025-01-06 00:00:00 UTC | 2025-01-13 00:00:00 UTC | 0 | 0 | 0 |
| Jan 13 | 2025-01-13 00:00:00 UTC | 2025-01-20 00:00:00 UTC | 0 | 0 | 0 |
| Jan 20 | 2025-01-20 00:00:00 UTC | 2025-01-27 00:00:00 UTC | 0 | 0 | 0 |
| Jan 27 | 2025-01-27 00:00:00 UTC | 2025-02-03 00:00:00 UTC | 0 | 0 | 0 |
| Feb 3 | 2025-02-03 00:00:00 UTC | 2025-02-10 00:00:00 UTC | 0 | 0 | 0 |
| Feb 10 | 2025-02-10 00:00:00 UTC | 2025-02-17 00:00:00 UTC | 0 | 0 | 0 |
| Feb 17 | 2025-02-17 00:00:00 UTC | 2025-02-24 00:00:00 UTC | 0 | 0 | 0 |
| Feb 24 | 2025-02-24 00:00:00 UTC | 2025-03-03 00:00:00 UTC | 0 | 0 | 0 |
| Mar 3 | 2025-03-03 00:00:00 UTC | 2025-03-10 00:00:00 UTC | 0 | 0 | 0 |
| Mar 10 | 2025-03-10 00:00:00 UTC | 2025-03-17 00:00:00 UTC | 0 | 0 | 0 |
| Mar 17 | 2025-03-17 00:00:00 UTC | 2025-03-24 00:00:00 UTC | 0 | 0 | 0 |
| Mar 24 | 2025-03-24 00:00:00 UTC | 2025-03-31 00:00:00 UTC | 0 | 0 | 0 |
| Mar 31 | 2025-03-31 00:00:00 UTC | 2025-04-07 00:00:00 UTC | 0 | 0 | 0 |
| Apr 7 | 2025-04-07 00:00:00 UTC | 2025-04-14 00:00:00 UTC | 0 | 0 | 0 |
| Apr 14 | 2025-04-14 00:00:00 UTC | 2025-04-21 00:00:00 UTC | 0 | 0 | 0 |
| Apr 21 | 2025-04-21 00:00:00 UTC | 2025-04-28 00:00:00 UTC | 0 | 0 | 0 |
| Apr 28 | 2025-04-28 00:00:00 UTC | 2025-05-05 00:00:00 UTC | 0 | 0 | 0 |
| May 5 | 2025-05-05 00:00:00 UTC | 2025-05-12 00:00:00 UTC | 0 | 0 | 0 |
| May 12 | 2025-05-12 00:00:00 UTC | 2025-05-19 00:00:00 UTC | 0 | 0 | 0 |
| May 19 | 2025-05-19 00:00:00 UTC | 2025-05-26 00:00:00 UTC | 0 | 0 | 0 |
| May 26 | 2025-05-26 00:00:00 UTC | 2025-06-02 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2 | 2025-06-02 00:00:00 UTC | 2025-06-09 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
2 sources> The naive way to do so would be via a static mapping of state to time zone but there are a few edge cases that preclude doing this
More than a few, state is really the wrong resolution here, US timezones follow counties and native reservations borders.
ZIP codes should probably be good enough but I'd be careful too. If your volume of addresses isn't too crazy, the robust way is to reverse geocode them and use a library that gets you the IANA identifier from timezone shapes.
https://github.com/RomanIakovlev/timeshape is maintained by a former coworker who could open source some of the work we did internally.
In Australia/Lord_Howe is the weirdest timezone