• 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

Popup cycleways - suggested

Suggested popup cycleway infrastructure, arising from research work at Leeds University.

This API represents the same data in the Rapid Cycleway Prioritisation Tool.

Example

Example which retrieves suggested popup cycleways locations in the area of Cambridge.

https://api.cyclestreets.net/v2/advocacydata.popupcycleways.suggested?bbox=0.081282,52.203872,0.205564,52.215969

Result:

{
    "type": "FeatureCollection",
    "features": [
        {
            "type": "Feature",
            "id": 95,
            "properties": {
                "name": "Newmarket Road",
                "ref": "A1134",
                "status": "Top ranked new cycleways",
                "mean_cycling_potential": 326,
                "spare_lane": false,
                "estimated_width": "10-15 m",
                "length_(m)": 804,
                "group_id": 57,
                "speed_limit": "30 mph"
            },
            "geometry": {
                "type": "MultiLineString",
                "coordinates": [
                    [
                        [
                            0.16277,
                            52.21229
                        ],
                        [
                            0.16275,
                            52.21233
                        ],
                        [
                            0.16274,
                            52.21236
                        ],
                        [
                            0.16275,
                            52.21241
                        ],
                        ...
                    ]
                ]
            }
        },
        ...
    ]
}

Request parameters - required

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

Boundaries of a region.

Request parameters - optional

None.

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