• Help
• Journey Planner
• How it works
• OSM
• Developers
• API
• Photomap
• Photo licensing

CycleStreets API (v2)

• Details for:

  * Introduction * Overview & how to specify the API key Cycle routing - plan new journey Cycle routing - retrieve Cycle routing - plan leisure (circular) route Journeys of user Isochrones - show Nearest point Batch routes matrix - create job Batch routes matrix - control job Batch routes matrix - job data Batch routes matrix - delete job Geocoder Photomap locations Photomap location Photomap categories Add photo Update photo Like photo Photo of the day Photomap tags Points of Interest (POIs) Points of Interest (POIs) - types Collisions data Collision report Collisions metadata Traffic counts data Popup cycleways - locations being implemented Popup cycleways - suggested LTNs: Modal filters LTNs: Streets LTN statistics Infrastructure locations Infrastructure location Infrastructure schema GPS tracks - add List galleries Retrieve a specified gallery Create a gallery Update a gallery User authenticate User create Map downloads Status API testing - multiple API testing - run one API testing - list of tests Add feedback API V1 documentation (deprecated)
• API overview
• Obtain API key
• Usage policy
• Uptime policy

LTNs: Modal filters

Modal filters (or 'point closures') are measures to restrict through-traffic. These facilitate safer streets for cycling and walking, as well as improving residential amenity.

Various types are shown see optional parameters.

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

This data should be considered beta level. We continue to refine the analysis to remove false-positives and to add additional types.

A maximum of 2,000 results are returned within the supplied bounding box. Geometries are simplified to 5 decimal places.

Coverage is currently the UK and Ireland.

Example

Example which retrieves modal filters in an area of central Cambridge.

https://api.cyclestreets.net/v2/advocacydata.modalfilters?bbox=0.101131,52.195807,0.170288,52.209719

Result:

{
    "type": "FeatureCollection",
    "features": [
        {
            "type": "Feature",
            "properties": {
                "osmId": 20826564,
                "osmType": "node",
                "modalfilter": "bollard",
                "name": "Abbey Street",
                "colour": "#888"
            },
            "geometry": {
                "type": "Point",
                "coordinates": [
                    0.13933,
                    52.20852
                ]
            }
        },
        {
            "type": "Feature",
            "properties": {
                "osmId": 862027210,
                "osmType": "node",
                "modalfilter": "gate",
                "name": "Adam and Eve Street",
                "colour": "#952"
            },
            "geometry": {
                "type": "Point",
                "coordinates": [
                    0.13329,
                    52.20547
                ]
            }
        },
        ...
    ]
}

Request parameters - required

bbox comma separated bounds: west,south,east,north

Boundaries of the data in degrees longitude / latitude.

Request parameters - optional

type One of the following values, or omit for all:

bollard

Bollards/gates within a street, that prevent through-traffic but allow walking and cycling

gate

Gaps within a street that form a short section of cycleway/walkway, similarly preventing through-traffic

gap

Streets abutting main roads but with only a cycleway/pavement between them

busgate

Bus gates, which allow bus and cycle access to particular areas

cyclewayfilter

No entry except cycles filters

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."
}