Skip to main content

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

Uttlesford District Council

Tree preservation zone

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset

Area 1

reference
1/74/05-052
name
Area 1
tree-preservation-order

undefined

1/74/05-052
tree-preservation-zone-type
area
geometry
MULTIPOLYGON (((0.201021 52.065125,0.200841 52.065213,0.200934 52.065346,0.200934 52.065369,0.200671 52.065504,0.200397 52.065302,0.200113 52.065121,0.200019 52.065065,0.199735 52.064884,0.199650 52.064864,0.199333 52.064779,0.199313 52.064751,0.199278 52.064693,0.199223 52.064621,0.198855 52.064412,0.198895 52.064388,0.199179 52.064198,0.199271 52.064134,0.199461 52.064008,0.199549 52.063944,0.199786 52.063787,0.199809 52.063770,0.199813 52.063772,0.199838 52.063756,0.200027 52.063629,0.200206 52.063540,0.200362 52.063638,0.200544 52.063749,0.200561 52.063775,0.200611 52.063806,0.200969 52.064012,0.201070 52.063957,0.201134 52.063998,0.201261 52.064084,0.201361 52.064148,0.201375 52.064160,0.201476 52.064234,0.201535 52.064231,0.201562 52.064210,0.201631 52.064161,0.201672 52.064129,0.201755 52.064070,0.201798 52.064037,0.201797 52.064036,0.201866 52.063996,0.201874 52.063988,0.201906 52.063963,0.201957 52.063917,0.202030 52.063839,0.202574 52.063985,0.202292 52.064236,0.202232 52.064307,0.202406 52.064382,0.202375 52.064416,0.202321 52.064487,0.202037 52.064684,0.201924 52.064760,0.201838 52.064807,0.201259 52.065175,0.201133 52.065081,0.201021 52.065125)))
point
POINT (0.200662 52.064469)
notes
entry-date
1974-09-27
start-date
1974-09-27
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The Tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

How to improve Uttlesford District 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