Skip to main content

This is a new service – your feedback will help us to improve it.

London Borough of Islington

Brownfield land

There is a problem

  • 66 entries must have valid URIs

P2017/2330/FUL

OrganisationURI
SiteReference
P2017/2330/FUL
SiteNameAddress
Elthorne Community Care Centre, 17-23 Beaumont Rise
GeoX
POINT(-0.125973 51.571544)
GeoY
POINT(-0.125973 51.571544)
SiteplanURL
http://mapapp.islington.gov.uk/mapthatol/Login.aspx?user=public&utm_content=stcms2.islington.gov.uk
Hectares
0.18
OwnershipStatus
owned-by-a-public-authority
PlanningStatus
permissioned
PermissionType
full-planning-permission
PermissionDate
2017-11-30
PlanningHistory

PlanningHistory must be a real URL

http://planning.islington.gov.uk/Northgate/PlanningExplorer/Generic/StdDetails.aspx?PT=Planning%20Applications%20On-Line&TYPE=PL/PlanningPK.xml&PARAM0=452382&XSLT=/Northgate/PlanningExplorer/SiteFiles/Skins/Islington/xslt/PL/PLDetailsSiteHistory.xslt&FT=Planning%20Application%20Details&PUBLIC=Y&XMLSIDE=/Northgate/PlanningExplorer/SiteFiles/Skins/Islington/Menus/PL.xml&DAURI=PLANNING
Deliverable
yes
NetDwellingsRangeFrom
27
NetDwellingsRangeTo
27
HazardousSubstances
Notes
Site plan is available on Islington interactive mapping website. Specific site is identifiable via SiteReference and SiteNameAddress attribute data.. The demolition of an existing two storey building and the erection of two five storey buildings to provide 9 x 2b and 1 x 1b wheelchair self-contained flats and 17 supported living units (C2 Use), together with communal rooms, staff/meeting facilities, cycle parking, private amenity space, refuse storage and a communal landscaped garden area.
FirstAddedDate
2018-12-19
LastUpdatedDate
2018-12-19
EndDate
2021-12-14

How to fix this issue

Your dataset is missing the PlanningHistory column.

The Brownfield land guidance explains how to fix the issue:

PlanningHistory

How to improve London Borough of Islington’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL