You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: application/templates/pages/guidance/specifications/tree-preservation-order.md
+36-38
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
**Last updated:**20 November 2024<br/>
1
+
**Last updated:**8 January 2025<br/>
2
2
3
3
---
4
4
@@ -100,12 +100,6 @@ Write in YYYY-MM-DD format.
100
100
101
101
Example: `2022-12-20`
102
102
103
-
### start-date
104
-
105
-
The date that the tree preservation order came into force, written in `YYYY-MM-DD` format.
106
-
107
-
Example: `1984-03-28`
108
-
109
103
### confirmed-date
110
104
111
105
The date a tree preservation order is confirmed as being in effect, and the tree or trees are fully protected. This comes after all objections have been considered.
@@ -114,16 +108,6 @@ Write in YYYY-MM-DD format.
114
108
115
109
Example: `2022-12-20`
116
110
117
-
### end-date
118
-
119
-
Where the tree preservation order is [revoked](https://standards.planning-data.dev/principles/#we-shouldn%E2%80%99t-delete-entries-in-a-register), this should be the date that it was no longer in effect, written in `YYYY-MM-DD` format. If the TPO is still active, leave this field blank. If the tree has been felled, use the felled-date field.
120
-
121
-
Example: `1999-01-20`
122
-
123
-
### felled-date
124
-
125
-
If applicable, the date that the tree was felled, written in `YYYY-MM-DD` format. If the tree hasn't been felled, leave this field blank.
126
-
127
111
### entry-date
128
112
129
113
The date the entity was last updated.
@@ -134,6 +118,18 @@ Write in `YYYY-MM-DD` format.
134
118
135
119
Example: `2022-12-20`
136
120
121
+
### start-date
122
+
123
+
The date that the tree preservation order came into force, written in `YYYY-MM-DD` format.
124
+
125
+
Example: `1984-03-28`
126
+
127
+
### end-date
128
+
129
+
Where the tree preservation order is [revoked](https://standards.planning-data.dev/principles/#we-shouldn%E2%80%99t-delete-entries-in-a-register), this should be the date that it was no longer in effect, written in `YYYY-MM-DD` format. If the TPO is still active, leave this field blank. If the tree has been felled, use the felled-date field.
130
+
131
+
Example: `1999-01-20`
132
+
137
133
---
138
134
139
135
Tree preservation zone dataset
@@ -195,6 +191,16 @@ If you’re providing geometry in a GeoJSON, GML or Geopackage, use the associat
195
191
196
192
Optional text on how this data was made or produced, or how it can be interpreted.
197
193
194
+
### entry-date
195
+
196
+
The date the entity was last updated.
197
+
198
+
If the entity has never been updated, enter the same date as start-date.
199
+
200
+
Write in `YYYY-MM-DD` format.
201
+
202
+
Example: `2022-12-20`
203
+
198
204
### start-date
199
205
200
206
The date that the tree preservation order came into force, written in `YYYY-MM-DD` format.
@@ -207,15 +213,6 @@ If applicable, the date that the tree preservation order was revoked, written in
207
213
208
214
Example: `1999-01-20`
209
215
210
-
### entry-date
211
-
212
-
The date the entity was last updated.
213
-
214
-
If the entity has never been updated, enter the same date as start-date.
215
-
216
-
Write in `YYYY-MM-DD` format.
217
-
218
-
Example: `2022-12-20`
219
216
220
217
---
221
218
@@ -297,18 +294,6 @@ Example: `100 High Street, Bath`
297
294
298
295
Optional text on how this data was made or produced, or how it can be interpreted.
299
296
300
-
### start-date
301
-
302
-
The date from which the tree preservation order affects the tree, written in `YYYY-MM-DD` format.
303
-
304
-
Example: `1984-03-28`
305
-
306
-
### end-date
307
-
308
-
Where the tree preservation order is [revoked](https://standards.planning-data.dev/principles/#we-shouldn%E2%80%99t-delete-entries-in-a-register), this should be the date that it was no longer in effect, written in `YYYY-MM-DD` format. If the TPO is still active, leave this field blank. If the tree has been felled, use the felled-date field.
309
-
310
-
Example: `1999-01-20`
311
-
312
297
### felled-date
313
298
314
299
If applicable, the date that the tree was felled, written in `YYYY-MM-DD` format. If the tree hasn't been felled, leave this field blank.
@@ -323,6 +308,19 @@ Write in `YYYY-MM-DD` format.
323
308
324
309
Example: `2022-12-20`
325
310
311
+
### start-date
312
+
313
+
The date from which the tree preservation order affects the tree, written in `YYYY-MM-DD` format.
314
+
315
+
Example: `1984-03-28`
316
+
317
+
### end-date
318
+
319
+
Where the tree preservation order is [revoked](https://standards.planning-data.dev/principles/#we-shouldn%E2%80%99t-delete-entries-in-a-register), this should be the date that it was no longer in effect, written in `YYYY-MM-DD` format. If the TPO is still active, leave this field blank. If the tree has been felled, use the felled-date field.
0 commit comments