• 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

Photomap tags

This API call returns a list of tags in the Photomap.

Tags are retrieved by the most popular, but then returned in order of tag name.

An example use of this can be seen on the Photomap tags page.

Example

This example retrieves the 5 most popular tags.

https://api.cyclestreets.net/v2/photomap.tags?key=registeredapikey&limit=5

Result:

[
    {
        "tag": "cambridge",
        "total": 1595
    },
    {
        "tag": "cycle",
        "total": 1243
    },
    {
        "tag": "cycling",
        "total": 1456
    },
    {
        "tag": "france",
        "total": 1914
    },
    {
        "tag": "germany",
        "total": 1181
    }
]

Request parameters - required

None.

Request parameters - optional

limit integer default 200

Limit the number of results.

match string

Match against this string. Useful for auto-complete. Matches are performed from the start of the string.

Response

JSON structure as per example above.

Error response

JSON object containing an error key and a text string.

Example error (text string will vary):

{
    "error": "The value of the supplied limit was not numeric."
}