A node.js module to find the timezone based on gps coordinates
Clone or download
Latest commit a2be2a3 Jan 5, 2019

README.md

node-geo-tz

npm version Build Status Dependency Status Test Coverage

The most up-to-date and accurate node.js geographical timezone lookup package. It's fast too!

Install

npm install geo-tz

Usage

    var geoTz = require('geo-tz')

    geoTz.preCache()  // optionally load all features into memory
    geoTz(47.650499, -122.350070)  // ['America/Los_Angeles']
    geoTz(43.839319, 87.526148)  // ['Asia/Shanghai', 'Asia/Urumqi']

API Docs:

As of Version 5, the API now returns a list of possible timezones as there are certain coordinates where the timekeeping method will depend on the person you ask.

geoTz(lat, lon)

Returns the timezone names found at lat, lon. The timezone names will be the timezone identifiers as defined in the timezone database. The underlying geographic data is obtained from the timezone-boudary-builder project.

This library does an exact geographic lookup which has tradeoffs. It is perhaps a little bit slower that other libraries, has a larger installation size on disk and cannot be used in the browser. However, the results are more accurate than other libraries that compromise by approximating the lookup of the data.

The data is indexed for fast analysis with automatic caching with time expiration (or optional an unexpiring cache of the whole world) of subregions of geographic data for when a precise lookup is needed.

geoTz.preCache()

Loads all geographic features into memory in an unexpiring cache. This has tradeoffs. More memory will be consumed and it will take a little longer before the program is ready to start looking up features, but future lookups will be a lot faster - especially for areas which haven't had a lookup in a while.

Limitations

This library is not intended to be used in the browser due to the large amount of files that are included to perform exact geographic lookups.

An Important Note About Maintenance

Due to the ever-changing nature of timezone data, it is critical that you always use the latest version of this package. If you use old versions, there will be a few edge cases where the calculated time is wrong. If you use greenkeeper, please be sure to specify an exact target version so you will always get PR's for even patch-level releases.