diff options
author | zverok <zverok.offline@gmail.com> | 2021-05-09 11:43:23 +0300 |
---|---|---|
committer | zverok <zverok.offline@gmail.com> | 2021-05-09 11:43:23 +0300 |
commit | 28a0a7d74f2912a4ff245a44e962a6ee7a0a89d5 (patch) | |
tree | b0d0ea7cb4537629b2db798dadf9099542dd2008 | |
parent | 959778fa7eeb8e97a4b9296fc2c4c4857b828167 (diff) | |
download | timezone-boundary-builder-28a0a7d74f2912a4ff245a44e962a6ee7a0a89d5.tar.gz |
README: Add Ruby library
-rw-r--r-- | README.md | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -35,6 +35,7 @@ A few common languages already have libraries with an API that can be used to lo | [Geo-Timezone](https://github.com/minube/geo-timezone) | php | | [timezonefinder](https://github.com/MrMinimal64/timezonefinder) | Python | | [lutz](https://github.com/ateucher/lutz) | R | +| [wheretz](https://github.com/zverok/wheretz) | Ruby | 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. |