Re: [tz] Request to add entry to "Programmatic interfaces that map geographical coordinates"
The package tz-lookup and geo-tz are independent of each other. As far as I know, the major difference between the two is the data source that is used. geo-tz is released under the MIT license. Feel free to link to the timezone tag. Although in my opinion a lot of the packages aren't the best because they don't get updated frequently enough with changes to the timezone db. Evan On Saturday, 10 December 2016, 12:02, Paul Eggert <eggert@cs.ucla.edu> wrote: Evan Siroky via tz wrote:
I maintain a node.js library that looks up the timezone name at a GPS coordinate. The project is called geo-tz: https://www.npmjs.com/package/geo-tz My library uses data produced from timezone-boundary-builder. Can you please add an entry to tz-link.html for my project?
What's a good way to do that? Currently tz-link.htm says: <li>The <a href="https://www.npmjs.com/package/tz-lookup">tz-lookup module</a> for <a href="https://nodejs.org/en/">Node.js</a> is in the public domain.</li> How should the relationship between tz-lookup and geo-tz be described? Also, what's the license for geo-tz? It is not obvious from its web page. In looking at <https://www.npmjs.com/browse/keyword/timezone> I see several more Node.js time zone packages that seem relevant. Perhaps we should link to that page?
Thanks for the extra info. I installed the attached, which I hope is good enough.
The header above the section says "Programmatic interfaces that map geographical coordinates via tz_world to tz regions include:". The geo-tz package no longer uses data from tz_world. So maybe you can remove the reference to tz_world and say "... geographic coordinates to tz regions include:" On Monday, 12 December 2016, 10:58, Paul Eggert <eggert@cs.ucla.edu> wrote: Thanks for the extra info. I installed the attached, which I hope is good enough.
geo-tz uses data produced from the timezone-boundary-builder project: https://github.com/evansiroky/timezone-boundary-builder On Monday, 12 December 2016, 18:03, Paul Eggert <eggert@cs.ucla.edu> wrote: Evan Siroky wrote:
The geo-tz package no longer uses data from tz_world.
Where does it get its data from?
I keep a bit of an eye on the Node.js ecosystem for tz-related projects, and I also recommend not linking to the “timezone” keyword page on npmjs.com Many projects listed on that page are API wrappers of the moment-timezone project, and some are integration points for frontend frameworks. Many others are small scripts written by people who clearly haven’t encountered the ambiguities and ever-changing definitions that happen when dealing with time zones. For example, I know of one package that simply returns the UTC offset of a named time zone, but completely fails to account for daylight saving time. A low barrier to entry means digging a bit to find the good stuff. When it comes to the Node ecosystem, a curated list of known high-quality projects is always better than linking to a keyword search.
On 13 Dec 2016, at 4:20 AM, Evan Siroky via tz <tz@iana.org> wrote:
The package tz-lookup and geo-tz are independent of each other. As far as I know, the major difference between the two is the data source that is used. geo-tz is released under the MIT license.
Feel free to link to the timezone tag. Although in my opinion a lot of the packages aren't the best because they don't get updated frequently enough with changes to the timezone db.
Evan
On Saturday, 10 December 2016, 12:02, Paul Eggert <eggert@cs.ucla.edu> wrote:
In looking at <https://www.npmjs.com/browse/keyword/timezone <https://www.npmjs.com/browse/keyword/timezone>> I see several more Node.js time zone packages that seem relevant. Perhaps we should link to that page?
participants (3)
-
Evan Siroky -
Gilmore Davidson -
Paul Eggert