This dataset contains road collisions in Camden dating back to 2005. Data is provided by TfL (Transport for London) on an annual basis in three parts – this is the attendant part, casualties and vehicles are available on the open data platform as separate datasets and they can all be joined together using the Reference column. If joined, where multiple attendants/casualties/vehicles exists for one Accident Reference there will be multiple records for the same accident. To avoid anomalies it is suggested any data analysis undertaken should use three years of data.

This dataset contains planning applications in the London Borough of Camden dating back to 01/01/2010. Planning application extents are captured against the OS MasterMap product, due to licensing restrictions with this product, this dataset is represented as point geometry, located to the nearest postcode (derived from the OS Code-Point Open product). Attribution includes application number, development address, development description, registered date, decision date and case officer.

This dataset contains road collisions in Camden dating back to 2005. Data is provided by TfL (Transport for London) on an annual basis in three parts – this is the casualties part, attendants and vehicles are available on the open data platform as separate datasets and they can all be joined together using the Reference column. If joined, where multiple attendants/casualties/vehicles exists for one Accident Reference there will be multiple records for the same accident. To avoid anomalies it is suggested any data analysis undertaken should use three years of data.

This dataset contains planning applications in the London Borough of Camden dating back to 01/01/2010. Planning application extents are captured against the OS MasterMap product, due to licensing restrictions with this product, this dataset is represented as point geometry, located to the nearest postcode (derived from the OS Code-Point Open product). Attribution includes application number, development address, development description, registered date, decision date and case officer.

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

This data contains the centroid (central point) of each Camden Neighbourhood profile. When displayed on a map, the centroid can be clicked to reveal the URL to the corresponding neighbourhood profile document.

DWP Claimant Count unemployment measure, combining Jobseekers Allowance (JSA) claimants and Universal Credit claimants who are actively seeking work. Latest month (provisional) and revised previous month (final) data.

This dataset contains the National Statistics Postcode Lookup (NSPL) for the United Kingdom. The NSPL relates current postcodes to a range of current statutory administrative, electoral, health and other statistical geographies via ‘best-fit’ allocation from the 2011 Census output areas. It supports the production of area based statistics from postcoded data. The NSPL is produced by ONS Geography, which provides geographic support to the Office for National Statistics (ONS) and geographic services used by other organisations.

This public health intelligence profile describes the trends and patterns in the prevalence of diagnosed serious mental illness in people aged 18 and over in Camden.

Containing all registered planning applications where a decision has not been made. Planning application extents are captured against the OS MasterMap product, due to licensing restrictions with this product, this dataset is represented as point geometry, located to the nearest postcode (derived from the OS Code-Point Open product). Attribution includes application number, development address, development description, registered date, decision date and case officer.