This dataset contains a list of Camden's housing stock; attributes include the property type, number of bedrooms and approximate location. Location is based on the centre point of the housing estate the property resides in; estates which contain less than twenty properties do not have a location to provide anonymity to the tenant.

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 vehicles part; some information has been added from the attendants part. Attendants and casualties 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 public health intelligence profile describes the trends and patterns in the prevalence of
diagnosed depression and anxiety in people aged 18 and over in Camden.

The neighbourhood profiles are 22 data profiles that, collectively, cover the whole borough of Camden. The profiles contain comprehensive, verifiable and up-to-date statistics from a variety of sources about the community characteristics, assets and strengths, challenges and needs in each neighbourhood. They are designed to help the Council, other statutory partners and the VCS understand what is being delivered in small areas and the resources that already exist in each area, and identify any gaps.

The neighbourhoods are composites of lower super output areas (LSOAs), which are smaller than wards. The neighbourhoods do not conform to administrative boundaries or electoral wards. Their borders are instead based on the actual way that residents identify with particular areas and how they really move about within certain localities.

Under the Local Government Transparency Code, local authorities must publish details of any contract, commissioned activity, purchase order, framework agreement and any other legally enforceable agreement with a value that exceeds £5,000.

This dataset contains the parking bays location in the London Borough of Camden. A parking bay consists of a number of parking spaces, therefore individual parking spaces cannot be identified in this dataset, however the attribution includes the approximate length of the parking bay in metres, and the approximate number of spaces in the parking bay. Other attribution includes restriction type, times of operation, maximum stay, tariff, road name and CPZ (Controlled Parking Zone). The Easting and Northing (and Longitude and Latitude) attributes are automatically calculated based on an arbitrary node along the polyline geometry of the parking bay; the WKT (Well Known Text) attributes can be used to redraw the full extent of each parking bay using a GIS (Geographic Information System).

This dataset contains the Camden, Barnet, Brent, City of London, City of Westminster, Haringey and Islington extract of the OS Open Names dataset.

This view shows planning applications received in the last seven days by the London Borough of Camden. It updates daily.

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 building in the OS Open Map-Local product. Attribution includes application number, development address, development description, registered date, decision date and case officer.

The data shows property and bid information for homes advertised by the London Borough of Camden on the Home Connections website.

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.