aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRomanIakovlev <iakovlev@live.de>2018-04-14 15:35:10 +0200
committerGitHub <noreply@github.com>2018-04-14 15:35:10 +0200
commitee83fc871a8a04734d32b772394592b81be16d62 (patch)
tree6cd711205d6b87cb05d47bd7f9f042e8652452a2
parent4ea4aa63b8fd2d1d12cb7581d674952029eab73f (diff)
downloadtimezone-boundary-builder-ee83fc871a8a04734d32b772394592b81be16d62.tar.gz
Update README.md
Added Java-based data wrapper library to readme.
-rw-r--r--README.md1
1 files changed, 1 insertions, 0 deletions
diff --git a/README.md b/README.md
index c1e82f3..2e5372f 100644
--- a/README.md
+++ b/README.md
@@ -25,6 +25,7 @@ A few common languages already have libraries with an API that can be used to lo
| [tz-lookup](https://github.com/darkskyapp/tz-lookup/) | JavaScript (node.js and in browser) |
| [timezonefinder](https://github.com/MrMinimal64/timezonefinder) | Python |
| [GeoTimezone](https://github.com/mj1856/GeoTimeZone) | .NET |
+| [Timeshape](https://github.com/RomanIakovlev/timeshape) | Java |
Another common way to use the data for lookup purposes is to load the shapefile into a spatially-aware database. See this [blog post](https://simonwillison.net/2017/Dec/12/location-time-zone-api/) for an example of how that can be done.