diff options
| author | Evan Siroky <evan.siroky@yahoo.com> | 2018-07-30 11:34:07 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-07-30 11:34:07 -0700 |
| commit | 188855d82534e6fa05f0faabd712b1b84235b376 (patch) | |
| tree | 59fc793581ae4c752443e2a57eae8a8fe5c805ae | |
| parent | 283ebbcf4191584b36354f5f71bd3409793e715d (diff) | |
| download | timezone-boundary-builder-188855d82534e6fa05f0faabd712b1b84235b376.tar.gz | |
Add lutz lookup library to README
| -rw-r--r-- | README.md | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -28,6 +28,7 @@ A few common languages already have libraries with an API that can be used to lo | [GeoTimezone](https://github.com/mj1856/GeoTimeZone) | .NET | | [Geo-Timezone](https://github.com/minube/geo-timezone) | php | | [timezonefinder](https://github.com/MrMinimal64/timezonefinder) | Python | +| [lutz](https://github.com/ateucher/lutz) | R | 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. |