Skip to main content
Brighton and Hove City Council

Brownfield land

There is a problem

  • 172 entries must be within England

SHLAA6099

SiteReference
SHLAA6099
SiteNameAddress
P&H House 106-112 Davigdor Road Hove
Deliverable
yes
HazardousSubstances
Hectares
0.09
MinNetDwellings
NetDwellingsRangeFrom
100
NetDwellingsRangeTo
57
OwnershipStatus
not-owned-by-a-public-authority
PermissionDate
2020-03-10
PermissionType
other
PlanningHistory
https://planningapps.brighton-hove.gov.uk/online-applications/applicationDetails.do?keyVal=QZ20KWDM0P900&activeTab=summary|https://planningapps.brighton-hove.gov.uk/online-applications/applicationDetails.do?keyVal=QW50XBDMJ2K00&activeTab=summary|https://planningapps.brighton-hove.gov.uk/online-applications/applicationDetails.do?keyVal=QTT29ADMHHJ00&activeTab=summary|https://planningapps.brighton-hove.gov.uk/online-applications/applicationDetails.do?keyVal=Q7NNCSDMJ8000&activeTab=summary|https://planningapps.brighton-hove.gov.uk/online-applications/applicationDetails.do?activeTab=summary&keyVal=Q2T9IZDM0K600|https://planningapps.brighton-hove.gov.uk/online-applications/applicationDetails.do?activeTab=summary&keyVal=PSXNYNDM0PC00|https://planningapps.brighton-hove.gov.uk/online-applications/applicationDetails.do?activeTab=summary&keyVal=OZV8VCDM0PA00|https://planningapps.brighton-hove.gov.uk/online-applications/applicationDetails.do?activeTab=summary&keyVal=ZZZR67DMXE414
PlanningStatus
permissioned
SiteplanURL
https://new.brighton-hove.gov.uk/sites/default/files/planning_bc_regen/policy/brownfield-sites/shlaa6099-ph-house-106-112-davigdor-road-hove.pdf
GeoX
POINT(-0.156689 50.831858)
GeoY
POINT(-0.156689 50.831858)
Notes
SHLAA call for sites 2017. Part of CPP1 Strategic Site Allocation 3. Commenced 202122. BH2019/01739 + BH2021/00391
OrganisationLabel
OrganisationURI
LastUpdatedDate
2022-12-05
FirstAddedDate
2017-09-21
EndDate
GeoX,GeoY

Geometry must be in England

How to improve Brighton and Hove City 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