Skip to content

Commit 65cf451

Browse files
authored
Merge pull request #345 from digital-land/gwencariad-patch-3
Update tree-preservation-order.md
2 parents d8d32b4 + e58b9e8 commit 65cf451

File tree

1 file changed

+36
-38
lines changed

1 file changed

+36
-38
lines changed

application/templates/pages/guidance/specifications/tree-preservation-order.md

+36-38
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
**Last updated:** 20 November 2024<br/>
1+
**Last updated:** 8 January 2025<br/>
22

33
---
44

@@ -100,12 +100,6 @@ Write in YYYY-MM-DD format.
100100

101101
Example: `2022-12-20`
102102

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-
109103
### confirmed-date
110104

111105
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.
114108

115109
Example: `2022-12-20`
116110

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-
127111
### entry-date
128112

129113
The date the entity was last updated.
@@ -134,6 +118,18 @@ Write in `YYYY-MM-DD` format.
134118

135119
Example: `2022-12-20`
136120

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+
137133
---
138134

139135
Tree preservation zone dataset
@@ -195,6 +191,16 @@ If you’re providing geometry in a GeoJSON, GML or Geopackage, use the associat
195191

196192
Optional text on how this data was made or produced, or how it can be interpreted.
197193

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+
198204
### start-date
199205

200206
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
207213

208214
Example: `1999-01-20`
209215

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`
219216

220217
---
221218

@@ -297,18 +294,6 @@ Example: `100 High Street, Bath`
297294

298295
Optional text on how this data was made or produced, or how it can be interpreted.
299296

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-
312297
### felled-date
313298

314299
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.
323308

324309
Example: `2022-12-20`
325310

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.
320+
321+
Example: `1999-01-20`
322+
323+
326324
---
327325

328326
### Technical specification

0 commit comments

Comments
 (0)