This dataset contains previous/historic parking suspensions from 1st January 2020.

This dataset contains Camden's Controlled Parking Zones (CPZ)

Installed and proposed/planned cycle hangars in Camden

This dataset contains transactional penalty charge notice data held in the London Borough of Camden's parking management system; inclusive of penalty charge notices issued by Civil Enforcement Officers on street and those issued by Civil Enforcement Officers via CCTV. Attribution includes contravention code, ticket type, street, parking restriction, vehicle category and status of case.

Where possible, the approximate location of the PCN has been captured. The 'Spatial Accuracy' column can be used to determine what level of location has been captured:

Civil Enforcement Officer GPS Location = the GPS location reported by the CEO's handheld device
Fixed CCTV Camera = the location of the CCTV camera, this could be many metres from the vehicle in contravention
Unknown = No location has been captured

Cycling in Camden is becoming ever more popular with the introduction of safe, convenient and protected routes. There are several cycle counters in Camden which provide counts of cyclists along these routes.

This dataset contains traffic count surveys stored in 50 Microsoft Excel files.

Cycling in Camden is becoming ever more popular with the introduction of safe, convenient and protected routes. There are several cycle counters in Camden which provide counts of cyclists along these routes.

Cycling in Camden is becoming ever more popular with the introduction of safe, convenient and protected routes. There are several cycle counters in Camden which provide counts of cyclists along these routes.

This dataset contains traffic count surveys stored in 47 Microsoft Excel files.

The Parking Bay dataset was created in the open data portal several years ago and only exports the data as point GeoJSON.

This Python3 Script downloads Camden Council parking bay data as CSV and converts it into line/polygon GeoJSON using either the EPSG:27700 or EPSG:4326 projection (see line #25); the projection clause is not included in the file so may need to be specified when importing the file into a GIS.

The script file will need renaming from .txt to .py.