Skip to main content

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

East Hampshire District Council

Tree preservation zone

There is a problem

  • You have 766 tree preservation zones outside of your boundary

Entity: 19216261

dataset
tree-preservation-zone
end-date
entity
19216261
entry-date
1991-05-21
geojson
geometry
MULTIPOLYGON (((-0.945835 50.998874,-0.946065 50.998669,-0.946056 50.998570,-0.946061 50.998374,-0.946060 50.998282,-0.946163 50.998216,-0.946241 50.998057,-0.946245 50.997982,-0.946266 50.997909,-0.946306 50.997847,-0.946347 50.997774,-0.946388 50.997676,-0.946453 50.997619,-0.946409 50.997603,-0.946237 50.997490,-0.946121 50.997416,-0.946025 50.997366,-0.945890 50.997303,-0.945755 50.997265,-0.945698 50.997215,-0.945564 50.997103,-0.945275 50.996941,-0.945121 50.996866,-0.944967 50.996803,-0.944754 50.996752,-0.944553 50.996729,-0.944248 50.996755,-0.943832 50.996804,-0.943716 50.996622,-0.943674 50.996552,-0.943530 50.996603,-0.942989 50.996828,-0.942817 50.996897,-0.943003 50.997027,-0.943130 50.997155,-0.942695 50.997360,-0.942752 50.997410,-0.942643 50.997480,-0.942442 50.997583,-0.942319 50.997639,-0.942060 50.997748,-0.942104 50.997821,-0.942058 50.997838,-0.942213 50.998019,-0.942075 50.998092,-0.941839 50.998188,-0.941441 50.998355,-0.941693 50.998517,-0.942207 50.998528,-0.942594 50.998531,-0.942844 50.998529,-0.943058 50.998531,-0.943241 50.998536,-0.943430 50.998549,-0.944021 50.998613,-0.944205 50.998627,-0.944457 50.998654,-0.945020 50.998697,-0.945237 50.998705,-0.945342 50.998732,-0.945374 50.998759,-0.945437 50.998800,-0.945524 50.998833,-0.945835 50.998874)))
name
(EH244)91
organisation-entity
122
point
POINT (-0.944286 50.997706)
prefix
tree-preservation-zone
quality
authoritative
reference
2690-tpz-1
start-date
1991-05-21
typology
geography
notes
Various Species
tree-preservation-order
area-2690-tpo-1
tree-preservation-zone-type
area

How to improve East Hampshire 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