The goal of this project is to produce a shapefile with the boundaries of the world's timezones using OpenStreetMap data.
The shapefiles are available for download in this project's releases. As of release 2018d shapefiles are available with or without oceans. Each shape or geojson object has a single attribute or property respectively called tzid. The tzid corresponds to the timezone name as defined in the timezone database (for example: America/Los_Angeles or Asia/Shanghai).
This project aims to stay up-to-date with all of the currently valid timezones that are defined in the timezone database. This project also will attempt to provide the most accurate possible boundaries of timezones according to community input.
The underlying data is downloaded from OpenStreetMap via the overpass turbo API. Various boundaries are assembled together to produce each zone with various geographic operations. In numerous edge cases arbitrary boundaries get created in various zones which are noted in the timezones.json file.
To maintain consistency with the timezone database, this project will only create a new release after the timezone database creates a new release. If there are no new timezones created or deleted in a timezone database release, then this project will only create a release if there have been changes performed to the boundary definitions of an existing zone within this project.
A few common languages already have libraries with an API that can be used to lookup the timezone name at a particular GPS coordinate. Here are some libraries that use the data produced by timezone-boundary-builder:
| Language | Library |
|---|---|
| C | ZoneDetect |
| Elixir | tz_world |
| Go | timezoneLookup |
| Java & Android | TimeZoneMap |
| Java | Timeshape |
| JavaScript (node.js only) | node-geo-tz |
| JavaScript (node.js and in browser) | timespace |
| JavaScript (node.js and in browser) | tz-lookup |
| .NET | GeoTimezone |
| php | Geo-Timezone |
| Python | timezonefinder |
| R | lutz |
| Ruby | wheretz |
Another common way to use the data for lookup purposes is to load the shapefile into a spatially-aware database. See this blog post for an example of how that can be done.
If the data in the releases are not sufficiently recent or you want to build the latest from master, it is possible to run the script to generate the timezones. However, due to the ever-changing nature of OpenStreetMap, the script should be considered unstable. The script frequently breaks when unexpected data is received or changes in OpenStreetMap cause validation issues. Please see the troubleshooting guide for help with common errors.
Run the script to generate timezones for all timezones.
node --max-old-space-size=8192 index.jsRun the script to generate timezones for only specified timezones.
node --max-old-space-size=8192 index.js --included_zones America/New_York America/ChicagoRun the script to generate timezones while excluding specified timezones.
node --max-old-space-size=8192 index.js --excluded_zones America/New_York America/ChicagoRun the script with custom working / output directories.
timezone-boundary-builder downloads boundaries from OpenStreetMap and places them in the ./downloads directory. It writes various intermediate files to ./working. All files included in releases are written to the ./dist directory.
If you want to use different directories, you can do so with the --downloads_dir, --dist_dir and --working_dir flags.
node --max-old-space-size=8192 index.js --downloads_dir ./downloads2 --dist_dir ./dist2 --working_dir ./working2Other command line flags
Other command line flags:
--help- show some basic usage information--skip_analyze_diffs- do not analyze differences between the current output and another version--skip_shapefile- do not create the shapefile from the geojson file--skip_validation- do not validate the time zone boundaries--skip_zip- do not zip the generated geojson files
There are three config files that describe the boundary building process. The osmBoundarySources.json file lists all of the needed boundaries to extract via queries to the Overpass API. The timezones.json file lists all of the timezones and various operations to perform to build the boundaries. The expectedZoneOverlaps.json file lists all timezones that are allowed to overlap each other and the acceptable bounds of a particular overlap.
The index.js file downloads all of the required geometries, builds the specified geometries, validates that there aren't large areas of overlap (other than those that are expected), analyzes the difference between the current output and the last release, outputs one huge geojson file, and finally zips up the geojson file using the zip cli and also converts the geojson to a shapefile using the ogr2ogr cli. The script has only been verified to run with Node.js 10 on the MacOS platform.
The code does query the publicly available Overpass API, but it self-throttles the making of requests to have a minimum of 4 seconds gap between requests. If the Overpass API throttles the download, then the gap will be increased exponentially.
The validation and difference analysis can take a really long time to compute. If these tasks are not needed, be sure to add the --skip_analyze_diffs and --skip_validation flags.
As of release 2020a, it is possible to run the script with the underlying input data that was used to build the timezone geometries at the time of the release. In the release files, the input-data.zip will have all of the necessary input data including the downloaded files from overpass, the timezones.json file and the osmBoundarySources.json file as well.
The data is almost completely comprised of OpenStreetMap data which is editable by anyone. There are a few guesses on where to draw an arbitrary border in the open waters and a few sparsely inhabited areas. Some uninhabited islands are omitted from this project. This project does include timezones in the oceans, but strictly uses territorial waters or Etc/GMT timezones instead of unofficially observed areas such as Exclusive Economic Zones.
Pull requests are welcome! Please follow the guidelines listed below:
Will be approved subject to code review.
Any change to the boundary of existing timezones must have some explanation of why the change is necessary. If there are official, publicly available documents of administrative areas describing their timezone boundary please link to them when making your case. All changes involving an administrative area changing their observed time should instead be sent to the timezone database.
A linting script will verify the integrity of the timezones.json, osmBoundarySources.json and expectedZoneOverlaps.json files. The script verifies if all needed overpass sources are properly defined and that there aren't any unneeded overpass downloads. If an operation to make a timezone boundary requires the use of a manual geometry, a description must be added explaining the operation. All expected zone overlaps must have a description.
Thanks to following people whose open-source and open-data contributions have made this project possible:
- All the maintainers of the timezone database.
- Eric Muller for constructing and maintaining the timezone shapefile at efele.net.
- The OpenStreetMap contributor Shinigami for making lots of edits in OpenStreetMap of various timezone boundaries.
- Björn Harrtell for all his work and help with jsts.
The code used to construct the timezone boundaries is licensed under the MIT License.
The outputted data is licensed under the Open Data Commons Open Database License (ODbL).