Brighton and Hove City Council

Brownfield land

There is a problem

• 210 entries must have valid coordinates

SHLAA0001

• SiteReference: SHLAA0001
• SiteNameAddress: Gas Works Site Boundary Road Brighton
• GeoX: POINT(-0.105411 50.816018)
• GeoY: POINT(-0.105411 50.816018)
• SiteplanURL: https://new.brighton-hove.gov.uk/sites/default/files/planning_bc_regen/policy/brownfield-sites/shlaa0001-gas-works-site-boundary-road-brighton.pdf
• Hectares: 2.34
• OwnershipStatus: mixed-ownership
• PlanningStatus: not-permissioned
• PlanningHistory: https://planningapps.brighton-hove.gov.uk/online-applications/applicationDetails.do?activeTab=summary&keyVal=PDG5TVDM0PA00|https://planningapps.brighton-hove.gov.uk/online-applications/applicationDetails.do?activeTab=summary&keyVal=ZZZR7SDMXE993|https://planningapps.brighton-hove.gov.uk/online-applications/applicationDetails.do?activeTab=summary&keyVal=R34OC8DM0TY00
• Deliverable: yes
• NetDwellingsRangeFrom: 340
• NetDwellingsRangeTo: 340
• HazardousSubstances: yes
• Notes: Application BH2021/04167 for 533 units under consideration. The Gas Works site is included within CPP1 policy DA2 Brighton Marina. The Gas Works Site is an existing Strategic Allocation for business floorspace 85 residential units and some ancillary retail. Land slopes to the south - opportunities for higher density development. Southern part of sites contains non-operational land formally used for storage and production of gas. The northern part of the site is occupied by 2 operational gas holders. The northern part of site is owned by Southern Gas Network plc and use would require decommissioning and removal of gasholders. Owners of site consider there is a reasonable prospect that residential development will take place on the land within 5 years
• FirstAddedDate: 2017-09-18
• LastUpdatedDate: 2022-12-05
• GeoX,GeoY:

  Geometry must use WGS84, OSGB or Mercator coordinates

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