Skip to main content

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

Your data has issues

There is a problem

  • 2 entries must have dates in YYYY-MM-DD format
Reference Name Organisation Site address Point Site plan URL Hectares Ownership status Planning permission status Planning permission type Planning permission date Planning permission history Deliverable Minimum net dwellings Maximum net dwellings Hazardous substances Notes Start date Entry date End date
BFR W15 BFR W15 George Cox Shoes, Westfield Road, Wellingborough, NN8 3JR POINT(-0.704895 52.302309) http://www.nnjpdu.org.uk/site/assets/files/1416/bfr_w15.pdf 0.55 not-owned-by-a-public-authority permissioned full-planning-permission

Invalid date

31 76 Previously assessed through SHLAA as site 893. Part of the site for 45 Retirement flats was completed in 2018. (WP/16/00375/FUL). The other part for 31 apartments is currently under construction (WP/16/00492/FUL). No change. 2016-06-30 2024-04-01
BFR W42 BFR W42 Site G TCAAP - Alma St/Cambridge Street Backlands, Cambridge Street, Wellingborough, NN8 4DJ POINT(-0.690942 52.303443) http://www.nnjpdu.org.uk/site/assets/files/1416/bfr_w42.pdf 0.83 not-owned-by-a-public-authority not-permissioned full-planning-permission

Invalid date

50 50 Council owned site although currently the businesses on the site have a 10 year rent contract. The five dwelling units pursuant to WP/15/00092/FUL were completed in June 2016 and are located at the rear of the working mens club. The 5 self-contained residential units pursuant to WP/15/00094/FUL were completed in September 2016. Works relating to WP/16/00682/FUL commenced in August 2017 and was completed in 2019. No further progress has been made on this site in 2022. 2016-06-30 2024-04-01

How to fix this issue

Your dataset is missing the PermissionDate column.

The Brownfield land guidance explains how to fix the issue:

PermissionDate

How to improve North Northamptonshire 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