Skip to main content
Barnsley Metropolitan Borough Council

Brownfield land

There is a problem

  • 49 entries must have valid URIs

TCDS3

SiteReference
TCDS3
SiteNameAddress
The Seam/Courthouse Campus
Deliverable
yes
HazardousSubstances
Hectares
4.6
MinNetDwellings
NetDwellingsRangeFrom
57
NetDwellingsRangeTo
57
OwnershipStatus
owned-by-a-public-authority
PermissionDate
2021-12-17
PermissionType
other
PlanningHistory

PlanningHistory must be a real URL

PlanningStatus
permissioned
SiteplanURL
https://www.barnsley.gov.uk/services/planning-and-buildings/local-planning-and-development/brownfield-land-register/
GeoX
POINT(-1.479683 53.556032)
GeoY
POINT(-1.479683 53.556032)
Notes
This site is a Local Plan allocated town centre development site. Local Plan policy (BTC22) Development site 3, allows for mixed use developments which could include, education and community facilities, residential (including live-work units), offices and developments designed to support digital industries. Any development proposals would need to support the Digital Campus and it's ambitions for growth. Part of the site is in private ownership and is the subject of prior notification for change of use from commercial offices to 39 dwellings. This development is under construction. https://www.barnsley.gov.uk/services/planning-and-buildings/local-planning-and-development/our-local-plan/barnsleys-local-plan/
OrganisationLabel
OrganisationURI
LastUpdatedDate
2024-10-25
FirstAddedDate
2017-08-02
EndDate

How to fix this issue

Your dataset is missing the PlanningHistory column.

The Brownfield land guidance explains how to fix the issue:

PlanningHistory

Enter links to any web pages that give information on the site’s planning history (include the “http://” or “https://” prefix). Fields in this column can contain more than one link, as long as you separate multiple links with the pipe character (‘|’). You can leave this field blank.

How to improve Barnsley Metropolitan 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