Tree preservation order
There is a problem
- documentation-url column is missing values
Trees at Land At Brookdene 71 Holden Road, London, N12 7DR And Between The Dollis Brook And 51 To 71 Holden Road, London, N12 Tree Preservation Order 2015
- reference
- 15/TPO/004
- name
- Trees at Land At Brookdene 71 Holden Road, London, N12 7DR And Between The Dollis Brook And 51 To 71 Holden Road, London, N12 Tree Preservation Order 2015
- documentation-url
- document-url
- made-date
- 2015-10-20
- confirmed-date
- 2016-01-21
- notes
- organisation
- entry-date
- 2025-06-01
- start-date
- 2015-10-20
- end-date
How to fix this issue
Your dataset is missing the documentation-url column.
The Tree preservation order guidance explains how to fix the issue:
documentation-url
The URL of the webpage on your website that introduces the document.
Each document should be linked to from a documentation webpage that includes a short description of the data and the document you’re linking to. Each tree preservation order should have a unique URL. This means you can create a separate page for each one, or you could list several on one page. If you do that, there must be a separate anchor link (fragment identifier) for each one.
This means each section of your page should have its own URL. Most publishing systems will allow you to use a hashtag to create the identifiers for each tree preservation order you list - as in the examples shown.
Examples:
One tree preservation order per page:
http://www.LPAwebsite.org.uk/data/treepreservationorders/smithroad
More than one tree preservation order per page with an anchor link for each one:
http://www.LPAwebsite.org.uk/data/treepreservationorders#smithroad
http://www.LPAwebsite.org.uk/data/treepreservationorders#broadhousepark
How to improve London Borough of Barnet’s data
- Fix the errors indicated
- Use the check service to make sure the data meets the standard
- Publish the updated data on the endpoint URL