From efb144efc5a742e466b974511f97e0b2d0d0ed75 Mon Sep 17 00:00:00 2001 From: Ed Freyfogle Date: Thu, 1 Aug 2019 22:34:09 +0200 Subject: [PATCH] update various OpenCage URLs OpenCage URL format changed --- doc/OPENCAGE.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/OPENCAGE.md b/doc/OPENCAGE.md index 4d854e8..724d2fa 100644 --- a/doc/OPENCAGE.md +++ b/doc/OPENCAGE.md @@ -1,6 +1,6 @@ # OpenCage -We now (since May 2018) recommend using [OpenCage](https://geocoder.opencagedata.com) as reverse geo-coding provider: their [pricing](https://geocoder.opencagedata.com/pricing) is attractive and they currently offer a free tier which allows up to 2,500 requests per day. +We now (since May 2018) recommend using [OpenCage](https://opencagedata.com) as reverse geo-coding provider: their [pricing](https://opencagedata.com/pricing) is attractive and they currently offer a free tier which allows up to 2,500 requests per day. Use the OpenCage API in Recorder simply by setting the `--geokey` option to the string `"opencage:"` with your API key concatenated to it. (Without the substring `opencage:` the Recorder falls back to using Google in order to maintain backwards-compatibility.) @@ -21,7 +21,7 @@ In order to use OpenCage with the Recorder using Lua, proceed as follows: ```bash luarocks install lua-opencage-geocoder ``` -2. Obtain an [OpenCage API key](https://geocoder.opencagedata.com/pricing), and make careful note of that. +2. Obtain an [OpenCage API key](https://opencagedata.com/pricing), and make careful note of that. 3. Before launching the Recorder, export the API key to the Recorder's environment ```bash export OPENCAGE_APIKEY="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"