diff options
| author | Evan Siroky <evan.siroky@yahoo.com> | 2021-05-18 09:08:25 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-05-18 09:08:25 -0700 |
| commit | 4e05cb681f519913cf847e4d1bf1621e759cb816 (patch) | |
| tree | b0d0ea7cb4537629b2db798dadf9099542dd2008 | |
| parent | 959778fa7eeb8e97a4b9296fc2c4c4857b828167 (diff) | |
| parent | 28a0a7d74f2912a4ff245a44e962a6ee7a0a89d5 (diff) | |
| download | timezone-boundary-builder-4e05cb681f519913cf847e4d1bf1621e759cb816.tar.gz | |
Merge pull request #98 from zverok/add-ruby-library
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. |