From 14c13f1007320b80edb031cc1d78f72159c4e323 Mon Sep 17 00:00:00 2001 From: Robin Date: Tue, 1 Aug 2017 19:22:09 +0100 Subject: [PATCH] Clarify get request (#3115) As per a query on the forum I have clarified the instructions for checking valid bus directions --- source/_components/sensor.uk_transport.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/sensor.uk_transport.markdown b/source/_components/sensor.uk_transport.markdown index 62358de3f74..759f37f982d 100644 --- a/source/_components/sensor.uk_transport.markdown +++ b/source/_components/sensor.uk_transport.markdown @@ -81,7 +81,7 @@ stop you're interested in 3. Tick the 'map data' layer, and wait for clickable objects to load 4. Click the bus stop node to reveal its tags on the left -The `destination` must be a valid location returned by the transportAPI query. Valid destinations can be checked by performing a GET query to `/uk/bus/stop/{atcocode}/live.json` in the [API reference webpage](https://developer.transportapi.com/docs?raml=https://transportapi.com/v3/raml/transportapi.raml##bus_information). A bus sensor is added in the following `configuration.yaml` file entry: +The `destination` must be a valid location in the "direction" field returned by a GET query to `/uk/bus/stop/{atcocode}/live.json` as described in the [API reference webpage](https://developer.transportapi.com/docs?raml=https://transportapi.com/v3/raml/transportapi.raml##bus_information). A bus sensor is added in the following `configuration.yaml` file entry: ```yaml # Example configuration.yaml entry for multiple sensors