• 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

LTN statistics

This data shows statistics about the proportion of streets in each area according to whether they are:

• 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.

Results are provided for a maximum of 10,000 areas within the supplied bounding box. Alternatively a census code can be provided to give the results for a particular area.

Coverage is currently the UK and Ireland.

Example

Example which retrieves statistics in an area of central Cambridge.

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

Result:

{
	"type": "FeatureCollection",
	"features": [
		{
			"type": "Feature",
			"properties": {
				"name": "Abbey Ward",
				"area_description": "District Ward",
				"census_code": "E05013050",
				"dataUrl": "https://api.cyclestreets.net/v2/advocacydata.ltns?key=&censuscode=E05013050",
				"noThroughStreetLengthPercent": 77,
				"throughStreetLengthPercent": 5,
				"calmedThroughStreetLengthPercent": 1,
				"mainRoadLengthPercent": 17,
				"noThroughStreetLengthMetres": 36872,
				"throughStreetLengthMetres": 2342,
				"calmedThroughStreetLengthMetres": 259,
				"mainRoadLengthMetres": 7950
			},
			"geometry": {
				"type": "MultiPolygon",
				"coordinates": [
					[
						[
							[
								0.179892752959072,
								52.2022378537638
							],
							[
								0.177381089988381,
								52.2032490729808
							],
							...,
							[
								0.179892752959072,
								52.2022378537638
							]
						]
					]
				]
			}
		},
		...
	]
} 

Request parameters - required

All parameters are optional.

Request parameters - optional

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

Boundaries of the data in degrees longitude / latitude.

type One of: 'wards', 'districts', 'highwayauthorities'.

Based on the area_description fields in the OS Boundary Line database. Wards includes wards and electorial divisions. All types are included when this parameter is omitted.

wards

Area descriptions matching:

• District Ward
• London Borough Ward
• Metropolitan District Ward
• Unitary Authority Ward
• Unitary Authority Electoral Division

districts

Area descriptions matching:

• District
• London Borough
• Metropolitan District
• Unitary Authority
• Ireland County
• Northern Ireland District

highwayauthorities

Area descriptions matching:

• Unitary Authority
• Metropolitan District
• County
• Greater London Authority
• Ireland County
• Northern Ireland District

zoom int/float (number between 1 and 19)

Geometries are simplified to reduce unnecessary detail at the given map zoom level.

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