Your data has issues
There is a problem
- 4 rows are missing a tree-preservation-order
| Reference | Name | Tree preservation order | Uprn | Address text | Point | Geometry | Notes | Felled date | Entry date | Start date | End date |
|---|---|---|---|---|---|---|---|---|---|---|---|
| TPO_point_ref_1735 |
Missing value |
0 | , 0 , | POINT (0.014066 51.574358) | end_date is generic and so not correct | 2025-03-20 | 2025-10-30 | 2025-03-20 | |||
| TPO_point_ref_1736 |
Missing value |
0 | , 0 , | POINT (0.014047 51.574381) | end_date is generic and so not correct | 2025-03-20 | 2025-10-30 | 2025-03-20 | |||
| TPO_point_ref_1737 |
Missing value |
0 | , 0 , | POINT (0.014031 51.574410) | end_date is generic and so not correct | 2025-03-20 | 2025-10-30 | 2025-03-20 | |||
| TPO_point_ref_1738 |
Missing value |
0 | , 0 , | POINT (0.014001 51.574440) | end_date is generic and so not correct | 2025-03-20 | 2025-10-30 | 2025-03-20 |
How to fix this issue
Your dataset is missing the tree-preservation-order column.
The Tree guidance explains how to fix the issue:
tree-preservation-order
The reference for the tree preservation order that affects this tree.
Example: TPO1
How to improve London Borough of Waltham Forest’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