Skip to main content

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

Gravesham Borough Council

Brownfield land

There is a problem

  • You have 4 brownfield land sites outside of your boundary

Entity: 1701232

dataset
brownfield-land
end-date
null
entity
1701232
entry-date
2023-03-31
geojson
geometry
name
EDC/16/0004
organisation-entity
149
point
POINT(0.333916 51.446905)
prefix
brownfield-land
quality
authoritative
reference
EDC/16/0004
start-date
2017-12-20
typology
geography
planning-permission-status
permissioned
site-address
Northfleet Embankment West
minimum-net-dwellings
532
planning-permission-type
outline-planning-permission
planning-permission-date
2018-06-08
planning-permission-history
http://applications.ebbsfleetdc.org.uk/online-applications/applicationDetails.do?activeTab=relatedCases&keyVal=KH2EC1HP02600
maximum-net-dwellings
532
ownership-status
not-owned-by-a-public-authority
hectares
31.14
site-plan-url
http://applications.ebbsfleetdc.org.uk/online-applications/applicationDetails.do?activeTab=map&keyVal=KH2EC1HP02600
deliverable
yes
notes
Under construction. Outline application for a mixed development and comprising up to 532 Homes, related car parking and landscaping (C3); up to 46,000 sq m Employment Floorspace, related car parking, servicing and landscaping (B1/B2/B8); Mixed Use Neighbour Centre comprising mix of: up to 850 sq m retail/cafe/takeaway floor space (A1/A2/A3/A5); residential uses (C3); community centre (D1); up to 1,000 sq m clinic/health centre (D1) and related car parking and landscaping; Riverside Food and Drink Uses comprising up to 500 sq m of pub or food and drink uses (A3/A4); Public Open Space including riverside promenade, public park with equipped play areas and playing field with shared public/school use and wildlife corridors;. http://applications.ebbsfleetdc.org.uk/online-applications/applicationDetails.do?activeTab=constraints&keyVal=KH2EC1HP02600

How to improve Gravesham Borough Council’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