Donate using PayPal

CycleStreets API (v2)

  • Details for:
  • API overview
  • Obtain API key
  • Usage policy
  • Uptime policy

LTNs: Streets

This data shows whether each street is either:

  • An LTN / no-through traffic
  • A through-route (i.e. rat-running possible)
  • A through-route, but with traffic calming

The data shown here is the result of automated analysis of OpenStreetMap data.

This work is experimental at present, with known bugs. We continue to refine the analysis.

A maximum of 2,000 results are returned within the supplied bounding box.

Coverage is currently the UK and Ireland.

Example

Example which retrieves streets marked as LTN/rat-run/traffic-calmed in an area of central Cambridge.

https://api.cyclestreets.net/v2/advocacydata.ltns?bbox=0.101131,52.195807,0.170288,52.209719&zoom=15

Result:

{
    "type": "FeatureCollection",
    "features": [
        {
            "type": "Feature",
            "properties": {
                "name": "York Street",
                "ratrun": "no",
                "traffic_calmed": "n/a",
                "osmId": 3987016,
                "colour": "#8bb"
            },
            "geometry": {
                "type": "LineString",
                "coordinates": [
                    [
                        0.14235,
                        52.20378
                    ],
                    [
                        0.14086,
                        52.20662
                    ],
                    [
                        0.13978,
                        52.20758
                    ]
                ]
            }
        },
        {
            "type": "Feature",
            "properties": {
                "name": "New Street",
                "ratrun": "yes",
                "traffic_calmed": "no",
                "osmId": 3987006,
                "colour": "#d44"
            },
            "geometry": {
                "type": "MultiLineString",
                "coordinates": [
                    [
                        [
                            0.137,
                            52.20656
                        ],
                        [
                            0.13707,
                            52.20666
                        ],
                        [
                            0.13875,
                            52.20732
                        ]
                    ],
                    [
                        [
                            0.13875,
                            52.20732
                        ],
                        [
                            0.13931,
                            52.20746
                        ]
                    ],
                    [
                        [
                            0.13931,
                            52.20746
                        ],
                        [
                            0.13967,
                            52.20756
                        ],
                        [
                            0.13978,
                            52.20758
                        ]
                    ]
                ]
            }
        },
          ...
    ]
}

Request parameters - required

bbox comma separated bounds: west,south,east,north
Boundaries of the data in degrees longitude / latitude.
When a censuscode has been provided this parameter is not required and is ignored.

Request parameters - optional

censuscode char (9)
A string of exactly nine characters containing only digits and letters A-Z. Identifies a geographical region matching the corresponding census_code in the OS Boundary Line database (GB only). Codes for regions outside GB have been auto-generated by CycleStreets and no assurances can be made about how constant they remain over time. When provided any bbox parameter is ignored.
Browsers given this link will force a download using a filename of the form: LTN streets - <human readable area name> (<census code>) - CycleStreets.geojson
zoom int/float (number between 1 and 19)
The map zoom at which the photo location was set (which helps us determine the most appropriate lines to show).

Response

JSON structure as per example above.

Error response

JSON object containing an error key and a text string.

Example error (text string may vary):

{
    "error": "No bbox parameter was supplied."
}

We welcome your feedback, especially to report bugs or give us route feedback.

My comments relate to: *






Your comments: *
URL of page: * https://portsmouth.cyclestreets.net/api/v2/advocacydata.ltns/
How did you find out about CycleStreets?:
Your name:
Our ref: Please leave blank - anti-spam measure

* Items marked with an asterisk [*] are required fields and must be fully completed.